Encryption
Data is encrypted in transit (HTTPS) and encrypted at rest by our database provider.
Security and data protection
This page explains how Docyment protects clinical data today. We only list measures that are in place.
Data is encrypted in transit (HTTPS) and encrypted at rest by our database provider.
Access is role-based, so each person sees only what their role allows. Accounts that sign in with email and password must set up two-step verification with an authenticator app before they can access patient data. Google and Apple sign-in rely on the security of your Google or Apple account.
Every document is drafted for review. A clinician reviews and approves each one before it is used. The transcript or notes a document was drafted from are kept with it.
We do not use patient data to train AI models.
Our clinical database is hosted by Supabase. We use Vercel to serve the web application, and OpenAI and AssemblyAI for relevant transcription and document processing.
View our sub-processor listIf you use Record to capture a consultation, you are responsible for telling the patient and obtaining their consent in line with your professional and data protection obligations.
Security issues: security@docyment.com
Privacy questions: privacy@docyment.com