Security & IG pack · Template
Data protection impact assessment (DPIA)
A DPIA template for practices using Stocta. It follows the structure of the ICO’s sample DPIA template (steps 1 to 7). Stocta has filled in what it knows about the processing. Your practice completes the highlighted parts and your DPO signs it off.
Details
| Practice (controller) | [practice name and address] |
|---|---|
| ICO registration number | [practice’s ICO registration number] |
| Data protection officer | [DPO name and contact details] |
| DPIA owner | [name and role of the person completing this DPIA] |
| Supplier (processor) | Haris Nazir, trading as Stocta, London, United Kingdom. Contact: haris@stocta.com |
| System | Stocta, web-based stock control for clinics (https://stocta.com) |
| Stocta information current at | 3 November 2026 |
| Date of this DPIA | [date] |
Step 1: Identify the need for a DPIA
What the project aims to achieve
The practice will use Stocta to track medicines and supplies: stock in and out by barcode scanning, batch numbers and expiry dates, fridge temperature readings, stock takes and purchase orders. The aim is to reduce waste and expired stock, keep an accountable record of stock movements, and support the cold chain.
Practice’s own aims: [for example, replace paper fridge logs and spreadsheets at named sites]
Why a DPIA is being considered
The processing involves personal data about staff, held by a third-party supplier in the cloud. Stocta holds no patient data and no special category data. It does not connect to NHS or clinical systems. It records which member of staff made each stock movement, and admins can see activity reports by staff member.
On Stocta’s side, this points to low risk: the personal data is limited to work contact details and activity records of the practice’s own staff. A DPIA may not be mandatory. Many practices still complete one as good practice for any new supplier. Your DPO decides.
Practice’s reason for completing this DPIA: [for example, new cloud supplier; DPO request; good practice]
Step 2: Describe the processing
Nature of the processing
- Collection: an admin at the practice invites each user by name and work email address. Stocta then records the user’s role, sign-ins, and the stock movements, fridge readings and notes they enter.
- Use: to sign users in, control what each role can do, keep an audit trail of who did what and when, send emails (invitations, password resets, low-stock and fridge alerts), and show stock and activity reports to managers and admins.
- Storage: PostgreSQL database on Supabase in London, UK (AWS eu-west-2). Application servers on Vercel in London, UK (Vercel lhr1). Encrypted in transit (TLS) and at rest (AES-256). Daily automated database backups, kept for 7 days.
- Sharing: Stocta does not sell data. It shares it only with the sub-processors listed below, or where the law requires.
- Deletion: at contract end Stocta offers an export, then deletes the practice’s data within 90 days. Backups roll off within a further 7 days.
Sub-processors
| Provider | Purpose | Data processed | Location |
|---|---|---|---|
| Supabase Supabase, Inc. | 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. | 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) | 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. | 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 | 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 |
A data flow description is in section 2 of the security pack.
Scope of the processing
Data Stocta holds:
- 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)
Personal data within that:
- Staff name, work email address and role
- Sign-in records
- Records of the stock movements, fridge readings and notes each person made, with dates and times
- Usage analytics (pages visited and in-app events) and error reports, linked to the user
- IP addresses in hosting request logs
- Supplier contact email addresses or phone numbers, where these identify a person
Special category or criminal offence data: none. Stocta holds no patient data. The only way patient data could enter Stocta is by staff typing it into a free-text field by mistake. See risk R3.
- Number of people: [number of staff who will have accounts]
- Sites covered: [sites or locations using Stocta]
- Frequency: daily, whenever staff receive, use or count stock
- Retention: for as long as the practice uses Stocta, so the audit trail stays complete. When a staff member leaves, an admin removes their access. Their name stays on the movements they recorded. [any shorter retention the practice requires]
- Geography: stored in the UK (database) and the EU (email and analytics)
Context of the processing
- Data subjects: the practice’s own staff. No patients, and no children.
- Relationship: employment or engagement with the practice. Staff would reasonably expect the practice to record who handled stock, as part of normal medicines management.
- Control: staff cannot opt out of the audit trail while they handle stock in Stocta. This should be explained to them (see risk R4).
- Technology: a standard web application. No new or novel technology, no automated decisions about individuals, no profiling.
- Known gaps: no multi-factor authentication, single sign-on, independent penetration test or security certification yet. See the security pack.
- Free-text fields where staff could enter a patient identifier by mistake: Stock movement notes and reasons; Fridge reading notes; Stock-take discrepancy notes; Purchase order and delivery notes; Product, location and supplier descriptions.
- Practice’s context: [any prior concerns, staff groups affected, or local policies that apply]
Purposes of the processing
- Run accurate stock control for medicines and supplies
- Keep an accountable record of who received, used, adjusted or counted stock
- Record fridge temperatures and act on out-of-range readings
- Alert staff to low stock and fridge problems by email
- Secure the system: sign-in, roles and access control
- Improve the service and fix errors (Stocta’s analytics and error tracking)
Benefits: less expired and wasted stock, better cold chain records, and less time spent on paper logs. Practice’s expected benefits: [practice’s expected benefits]
Step 3: Consultation process
- Processor: Stocta has provided this pre-filled template, the security pack and the data processing agreement. Stocta will answer further questions at haris@stocta.com.
- DPO: [date and summary of DPO consultation]
- Staff or their representatives: [how and when staff were consulted, or why not]
- Others: [for example, IT support, clinical safety lead, partners]
Step 4: Assess necessity and proportionality
- Lawful basis (Article 6): [lawful basis chosen by the practice]. Your DPO decides. Practices often consider legitimate interests in running safe, accountable stock control.
- Special category condition (Article 9): not applicable. Stocta holds no special category data.
- Does the processing achieve the purpose? Yes. An audit trail needs to show who did what, so linking movements to named users is necessary.
- Data minimisation: Stocta asks only for name, work email and role. It holds no patient data, no home addresses and no HR records.
- Preventing function creep: Stocta uses the data only to provide the service, under the data processing agreement. Practice’s own measures: [for example, activity reports used for stock control only]
- Data quality: admins can update names and roles. Corrections to stock records are made as new adjusting entries, so the original stays visible.
- Information to staff: [how the practice tells staff about Stocta, for example the staff privacy notice]
- Individual rights: the practice handles requests from its staff. Stocta helps on request, for example with exports or redaction, as set out in the data processing agreement.
- Processor compliance: covered by the data processing agreement, including sub-processor notice, breach notification and deletion.
- International transfers: email and analytics are processed in the EU. The sub-processors are US-headquartered and their data processing terms cover any access from outside the UK.
Step 5: Identify and assess risks
Likelihood is remote, possible or probable. Severity is minimal, significant or severe. Overall risk is low, medium or high. These are Stocta’s assessments. Adjust them to your practice.
| Ref | Risk to individuals | Likelihood of harm | Severity of harm | Overall risk |
|---|---|---|---|---|
| R1 | Another clinic, or someone signed out, reads your staff data or stock records. | Remote | Significant | Low |
| R2 | A staff password is guessed, reused or shared, and someone uses that account. Stocta does not offer multi-factor authentication yet. | Possible | Minimal | Low |
| R3 | Staff type a patient identifier (name, NHS number, date of birth) into a free-text note. That would put patient data, possibly health data, into Stocta. | Possible | Significant | Medium |
| R4 | Staff are not aware that their stock activity is recorded and visible to admins, or the records are used for a purpose they would not expect, such as performance management. | Possible | Minimal | Low |
| R5 | A security incident at one of Stocta’s sub-processors exposes clinic data. | Remote | Significant | Low |
| R6 | Records are lost or changed, for example by accidental deletion or an outage, and you cannot show your stock or cold chain history. | Remote | Significant | Low |
| R7 | Personal data is processed outside the UK and is harder to protect or recover there. | Remote | Minimal | Low |
| R8 | Data is kept for longer than needed after you stop using Stocta. | Remote | Minimal | Low |
| R9 | The supplier’s own administrative access is misused or compromised. Stocta is run by one person. | Remote | Significant | Low |
| R10 | [any further risk the practice identifies] | [likelihood] | [severity] | [overall] |
Step 6: Identify measures to reduce risk
| Ref | Measures | Effect on risk | Residual risk | Measure approved |
|---|---|---|---|---|
| R1 | Row-level security on every clinic table, enforced by the database. A restrictive rule requires active membership of your clinic to read anything. Automated tests check these rules before every change reaches production. | Reduced | Low | [yes / no] |
| R2 | Passwords are hashed by Supabase Auth. Roles limit what each account can see: staff accounts can only scan. Admins invite every user and can remove leavers at once. Clinic: ask staff to use unique passwords and remove leavers promptly. | Reduced | Low | [yes / no] |
| R3 | Published guidance for staff (security pack, section 5). Most notes can be edited by managers. Stocta redacts append-only movement and fridge notes on request. Clinic: brief staff before go-live and use product or batch references instead. | Reduced | Low | [yes / no] |
| R4 | Recording who made each movement is needed for an accountable audit trail. Clinic: tell staff what is recorded and why (for example in your staff privacy notice), and decide whether activity reports may be used for anything beyond stock control. | Reduced | Low | [yes / no] |
| R5 | Established providers under data processing terms. Data encrypted in transit and at rest. Stocta notifies you of a personal data breach without undue delay and within 48 hours of becoming aware. 30 days’ notice of sub-processor changes. | Reduced | Low | [yes / no] |
| R6 | Stock movements and fridge readings are append-only: app users cannot edit or delete them. Daily database backups, kept for 7 days. Clinic: keep your fridge’s own data logger records as well. | Reduced | Low | [yes / no] |
| R7 | The database and application servers are in London. Email (Ireland) and analytics (Germany) are in the EU, which the UK recognises as adequate. The providers are US-headquartered and their data processing terms cover any access from outside the UK. | Accepted | Low | [yes / no] |
| R8 | At contract end Stocta offers an export, deletes your data within 90 days, and backups roll off within a further 7 days. | Reduced | Low | [yes / no] |
| R9 | Access to the production database and hosting accounts is limited to the founder. Privileged server keys are held only on the server, never in the browser. Stocta accesses clinic data only to run the service, fix a problem or on your request. | Reduced | Low | [yes / no] |
| R10 | [measures] | [effect] | [residual risk] | [yes / no] |
Residual risk (Stocta’s view): low, provided the practice briefs staff not to enter patient identifiers (R3) and tells staff what is recorded about them (R4). No residual risk is high, so Stocta does not expect prior consultation with the ICO to be needed. Your DPO decides.
Step 7: Sign off and record outcomes
| Item | Name and date | Notes |
|---|---|---|
| Measures approved by | [name, role, date] | Integrate actions back into the project plan, with dates and owners. |
| Residual risks approved by | [name, role, date] | If accepting any high residual risk, consult the ICO before going ahead. |
| DPO advice provided | [DPO name, date] | The DPO should advise on compliance, the step 6 measures and whether processing can proceed. |
| Summary of DPO advice | [DPO advice] | |
| DPO advice accepted or overruled by | [name, role, date] | If overruled, record the reasons. [reasons] |
| Consultation responses reviewed by | [name, role, date] | If your decision departs from staff views, record the reasons. [reasons] |
| This DPIA will be kept under review by | [name, role] | Review date: [review date]. The DPO should also review ongoing compliance. |
Stocta gives 30 days’ notice of any sub-processor change. The current position on hosting, sub-processors and controls is always on the security pack page.