GDPR & data protection — clinic overview
One-page summary for IT, DPO, and clinical leadership meetings.
Levio is designed for GDPR-aligned psychiatric clinical documentation. This document summarises how patient and clinician data are handled, stored, and deleted.
1. EU data storage (Supabase — Frankfurt)
Primary application and database hosting uses Supabase in the EU (Frankfurt region). Health-related records are kept within EU infrastructure subject to our data processing agreements.
2. Deepgram — speech-to-text
Audio is streamed to Deepgram for real-time transcription. Audio is processed transiently for transcription and is not retained by Deepgram for Levio sessions after processing.
3. Claude (Anthropic) — clinical text generation
Transcript text may be sent to Claude in the configured region (EU where available). API traffic is not used to train foundation models. Outputs are decision-support only and must be reviewed by the clinician.
4. Encryption
Sensitive fields use strong encryption at rest (AES-256-GCM) and TLS for data in transit. Access is restricted by authentication and database policies.
5. Isolation & access control
Clinical data is isolated per logical tenant with schema-per-user style separation where implemented, complemented by row-level security (RLS) as defense in depth.
6. Audit trail
Key actions and access patterns are logged to support accountability, security monitoring, and regulatory expectations for health data systems.
7. Deletion & retention
Where a full account deletion is executed, associated personal data is removed in line with our policy, including cascade deletion targets within 30 days where applicable, subject to overriding legal retention duties for medical records.
8. Patient consent before recording
Recording must not start until the clinician confirms that the patient has been informed and consent requirements are met for that consultation.
This page is a high-level summary and does not replace the Privacy Policy, Terms, or your clinic’s own legal assessment.