Legal
Subprocessors
Last updated 7 October 2026
The service providers Kaizo Ltd uses to deliver Kaizo, what each one does for us, and the data each one touches.
Dental practices using Kaizo are the data controllers for their patient and enquiry data. Kaizo Ltd is their data processor and, as permitted under Article 28 of the UK GDPR, uses a small number of service providers (“subprocessors”) to deliver parts of the service. Each subprocessor processes data only for the purpose shown below. We are putting written data processing agreements in place with each of them.
| Provider | What they do for Kaizo | Data involved |
|---|---|---|
| Dentally | Practice management sync, and writing appointments back to the practice's diary | Patient and appointment records. Kaizo writes to the diary only when staff book or move an appointment in Kaizo; a booking an assistant proposes is written only after a member of staff approves it |
| Twilio | SMS, phone calls, call recordings, and live speech for the AI receptionist | Phone numbers, message content, call audio while a call is live, voicemail recordings, and recordings of staff calls until they are transcribed and deleted. For AI receptionist calls, Twilio turns the caller's speech into text and Kaizo's replies into speech |
| Resend | Email delivery | Email addresses and message content |
| Anthropic | AI drafting and summaries, and the AI receptionist's replies on calls | Text the feature needs, which can include health data: consultation transcripts and findings, appointment details, patient names, enquiry and message text, what callers say to the AI receptionist (as text), and transcripts of calls for summaries |
| OpenAI | Transcription and AI features | Audio and operational text |
| Deepgram | Dictation transcription | Audio |
| Stripe | Payment processing for practices that enable payments | Payment amounts, Kaizo payment references, and the practice's name and contact email to set up its Stripe account. Patients enter their card details on Stripe's page, on the practice's own Stripe account; card details never reach Kaizo |
| Meta Platforms | Instagram, Facebook and WhatsApp messaging | Message content and sender profile details |
| Amazon Web Services | Hosting and storage | All service data |
| Vercel | Hosts the web app and passes every request to the Kaizo API; cookie-free traffic measurement | Everything sent between your browser and Kaizo, including patient data, in transit; request logs; page and performance counts with no cookies |
| Clerk | Authentication and session management | Email addresses, sign-in credentials and session identifiers for practice staff, never patient data |
| Cloudflare | Bot protection and rate limiting in front of sign-in, used by Clerk | IP address and request metadata |
| Sentry | Error monitoring | Error reports, including the data in the request that failed, which can include patient data |
Changes to this list
We notify customers before adding or changing subprocessors, so they can review the change and raise any objection. The last updated date above shows when this page last changed.
Questions? Email privacy@kaizosystems.com. See also our Privacy Policy, Terms of Service, Cookie Policy and Data Deletion pages.