Trust & Security

Built so patient data never sticks around

ClearPass.health is run by a practising physician. It's designed around one principle: do the documentation work, hold none of the data. Here's exactly how that works.

Clinical text is never stored on our servers

When you generate a note, your text is processed in memory to produce the output, then discarded the moment the response is returned. We never write your clinical text to disk, and we keep no server-side history of your notes.

Your note history stays on your device

Generated notes are saved only in your own browser, on your device. They never reach our servers, and clearing your browser clears them.

Identifiers are auto-redacted before processing

Before any text leaves our backend, a redaction pass strips common identifiers — emails, MRNs, labelled names and dates of birth, and national ID and phone numbers in the formats it recognises (others are caught only when they are labelled). You should still enter only the minimum detail needed; the redactor is a safeguard, not a substitute for your judgment. This applies to typed and dictated text — photos you upload are processed as-is and are not auto-redacted, so remove patient identifiers before uploading.

Consultation audio is never stored on our servers

The optional Transcribe feature turns a consultation into a clinical note, written in English or in the note language you choose. Audio is processed in memory only — never written to disk on our servers — and transcribed by a speech-to-text provider (ElevenLabs, US) that our backend instructs to delete its copy immediately after processing. Transcribing always starts with you confirming the patient's (or guardian's) informed consent, and because voice cannot be auto-redacted, the redaction pass applies to the transcript text before summarisation.

Your notes are never used to train AI

Generation runs on Anthropic's commercial API, which does not train on inputs or outputs and states that it deletes them within 30 days. We don't run ads, we don't sell data, and we use no analytics or advertising trackers. Our pages load a web font from Google and the checkout script from Paddle, which see your IP address as any web server does.

Encrypted, access-controlled, minimal

All traffic is encrypted over HTTPS/TLS. Account data is encrypted at rest, and only the operator has administrative access, behind a password with repeated failed attempts blocked and logged. Because no clinical content is stored, there is little for an incident to expose.

You stay in charge

Everything ClearPass.health produces is a draft for you to review, edit and sign off before it goes into a record or to an insurer. ClearPass.health is a documentation aid — the treating clinician remains responsible for the final content.

The law we answer to. ClearPass.health handles data under the data protection law of the country it is operated from, which the Privacy Policy names. If you practise elsewhere, your own country’s law still applies to you — the Privacy Policy says how. For the full legal detail — subprocessors, retention periods, cross-border safeguards and your data rights — see the documents below.