Safety

How we protect patient data.

What we store and what we don't, how the record is encrypted, and who can see it.

The recording

Session audio is not stored.

Most clinical AI records the session and keeps the file. We do not, in the room or on a video call. Speech is transcribed in memory, the words carry forward into the record, and the audio is never saved.

No recording archiveThere is no library of session recordings on our systems, so there is none to leak.
Consent before the microphoneCapture starts, in the room or on a call, only after the patient's consent is on record.
The same rule in the journal appEntries spoken aloud keep the words and lose the audio.

Identity

Records are held under a code, not a name.

Identifiers are removed on the way in, including inside free text, where they usually survive.

The filter runs before storage, not after, and the identity behind each code is held encrypted.

the clinician sees their patient

NameAanya Rao
Date of birth12 March 1991
Contactaanya.r@mail.com · +91 98•••
AddressIndiranagar, Bengaluru
Session textthe merger at Acme has me up at 3am

Defense in depth

Four layers around one record.

Four controls, each assuming the one outside it has already failed.

Patient data is never sold, model improvement uses de-identified data only, and there are no advertising trackers in the app.

Clinical safety

Every clinical decision stays with the clinician.

Empaithy highlights patterns for review. It does not diagnose or predict a crisis, and nothing enters the chart without a person approving it.

Read why we designed it that way

Governance

Compliance and agreements.

HIPAA-ready · BAA available GDPR aligned · DPA Encrypted in transit and at rest Audit logs on every read

For the current DPA or BAA, write to support@empaithy.com.

Questions about security?

Write to us and the right person on our team will answer.