Skip to content

Security and patient data

Health data is special category data under UK GDPR. These are the controls built into Sovica, and how we handle the data your clinic puts in it.

Last updated: 29 October 2026

1. Your clinic stays in control

Your clinic is the controller of its patients’ data. Vahue Ltd is its processor: we use the data only to run Sovica for you, under a data processing agreement, and we list every subprocessor we use. For how we handle data on this website, see the privacy policy.

2. Where data lives

UK clinics’ data is stored and processed in the AWS London region (eu-west-2) and does not leave the UK for hosting.

3. Isolation between clinics

Every record belongs to one clinic. The database itself enforces this with row-level security, so a query for one clinic cannot return another clinic’s rows, even if application code makes a mistake.

4. Encryption

Data is encrypted in transit with TLS and at rest with keys managed in AWS KMS. Files and photos are encrypted in storage.

5. Access and sign-in

  • Role permissions: each role sees only what it needs; clinical notes, finances and settings are separate permissions.
  • Staff accounts support two-factor authentication and passkeys.
  • Sessions are tied to one person, and sensitive actions ask you to confirm.

6. Audit trail

Every change to business data is written to an append-only audit log: who changed what, and when. It cannot be edited or deleted, so you can show it to an inspector or an insurer.

7. Your data is yours

Export patients, appointments, notes, forms and financial data at any time. If you leave, we delete your data on request.

8. Reporting a security issue

Found something? Email security@sovica.ai with “Security” in the subject. We reply within two working days.