GDPR safeguards and responsibilities

When a clinician determines why and how patient data is processed, the clinician is the controller and Maestra acts as processor for that clinical data. Maestra separately controls its account and service-operation data.

Implemented measures

Sensitive patient, clinical, financial, transcript, biometric speaker, assistant, and retrieval values are encrypted on-device before storage and sync.
The database retains readable account and structural metadata needed for authentication, relationships, scheduling, consent attestation, processing status, and subscriptions.
TLS protects data in transit. Necessary plaintext passes transiently through the relay and contracted processors for transcription, AI, import, retrieval, and PDF tasks.
Version 3 export provides user metadata and patient records. Each patient PDF uses transient relay rendering.
Account deletion removes Maestra-held records and wrapped key material, making server-side ciphertext unavailable to Maestra. User backups and other-device copies remain outside that boundary.
The counsel-reviewed ROPA records executed DPAs and SCC safeguards for applicable transfers, a processing record, incident response, and the designated DPO.

Controller responsibilities

The clinician must establish the applicable Article 6 and Article 9 basis, give required privacy information, complete a DPIA when required, configure and use the service appropriately, respond to data-subject requests, and assess the disclosed processors and transfer safeguards.

Current limitation

Modal transcription and retrieval processing includes a documented transient US transfer under the recorded DPA and SCC arrangement. Do not treat the service as fully region-contained.

For statutory privacy matters, contact Diogo Carpanedo do Carmo at [email protected].