Security & Compliance
How Surgerly handles your patients' data.
An honest overview of where data lives, who can access it and what we do to keep it safe. This page describes our hosted platform; licensees operate and configure their own installations. It answers the questions a procurement team or DPO will ask before signing.
Security at a glance
UK data residency
Patient records are stored in UK data centres.
Privacy tools
Consent records, audit trails and data export that support a clinic's own duties.
Audit logs
Sign-ins, changes and staff access to patient records are logged.
Encrypted in transit & at rest
HTTPS uses TLS 1.2 or later. Azure encrypts stored patient records and backups.
Where data lives
Patient records are stored in UK data centres. Backups are held in the same place.
Diagnostic reports are stored with the UK-hosted installation. If AI error triage is enabled, Microsoft may process diagnostic content outside the UK. Reports can contain personal data. Processing purposes, locations and safeguards are listed in our privacy policy.
Access control
Staff access requires an authenticated account. Organisation administrators manage permissions for the staff who work with their data. Staff access to patient records is logged.
Role-based permissions control who can view records, edit appointments, manage staff, send correspondence and access reporting. Two-factor authentication is supported for staff accounts.
Encryption
Public web traffic uses HTTPS with TLS 1.2 or higher. Patient data and database backups are encrypted at rest with AES-256, using keys managed by Microsoft Azure.
Patient-facing authentication uses one-time codes and signed session tokens; we never store passwords for patients in our database.
Audit logging
Surgerly records staff sign-ins, changes to records and staff access to patient records, along with administrative actions such as permission changes and exports.
Engineer access to a patient's record is recorded in the same trail, and clinic admins can see a patient's access history in the record's Audit tab.
Backups & recovery
Azure provides point-in-time database recovery within the configured retention period. The Company platform keeps 35 days of encrypted backups in the same region. Recovery requires a restore; an on-site standby is not currently provided.
Data subject rights
Clinics can view, correct and export patient information in Surgerly. For erasure, and for a complete export in answer to a subject access request, we work with the clinic.
Our sub-processor list is available on request.
Incident response
We watch application errors and service health, and record failed sign-ins. If an incident affects a clinic's data, we tell that clinic without undue delay so it can meet its own reporting duties.
Sub-processors
Surgerly uses a small, deliberate set of sub-processors. The current list, with each one's purpose and processing location, is section 7 of our privacy policy. That is the canonical version, and clinics are notified before we add or replace one.
- Microsoft Azure (UK data centres): hosting, database, file storage, real-time messaging
- Microsoft Azure Communication Services: transactional and bulk email
- Stripe: card payments, where a clinic enables it
- Twilio: SMS delivery, where a clinic enables it
Which of these see patient data. Microsoft Azure hosts patient records and processes the communications and optional features described in our privacy policy. Stripe receives payer details, Twilio receives mobile numbers and message bodies, and Azure Communication Services receives recipient addresses and message bodies. Tailscale handles administrative connection and device metadata.
Talk to us
Need our sub-processor list or help with your DPIA?
Email security@surgerly.co.uk or book a chat, and we'll send what you need for procurement.
Book a chat