Security & IG pack
Data processing agreement
This agreement sets out how Stocta processes personal data on behalf of your clinic, as UK GDPR Article 28 requires. Your clinic is the controller. Stocta is the processor.
1. Parties
| Controller (“the Clinic”) | [Clinic or practice legal name] [Registered address] ICO registration number: [ICO number] Data protection contact: [Name and email] |
|---|---|
| Processor (“Stocta”) | Haris Nazir, trading as Stocta London, United Kingdom Data protection and breach contact: haris@stocta.com |
This agreement forms part of Stocta’s terms of service (the “Terms”) and any order form between the parties. If this agreement and the Terms conflict on a data protection matter, this agreement wins.
2. Definitions
“UK GDPR”, “controller”, “processor”, “personal data”, “data subject”, “personal data breach” and “processing” have the meanings given in the UK GDPR and the Data Protection Act 2018 (together, “Data Protection Law”). The “Service” is the Stocta stock-management software described in the Terms. “Clinic Personal Data” is the personal data Stocta processes for the Clinic through the Service.
3. Details of the processing
| Subject matter | Providing the Service: recording and reporting the Clinic’s stock of medicines and supplies. |
|---|---|
| Duration | For as long as the Clinic uses the Service, then until the data is deleted under section 13. |
| Nature of the processing | Collecting, storing, organising, displaying, reporting on, emailing, backing up and deleting data, as needed to run the Service. |
| Purpose | Letting the Clinic’s staff sign in, record stock movements, stock takes, fridge temperatures and orders, receive alerts, and see who did what (an audit trail). Supporting and securing the Service, and fixing faults. |
| Categories of data subjects |
|
| Types of personal data |
|
| Special category data | None. See section 4. |
The Service holds the following business data, which is not personal data in itself:
- Products, stock levels, batch numbers and expiry dates
- Stock movements (who scanned what in or out, when, and where)
- Fridge temperature readings and breach notes
- Suppliers (including a contact email and phone number if you add them), purchase orders and delivery records, including uploaded invoices or delivery notes
- Staff accounts: name, work email address, role, sign-in records and pending invitations
- Per-staff activity summaries that clinic admins can view (for example, scans recorded)
4. No patient data
The Service is not designed to process patient data or any special category data, including data about health. It does not connect to NHS clinical systems. The Clinic instructs its staff not to enter patient names, NHS numbers, dates of birth or any other information that could identify a patient. This includes the free-text fields:
- Stock movement notes and reasons
- Fridge reading notes
- Stock-take discrepancy notes
- Purchase order and delivery notes
- Product, location and supplier descriptions
If Stocta becomes aware that patient data has been entered, it will tell the Clinic so the Clinic can remove it. Stocta will treat any such data with the same protections as other Clinic Personal Data until it is removed.
5. The Clinic’s instructions
Stocta will process Clinic Personal Data only on the Clinic’s documented instructions. Those instructions are this agreement, the Terms, and the Clinic’s use and configuration of the Service (for example, inviting users, setting roles and exporting data). This includes instructions about transfers outside the UK (section 15).
The only exception is where UK law requires Stocta to process the data. In that case Stocta will tell the Clinic before processing, unless the law forbids it.
Stocta will tell the Clinic straight away if it thinks an instruction breaks Data Protection Law.
The Clinic is responsible for having a lawful basis for the processing, for giving its staff a privacy notice that covers the Service, and for the accuracy of the data it enters.
6. Confidentiality
Stocta will make sure that anyone it authorises to process Clinic Personal Data is bound by a duty of confidentiality, by contract or by law. Access is limited to people who need it to run, support or secure the Service.
7. Security
Stocta will put in place appropriate technical and organisational measures to protect Clinic Personal Data, as Article 32 of the UK GDPR requires. The current measures are described on the security page. They include:
- Hosting: database in London, UK (AWS eu-west-2); server functions in London, UK (Vercel lhr1).
- Encryption: Encrypted in transit (TLS) and at rest (AES-256).
- Backups: Daily automated database backups, kept for 7 days.
- Each clinic’s data is kept separate at database level, and access is controlled by role.
Stocta may update these measures over time, but will not reduce the overall level of protection.
8. Sub-processors
The Clinic gives general authorisation for Stocta to use the sub-processors listed in Annex A.
- Stocta will give the Clinic at least 30 days’ notice by email before adding or replacing a sub-processor.
- The Clinic may object on reasonable data protection grounds within that notice period. The parties will discuss the objection in good faith. If it cannot be resolved, the Clinic may end the Service without penalty and receive a refund of any fees paid for the period after it ends.
- Stocta will have a written contract with each sub-processor that gives Clinic Personal Data the same level of protection as this agreement.
- Stocta remains responsible to the Clinic for how its sub-processors handle Clinic Personal Data.
9. Helping with data subject rights
Taking into account the nature of the processing, Stocta will help the Clinic respond to requests from people exercising their rights under Data Protection Law (such as access, correction or erasure). If Stocta receives a request directly, it will pass it to the Clinic without undue delay and will not respond itself unless the Clinic asks it to. Clinic admins can see and manage their users, including deactivating accounts, in the Service.
10. Helping with security, DPIAs and the ICO
Stocta will give the Clinic reasonable help, using the information available to it, with the Clinic’s own obligations on security, breach notification, data protection impact assessments (DPIAs) and any prior consultation with the Information Commissioner’s Office (ICO). The security page and this agreement are designed to support a DPIA.
11. Personal data breaches
Stocta will notify the Clinic of a personal data breach affecting Clinic Personal Data without undue delay, and in any case within 48 hours of becoming aware of it. The notice will go to the Clinic’s data protection contact in section 1, or the Clinic’s admin users if none is given.
As far as it is known at the time, the notice will describe:
- what happened, and the categories and approximate number of people and records affected;
- the likely consequences;
- the steps taken or proposed to deal with the breach and reduce its effects;
- a contact for more information.
Where not all of this is known at first, Stocta will send it in stages as it becomes known. Stocta will help the Clinic decide whether to report the breach to the ICO or tell the people affected. The Clinic, as controller, makes that decision.
To report a suspected breach to Stocta, email haris@stocta.com.
12. Records
Stocta will keep a record of the processing it carries out for the Clinic, as Article 30(2) of the UK GDPR requires.
13. Return and deletion at the end of the Service
When the Service ends:
- Stocta will offer the Clinic an export of its data in a common format (such as CSV).
- Stocta will delete Clinic Personal Data from the live Service within 90 days of the end date, unless the Clinic asks for earlier deletion or UK law requires it to be kept.
- Copies in backups are overwritten within a further 7 days, as backups roll off.
Stocta will confirm deletion in writing if the Clinic asks.
14. Information and audits
Stocta will make available the information needed to show it is meeting Article 28 of the UK GDPR. In practice:
- Once a year, the Clinic may ask for written information or send a security questionnaire, which Stocta will answer within a reasonable time.
- The Clinic may also ask for information after a personal data breach, or if the ICO requires it.
- On-site audits or inspections may take place by agreement, on reasonable notice, during working hours and subject to confidentiality. Each party pays its own costs.
15. International transfers
Clinic Personal Data is stored in the UK. Some sub-processors process data in the European Economic Area, which the UK recognises as giving adequate protection. Several sub-processors are headquartered in the United States and may access data from there, for example to provide support. Those transfers are protected by the safeguards in each provider’s data processing agreement, such as the UK International Data Transfer Addendum.
Stocta will not transfer Clinic Personal Data outside the UK in any other way unless the transfer meets the requirements of Data Protection Law.
16. Liability
Each party is responsible for its own compliance with Data Protection Law. Liability under this agreement is subject to the limits in the Terms. Nothing in this agreement limits liability that cannot be limited by law, or the rights of data subjects.
17. Signatures
| For the Clinic (controller) | For Stocta (processor) | |
|---|---|---|
| Name | [Name] | [Name] |
| Role | [Role] | [Role] |
| Signature | [Signature] | [Signature] |
| Date | [Date] | [Date] |
Stocta signs as Haris Nazir, trading as Stocta.
Annex A: Authorised sub-processors
These are the sub-processors Stocta uses to provide the Service. The current list is always published here.
| Sub-processor | What it does | Data it handles | Where |
|---|---|---|---|
| Supabase Supabase, Inc. Privacy policy | Database, sign-in (authentication) and file storage (purchase-order attachments) | All clinic data: stock, batches, fridge readings, purchase orders, supplier contact details, staff names, email addresses and roles; website enquiries | London, UK (AWS eu-west-2) |
| Vercel Vercel Inc. Privacy policy | Application hosting. Server code runs in London; static website files are served from a global CDN | Clinic data in transit while a request is handled; request logs (IP address, URL, time) | Server functions in London, UK (lhr1) |
| Resend Plus Five Five, Inc. (Resend) Privacy policy | Sending email: invitations, password resets, low-stock and fridge alerts | Recipient name and email address, and the content of the email | Dublin, Ireland (AWS eu-west-1) |
| PostHog PostHog, Inc. Privacy policy | Product analytics and error tracking. No cookies, no session recording, no automatic capture of page text | Staff user ID, email address and role; clinic name; pages visited and named in-app events; error reports | Frankfurt, Germany (PostHog EU Cloud) |
| Google Workspace Google Cloud EMEA Limited Privacy policy | The Stocta mailbox: support requests, website enquiries and breach reports sent to us by email | Whatever is in emails you send us, usually names, work email addresses and the question asked | Google data centres, which may be outside the UK |
Annex B: Security measures
The technical and organisational measures are described on the security page, which forms part of this agreement. The version in force when this agreement is signed can be saved with the “Download as PDF” button on that page and attached here.