This policy explains how SmileLine Technologies Ltd, company number 17408336 ("Smileline", "we") handles personal data in connection with the smileline.io website and the Smileline platform (the "Service"). We process personal data in two distinct roles, and it matters which one applies:
- As a controller — for the data of the people we deal with directly: visitors to this website, and the staff of practices who hold Smileline accounts.
- As a processor — for the patient data that dental practices store in the Service. The practice is the controller of its patients' data; we process it only on the practice's instructions, under our Data Processing Agreement. If you are a patient of a practice that uses Smileline, contact the practice directly about your data — this policy's sections 1–6 do not govern that data.
1. Data we collect as a controller
- Account data — name, email address, password hash, role, avatar, language, and the practice you belong to.
- Billing data — subscription state and invoicing details. Card details are collected and held by Stripe, not by us.
- Usage and security data — sign-in timestamps, IP address, browser user agent, product interactions, error diagnostics, masked session replays of your use of the platform and an audit trail of actions taken in the platform. Session replay masks form inputs and rendered text and does not record request or response bodies.
- Agreement records — when you accept our Terms, this policy or the DPA, we record who accepted, the document version, the time and the capacity in which it was accepted, as minimised evidence of the agreement. We do not attach an IP address or browser user agent to the acceptance.
- Contact data — messages you send to our sales or support addresses.
2. Why we process it (lawful bases)
- Performance of a contract — providing the Service, authentication, billing, support.
- Legitimate interests — securing the platform, keeping audit trails, preventing abuse, improving the product.
- Legal obligation — accounting records, and evidencing consent and contract acceptance.
We do not sell personal data, and we do not use it for advertising.
3. Cookies and storage on your device
Our own website, smileline.io, sets no analytics or advertising cookies. The platform sets one strictly necessary cookie: a session cookie that keeps you signed in. It is kept for 30 days from your last visit and is removed when you sign out.
Signed-in product analytics and masked session replay store an identifier in your browser's local storage rather than in a cookie. We describe it here rather than treating it as exempt: the law on storing information on your device covers local storage the same way it covers cookies, and it is used for our own product analytics rather than to deliver the Service. It runs only for signed-in practice staff using the platform — never for patients, and never on smileline.io or on any practice's website. Session replay masks text and form inputs, and does not record request or response bodies. If you would rather not be included, write to privacy@smileline.io and we will exclude your account.
The website tracking script that practices install on their own websites is a separate thing, described in the Data Processing Agreement. It stores a visitor identifier on the visitor's device, and for practices in the UK and the EU it waits for the visitor's consent before doing so. It also honours the Global Privacy Control signal wherever it is sent.
On a practice's own website, the same script can also give the practice website analytics (which pages visitors view, for how long, and where they came from), A/B page tests (which of two versions of a page a visitor was shown, and whether visitors who saw each version went on to book) and heatmaps and session replays (recordings of how visitors scroll, click and move through the practice's pages, with anything typed into a form masked). For these, the practice is the controller and we act as its processor under the Data Processing Agreement; the data subjects are the practice's website visitors. Page views are linked to the visitor identifier only where the practice's consent setting and the visitor's own choices allow the identifier to be stored; otherwise they are counted only in anonymous totals. Heatmaps and session replays are recorded only for visitors whose identifier is stored and who have not refused analytics, never for a browser sending the Global Privacy Control signal, never on the forms and booking pages Smileline hosts for practices, and never on smileline.io. Visit-level records, including recordings, are held in the practice's service region (section 5) and deleted after 13 months. These features run within the Service, on the providers described in section 4; no third-party analytics provider receives this data.
4. Who we share data with
We use a small number of service providers to run Smileline. Those that process personal data on our behalf are listed in the Data Processing Agreement (sub-processors) — principally Cloudflare (hosting), our managed database provider, Stripe (payments), Resend (transactional email) and Telnyx, which carries calls for practices using our calling features — for practices on SmileLine Voice, inbound and outbound calls, voicemail and call recordings where the practice switches recording on. Where a practice enables SmileLine Voice, stored call recordings and voicemail messages also go through post-call transcription by ElevenLabs' speech-recognition service in the United States, which keeps no audio or transcript of what it is sent; our transcripts are kept no longer than the recording they came from. ElevenLabs also transcribes call recordings from the Power Dialer or a practice's own phone system, a clinician's voice notes, speech dictated into the in-app AI assistant, the chart's 3D view chat and the phone app's Send as text, and patients' voice messages (one longer than two hours, or of unknown length, is transcribed on Cloudflare's infrastructure instead). Where such a practice records its calls in the UK or the US, Call AI also transcribes the call live — Telnyx passes the audio to its speech-recognition provider, AssemblyAI (from 20 November 2026, Deepgram) — so the practice's staff can follow the conversation and see short answers from the practice's own information (its website, documents and the details it keeps in Smileline) during the call; a model running on Cloudflare's infrastructure (Workers AI), which keeps nothing after it answers, picks which answer fits. From 20 November 2026, for UK practices, when a caller asks how to get to the practice from a place they name, only the name of that place is sent to Google Maps to show the travel time — never who the caller is. After the call, OpenAI analyses the transcript to write a summary, the outcome, a suggested next step and, where useful, a follow-up email for a person at the practice to review and send, along with coaching notes for the practice's team. Live transcripts and call analyses are kept no longer than the recording of the call. If you try the public phone demo on smileline.io, we keep the number you entered for seven days and, when you book a slot on that call from a mobile, may send it one text with a link to a recap of the demo booking. Calls on SmileLine Voice are offered on an unlimited fair-use basis to practices on earlier pricing, and are charged per minute to practices on pay-as-you-go pricing. Either way, we monitor aggregate calling volumes to detect fraud and resale, and we may contact a practice whose usage is far outside normal practice patterns. To suggest when a practice's team should call people back, we count how many of the practice's outbound calls were answered in each hour of the week and, where the practice has accepted our Data Processing Agreement's terms for it, add those counts — which hold no name, number or call — to the same counts of other practices in the same country; a combined count drawn from fewer than five practices is never used, and only the suggested time is ever shown. For a practice on pay-as-you-go pricing, or one that enables the AI add-on on earlier pricing, we also use two AI providers for different features: OpenAI for inbox assistance and search embeddings, and xAI for the answering model behind the patient-facing chat widget. Where a practice switches on the AI receptionist, on a call it answers or places the caller's speech is recognised live by ElevenLabs, and the assistant that conducts the call and speaks its replies is Phonic's speech-to-speech model, Phonic-1, in the United States. 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. OpenAI writes the summary after the call and, during it, listens 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; to check a date of birth, the date of birth the practice holds for the caller is sent to OpenAI with it as a hint. OpenAI works under zero-data-retention terms. The transcript of such a call comes from that live session; recordings, where the practice switches them on, are transcribed afterwards by ElevenLabs as described above. The assistant always introduces itself as the practice's AI assistant, and you can ask for a person at any time. Practices can also use Smileline's in-app AI assistant, which answers their team's questions about the practice's account and helps prepare changes the team member confirms. It reads only what the team member asking can see, never clinical records, and uses OpenAI, which does not use what it is sent to train its models. Conversations are private to the team member, deleted 30 days after their last message, and deleted straight away when a patient they used is erased. Where a member of a practice's team asks for an AI smile simulation on a face photo, OpenAI finds where the smile is in the photo, and the part of the photo around the mouth is sent to fal (Features & Labels, Inc., in the United States), which passes it to the maker of the AI model that draws the simulated teeth; for a short video of the simulation, the simulated picture of the face is sent the same way. Neither receives the patient's name or contact details. We ask fal not to store what it is sent and to delete its copy once we hold the result, which is kept with the photo and marked as a simulation. We use PostHog in an EU-hosted project for authenticated product analytics, masked session replay and error diagnostics. Where a practice owner or manager opens the Zapier builder under Settings → Integrations, we pass their name and email address to Zapier so it can sign them in; Zapier then processes it under its own privacy policy. We may also disclose data where required by law. We do not share personal data with anyone else.
5. Where your data is hosted, and international transfers
Every practice is pinned to a service region by the legal country it chose at sign-up, and that choice does not change afterwards. Practices in the United Kingdom and the European Union are served from our EU region, with the primary database hosted in Germany. Practices in the United States are served from our US region, with their data hosted in the United States. A practice's own records, as Smileline stores them, stay in its region; ElevenLabs, which transcribes speech (section 4), does so in the United States and keeps none of what it is sent.
Some of the providers listed in section 4 process personal data outside that region — the AI providers and parts of our telephony and email delivery operate in the United States. For personal data originating in the UK, those transfers rely on UK adequacy regulations or on standard contractual clauses with the UK International Data Transfer Addendum. For personal data originating in the EU, they rely on an adequacy decision or on the European Commission's Standard Contractual Clauses (Decision (EU) 2021/914). You can ask us for a copy of the safeguards that apply to a particular transfer by writing to privacy@smileline.io.
6. Retention
- Account data is kept while the account exists and deleted or anonymised within 90 days of account deletion.
- Billing records are kept for 6 years to meet accounting obligations.
- Agreement-acceptance records are kept for the life of the practice's account and for 6 years after, as evidence of the contract.
- Visit-level website analytics, A/B page test, heatmap and session replay records from practices' websites are kept for 13 months and then deleted. After 12 months each day is summarised into daily totals that identify no visitor, which are kept for the life of the practice's account.
- Practices can set retention periods for message content, patient-bearing activity and audit detail, and call recordings. Shorter periods are applied progressively to existing detail. Structural records needed to preserve security, accountability and operational integrity may remain after that detail is redacted or deleted. See the DPA.
YouTube integration
Smileline uses YouTube API Services to connect the channel you select, upload videos on your instructions, and display its videos and statistics. We access and store the channel identifier, name, handle and image; video identifiers, links, titles, publication dates and thumbnails; subscriber and video statistics; and encrypted authorisation credentials. We send Google the videos you select for upload, their title, privacy and audience settings, and the credentials needed to carry out your requests.
This information is available to authorised staff of your practice and processed by our hosting providers described above in your practice’s hosting region. We do not sell Google user data, use it for advertising, or use it to train general-purpose AI models. Our use and disclosure of Google API information comply with the Google API Services User Data Policy, including its Limited Use requirements. Google’s own handling is described in the Google Privacy Policy.
We check that Google still authorises the connected channel and refresh or delete cached channel and video metadata at least every 30 days. Historical statistics may remain while that authorisation and the channel continue to exist. Removing a YouTube account stops Smileline’s access and starts deletion of its cached YouTube data without revoking a shared Google grant. A practice owner can instead choose Revoke Google access and delete YouTube data in Social → Accounts; this can disconnect other practices and Smileline integrations sharing the grant. Revocation starts immediately and deletion must finish within seven days. If you revoke through Google, we delete the affected cached data within 30 days. Pending deletion and any failure remain visible in Accounts until cleanup finishes, independently of subscription access.
You can also revoke access through Google’s security settings or request deletion at giulio@smileline.io. These actions do not delete videos already uploaded to YouTube or the content and media you authored in Smileline; you control those separately.
7. Automated decision-making
We do not make decisions about you that produce legal effects or similarly significantly affect you on an automated basis alone. The platform does automate work for practices — routing enquiries, scoring and prioritising leads, sending scheduled messages and placing AI voice calls — but a person at the practice decides on treatment, on booking and on anything else that affects a patient. Where the AI assistant or the AI voice agent handles an enquiry, the practice's team remains reachable and takes over on request. Call AI's summaries, scores and suggestions only help the practice's staff: an email it drafts is sent only by a person, and a person at the practice decides every next step.
8. Whether you have to give us data
For account holders, the account data in section 1 is required to enter into and perform our contract with the practice: without it we cannot create an account or provide the Service. Everything else you give us is optional. If you are a patient of a practice that uses Smileline, the practice decides what it records about you — ask the practice.
9. Your rights
Under the UK GDPR and the EU GDPR you can ask us for access to, correction, deletion, restriction or portability of the personal data we hold about you as a controller, and you can object to processing based on legitimate interests. Where we rely on your consent for anything, you can withdraw it at any time; withdrawing it does not affect the lawfulness of what we did before you withdrew.
Write to privacy@smileline.io — we acknowledge promptly and respond within one month. If you are not satisfied with our response, say so in reply and a different person will review it; we will tell you the outcome of that review in writing.
You can also complain to a supervisory authority. In the UK that is the Information Commissioner's Office (ico.org.uk). In the EU it is the supervisory authority of the country where you live or work, or where the problem happened — you do not have to come to us first, though we would appreciate the chance to put things right.
10. Security
All traffic is encrypted in transit (TLS); data is encrypted at rest; access to production systems is restricted, credential-based and logged. Channel-connection credentials stored for a practice are individually encrypted. See the DPA for the security measures we commit to contractually.
11. Changes and contact
Each revision of this policy carries a version date, shown at the top of the page; material changes are re-presented in the app for acceptance. Questions: privacy@smileline.io · SmileLine Technologies Ltd · Company 17408336 · 1 Lyric Square, London, England, W6 0NB.