Kaido — security summary
One page for the practice manager. Print or save as PDF and forward. Full detail: kaidohealth.co/security · kaidohealth.co/privacy
What Kaido is
Criteria-based rehab planning for physiotherapy clinics. The plan engine is deterministic — it compares a patient’s recorded values against fixed, published criteria and reports whether each is met. It proposes and monitors; a named clinician approves every change.
Data residency
UK/EU residency: the database runs in EU-West-2 (London). TLS in transit, encryption at rest.
Third-party AI models
The plan engine itself never calls a model: what a plan contains, and whether a criterion is met, is a deterministic comparison in Kaido’s own code, every time. Voice dictation is transcribed and structured entirely on the clinician’s own device (Apple’s on-device speech recognition, then Apple Intelligence); the audio never leaves the phone and is discarded once transcribed, and there is no code path that could send it elsewhere. Two smaller, separate features — built, not yet switched on in production — would send a patient’s free text to Anthropic’s Claude API: sentiment-scoring a flare note, and drafting a suggested plan adjustment for a clinician to review. Neither writes to a plan directly. Full detail, including current status: kaidohealth.co/security.
Isolation and audit
Every clinic’s data is isolated by the database’s own row-level security — tested against real cross-tenant access attempts, failure mode “see no data,” never “see another clinic’s data.” Every write to a patient's record — the patient, their plans, criteria and readings, notes, appointments, invoices and documents — lands in an append-only audit log that cannot be edited or deleted, including by us, and is exportable in full by the clinic owner.
Patient rights
UK GDPR Article 15 access and Article 17 erasure are built and tested — including redacting a patient’s identifying details out of historical audit-log entries, not just deleting the current record.
Accounts and access
MFA (TOTP), scrypt-hashed passwords, refresh-token rotation with reuse detection, self-service password reset with single-use one-hour links. Patient accounts are invite-only — a single-use link from the clinic, good once. The patient sets their own email and password when they claim it; nobody self-serves onto a clinic’s list.
Regulatory position (MHRA, July 2026 guidance)
Kaido compares numbers to a fixed line; it does not diagnose. It sits in the guidance’s documentation-assistance category — a deterministic comparison, not generated diagnostic “insights” — and nothing is applied to a patient’s plan without a clinician’s explicit approval. The full reasoning, with the guidance linked, is at kaidohealth.co/security.
In progress — stated, not claimed
Formal Data Processing Agreement with each clinic and Cyber Essentials certification (Plus and an independent penetration test to follow). Registered with the ICO as of 5 September 2026. Not ISO 27001 certified and not claiming it. None are claimed early; the full register is at kaidohealth.co/security#compliance.
Sub-processors
The complete current list is maintained at kaidohealth.co/privacy. Clinical audio never reaches any sub-processor at all (it never leaves the device); the transcribed text is held only in Kaido’s own database.
Questions: hello@kaidohealth.co