Production checklist

Use before production traffic. Complements the DPDP operational checklist. Completing this list does not mean legal compliance.

Access

• Strong passwords (min 12)
• Correct Owner/Admin/Viewer roles
• Publishable keys not committed to git
• Operator sessions treated as sensitive (HttpOnly cookie; still protect against XSS)
• Mailer configured for OTP (and password reset if used)

Consent

• Notice copy reviewed with legal/product owners
• Published version only in production SDK config
• Allowed origins listed for production hosts
• Production apiBaseUrl / origin points at your real Erasure host
• Receipts observed in staging before production cutover
• Optional: consent webhook signature verified

Systems

• Production SQL uses TLS
• Least-privilege DB users (SELECT for discovery/preview + DELETE on mapped tables)
• HTTP/Webhook targets SSRF-safe and intentional
• Health green or consciously accepted degraded
• Secrets only via product rotate paths

Data Maps

• Personal data tables/collections mapped
• Retention tables marked SKIP with intent
• Preview counts reviewed on staging subjects
• Re-discover after schema migrations

Execution

• Worker always on
• Operational Readiness not blocked
• Test COMPLETED case in staging
• Evidence export tested
• Public intake OTP path tested if subjects use it

Ops

• Backups owned for Postgres (Erasure does not replace backup policy)
• Billing entitlements match expected volume
• Security contact path known for disclosure

Next

Security · Self-hosting · FAQ