This Data Processing Agreement ("DPA") forms part of the Terms of Service between Smileline Technologies Ltd, company number 17408336, with its registered office at 1 Lyric Square, London, England, W6 0NB (the "Processor"), and the practice accepting it (the "Controller" or "Practice"). It is entered into when the Practice owner accepts it in the app, and it governs all processing of Practice Data that contains personal data. It is written to satisfy Article 28 of the UK GDPR and, for a Practice established in the European Union or processing the personal data of people in the EU, Article 28 of Regulation (EU) 2016/679. Where those two differ, whichever applies to the Practice governs; references to "data protection law" mean the one that applies to it.
1. Roles and scope
The Practice is the controller of the personal data it stores in the Service — its patients, leads and contacts. Smileline is the processor and processes that data only to provide the Service, on the documented instructions given through the Practice's use of the platform. Smileline is a separate, independent controller of its own account, billing and security data, as described in the Privacy Policy.
2. Details of the processing
| Subject matter | Hosting and operating a dental CRM: lead capture, patient records, journeys, messaging, scheduling, reporting and integrations. |
|---|---|
| Duration | The term of the Practice's subscription, plus the deletion window in section 9. |
| Nature and purpose | Storage, retrieval, display, transmission (messages the Practice sends), analysis (reports) and the automated workflows the Practice configures. Where the Practice switches them on, this also covers: visitor tracking on the Practice's own website, including the website tracking script and dynamic insertion of tracking telephone numbers; website analytics on the Practice's website (the pages visitors view, for how long and where they came from), A/B page tests (showing each visitor one of two versions of a page and counting, per version, the visitors who went on to make an enquiry that led to a booking), and heatmaps and session replays (recordings of how visitors scroll, click and move through the Practice's web pages, with anything typed into a form masked); upload of conversion events derived from Practice Data to the advertising platforms the Practice connects; and the AI voice agent, which holds spoken conversations with patients and prospective patients on the Practice's behalf; and Call AI, for Practices on SmileLine Voice that record their calls: live transcription of recorded calls, live on-screen suggestions for Practice staff drawn from the Practice's own call playbook, and AI analysis of each call and of each week's calls (summaries, outcomes, suggested follow-ups and email drafts for staff to review and send, and coaching for the Practice's team). |
| Data subjects | The Practice's patients, prospective patients (leads/enquiries), their contacts, visitors to the Practice's website, and Practice staff. |
| Categories of personal data | Contact details, demographic details, enquiry and communication history, appointment and treatment-interest information, payment status, marketing consents, and identifiers from connected systems. Where the Practice uses SmileLine Voice: call metadata (the number called, the staff member who called, the time, duration and result of each call) and, where the Practice switches call recording on, the recorded audio of answered calls and, with Call AI, each recorded call's transcript and its AI analysis. For visitors to the Practice's website: online identifiers (a pseudonymous visitor identifier stored in the visitor's browser), the pages viewed and for how long, the referring website and campaign parameters, approximate location (country and city) and device type derived from the request, which version of a tested page was shown and, for heatmaps and session replays, recordings of page content and of scrolling, clicks and pointer movement, with anything typed into a form masked. Visitors' IP addresses are not stored with these records. |
| Special category data | Data concerning health — dental history, treatment plans and clinical context the Practice records or syncs from its practice management system. Recorded calls are also likely to contain data concerning health, because patients describe symptoms, treatment and medical circumstances on the phone; the Practice decides whether to record calls at all and how long recordings are kept. The Practice is responsible for its Article 9 condition for processing this data (typically the provision of health care, Art. 9(2)(h)) and for telling callers that calls may be recorded. |
Website analytics, page tests, heatmaps and session replays. The Practice chooses, through its consent setting in the Service, when the visitor identifier may be stored, and is responsible for the privacy information and consent its website's visitors need, including under the rules on storing information on a visitor's device. Page views are linked to the visitor identifier only where that setting and the visitor's own choices allow the identifier to be stored; otherwise they are counted only in anonymous totals. A browser's Global Privacy Control signal is always treated as a refusal. Heatmaps and session replays record only visitors whose identifier is stored and who have not refused analytics, mask what visitors type, and never record the forms and booking pages Smileline hosts for the Practice. To count which version of a page leads to more bookings, Smileline matches a visitor's identifier with the Practice's own enquiry and booking records, and shows the Practice only totals per version — never which visitor made which enquiry. Visit-level records, including recordings, are held in the Practice's service region (section 7) and deleted after 13 months; after 12 months each day is summarised into daily totals that identify no visitor. When the Practice erases a patient, Smileline also deletes the website records linked to that patient's visitor identifiers. These features run on Smileline's own systems and the sub-processors in section 5; no third-party analytics provider receives this data.
3. The Processor's obligations
Smileline shall:
- process Practice Data only on the Practice's documented instructions (the platform's features and settings), including with regard to transfers of Practice Data to a third country or an international organisation, unless required to do so by law to which Smileline is subject — in which case it will inform the Practice of that legal requirement before processing, unless the law prohibits it;
- immediately inform the Practice if, in Smileline's opinion, an instruction infringes the UK GDPR, the EU GDPR or other applicable data protection law;
- not process Practice Data for its own purposes, and not use Practice Data — or permit any sub-processor to use it — to train, fine-tune or otherwise improve any artificial-intelligence model;
- as the one exception to the point above, count how many of the Practice's outbound calls a person answered in each hour of each day of the week, and add those counts to the same counts of the other practices in the same country that have accepted this version of this DPA, solely so that the Service can suggest when each of those practices should call people back. The counts hold no patient, telephone number, call or other personal data; the combined counts are worked out when needed and never stored, shown or shared; and a combined count drawn from fewer than five practices is never used;
- ensure everyone authorised to access Practice Data is bound by confidentiality;
- implement the technical and organisational measures in section 6;
- respect the sub-processing conditions in section 5;
- assist the Practice, taking into account the nature of the processing, in responding to data-subject rights requests and in meeting its obligations on security, breach notification and impact assessments;
- delete or return Practice Data as set out in section 9;
- make available the information reasonably necessary to demonstrate compliance with this DPA, and allow audits as set out in section 11.
4. The Practice's obligations
The Practice warrants that it has a lawful basis (and, for health data, an Article 9 condition) for the personal data it stores in the Service; that its patient-facing privacy information covers the use of a CRM processor; and that the instructions it gives through the platform comply with UK data protection law. The Practice controls — and is responsible for — who on its team can access what, through the platform's roles.
5. Sub-processors
The Practice gives general authorisation to the sub-processors below. Smileline updates this list when it adds or replaces a sub-processor. The Practice may object to a sub-processor on reasonable data-protection grounds by contacting Smileline; if the objection cannot be resolved, the Practice may terminate and export its data.
| Sub-processor | Purpose | Location |
|---|---|---|
| Cloudflare, Inc. | Application hosting, networking, storage | UK/EU edge; global network |
| Hetzner Online GmbH | Server infrastructure for the primary database and application services in the EU region | Germany |
| PostHog, Inc. | Product analytics, masked session replay and error diagnostics for signed-in practice staff using the Service, in an EU-hosted project. Patients and visitors to the Practice's website are never included: website analytics, heatmaps and session replays on the Practice's website (section 2) are never sent to PostHog. | EU |
| Telnyx | Telephony for the Practice's calling features — carrying, for Practices on SmileLine Voice, inbound and outbound calls, voicemail capture and call recordings where the Practice switches recording on, and the live transcription of recorded calls for Call AI, which Telnyx performs through AssemblyAI and, from 20 November 2026, through Deepgram (below). Smileline holds the account with Telnyx; the Practice does not contract with Telnyx. | UK/EU carriage; US |
| AssemblyAI, Inc. (engaged through Telnyx) | Live speech recognition of recorded calls for Practices using Call AI on SmileLine Voice, until 20 November 2026, when Deepgram replaces it. The call audio is processed transiently, while the call is live, to produce the transcript. | US |
| Deepgram, Inc. (engaged through Telnyx), from 20 November 2026 | Live speech recognition of recorded calls for Practices using Call AI on SmileLine Voice, replacing AssemblyAI. The call audio is processed transiently, while the call is live, to produce the transcript. | US |
| Cloudflare, Inc. (Workers AI) | Automatic speech recognition of a patient's voice message longer than two hours, or of unknown length, and, for Call AI, choosing which of the Practice's own answers to show staff during a call (Cloudflare's Clef-flash model) and, from 20 November 2026, reading the place a caller names for a travel time (Google's Gemma model, run by Cloudflare), using models hosted on Workers AI that retain nothing. Audio and text are processed transiently; a transcript is deleted with the message it came from. | UK/EU edge; global network |
| Eleven Labs Inc. (ElevenLabs) | Automatic speech recognition: the recording of a voice note and its live words while it is recorded; speech dictated into the in-app AI assistant, the chart's 3D view chat and the phone app's Send as text; stored call recordings and voicemail, from SmileLine Voice, the Power Dialer or the Practice's own phone system; and patients' voice messages whose length is known to be at most two hours; and, where the Practice enables the AI receptionist, the caller's speech while a call it answers or places is live. ElevenLabs works under zero-data-retention terms: it keeps no audio or transcript of what it transcribes, and does not use it to train its models. Smileline's transcripts are deleted with the recording or message they came from. | US |
| Google LLC (Google Maps Platform), from 20 November 2026 | For Practices in the UK using Call AI, travel times and a map from a place a caller names during a call to the Practice. Only the name of the place is sent, from the staff member's browser, never who the caller is. | Global |
| Stripe Payments Europe, Ltd. | Subscription billing | EU/US |
| Resend, Inc. | Transactional email delivery | EU/US |
| OpenAI, LLC | Inbox AI assistance (drafting and summarising replies to patients) and the search embeddings behind the knowledge base — for every Practice on pay-as-you-go pricing, where these features need no add-on, and for a Practice on earlier pricing only where it enables the AI add-on. The in-app AI assistant, for every Practice: answering a team member's questions about the Practice's account and preparing changes the team member confirms, from the records that team member can access — never clinical records, medical alerts or notes; what it sends is never used to train OpenAI's models, and a conversation is deleted 30 days after its last message, and at once when a patient it used is erased. For Practices on the AI receptionist, also the written summary produced after each call and, during the call, listening again to a few seconds of the caller's speech (a date of birth, or an answer said in pieces) to check what was said; for a date of birth, the date of birth the Practice holds for the caller is sent with it as a hint. This is under OpenAI's zero-data-retention terms: nothing from a call is stored by OpenAI or used to train its models. For Practices using Call AI on SmileLine Voice, also the analysis of each recorded call's transcript after the call, the weekly call insights and the Practice's call playbook; call content sent for analysis is never used to train OpenAI's models. For Practices using voice notes, also the written draft of each note from its transcript, and the live draft shown while it is recorded; what it sends is never used to train OpenAI's models. For an AI smile simulation on a face photo (Features & Labels, below), also finding where the smile is in the photo; OpenAI keeps no copy of the photo and does not use it to train its models. | US |
| Phonic, Inc. | The speech-to-speech AI model (Phonic-1) behind the AI receptionist — only where the Practice enables it. It conducts a call the AI receptionist answers or places: it receives what the caller says and speaks the assistant's replies, transiently, while the call is live. Zero data retention with Phonic is being switched on for Smileline's account. Phonic is not asked to keep the call's audio or transcript, but until zero retention is on, that is not yet guaranteed. | US |
| xAI | The answering model behind the patient-facing chat widget — only where the Practice switches on the widget's AI answers and publishes the widget, and, on earlier pricing, has the AI add-on. Website visitors' messages and the practice content the widget answers from are sent to xAI to generate a reply. xAI is not engaged for telephone calls. | US |
| Modal Labs, Inc. | GPU processing of CBCT scan images (without the patient's name or details) for SmileGuide's AI segmentation | US |
| Features & Labels, Inc. (fal) | AI smile simulations on a patient's face photo, made only when a member of the Practice's team asks for one (Generate after, and a short video of it): the part of the photo around the mouth — for the video, the simulated picture of the face — is sent to fal with the options and any note the team member typed, and never the patient's name or details. fal passes it to the maker of the AI model that draws the result (Seedream, by ByteDance, for the picture; Kling, by Kuaishou, for the video). Smileline asks fal not to store what it is sent and to delete its copy once Smileline holds the result. fal's own terms say its service is not designed for special categories of personal data. | US; and where the model's maker processes it |
This list does not include providers the Practice connects with its own account and its own credentials — its messaging providers, its practice management system, its advertising platforms and its payment account for booking deposits. Those act under the Practice's own agreements with them and are not Smileline sub-processors. The carve-out reaches no further than that: where Smileline supplies the account, the credentials and the commercial relationship, the provider is a Smileline sub-processor and is listed above even though the Practice's patients are the data subjects. SmileLine Voice telephony is the clearest example — the Telnyx account, the numbers, the invoice and the patient telephone numbers dialled through it are all Smileline's responsibility as processor.
6. Security measures
- Encryption in transit (TLS 1.2+) and at rest;
- per-practice data isolation enforced at the application layer on every query;
- role-based access control within the Practice, and audit logging of actions taken in the platform;
- additional envelope encryption for stored channel credentials and secrets;
- restricted, credentialed access to production systems for Smileline staff, limited to what operating the Service requires;
- backups and tested restore procedures.
7. Hosting location and international transfers
Practice Data is held in the service region fixed by the Practice's legal country at sign-up. Practices in the United Kingdom and the European Union are served from the EU region, with the primary database in Germany. Practices in the United States are served from the US region, with Practice Data held in the United States. This is where Smileline itself stores Practice Data. ElevenLabs (section 5) transcribes audio, for Practices in either region, in the United States and keeps none of it.
Several sub-processors in section 5 process personal data outside that region. Where Practice Data originating in the UK is transferred outside the UK, the transfer relies on UK adequacy regulations or on standard contractual clauses with the UK International Data Transfer Addendum. Where Practice Data originating in the EEA is transferred outside the EEA, the transfer relies on an adequacy decision or on the European Commission's Standard Contractual Clauses (Implementing Decision (EU) 2021/914), which are incorporated into this DPA by reference and take effect automatically for any such transfer. Smileline will supply the Practice with a copy of the safeguards applying to a given transfer, and with the information the Practice needs for its own transfer risk assessment, on request.
8. Personal data breaches
Smileline will notify the Practice without undue delay, and in any event within 48 hours, after becoming aware of a personal data breach affecting Practice Data, and will provide the information the Practice needs for its own notification obligations, cooperating in the investigation and remediation.
9. Return and deletion
The Practice can export its data from the platform at any time, and the export tools stay available for 30 days after the subscription ends so nothing has to be retrieved in a hurry.
At the Practice's choice, Smileline will either return Practice Data to the Practice or delete it. Tell us which you want before the end of that 30-day window. If you ask for a return, we provide the data in a structured, commonly used, machine-readable format and delete our copies afterwards. If you ask for deletion, or if the window passes without a choice, Smileline deletes Practice Data from production systems within 90 days of the subscription ending, and from backups as they expire on their rotation schedule. We keep data only where storage is required by law, and only for as long as that law requires.
Deleting Practice Data from Smileline does not discharge the Practice's own duty to keep dental records for the period its regulator requires, which is considerably longer than we hold anything. Export what you are required to keep before asking us to delete.
10. Professional secrecy (Germany and Austria)
This section applies where the Practice is bound by a professional secrecy obligation under section 203 of the German Criminal Code (Strafgesetzbuch) or an equivalent provision of Austrian law.
Smileline acts as a person cooperating in the Practice's professional activity (mitwirkende Person) within the meaning of section 203(3) StGB. Smileline is obliged to secrecy in respect of all Practice Data covered by that obligation, and this obligation continues after this DPA ends. Smileline will disclose such data only where necessary to provide the Service, will oblige every person and every sub-processor it gives access to in the same terms before access is granted, and will remain responsible for their compliance. Smileline will notify the Practice without undue delay of any breach of this obligation of which it becomes aware, and of any legal demand for the disclosure of such data, unless prohibited by law from doing so.
11. Audits
Smileline will make available documentation demonstrating compliance with this DPA. Where that is insufficient, the Practice (or its appointed auditor, not a Smileline competitor) may audit once in any 12-month period, on 30 days' notice, during business hours, without disrupting the Service, and subject to confidentiality.
12. Liability and precedence
The liability provisions of the Terms of Service apply to this DPA. If this DPA conflicts with the Terms on data-protection matters, this DPA prevails. This DPA is governed by the laws of England and Wales.
13. Record of acceptance
The Practice owner accepts this DPA in the app during onboarding (and again when a new version is published). Smileline records who accepted, the signing capacity, the version and the time as minimised evidence. It does not attach an IP address or browser user agent to the acceptance. The Practice can view its acceptance record at any time in Settings → Agreements.