Security built for healthcare data
Every architectural decision in PatientLetterHub was made with PHI in mind. Here's exactly how we protect your patient data.
Core security features
Encryption
All files encrypted in transit (TLS 1.2+) and at rest (AES-256)
Access Controls
Role-based permissions ensure only authorized users access PHI
Audit Logging
Every action logged with timestamp and user for compliance reporting
Infrastructure
U.S.-based servers on Microsoft Azure and Vercel — both SOC 2 certified platforms
PHI never touches our web servers
Most web applications route file uploads through the application server — which means PHI passes through infrastructure that isn't designed for it. We built a different approach.
Browser requests upload URL
Our server generates a time-limited Azure Blob SAS URL
File uploads directly to Azure
PHI goes browser → Azure Blob Storage. Our servers never see the file contents.
Secure private container
Files stored in a private Azure container. Access requires a fresh signed URL every time.
HIPAA compliance
BAA required before PHI moves
No PHI upload is permitted until a signed Business Associate Agreement is on file. No workarounds, no opt-outs.
PHI attestation on every job
Users must explicitly attest that uploaded files contain PHI before the system accepts them.
Role-based access control
Practice admins, staff, and external auditors have different permission levels. PHI access is scoped to the account that owns the job.
Full audit trail
Every action — upload, approval, proof view, status change — is logged with timestamp, user ID, and IP address.
Tenant isolation
Every job, file, and record is scoped to a practice. Cross-account data access is architecturally prevented.
Signed proof links
Proof PDFs are served via HMAC-signed time-limited URLs. Direct file access without a valid signature is rejected.
Business Associate Agreement
PatientLetterHub qualifies as a Business Associate under HIPAA. We provide a standard BAA to all covered entities using our platform. The BAA is required before any PHI is uploaded — it's part of the onboarding workflow, not an afterthought.
Infrastructure
PatientLetterHub runs on enterprise-grade infrastructure from providers that are independently audited and certified.
Microsoft Azure
Database and file storage. Azure is SOC 2 Type II certified and HIPAA eligible.
Vercel
Application hosting. Vercel is SOC 2 Type II certified. All compute in the United States.
Clerk
Authentication and session management. Clerk is SOC 2 Type II certified.
PatientLetterHub itself is not currently SOC 2 certified. SOC 2 audit is on our roadmap as the platform scales.