Encryption
AES-256 at rest. TLS 1.3 in transit. No exceptions.
- Per-tenant key isolation on GCP KMS
- Encrypted backups with rotation
- Zero plaintext PHI in logs
Every design decision starts from a simple question: would a privacy officer approve this before the feature ships? If not, it doesn't.
AES-256 at rest. TLS 1.3 in transit. No exceptions.
Every access to PHI is written, signed, and surfaced to the practice.
Role-based access and hardware-key MFA, scoped to the minimum necessary.
Multi-region failover with 99.9% uptime target
DDoS protection at the edge, managed by Google
Automated patching on a published cadence
Network segmentation and default-deny firewalls
Daily encrypted backups with tested recovery drills
US-only PHI residency by default
De-identification pipelines for any analytic workload
Retention schedules aligned with each covered entity
Vulnerability scanning at least every six months
Annual third-party penetration testing
Incident response runbooks with named on-call
HIPAA-compliant breach notification workflows
HIPAA
Business Associate Agreement on request. Administrative, physical, and technical safeguards in production.
SOC 2
Type II observation window underway. Audit report targeted for 2026.
GDPR & state laws
Data processing addenda available. CCPA, CPRA, and state-level PHI rules mapped to our controls.
Bring the questions your compliance committee hasn't signed off on yet. Our team includes a clinical privacy lead and a security engineer who ship the platform every day.
Request the security review