SStocta
Security & IGPrivacyTerms

For practice managers, IG leads and DPOs

Security & information governance pack

This pack answers the questions an information governance review usually asks: what data Stocta holds, where it is hosted, who processes it, how it is protected, and where we stand on NHS assurance.

Where something is not in place, we say so and say when we will do it. If a question is not answered here, email haris@stocta.com.

Last updated 3 November 2026

Stocta holds no patient data and does not connect to any NHS system. It stores stock, batches, fridge readings and staff accounts only. There is no connection to EMIS, SystmOne or any other clinical system (no IM1 integration), and Stocta does not use NHSmail.

Contents

  1. What Stocta is and isn’t
  2. Where data is hosted and how it flows
  3. Sub-processors
  4. Technical and organisational controls
  5. Keeping “no patient data” true
  6. Your role and ours
  7. Incidents and personal data breaches
  8. NHS DSPT, Cyber Essentials, DTAC and DCB0129
  9. Documents in this pack

1. What Stocta is and isn’t

Stocta is stock control software for UK clinics. Staff scan medicines and supplies in and out, record fridge temperatures, run stock takes and raise purchase orders. It is an operational tool, not a clinical one.

What 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)

The only personal data is about your staff: their name, work email address, role, sign-in records and the stock movements they record.

What Stocta never holds

  • Patient names, NHS numbers, dates of birth, addresses or any other patient identifier
  • Clinical records, prescriptions, appointments or anything about a patient’s care
  • Special category data (for example, health data about any person)
  • Payment card details

Stocta has free-text fields, so a patient identifier could be typed in by mistake. Section 5 explains how to prevent that and what to do if it happens.

2. Where data is hosted and how it flows

DatabasePostgreSQL on Supabase (Pro plan), London, UK (AWS eu-west-2)
Application serversVercel server functions, London, UK (Vercel lhr1)
EncryptionEncrypted in transit (TLS) and at rest (AES-256)
BackupsDaily automated database backups, kept for 7 days

How data flows

  1. A member of staff signs in and uses Stocta in their web browser. All traffic is encrypted with TLS.
  2. The website’s static files (code, styles and images, no clinic data) are served from Vercel’s global network. Requests that handle clinic data run on Vercel server functions in London, UK (Vercel lhr1).
  3. Clinic data is read from and written to the database in London, UK (AWS eu-west-2), either by those server functions or directly from the browser. Either way, the database checks who the user is and which clinic they belong to before returning anything (see section 4).
  4. When Stocta sends an email (an invitation, a password reset, or a low-stock or fridge alert), the recipient’s name, email address and the email content pass to Resend in Dublin, Ireland.
  5. Product analytics and error reports go to PostHog EU Cloud in Frankfurt, Germany. This records which pages and features staff use, not the stock or fridge data itself.

Data is stored in the UK (database) and the EU (email and analytics). Each provider is a US-headquartered company. Their data processing terms cover any access from outside the UK, for example by their support staff.

3. Sub-processors

These are the companies that process clinic data on Stocta’s behalf. We will give you at least 30 days’ notice before adding or replacing a sub-processor, so you can object.

ProviderPurposeData processedLocation
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 enquiriesLondon, 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 CDNClinic 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 alertsRecipient name and email address, and the content of the emailDublin, 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 textStaff user ID, email address and role; clinic name; pages visited and named in-app events; error reportsFrankfurt, 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 emailWhatever is in emails you send us, usually names, work email addresses and the question askedGoogle data centres, which may be outside the UK

4. Technical and organisational controls

Each clinic’s data is kept separate

Every table that holds clinic data is tagged with the clinic it belongs to. The database itself enforces this with row-level security on every one of those tables, so the separation does not depend on the application code getting it right. A further restrictive rule means a person must be an active member of the clinic to read any of its data. Someone who is signed out, or who belongs to another clinic, gets nothing back.

A few server-side tasks need wider access than a signed-in user has: sending invitations and password resets, the scheduled fridge and low-stock checks, and showing a clinic’s name on its sign-in page. They use a privileged server key that is held only on the server and never sent to a browser. Tasks done for a user check that they are signed in with the right role first. Scheduled tasks need a secret that only our scheduler holds. The public “forgot password” form is rate-limited.

Role-based access

Your admins decide who has access and at what level. People join only by invitation from an admin. Each role sees only the parts of Stocta it needs.

RoleCan use
StaffScanning only
ManagerProducts, stock, purchase orders, stock takes, fridges and reports, plus scanning
AdminUsers and settings, plus everything a manager can do

Append-only audit trail

Stock movements and fridge temperature readings are append-only. The database gives app users no way to edit or delete them. A mistake is corrected with a new adjusting entry, so the original stays on record. Every movement records who made it, what moved, when, and where.

Sign-in

Staff sign in with an email address and password through Supabase Auth. Passwords are hashed and never stored in plain text. Password resets are sent by email.

Encryption and backups

  • Encrypted in transit (TLS) and at rest (AES-256).
  • Daily automated database backups, kept for 7 days.

Who at Stocta can access your data

Stocta is run by its founder, Haris Nazir, trading as Stocta. Access to the production database and hosting accounts is limited to the founder. We access a clinic’s data only to run the service, to fix a problem, or when you ask us to.

How changes are made

Database changes are made through version-controlled migration files, not by hand. Before a change reaches production, automated tests rebuild the database from scratch and check its security rules, for example that row-level security is switched on and that signed-out users cannot read clinic data.

Not in place yet

So that you can assess the gaps, these are things Stocta does not currently have:

  • Multi-factor authentication (MFA) for staff sign-in
  • Single sign-on (SSO)
  • An independent penetration test
  • Any security certification, including Cyber Essentials and ISO 27001 (see section 8)
  • Out-of-hours or 24/7 support

If any of these is a condition of approval for you, please tell us. It directly shapes what we do next.

5. Keeping “no patient data” true

Stocta is designed to hold no patient data, but it has free-text fields. If staff type a patient’s details into one, that changes the data Stocta holds. Please brief your team.

Free-text fields to watch

  • Stock movement notes and reasons
  • Fridge reading notes
  • Stock-take discrepancy notes
  • Purchase order and delivery notes
  • Product, location and supplier descriptions

What to tell staff

  • Never type a patient’s name, NHS number, date of birth, address or any other identifier into Stocta.
  • If a note needs to link stock to a patient, use a reference that only means something inside your clinical system, such as the product and batch number. Record the patient link in your clinical system, not in Stocta.

If it happens

  • Most notes (stock-take, purchase order, delivery, product, location and supplier) can be edited. A manager or admin can remove the identifier straight away.
  • Notes on stock movements and fridge readings are part of the append-only audit trail, so nobody at the clinic can edit them. Email haris@stocta.com and we will redact the note for you.
  • Decide, under your own procedures, whether the incident needs recording or reporting.

6. Your role and ours

  • Your clinic is the controller of your staff’s personal data held in Stocta. You decide who is invited and what they record.
  • Stocta is your processor under UK GDPR. We process that data only on your instructions and to provide the service, under our data processing agreement.
  • Stocta is the controller for its own website enquiries, such as demo requests. Our privacy policy covers those.

When your contract ends

We will offer you an export of your data. We then delete your clinic’s data within 90 days. Copies in our backups roll off within a further 7 days.

7. Incidents and personal data breaches

How to report a concern

Email haris@stocta.com. Put “Security” in the subject line. Tell us what you saw, when, and which account or clinic it affects.

What we do

  1. Contain the problem, for example by revoking access or taking an affected feature offline.
  2. Work out what happened, what data is affected and which clinics.
  3. If a personal data breach affects your clinic’s data, we notify you without undue delay and within 48 hours of becoming aware of it. We tell you what we know, what we have done, and what we are still checking.
  4. Give you the information you need to decide whether to report it to the ICO, and update you as we learn more.
  5. Fix the cause and tell you what we changed.

As controller, your clinic decides whether a breach must be reported to the ICO (within 72 hours of you becoming aware) and to the people affected. We will help you with that.

8. NHS DSPT, Cyber Essentials, DTAC and DCB0129

Current status, and what would make us do each one.

StandardStatus todayWhen we will do it
NHS Data Security and Protection Toolkit (DSPT)Not held. Not required today: the DSPT applies to organisations that access NHS patient data or connect to NHS systems, and Stocta does neither.Before any of these: an integration with EMIS or SystmOne (IM1 requires the DSPT); handling any patient data; using an NHS system such as NHSmail; or a contract with a PCN, federation or ICB that makes it a condition.
Cyber EssentialsNot held.When any of the DSPT triggers applies, when we need a DTAC assessment, or when a customer group makes it a condition of purchase.
Digital Technology Assessment Criteria (DTAC)Not assessed.When an NHS buyer, such as a PCN or ICB, requires it. Cyber Essentials comes first, as DTAC needs it.
DCB0129 (clinical risk management)No clinical safety case or hazard log. Our view is that Stocta is not a clinical system: it holds no patient data and does not support decisions about individual patients.If Stocta starts to handle patient data or integrate with a clinical system, or if a customer or NHS buyer requires it. We would then appoint a Clinical Safety Officer and publish a hazard log.
ISO 27001Not held, and not planned at present.We will review this if customers ask for it.

A note on clinical safety

Stocta does not make clinical decisions, but stock expiry and fridge temperature records can matter to patient safety. An expired or temperature-damaged vaccine is a patient safety issue. Stocta supports your cold chain and stock checks. It does not replace your cold chain policy, your fridge’s own data logger, or the checks staff make before giving a medicine. Your clinical safety lead may want to consider this when deploying Stocta.

9. Documents in this pack

  • Data processing agreement: the UK GDPR Article 28 terms between your clinic and Stocta.
  • DPIA template: a data protection impact assessment, pre-filled with Stocta’s side, for your DPO to complete.
  • Privacy policy: how Stocta handles personal data.
  • Terms of service: the terms for using Stocta.

Every page can be saved as a PDF with the “Download as PDF” button at the top. Questions, or a 30-minute walkthrough for your IG lead: haris@stocta.com.

© 2026 Haris Nazir, trading as Stocta · London, United Kingdom

Questions about security or data protection: haris@stocta.com