Skip to main content

trust center · updated May 2026

Trust & security.

Pharmacy delivery data is some of the most sensitive on the internet. Everything on this page is real, in production today, and open for audit. What's on the roadmap is listed too — with target dates. No puffery.

how we protect phi

Six pillars covering the HIPAA Security Rule.

Encryption, access control, audit, minimum necessary, availability, breach response.
01

Encryption

Live

Every 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
02

Access control

Live

Role-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
03

Audit logging

Live

Every delivery event is recorded and queryable.

  • Immutable delivery_events log 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
04

Minimum necessary

Live

We only collect what a delivery requires. No more.

  • No diagnosis data, no lab results, no clinical history
  • Driver app shows first name, address, instructions, window — that's it
  • Medication-level data restricted to pharmacy roles
  • Patient phone numbers never shared with third parties for marketing
05

Availability

Live

Multi-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
06

Breach response

Live

Faster 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

Frameworks, attestations, and regulatory regimes — today and on the roadmap.

HIPAA — Business Associate
Live
Signed BAA available. Standard form published at /baa.
HIPAA — Privacy & Security Rules
Live
Administrative, physical, and technical safeguards in place.
SOC 2 Type I
Roadmap
Audit firm engaged via Vanta. Target report: Q3 2026.
SOC 2 Type II
Roadmap
Following Type I. Target report: Q2 2027.
CTIA / TCPA — SMS compliance
Live
Transactional SMS only. Documented opt-in + STOP/HELP flow. See /sms.
PCI DSS
Note
We never store card data. Stripe handles payment processing.
State pharmacy courier registrations
Note
Required in some states for owned-fleet ops; not applicable to BYO-driver customers.

Need something specific (CAIQ, CSA STAR, custom security questionnaire)? Email security@monsi.app.

subprocessors

Who we use to run Monsi.

Anyone that could touch PHI has a signed Business Associate Agreement on file. Everyone is hosted in the US.
Supabase
Postgres database, Auth, Storage, Realtime
US
Signed
Vercel
Application hosting, edge functions
US
Signed (Enterprise)
Twilio
SMS notifications to patients
US
Signed
Resend
Transactional email
US
Signed
Anthropic
AI label recognition (OCR)
US
Signed (Claude for Work)
Stripe
Subscription billing
US
Not required (no PHI)
Mapbox
Mapping, geocoding, tracking UI
US
Not required (no PHI)
OSRM / Router
Route optimization
US / self-hosted
Not required (no PHI)

Material changes to this list are communicated to account administrators with reasonable advance notice. Customers may object in writing to any new subprocessor.

responsible disclosure

Found something? Tell us.

Responsible disclosure welcome. We respond to valid reports within 24 hours and acknowledge researchers publicly (with permission).