Data Processing Agreement
Effective 6 November 2026
This Data Processing Agreement ("DPA") is between SmileSort Ltd (company number 17457160, registered office 71–75 Shelton Street, Covent Garden, London, WC2H 9JQ — "SmileSort", "Processor") and the owner of each account on SmileSort — a dental practice, or a dentist for their own library ("the Practice", "Controller"). Where one person uses several accounts, this DPA applies to each separately. It governs how SmileSort processes your patients' personal data on your behalf, as required by Article 28 UK GDPR.
This DPA is incorporated into and forms part of our Terms of Service — accepting the Terms at signup accepts this DPA too, for any patient data you process through SmileSort. If your practice needs a separately countersigned copy for your own records, email privacy@smilesort.com and we'll send one.
1. Roles of the parties
In respect of Patient Data, the Practice is the Controller and SmileSort is the Processor. The Practice determines the purposes and means of processing its patients' clinical data; SmileSort processes it only to provide the Service, on the Practice's instructions.
The Practice's own lawful basis for processing Patient Data is its responsibility to establish and is outside the scope of this DPA — as a matter of general UK practice for dental care, this is ordinarily Article 6(1)(b) or 6(1)(e) combined with Article 9(2)(h) (health or social care), available to a registered dentist as a health professional under DPA 2018, Schedule 1, Part 1, paragraph 2. SmileSort does not need, and does not claim, an independent Article 6/9 basis for Patient Data — it processes that data solely on the Practice's documented instructions.
Separately, and outside the scope of this DPA: where SmileSort processes the Practice's own account and billing data, SmileSort is the Controller of that data under its own Privacy Policy.
A practice's account is the Practice's: the Practice is the Controller of the Patient Data in it, including Patient Data its team members add, who act on its behalf. A dentist's own library is that dentist's, and they are the Controller of the Patient Data in it. SmileSort keeps each account's Patient Data apart, and never moves it between accounts.
The Practice's records about its own team — which clinician each folder and photograph belongs to, who imported, filed or added it, and the Practice's audit log of team changes and access to its records — are processed for the Practice under this DPA too (Annex 1).
2. Processing on instructions
SmileSort shall process Patient Data only:
- to provide the Service in accordance with the Terms of Service (the Practice's standing instruction); or
- on further documented instructions from the Practice, given through the Service or in writing; or
- where required by UK law, notifying the Practice first unless the law prohibits it.
SmileSort will notify the Practice if, in its opinion, an instruction infringes Applicable Data Protection Law.
The Practice's settings in the Service — who is on its team, in what role and who counts as a clinician; whether clinicians see only their own records and, if so, whether managers still see every record; and its sign-in rules — are among its documented instructions.
3. Confidentiality
Anyone SmileSort authorises to process Patient Data, including its own personnel, is bound by a duty of confidentiality and only processes Patient Data as necessary for their authorised role. The Practice is likewise responsible for making sure everyone it gives access to — clinicians, managers and any other staff — is bound by a duty of confidentiality and uses only what their role needs. Where the Practice keeps clinicians to their own records, a manager sees every clinical record only if the Practice's owner allows it. SmileSort's application and internal admin tooling have no read access to patient, photo, folder or clinical-note data, enforced at the database level. SmileSort staff likewise have no read access to the notes the Practice's team write when they open a colleague's folder, or to the Practice's record of who opened, looked up or viewed its records. SmileSort staff can delete an account only when it holds no Patient Data, or remove a team member’s own account without deleting any of the Practice’s Patient Data; a Practice’s Patient Data is deleted only as Section 11 describes. Direct administrative access to the production database is limited to SmileSort's co-founders and used only for maintenance and incident response — see Annex 2.
3A. Service metadata
To run, support and improve the Service, SmileSort may count how the Practice uses it — for example how many photographs or patients an account holds and when a batch was last sorted — as numbers and dates only. These counts never contain Patient Data themselves, are seen only by SmileSort staff, and are never shared with anyone outside SmileSort. They are separate from the figures the Service shows the Practice about its own records — the time it estimates SmileSort saves the Practice, and the Practice's Insights: weekly counts for the Practice and, only where the Practice's owner turns them on after accepting templates SmileSort has approved, for each member of its team who counts as a clinician — which SmileSort works out from the Practice's records for the Practice, and which SmileSort staff don't see (to support the Practice's account, they see only how many photographs each person has added in all).
4. Security of processing
SmileSort implements appropriate technical and organisational measures to secure Patient Data, appropriate to the risk — see Annex 2 — and reviews and improves them over time.
5. Sub-processing
The Practice gives SmileSort general written authorisation to engage the sub-processors listed in Annex 3 to process Patient Data.
SmileSort will give at least 30 days' notice (by email to the account holder) before engaging a new sub-processor, so the Practice can object on reasonable data-protection grounds. SmileSort remains fully liable for a sub-processor's performance, and imposes terms no less protective of Patient Data than this DPA on every one of them.
6. International transfers
SmileSort's primary data store is hosted in the UK. Original photograph files are stored in the EU (Annex 3). Where Patient Data is transferred to a sub-processor established outside the UK — see Annex 3 — the transfer relies on that sub-processor's own Data Processing Addendum, each independently confirmed to incorporate the EU Standard Contractual Clauses and the UK's International Data Transfer Addendum, automatically forming part of their standard terms. SmileSort will not transfer Patient Data elsewhere without an appropriate safeguard in place.
7. Data subject rights
The Practice is responsible for responding to its patients' rights requests. SmileSort will not respond directly to a request it receives about Patient Data (beyond acknowledging it and redirecting the individual to the Practice), will notify the Practice without undue delay if it receives one, and provides reasonable technical assistance — including a self-service data export the Practice can use directly, without waiting on SmileSort.
Where the Practice keeps clinicians to their own records, a clinician's download of a patient holds only their own encounters and says so; the Practice's owner, and managers who see clinical records, can download the complete record, and the owner can export the whole account. Everyone on the Practice's team can see and download their own entries in its activity log while they're on the team, and the owner and managers can see and download all of it (a reason written in someone's own words only where they can see every clinical record), to help the Practice answer a team member's request. Someone no longer on the team can't see theirs, so the Practice answers for them.
8. Personal data breach
SmileSort will notify the Practice without undue delay, and in any event within 48 hours of becoming aware of a personal data breach affecting Patient Data — giving the Practice time to meet its own 72-hour notification duty to the ICO — describing what's known of the breach's nature, scope, likely consequences and the steps taken, with further assistance and updates as the investigation continues.
9. DPIA & consultation assistance
SmileSort will provide reasonable assistance with any data protection impact assessment or ICO prior consultation the Practice reasonably considers necessary for its use of the Service, including making the information in this DPA available for that purpose.
10. Audit and inspection
SmileSort will make available the information reasonably necessary to demonstrate compliance with this DPA, and allow for and contribute to audits by the Practice or its mandated auditor — in the first instance through a written compliance summary or security questionnaire, given the Service is a shared multi-tenant platform. Any on-site or system-level audit is limited to once in any 12-month period (unless triggered by a suspected breach), with at least 14 days' notice, reasonable scope, and mutual confidentiality.
11. Deletion or return of data
On termination, SmileSort will make Patient Data available for export and delete it per the Service's standard data lifecycle:
- Data deleted during an active subscription is held in Trash for 28 days, then permanently purged.
- Following cancellation, the account is read-only and exportable for 30 days, after which all Patient Data is permanently and irreversibly deleted, automatically.
- If a free trial ends without a plan being chosen, the account is read-only and exportable for 12 months after the trial ends, after which all Patient Data is permanently and irreversibly deleted, automatically.
- A share recipient's email address and the Practice's note on a share are cleared automatically 12 months after the share link expires or is revoked (for a link with no expiry, once it is revoked), and the country and shortened network address on a share link's activity log are cleared 12 months after each entry. The record of the share and its activity is kept until the account is deleted.
- Photographs imported from a Dropbox or Google Drive account stay there as well: SmileSort never changes or deletes anything in the account they came from, so deleting those copies is for the Practice.
- The Practice's audit log is kept for 24 months, and its record of folders opened with a reason for 24 months from each opening; a patient lookup's record and its single-use link go a day after they're made or stop working. All of it goes with the account.
- When someone leaves the Practice's team, the Practice keeps its record of their membership and the name it knew them by for as long as its account exists, so its records still say who did what.
SmileSort will delete Patient Data sooner on the Practice's written request, except where UK law requires it to retain it.
12. Liability
Each party's liability arising out of or in connection with this DPA is subject to the limitations and exclusions in Section 13 (Limitation of Liability) of our Terms of Service.
13. Term, termination & survival
This DPA takes effect from the Practice's acceptance of the Terms of Service and continues for as long as SmileSort processes Patient Data on the Practice's behalf. Clauses 3 (Confidentiality), 11 (Deletion or return of data) and 12 (Liability) survive termination to the extent needed to give them effect.
14. General provisions
Variation. This DPA may only be varied by written agreement, except that SmileSort may update Annex 3 in accordance with Clause 5.
Notices. Notices under this DPA go to the account holder's registered email (for the Practice) and to privacy@smilesort.com (for SmileSort).
Governing law. This DPA is governed by the laws of England and Wales.
Annex 1 — Details of processing
| Subject matter | Provision of the SmileSort clinical-photography management platform to the Practice. |
| Duration | For the term of the Agreement, plus the Trash and read-only retention windows in Clause 11 (after cancellation, or after a free trial that ends without a plan being chosen). |
| Nature & purpose | Secure storage, AI-assisted classification and sorting, importing photographs a user of the Practice chooses from a Dropbox or Google Drive account they connect (read only, for at most 2 hours each time), organisation into patient/visit folders, and controlled time-limited sharing at the Practice's direction, and, for practices with a team, access by role and a record of who did what and who looked at what; and weekly counts of the Practice's work, for the Practice and, where its owner turns them on, for each member of its team who counts as a clinician. |
| Frequency | Continuous, for the duration of the Practice's active use of the Service. |
| Data subjects | The Practice's patients whose clinical photographs are uploaded; the people the Practice chooses to share photographs with (share recipients); and the Practice's own team — its owner, managers and clinicians — as the Practice's records name them. While a user of the Practice chooses what to import from a cloud account, people appearing in the photographs shown to them as small previews; these are passed to the user and never stored. |
| Personal data | Patient name, date of birth, the Practice's own patient reference, clinical photographs (including extraoral/facial views), and any notes or labels attached. For share recipients: the email address the Practice enters, and an activity log of each share link — when it was opened and what was downloaded, with the country and a shortened network address (the IP address with its last part removed). The full IP address and browser details are never stored. For the Practice's team: which clinician each visit folder, photograph and encounter in review belongs to; who imported, filed or added a record; the name the Practice knows each person by, kept on its records after they leave; and the Practice's audit log — changes to its team, roles, who counts as a clinician, sign-in rules and other settings (including figures for each clinician), SmileSort's corrections or checks of a team member's GDC number (never the number), invitations (with the role, never the address), changes to a folder's clinician or a diary match, when someone switched into the Practice from another, what each person did with the Practice's records (photographs added or deleted, downloads and exports, including of the audit log), and, where the Practice keeps clinicians to their own records, who opened a colleague's folder, when, for how long and why (with the note they write for another reason), who looked a patient up by name and date of birth, or had a name and date of birth checked when adding or renaming a patient (that they did, how many records matched and whether they attached the patient to an encounter, never what they typed), and when an owner or manager viewed a colleague's folder. Where the Practice's owner turns them on, and only while it is on Enterprise, weekly counts of the work of each member who counts as a clinician — photographs added, encounters filed, patients added and links shared — worked out from these records when asked for, and not stored. |
| Special category data | Yes. Clinical photographs and notes constitute health data under Article 9(1); extraoral photographs are also identifiable facial images. |
| Recipients | The sub-processors in Annex 3, and any third party the Practice itself chooses to share a folder with via the Service's share links. |
Annex 2 — Technical & organisational measures
- Tenant isolation. Row-level security scopes every table holding patient or clinical data to the practice the requesting session is working in, on every read and write. A login in several practices works in one at a time; the database checks which on every request, and a page left open for one practice can't change another's records.
- Access within the Practice. The Practice's owner, and for clinicians its managers, decide who joins; the owner decides in what role (owner, manager or clinician) and who counts as a clinician, and the database enforces what each role may do; managers can manage clinicians but not other managers or the owner. Before the Practice invites its first clinician, its owner chooses whether everyone keeps seeing every clinical record or each clinician sees only their own, and the choice is recorded with when it was made and by whom. Keeping clinicians to their own records needs the owner's recent sign-in (and their second step, where the Practice requires one) and can't be undone; the owner also chooses whether managers then still see every record. A clinician — and a manager who doesn't see every record — then sees the visits they're responsible for, the patients they added and, where the Practice's diary is connected, the patients booked with them; records with no clinician yet are seen only by the owner, and managers who see every record, until they're assigned. A clinician treating a patient sees the dates and clinicians of that patient's other visits, and can open a colleague's folder read-only for 24 hours by giving a reason — care, referral, continuity of care, or another reason they write down — at most 20 in any 24 hours; SmileSort offers no way to share or download an opened folder, and its photographs can't become the patient's photo. To find a patient they can't see, a clinician gives the exact name and date of birth, at most 30 times in any 24 hours, and a match only lets them attach that patient to their encounter; the patient's other folders stay closed to them. In such a practice, display links last 15 minutes.
- Access records. Changes to the team, its roles and its sign-in rules, invitations, ownership handovers, changes to a folder's clinician or a diary match, switches into the Practice, folders opened with a reason, patient lookups, owners' and managers' views of a colleague's folder, and downloads of the audit log are written by the server — nobody in the Practice can write or change them. The owner and managers can read and download all of them, and everyone else their own, in Settings → Activity log; a reason someone wrote in their own words is shown only to the owner, managers who see every clinical record, and its writer. Each download, of at most 50,000 entries, is itself recorded. They're kept for 24 months. The Practice's owner is emailed, naming the person and never a patient or a note, when someone joins, a manager removes someone, someone else connects a Camera Link computer, the sign-in rules change, a diary match changes, a folder is opened for another reason, or someone reaches the limit of folders opened.
- Authentication. Session tokens are verified against the identity provider on every request, not merely decoded from a cookie. Signing out, or being removed from the Practice, ends access at the database at once. The Practice can require two-step verification (an authenticator app) and set an idle limit, enforced by the database, with a warning first.
- Storage. Photograph files sit in private object stores. The copies the Service shows are in a store gated by the same per-practice scoping as the database. The original files, as taken, are in a store in the EU: written only by SmileSort's server, or through short-lived links it issues for the Practice's own space, and read only through that server, which checks the requester's access first, including the access rules within the Practice above.
- Importing from a cloud account. A user of the Practice may connect their own Dropbox or Google Drive account to import photographs.
- SmileSort asks only to read, never to change or delete.
- It receives a key that expires within hours and that it can't renew. It keeps the key encrypted, where no user's or staff member's session can read it, and uses it only for the user who connected it, at most 2 hours after consent (an hour for Google Drive).
- It then cancels the key with that service and deletes it. No user or practice is deleted while it holds one: the deletion cancels it first, or waits until it has ended.
- The folders and small previews shown while choosing go to that user and are never stored. Only the photographs they choose are imported, each original written straight into the EU store above.
- No file or folder name, path, account or key is written to SmileSort's logs.
- SmileSort staff see only how many keys are live, and, in the Practice's audit log, who connected an account and when the access ended — never the account, a file or the key.
- Sharing. External share links use a 192-bit random token and are scoped to the folders or photographs chosen for them. A link shared with a lab, a mentor or a colleague holds an explicit list of photographs: while it is live, the Practice may add photographs or folders to it, or take photographs off it, at the same address, without extending its expiry; a photograph filed later in a shared folder is shared only when the Practice adds it, and one on the list that the Practice moves to Trash is hidden until it is restored. Photographs taken off a link stop loading within 15 minutes, as for revocation. Any other link — to a patient, or made before recipients were recorded — opens the folders it was created for, as they stand. Each link expires after the period the Practice chooses — 7 days by default, or 14 or 28 days — or, where the Practice deliberately selects "No expiry", remains active until the Practice revokes it; the Practice can change a live link's expiry at any time. A link also stops opening while the Practice's subscription does not allow sharing. Any link can be revoked at any time: it stops opening at once, and photographs a recipient already has open stop loading within 15 minutes. Every link is created as a new record with its own token — never a reused one — and its creation, emailing, opening, downloads, photographs added or removed, update emails, changes of expiry and revocation are logged server-side and shown to the Practice.
- Encryption. TLS in transit; at-rest encryption at the infrastructure level.
- Staff access control. SmileSort's application and internal admin tooling cannot read patient, photograph, folder or clinical-note data — enforced at the database level, not just hidden in the interface — and can delete an account only when it holds no patient data. Direct administrative access to the production database, which sits outside those controls, is limited to SmileSort's co-founders and used only for maintenance and incident response. SmileSort's staff tooling shows staff a practice's account changes (its team, roles, sign-in rules and other settings, its Enterprise offer and handovers), which staff can also read in the database, together with the practice's other audit entries — photographs added or deleted, downloads and shared-link activity — as ids, codes and counts with who acted, never a photograph, a patient's name or a note. Staff can't read the access records above — folders opened, lookups, views of a colleague's folder, switches into the Practice, changes to a folder's clinician or a diary match, or downloads of the audit log — or any reason note.
- Leaving the Practice. Removing someone ends their sessions in the Practice, withdraws the invitations they sent, disconnects the Camera Link computers they connected there and ends any Dropbox or Google Drive access they connected there; the Practice chooses whether their share links stay. A login that belongs to another practice or its holder's own library stays for those.
- Figures for each clinician. The Practice's Insights show weekly counts of its work. Counts for each member of its team are off until the Practice's owner turns them on, which needs the owner to accept a version of SmileSort's staff notice and legitimate interests assessment templates that SmileSort has approved for use (none is approved yet); the database refuses any other version, the acceptance (version, when and by whom) is recorded, and each change is in the audit log. Counts are kept only for members who count as clinicians, and only while the Practice is on Enterprise. The owner and managers then see one such member's counts at a time, never ranked, and each clinician only their own. Nothing is stored beyond the records they're counted from, and SmileSort staff can't read them (to support the Practice's account, they see only how many photographs each person has added in all).
- Automated data lifecycle. A 28-day recoverable Trash before permanent erasure; an account whose free trial ends without a plan being chosen is fully purged 12 months after the trial ends, and a cancelled subscription, or any other plan that ends, 30 days after it ends, automatically — as Clause 11 sets out.
- No unnecessary third-party exposure. No third-party analytics or error-tracking tool has access to Patient Data.
- Backup coverage — disclosed, not assumed. The database is backed up daily. Photograph files are not currently covered by a separate file-level backup; SmileSort has assessed and accepted this at current scale, and the Practice should factor it into its own risk assessment.
Annex 3 — Approved sub-processors
| Sub-processor | Entity & location | Purpose | Patient data? |
|---|---|---|---|
| Anthropic | Anthropic PBC — United States | AI classification and sorting of clinical photographs | Yes — image data |
| Supabase | Supabase Pte. Ltd — Singapore (data hosted in the UK) | Database, authentication, file storage | Yes — primary store |
| Cloudflare | Cloudflare, Inc. — United States (original photograph files stored in the EU) | Application hosting, execution and CDN; storage of the original photograph files | Yes — the original photograph files, stored in the EU; otherwise as the execution environment for each request, including photographs on their way in |
| Stripe | Stripe — see Stripe's own DPA | Subscription billing (account only) | No |
| Resend | Resend — see Resend's own DPA | Transactional email | A patient's email address only, when the Practice emails them a consent form |
| Klaviyo | Klaviyo, Inc. — United States | SmileSort's own emails to account holders — a welcome to each practice owner, anything more only with consent (account data only) | No |
Every sub-processor established outside the UK has its own DPA incorporating the EU Standard Contractual Clauses and the UK International Data Transfer Addendum, independently confirmed rather than assumed. Stripe and Klaviyo are listed for completeness — they never receive Patient Data, verified against every call site that uses them.
Dropbox and Google (Google Drive) are not sub-processors. Where a user of the Practice connects their own Dropbox or Google Drive account to import photographs, SmileSort reads from that account on the Practice's instruction and sends it no Patient Data. The account, and what it holds, remain the user's or the Practice's, under their own agreement with Dropbox or Google. Photographs imported from Google Drive are never sent to Anthropic.