Erasure Docs
Product documentation for founders, CTOs, and implementation teams.
Erasure Docs
Product documentation for using Erasure—not an engineering wiki.
Start here
| Page | Purpose |
|---|---|
| Getting Started | What Erasure is and the full first-run path |
| First 30 minutes | Guided evaluation walkthrough |
| Access & setup | Account, organization, project, keys |
Full library
| Section | What you will find |
|---|---|
| Getting Started | Onboarding |
| DPDP | Obligation-shaped framing → product capabilities |
| Core Concepts | Shared vocabulary |
| Guides | Task how-tos |
| API Reference | HTTP surfaces |
| SDKs | Browser consent SDK |
| Webhooks | Outbound events |
| Security | Diligence model |
| Changelog | User-visible history |
Rules of the road
- Derived from shipped product behaviour and internal engineering docs.
- TODO markers mean incomplete public wording—not an invitation to invent APIs.
- Erasure operationalizes privacy work; it does not certify legal compliance.
Open the app: Start free · Sign in