Privacy policy
Denty records dental appointments and writes the clinical notes. That means handling some of the most sensitive data there is: what people say about their health. This page explains, in plain English, what Denty collects, where it goes, how long it's kept, and the rights everyone involved has. It covers the Denty iPhone app, the Denty web app, patient report pages and this website.
1. Who we are
Denty is made by SwiftLab's full legal name, a company registered in the United Kingdom with company number company number, whose registered office is at registered office address. We're referred to here as "we" or "us". You can reach us about anything on this page at rob@swiftlab.co.uk.
We are registered with the Information Commissioner's Office (ICO) under number ICO registration number.
2. Who is responsible for what
Data protection law gives different jobs to different people, and that matters here:
- Appointment data (recordings, transcripts, clinical notes, patient reports and the patient details a clinician adds) belongs to the dental practice or clinician using Denty. They are the controller: they decide to record, what to keep and what to share. We are their processor: we handle it only on their instructions, under a data processing agreement, to provide Denty.
- Your Denty account, the waiting list and this website: here we are the controller.
So if you're a patient and have a question about your own appointment, your dental practice is the right first contact (see section 8).
3. What we collect
When a clinician uses Denty
- Account details: your name and email address, and how you sign in (Apple, Google or email and password). We never see your Apple or Google password.
- Appointment recordings: the audio of the appointment, made only when the clinician presses Record.
- Transcripts and notes: what was said, who said it (dentist, nurse, patient or companion), and the clinical note, options, teeth and summaries Denty writes from it.
- Patient details the clinician chooses to add: for example name, email address, mobile number, date of birth, address and NHS number. All of these are optional.
- Private notes the clinician writes for themselves. These never appear on a patient's report.
- Patient reports: the plain-English page a clinician can send to a patient. To send it, we pass the patient's email address or mobile number to our email or text provider; we don't store it with the report.
- Usage counts: how much AI processing each note used (counts only, never any text), to work out our costs.
- Device details: a push notification token for each iPhone or browser you use, so we can tell you when a note is ready.
- Subscription status: which plan you're on. Payments go through Apple's App Store; we never see your card details.
When you join the waiting list
Your name, email address, role, practice name if you give it, and whether you'd like to test the iPhone app through TestFlight.
4. How we use it, and why
- To provide Denty: to transcribe recordings, write and store notes, let clinicians search their own notes, and send patient reports when a clinician asks. For appointment data we act on the practice's instructions; the practice's lawful basis is usually its public task or legitimate interests in providing care (UK GDPR Article 6), and for health data, the provision of health care (Article 9(2)(h)) under a duty of confidentiality.
- To run your account: signing in, your plan, and notifications. Our basis is our contract with you.
- To keep Denty working and secure: fixing faults and preventing misuse. Our basis is our legitimate interests. We never write transcript or note text into our logs.
- To contact people on the waiting list about Denty and TestFlight. Our basis is our legitimate interests, and you can ask us to remove you at any time.
We do not sell personal data, use it for advertising, or train AI models on appointment data, and our providers can't either. Google's terms don't allow it to train AI models on our data, including when it runs Anthropic's Claude for us, and AssemblyAI doesn't use recordings sent to its European servers for training.
5. Where it's stored and who processes it
Recordings, transcripts, notes, patient details and patient reports are stored in London, on Google Cloud (Firebase) in the europe-west2 region. The AI that turns them into a transcript and a note runs in the European Union. Some steps need specialist providers, our sub-processors, each under a contract that limits them to that job:
| Provider | What they do | Where |
|---|---|---|
| Google Cloud (Firebase) | Storing recordings, transcripts, notes, patient details and reports; running our server code; search by meaning (Vertex AI) | United Kingdom (London) |
| AssemblyAI | Turning the recording into a transcript with speakers | European Union |
| Google Cloud (Vertex AI), running Anthropic's Claude | Writing the clinical note from the transcript, and the plain-English patient report | European Union |
| Google (Firebase Authentication) | Signing in: your name, email address and sign-in method | United States |
| Google (Firebase Cloud Messaging and Hosting) | "Your note is ready" notifications (the note's short title only); serving this website and report pages | Global |
| Resend | Sending report links by email. The email says only that the practice has shared a report, with the link. | Sent from Ireland (EU); delivery records in the United States |
| Twilio | Sending report links by text. The text has the patient's first name and the link, and says it's a summary of their dental appointment. | United States |
| Apple | Sign in with Apple, App Store subscriptions, notifications to iPhones | Global |
Transfers outside the UK. Recordings, transcripts and notes stay in the UK and the European Union. The EU has a UK adequacy decision, so transfers there need no extra safeguard. A few things do go to the United States: clinicians' sign-in details (Firebase Authentication runs only from US data centres), and, when a clinician sends a report, the patient's email address or mobile number and the message itself. We protect these transfers with the UK–US data bridge where the provider is certified under it, and otherwise with the UK International Data Transfer Addendum in our contract with them. A provider's support staff outside these regions may occasionally need to access data to fix a fault, under the same contracts and safeguards.
6. How long we keep it
- Recordings, transcripts and notes are part of the clinical record. They're kept until the clinician deletes them or closes their account. Deleting a note deletes its recording and its search index too.
- Patient details are kept until the clinician removes them or closes their account.
- Patient reports are a separate copy of the plain-English summary, kept until the clinician closes their account or asks us to remove it. If the clinician chose a 30-day link when sending, the link stops working after 30 days.
- Accounts are deleted on request: email us and we'll delete the account and everything in it within 30 days.
- Copies held by providers: we delete each transcript from AssemblyAI as soon as we have it, and AssemblyAI deletes the uploaded recording within 48 hours. Google doesn't keep the transcript or note once Claude has replied, except that a request its automated systems flag as possible misuse may be kept, in the EU, for up to 90 days for review. Resend and Twilio keep a record of each message they send under their own retention terms.
- The waiting list is kept until Denty launches or you ask us to remove you, whichever is sooner.
- Backups: our database keeps earlier versions of records for one hour, so mistakes can be undone. Google removes deleted data from its own backup systems within about six months.
Dental practices set their own retention rules for clinical records, and remain responsible for keeping records as long as the law requires.
7. How we protect it
- Everything is encrypted in transit and at rest.
- Each clinician's notes and patients can be reached only by that clinician's own account. Our database and storage rules enforce this, and you need a real account (Apple, Google or email) to sign in.
- A recording waiting for a signal stays in the iPhone app's private, encrypted storage, left out of device backups, until it's uploaded. In the web app, it's held only in that browser tab until it's uploaded.
- Patient report links are made from 32 random bytes, can't be guessed, aren't indexed by search engines, and the page shows no name or contact details.
- Transcript and note text never goes into our logs, and only our own staff can access production systems, for support and maintenance.
If a breach ever put personal data at risk, we'd tell the affected practices without delay so they can meet their own duties, and the ICO where the law requires it.
8. If you're a patient
Your dentist uses Denty to write up your appointment. They should tell you they're recording, and if you'd rather they didn't, they won't. Your practice controls your notes, so please ask them first if you'd like to see, correct or delete anything. We'll help them answer you. You can also contact us directly and we'll pass your request on.
If your practice sent you a link to your appointment, anyone with the link can open the page, so please don't forward it. It names no one, and if your practice chose, it stops working after 30 days.
9. Your rights
Under UK data protection law you can ask to:
- see the personal data held about you, and get a copy;
- have it corrected if it's wrong, or deleted;
- limit how it's used, or object to its use;
- take your data to another service (portability).
Some of these have limits for health records, which practices often have to keep. We'll reply within one month. If you're unhappy with how your data has been handled, you can complain to the Information Commissioner's Office at ico.org.uk, though we'd welcome the chance to put it right first.
10. This website
This site sets no cookies and has no analytics, advertising or tracking. Its fonts and films are served from our own hosting. Like any website, our hosting provider (Google) briefly logs technical details such as IP addresses to keep the service running and secure. If you join the waiting list, what you enter is stored in London, and we may be sent a copy by email through Resend.
11. Changes and contact
If we change how we handle personal data, we'll update this page and its date, and tell clinicians in the app before a significant change takes effect. Questions or requests: rob@swiftlab.co.uk.