Security & Compliance
Built so PHI never leaks, ever.
We treat patient data as a sacred trust. Every architectural choice starts with the question: what would happen if this data were stolen?
Encryption everywhere
AES-256 at rest. TLS 1.3 in transit. Per-tenant keys with quarterly rotation. Recordings are encrypted client-side before upload whenever the browser supports it.
Role-based access control
Doctors see only their own patients. Admins can manage staff and view audit trails. Roles live in a separate, RLS-protected user_roles table — never embedded in user profiles.
Immutable audit logs
Every authentication, view, edit, export, and deletion is logged with user, timestamp, IP, and resource. Logs are append-only and exportable for compliance review.
Tenant isolation
Row-level security at the database layer means a query for one practice can never return another practice's data — enforced by Postgres, not just app code.
Vendor diligence
All sub-processors are contractually bound by BAAs. We minimize them aggressively — fewer vendors, smaller surface.
Data lifecycle
Configurable retention. One-click PHI export and deletion. We don't retain decrypted backups beyond active service requirements.
Compliance status
- HIPAA technical safeguards
- Aligned
- Business Associate Agreement (BAA)
- Available on request
- SOC 2 Type II
- In progress
- Data residency
- United States
- Penetration testing
- Annual, third-party
- Sub-processor list
- Published, BAA-bound
Need our security packet for vendor review? Email security@medscribe.ai.