Blog
Written by the Erasure product and engineering team
Public product docs live at /docs
Erasure now ships product documentation on the marketing site. What it covers, and what it is not.
We published product documentation for Erasure at /docs on this site.
What this is
Documentation for founders, CTOs, and implementation teams who need to:
- understand what Erasure is
- get through first setup
- run consent, systems, deletion, and evidence workflows
- look up API surfaces and security posture
The docs are built with Fumadocs and live on the same origin as the marketing site (/docs). There is no separate docs. subdomain for this content.
What this is not
- Not a dump of internal engineering notes
- Not legal advice or a DPDP compliance certificate
- Not a substitute for the live product (invite-only beta via erasurehq.in)
Internal engineering documentation remains the product's app_docs/ source of truth. Public pages translate shipped behaviour. Where something is incomplete, public docs use TODO markers rather than inventing APIs or features.
Where to start
Conversion path (unchanged)
Marketing still deep-links into the product:
- Request invite → closed beta form (no public signup)
No waitlist. No marketing-site auth.
About this post
Written by the Erasure product and engineering team
Published 15 July 2026
This article is grounded in Erasure's product documentation and explains engineering and operational implications. Where it discusses regulation, it is not legal advice. See our editorial policy.