Editorial policy
How we write and verify this site
This page is a short, plain statement of how the content on this site is produced. If you find something that does not match what the product does, tell us, and we will fix it.
Who writes this
Content is written by the Erasure product and engineering team. We do not attribute posts to invented individuals or inflate credentials we do not have. When a post describes a product mechanism, the description comes from the product itself, not from a script.
What we verify
Product claims on this site are derived from the product as it is shipped, and from the public documentation that describes it. We do not market features that do not exist, and we do not describe planned work as if it were live. If a capability is limited or in beta, we say so.
What we do not do
We do not invent customers, testimonials, metrics, or statistics. Where a number is cited, it comes from a source we can name. Where a product behaviour is described, it is behaviour that exists in the shipped product.
The legal boundary
Erasure is privacy infrastructure, not a law firm. Articles that discuss regulation explain the engineering and operational implications. They are not legal advice and are not a guarantee of compliance. Your obligations depend on your facts, your sector, and your contracts, and should be reviewed with counsel.
Corrections
When the product changes, or when we get something wrong, we update the affected pages rather than leaving stale material up. If you spot an error, use the contact form or email hello@erasurehq.in.