Most healthcare AI tools rely on standard TLS encryption. We go further with AES-256-GCM envelope encryption, ECDH key exchange, and enforcement mode that rejects plaintext PHI at the server level. Your patients trust you with their health. You can trust us with their data.
AES-256-GCM
At rest; TLS in transit
BAA
On every plan, including the trial
A Business Associate Agreement on every plan, including the trial, accepted at sign-up, with administrative, physical and technical safeguards for PHI
SOC 2 Type I readiness is in progress and the Type II observation window is planned; we do not have a SOC 2 report yet. Infrastructure is hosted on providers with their own SOC 2 reports (OVH US and Google Cloud).
How we handle requests from EU data subjects is set out in our Privacy Policy
California privacy rights are set out in our Privacy Policy
Patient data is protected by five independent encryption layers on our enforced channels. CDN, edge infrastructure, and reverse proxies do not see plaintext PHI on those channels.
PHI in API requests is encrypted on your device before it is sent, so network intermediaries see only ciphertext. Our servers decrypt it in memory to process it.
Your notes and patient information are encrypted before they ever leave your device.
PHI in API responses is envelope-encrypted on the server before delivery. Intermediary systems see only ciphertext.
Generated notes are encrypted before being sent back to you.
Real-time transcription and rounding data is encrypted per-message over WebSocket connections, for clients on an up-to-date app version.
Live transcription during patient encounters is encrypted in real time on a current app version.
Audio is encrypted on your device before upload, then deleted as described in 'How long recordings are kept'.
Encounter audio is encrypted on your device before it is sent.
Individual PHI fields are encrypted at rest with organization-scoped data encryption keys (DEKs), wrapped by a master key encryption key (KEK) in Google Cloud KMS.
Each data field is independently encrypted in the database.
Encryption keys are negotiated using Elliptic Curve Diffie-Hellman (ECDH) on the P-256 curve. Plaintext keys are never transmitted between client and server. Each session derives fresh ephemeral keys, providing forward secrecy.
Enforcement mode is active on our covered PHI endpoints — API requests, API responses, and WebSocket connections from an up-to-date app. The server rejects a request or response on those endpoints that is not properly encrypted. This is not optional or configurable. Since October 2026, an app that does not encrypt live audio is refused. Two features still send data protected by TLS only, which Cloudflare can read in transit: calculator inputs and practice roster CSV uploads.
Because encryption happens at the application layer (above TLS), CDN nodes, edge proxies, load balancers, and reverse proxies only ever see ciphertext. A compromise of any intermediary infrastructure exposes no readable patient data on those channels.
Automated health checks run every 15 minutes to verify encryption integrity across all layers. Telemetry tracks encryption match rates, key exchange success, and enforcement compliance. Any anomaly triggers immediate alerts.
On our enforced channels, your patient data is protected by 5 independent layers of encryption. Keys are exchanged by ECDH, so plaintext keys are never transmitted, our servers reject unencrypted patient data on those channels, and CDN providers and network intermediaries see only ciphertext. Our servers decrypt PHI in memory to write your note, and stored data is encrypted at rest.
Defense-in-depth security protecting your practice and patients at every level
PHI is encrypted using AES-256-GCM envelope encryption with ECDH P-256 key exchange. Five independent encryption layers cover API requests, responses, WebSocket messages, audio streams, and field-level storage. Enforcement mode rejects plaintext PHI on covered request, response, and WebSocket paths.
A Business Associate Agreement (BAA) is included on every plan, including the trial. PHI is encrypted in transit and at rest, and access to it through the app is logged.
Data stored in the United States: application servers and database at OVH US and Firestore on Google Cloud (both with their own SOC 2 reports), encrypted backups at Backblaze B2, and a disaster-recovery standby on Scribeable-operated US servers. Every one is under a signed BAA or operated by Scribeable.
On our enforced channels, PHI is encrypted on your device with keys exchanged via ECDH (Elliptic Curve Diffie-Hellman), so plaintext keys are never transmitted and CDN and edge infrastructure see only ciphertext. Our servers decrypt PHI in memory to generate your note.
Complete audit logging of all data access and modifications. Immutable logs stored securely for compliance and forensic analysis.
Uptime, evidence freshness, policy reviews and subprocessors are published on our live Trust page. An independent SOC 2 audit is planned; we do not have a SOC 2 report yet.
Data Handling
Transparent data practices with patient privacy at the core
The note and transcript are kept, encrypted. This is how long the audio is kept.
Single-visit audio from the web is processed in memory on our servers and not stored there. Your browser keeps a backup copy on your computer for up to 2 hours so an interrupted upload can be retried. Live and finished recordings are encrypted on your device before upload.
A single-visit recording from the iOS app is encrypted on your iPhone before upload and processed in memory on our servers. The recording stays on your iPhone until you delete the note or sign out.
Audio is stored on our servers, encrypted, until it is transcribed, and is deleted within 24 hours after transcription. Audio that fails to transcribe is deleted after 7 days. If a technical fault stops us reading a recording, we hold it, encrypted, until we can retry it or destroy it. Fixing the fault does not involve listening to it.
There is no option to save a recording. When you close your account, recordings on our servers are destroyed at once. Section 3.13 of the BAA sets out audio retention. The note and transcript are kept, encrypted; the audio is not.
Security Partners
These six vendors are authorized to process PHI, each under a Business Associate Agreement. OpenAI currently receives none. Cloudflare carries our network traffic and SendGrid sends visit-summary emails without a BAA; see the Subprocessor List.
Provides AI note generation under a Business Associate Agreement. Anthropic may retain requests and outputs under its terms; we have no zero-retention arrangement.
Provides medical speech-to-text under a Business Associate Agreement. We opt out of Deepgram's model improvement program on every request.
Approved under a Business Associate Agreement, with modified retention, for extracting orders and classifying patient status. As of October 28, 2026, both tasks run on Anthropic Claude and no patient data is sent to OpenAI.
Provides Firestore and Cloud Storage for patient data and Cloud KMS encryption key management under Google's Business Associate Addendum in US data centers, plus Firebase Authentication for clinician sign-in.
Hosts the production application servers for HIPAA-scoped infrastructure in Vint Hill, Virginia, with a signed Business Associate Agreement.
Provides encrypted backup storage under a Business Associate Agreement.
Cloudflare does not store PHI; calculator inputs and practice roster CSV uploads reach it protected by TLS only. Stripe and Apple never touch PHI.
See the full list, including certifications and data locations, at /legal/subprocessors.
Documentation
Download our compliance documents and review our policies
Security FAQ
Answers to frequently asked security and compliance questions
Scribeable is built for HIPAA-covered practices. A Business Associate Agreement (BAA) is included on every plan, including the trial, at no extra cost, PHI is encrypted in transit and at rest, and access to it through the app is logged. HIPAA compliance is shared: your practice's own safeguards count too.
In the United States. Our application servers and PostgreSQL database run at OVH US in Vint Hill, Virginia; Firestore and encryption keys (Cloud KMS) are on Google Cloud; encrypted backups go to Backblaze B2; and a disaster-recovery standby runs on Scribeable-operated servers in the US. Every vendor that stores or processes PHI for us is under a BAA, except as the Subprocessor List states (Cloudflare carries network traffic and SendGrid sends visit-summary emails without one). Protected health information is encrypted with AES-256-GCM before it is stored, and all data is encrypted in transit (TLS), with 5 layers of envelope encryption on our enforced channels.
Yes, in limited cases. Our administrators hold the credentials for our servers and encryption keys, so they can technically decrypt patient data. Interactive access by our administrators to production servers requires a hardware security key. Our support tools show counts, status codes and pseudonymised IDs, not note content, and each use of them is logged. We open a specific patient record only to resolve a problem you report or when the law requires it. Rounding audio that we hold after a technical fault is retried or destroyed; fixing the fault does not involve listening to it. On the network, PHI is encrypted on your device on our enforced channels, so CDN and network intermediaries see only ciphertext.
Most healthcare AI tools rely on standard TLS (transport-layer) encryption, which protects data in transit but leaves it readable at every server and CDN node in the chain. Scribeable adds application-layer envelope encryption on top of TLS: on our enforced channels, data is encrypted on your device, stays encrypted across every intermediary, and is only decrypted at the final destination. Enforcement mode makes this a server-enforced technical control on those channels, not a policy.
We have comprehensive incident response procedures including immediate containment, forensic analysis, and affected-party notification in line with HIPAA breach-notification requirements.
We do not use your patient data to train AI models, and our requests to Deepgram opt out of its model improvement program.
Notes and transcripts persist in encrypted form, and you can delete them at any time. Audio is deleted as described under 'What happens to the audio recording'. When you close your account, voice recordings, rounding data and cached EHR data are destroyed at once. For your patient records, you choose: on an individual account you can have them destroyed from our live systems on or after the 30th day after closure (backup copies expire within 28 days after that, and we email you a certificate), or we keep them, and you can contact support for a copy or to have them destroyed (Privacy Policy §5.2). If your account belongs to a practice, the practice keeps the records.
iPhone: the recording stays on your iPhone until you delete the note or sign out. Web: your browser keeps a backup copy on your computer for up to 2 hours so an interrupted upload can be retried. Our servers process single-visit audio in memory and do not store it. Rounding Mode: audio is stored on our servers, encrypted, until it is transcribed, and is deleted within 24 hours after transcription. Audio that fails to transcribe is deleted after 7 days. If a technical fault stops us reading a recording, we hold it, encrypted, until we can retry it or destroy it. Fixing the fault does not involve listening to it. There is no option to save a recording. When you close your account, recordings on our servers are destroyed at once.