Erasure

Privacy evidence

Privacy evidence you can actually show

When someone asks what happened to a user's data, you need more than a pile of logs. This page covers what operational proof looks like—and what it can't be.

What evidence means here

Evidence is an exportable package built from real product events: what was published, what each person chose, what deletion ran, and whether it succeeded or failed. It answers one question: can you prove what happened?

What counts as proof

Four things, and each has a concrete artifact behind it:

  • What the person was shown—a snapshot of the notice or consent version.
  • What they chose—the receipt, tied to that version.
  • What ran on a deletion—the job, the systems, the outcomes.
  • What failed—honest statuses, not a clean 'all done' fiction.

What evidence is not

An exportable record is not a legal seal, not a compliance score, and not a certification. If someone markets 'court-ready hash-chained evidence' to you, that is theatre. Operational evidence is useful precisely because it is boring and verifiable.

What this does not solve

Evidence v1 is JSON, CSV, or a report—no PDF, no cryptographic seal, no SIEM. It documents Erasure-mediated actions; it is not a substitute for your own audit processes or legal records.

← All solutions

Invite-only beta

Try it on your own stack

Erasure is invite-only in beta. Request an invite and we will walk you through the parts that matter for your product.

See other solutions