Trust Centre
Clinical photography contains sensitive patient information. SmileSort is designed to protect it throughout its lifecycle — from upload and storage to sharing and deletion.
Last reviewed 6 November 2026
HTTPS only between your devices and SmileSort, encryption at rest, and each practice's data kept strictly separate — and, inside a practice, access by role.
Learn moreYour practice controls its patients' data. SmileSort processes it for you, keeps it only as long as set out, and uses it for nothing else.
Learn moreWhat the AI does with a photograph, and what our AI provider keeps: no training, deleted within 30 days.
Learn moreAn administrative tool for clinical photography, not a medical device. SmileSort doesn't diagnose or recommend treatment.
Learn moreExternal security testing and certification as SmileSort progresses towards wider deployment.
Learn moreSix services, each checked and bound by its own data processing agreement.
Learn moreSecurity
Protection at every stage of the clinical photography workflow.
Clinical data is encrypted in transit — every page, every upload from your browser or from SmileSort Camera Link, and every import from your Dropbox or Google Drive goes over HTTPS only — and at rest, with AES-256. The one exception is the hop on your practice's own network from a Wi-Fi camera to the computer running Camera Link, explained below.
SmileSort Camera Link, our desktop app (currently in beta), takes new photographs from your cameras on a computer at your practice and sends them to SmileSort for you to review. From that computer to SmileSort everything goes over HTTPS. The key the computer holds can only send photographs into SmileSort for review: it can't list, open or download anything already there, and you can disconnect it in Settings at any time. Until SmileSort confirms it has a photograph, Camera Link keeps it in its own folder on that computer, then deletes it; one it couldn't send stays there for 30 days, longer if Camera Link isn't running. It never deletes or changes anything on a camera's memory card.
That hop stays on your practice's own network or cable. Over Wi-Fi it isn't encrypted by the camera or by Camera Link — a Canon is read through its camera control over plain HTTP, and a Sony or Nikon sends by plain FTP — so your Wi-Fi's own encryption is what protects it, and anyone who can join that network could, with the right tools, read photographs as they pass. Use your practice's own password-protected staff network (WPA2 or WPA3), never a guest or open network or the camera's own hotspot, and a computer with disk encryption switched on. A Canon on its cable doesn't use the network. Camera Link talks only to cameras on your practice's network, gives each Sony or Nikon its own login, and locks out repeated wrong passwords. Encrypted transfer from the camera (FTPS) is planned, Nikon first; it isn't available yet.
You can import photographs from your own Dropbox or Google Drive (currently in beta). SmileSort asks each only to read: it never changes or deletes anything there. While you choose, the service lets SmileSort see everything in your account, so SmileSort can show you the folders you open, with small previews it doesn't keep. It imports only the photos you choose. Its access ends within 2 hours of your agreeing — within an hour for Google Drive — and then SmileSort cancels its key with that service and deletes it. The key is stored encrypted and can be used only for the person who connected it. No SmileSort tool can show it to anyone, our team included. No file or folder name, path or account goes into our logs. Each photograph comes to SmileSort over HTTPS, its original straight into our storage in the EU.
Sessions are verified against the identity provider on every request, not just decoded from a cookie — a revoked or expired session can't be replayed — and the database checks each one too: signing out, or being removed from a practice, ends access at once. A practice can require two-step verification with an authenticator app, and sign its team out after a time without activity, with a warning first.
Every table and every photo file is protected by rules in the database itself: anything done on a dentist's behalf reaches the practice they're working in and nothing else, whatever the application asks for. One login can belong to several practices and a library of its own, but works in one at a time, and the database checks which on every request. Inside a practice, what each person can do follows their role, and a practice can keep each clinician to their own patients' records, with a recorded, time-limited way to open a colleague's folder for a patient they're treating. The few server tasks that run without a signed-in dentist — opening a share link, the nightly clean-up — are limited to one practice in code. The key that lets SmileSort read your Dropbox or Google Drive while you import is kept where no one's session can read it, and is used only for the person who connected it.
A share link uses a 192-bit random token. A link to a lab, a mentor or a colleague opens an explicit list of photographs, which you can add to or take photographs off at the same address: a photograph filed later in a shared folder is shared only when you add it. A link to a patient opens the folders it was created for, as they stand. Every link shows the patient's name only if you choose to include it, stops working after 7 days by default — or after 14 or 28 days, or only when you revoke it, if you choose — and can be revoked at any time.
No SmileSort tool — including our internal admin portal — can show our team your patients' photographs, folders or notes, the reasons your team give for opening a colleague's folder, your practice's record of who opened or looked up which records, or the figures Insights shows your practice; that's enforced in the database, not just hidden in the interface. Direct access to the production database is limited to SmileSort's co-founders.
The database is backed up daily, with a week of backups kept. Photograph files are not currently covered by a separate file-level backup — a gap we've assessed and disclose rather than assume away.
Privacy & Data
Designed around data minimisation, transparency and controlled processing of patient photography.
SmileSort's data protection programme is built around UK GDPR, with a Data Protection Impact Assessment (signed September 2026) and a Record of Processing Activities, both kept internally.
SmileSort Ltd is registered with the Information Commissioner's Office — registration number ZC258400.
Your practice determines why clinical photographs are processed; SmileSort processes that data to provide the service, as your processor. SmileSort separately acts as controller for its own account and billing information.
AI classification never receives a patient name, date of birth or other structured identifier — only the photograph itself. Location data in a photograph's file is never read.
Deleted records stay in Trash for 28 days, then are permanently removed. An account whose free trial ends without a plan being chosen stays read-only and exportable for 12 months, and a cancelled account for 30 days; then every patient record and photograph is permanently deleted, with every login not also used in another practice or its holder's own library. Billing records stay with Stripe, as tax law requires, and usage statistics are kept only in anonymous form. Your practice remains responsible for its own clinical record-keeping obligations.
A practice's owner can export every filed photograph, patient record and folder at any time, including while the account is read-only (the 30 days after cancelling, or the 12 months after a free trial ends without a plan): as one archive, or for a large practice as several that together hold them all. You're not locked into SmileSort to keep your own records.
Anthropic (AI classification, as the fallback when the on-device model can't load or can't read a photograph), Supabase (database & storage), Cloudflare (hosting, and storing your original photograph files in the EU), Stripe and Klaviyo (billing and our own emails to account holders — no patient data), Resend (transactional email — and a patient's email address, when you email them a consent form) — every one individually checked, none holding patient data outside the UK/EU without an EU SCC + UK Addendum transfer mechanism in place. Dropbox and Google Drive aren't sub-processors: when you import from them, they're your own accounts, which SmileSort only reads from.
AI
What SmileSort's AI actually does with a clinical photograph, and what it doesn't.
AI does two things in SmileSort: it recognises which standard view each photograph is — including which way up it was taken, so it can be shown upright — and helps group photographs taken at the same appointment. It doesn't interpret what a photograph shows.
You check every AI result. A batch upload waits for your approval before anything is filed. In a Clinical Series, recognised views go straight into their slots for you to check — drag any photograph to another slot or take it out — and anything SmileSort can't place waits under Needs review.
Recognising the view runs on your own device, in the browser: a model SmileSort trained on public, licensed photographs names the view, and an open-source model, also running in the browser, reads a face's angle to tell a profile from a front view. Photographs are then grouped into likely appointments by when they were taken and the view recognised for each. A photograph sorted that way is not sent to any AI service. If the models can't load in your browser, SmileSort sends that browser's photographs to Anthropic, our AI provider, for those two tasks only — for an AI Batch Sort, including photographs imported from your Dropbox (never those imported from Google Drive), a small copy of each photograph, to group them into appointments. If they load but can't read a photograph, SmileSort sends that photograph to Anthropic to name its view — and, after repeated failures, the rest of that upload. Either way it is under Anthropic's Data Processing Addendum, which includes the EU Standard Contractual Clauses and the UK Addendum for the transfer to the US. Anthropic deletes what it receives within 30 days, and keeps it longer only if its safety systems flag a request or the law requires it.
Anthropic doesn't train its models on data sent through its API, and SmileSort hasn't joined the opt-in programme that would change that. SmileSort doesn't use your patients' photographs for marketing, research or improving its own AI.
Clinical & Regulatory
SmileSort is not a medical device. It stores, organises and shares clinical photographs — every clinical judgement stays with you.
SmileSort is an administrative tool for storing, organising and communicating clinical photographs. Under the UK Medical Devices Regulations 2002, software limited to storage, archiving, communication and simple search isn't a medical device, and SmileSort's intended purpose stays within that.
SmileSort's AI recognises which standard view a photograph is — an upper occlusal, a smile, a left buccal — and which way up it was taken, and groups photographs taken at the same appointment. That's how it knows where to file them and how to show them. It doesn't assess the teeth, detect conditions, measure anything or suggest a diagnosis.
Sharing sends photographs to a lab or colleague as you see them in SmileSort, through a secure link you control. The file is the one you stored; a rotation or flip you applied — and a turn SmileSort made to show it upright — travels with it as the standard orientation tag that photo software reads. A crop changes only how the photo is framed on the link and in a clinical PDF; the recipient can still open and download the whole photograph. SmileSort never flips a photograph itself, and adds no interpretation or annotation.
SmileSort doesn't recommend treatment, highlight areas of concern or automate clinical decisions. A photograph filed in the wrong place is a filing error you can correct, not a clinical output.
Before any new AI feature is built, it's checked against SmileSort's intended purpose. Anything that would interpret the clinical content of a photograph would need a fresh regulatory assessment first.
We're putting the NHS clinical risk management standard for health software in place, led by co-founder Dr Abdelrahman Mohamed, a GDC-registered dentist, as Clinical Safety Officer. It covers the ways a filing or sharing mistake could affect a patient's care — a photograph filed to the wrong patient, or shown the wrong way round — and, for practices with a team, an encounter attributed to the wrong clinician, earlier photographs a treating clinician can't see, and the wrong patient chosen when two share a name and date of birth.
Assurance
A status roadmap, not a certification wall — what's done, in progress, and planned.
UK government-backed baseline cyber security certification.
A third-party security assessment of the live application.
The audited tier of Cyber Essentials, following the base certification.
Formal information security management certification.
Documents
Published in full, not gated behind a request form.
How SmileSort handles your own account data.
The full Article 28 terms governing your patients' data.
The contract governing your use of SmileSort.
Every cookie SmileSort sets, and why.
Every third party, what it receives, and its transfer mechanism.
How long data is kept, and what happens when it's deleted.
How to report a security issue directly to us, and how to test safely.
If you're reviewing SmileSort for your practice or have a security question, we'd be happy to help.
Contact securityFound a vulnerability? Read our Responsible Disclosure Policy before you test.
Last reviewed 6 November 2026.