Trust & Security
Pharmacy delivery data is some of the most sensitive data on the internet. Everything on this page is real, in production today, and open for audit. What's on our roadmap is listed too, with target dates. No puffery.
How we protect PHI
Six pillars covering the HIPAA Security Rule end to end.
Encryption
LiveEvery byte of PHI is encrypted at rest and in transit.
- TLS 1.2+ enforced on every endpoint (HSTS preloaded)
- AES-256 encryption at rest across Postgres, Storage, and backups
- No PHI transmitted over unencrypted channels
- Per-tenant keys for file uploads in the proof-of-delivery bucket
Access control
LiveRole-based access with row-level isolation per tenant.
- Postgres Row-Level Security (RLS) on every tenant-scoped table
- Role-based access: Admin, Dispatcher, Viewer, Pharmacy Staff
- Drivers never see medication names or clinical data
- Short-lived session tokens; mandatory reauth on privileged actions
- Per-device login tracking with remote revoke
Audit logging
LiveEvery delivery event is recorded and queryable.
- Immutable delivery_events log written on every state transition
- Who, what, when, from where — including driver GPS context
- Exports available to Covered Entity on demand
- 7-year retention aligned with pharmacy recordkeeping obligations
Minimum necessary
LiveWe only collect what a delivery requires. No more.
- No diagnosis data, no lab results, no clinical history
- Driver app shows only first name, address, instructions, and window
- Medication-level data restricted to pharmacy roles
- Patient phone numbers never shared with third parties for marketing
Availability
LiveMulti-region, auto-scaled, instrumented.
- Hosted on Vercel + Supabase — SOC 2 and HIPAA-eligible infrastructure
- Automated database backups with point-in-time recovery
- Real-time alerting on error-rate and latency anomalies
- Target uptime 99.9% for production workloads
Breach response
LiveFaster notice than the HIPAA cap requires.
- Suspected Security Incidents reported within 24 hours of discovery
- Confirmed Breaches of Unsecured PHI reported within 10 calendar days
- Documented runbook for containment, eradication, and recovery
- On-call engineer + Privacy Officer rotation
Compliance status
Where we stand on frameworks, attestations, and regulatory regimes — today and on the roadmap.
Need something specific for a procurement review (CAIQ, CSA STAR, custom security questionnaire)? Email security@scriptrun.app.
Subprocessors
These are the services we use to operate ScriptRun. Anyone that could touch PHI has a signed Business Associate Agreement on file. Everyone is hosted in the US.
Material changes to this list are communicated to account administrators with reasonable advance notice. Customers may object in writing to any new subprocessor.
Found something? Tell us.
Responsible disclosure welcome. We respond to valid reports within 24 hours and acknowledge researchers publicly (with permission).