Erasure Docs
Product documentation for founders, CTOs, and implementation teams.
Erasure Docs
Product documentation for using Erasure: what the platform does today, how pieces connect, and how to run consent and deletion operations. This is not an engineering wiki and not legal advice.
What Erasure is
Erasure is a Privacy Operations Platform: one account, one organization model, shared billing. Modules for Accord (consent + SDK), Rights (deletion cases + jobs), Systems (connectors), Data Maps, and Evidence.
Erasure platform
Auth · Orgs · Projects · Billing · Notifications
│
┌──────────────────┼──────────────────┐
▼ ▼ ▼
Accord Rights Evidence
Consent + SDK Cases + jobs Packages on read
│ │
│ Systems + Data Maps
└──────────────────┘| You need… | Start here |
|---|---|
| Notice + durable consent proof | Accord / Consent · SDK |
| Subject deletion with audit trail | Rights / deletion jobs · Systems |
| Know where PII lives | Data Maps |
| Export what happened | Evidence |
| DPDP-shaped framing | DPDP overview |
Start here
| Page | Purpose |
|---|---|
| Getting Started | What Erasure is, mental model, first-run path |
| First 30 minutes | Guided evaluation walkthrough |
| Access & setup | Invite-only access, org, project, keys |
Full library
| Section | What you will find |
|---|---|
| Getting Started | Onboarding and access |
| DPDP | Obligation-shaped map → product capabilities (not certification) |
| Core Concepts | Shared vocabulary |
| Guides | Task how-tos |
| API Reference | HTTP surfaces |
| SDKs | Browser consent SDK @erasurehq/accord |
| Webhooks | Consent webhooks + Rights webhook Systems |
| Security | Auth, RBAC, secrets, connectors |
| Changelog | User-visible history |
Canonical terminology
| Use | Avoid |
|---|---|
| Organization | Tenant (legacy) |
| Project | Workspace (informal UI only) |
| Consent version / publish | "Policy pack" |
| Receipt | Cookie log |
| Rights request / case | Ticket; "DSAR" for the product |
| Systems | Connectors (engineering name for the same thing) |
| Data Maps | Schema inventory (generic) |
| Operational Readiness | Compliance score |
| Evidence | Activity timeline (Activity = events; Evidence = export package) |
| Publishable key | Generic "API key" |
Rules of the road
- Derived from shipped product behaviour (see internal
app_docswhen writing). - TODO markers mean incomplete public wording, not an invitation to invent APIs.
- Erasure operationalizes privacy work; it does not certify legal compliance or replace counsel.
- Do not market ACCESS/CORRECT rights, full GRC, or unconnected systems as if they were live.
Cloud access is invite-only. Request an invite from the marketing site. Invited teams use the link in their email. Self-hosting is documented under Self-hosting.
For the non-technical overview of the same topics, see the solutions guides.