Security Overview

1. Encryption and key management

All traffic uses TLS 1.2 or above with HSTS enabled. Data at rest is encrypted with AES-256. Object storage holding result PDFs uses per-object encryption keys.

Secrets and signing keys are held in a managed secret store, rotated on a defined schedule and never written to logs or source control.

2. Access control

Human access to production PHI requires a documented business justification, time-boxed approval and break-glass logging. Support staff see order metadata by default, not result values.

API access uses environment-scoped keys with least privilege. Keys can be rotated at any time from the dashboard; revocation takes effect within seconds.

3. Audit logging and monitoring

Every PHI access event is written to an append-only audit log with actor, action, resource and timestamp. Logs are retained for one year and are available to customers on request for their own orders.

Anomaly detection flags unusual access volume, repeated authentication failures and unexpected geography. Alerts route to an on-call engineer 24/7.

4. Infrastructure and resilience

The platform runs on Cloudflare’s edge network with D1 for relational data, R2 for object storage and KV for short-lived state. Backups are taken daily and restore is tested quarterly.

Production changes go through review, automated tests and staged rollout. Database migrations are reversible and applied with a documented runbook.

5. Incident response

Suspected incidents are triaged within 1 hour. Confirmed breaches affecting customer data are notified without undue delay and within 72 hours where GDPR applies, with a written summary of scope, cause and remediation.

6. Responsible disclosure

Report vulnerabilities to [email protected] with reproduction steps. We acknowledge within two business days, keep you updated until resolution, and do not pursue legal action for good-faith research that avoids privacy violations and service disruption.