VERIFIABLE DELETION
GDPR Article 17 gives every person a right to erasure. Everyone claims deletion; almost nobody can evidence it. Proof-of-Forgetting makes an erasure checkable — pairing a signed destruction record with a non-inclusion proof against a published, signed roster of the subjects your workspace still holds.
WHY A PROMISE ISN'T PROOF
When a customer asks you to erase their data, you delete some rows and reply “done.” But a deletion claim with no evidence is just a promise — unfalsifiable, and worthless to an auditor or a court. Article 17 obliges erasure; it does not, on its own, give you a way to demonstrate that it happened. Proof-of-Forgetting closes that gap with evidence you can hand over.
TWO PAIRED CLAIMS
Neither half is honest on its own. A receipt only records that you said you deleted; an absence proof carries no account of when, or by whose authority. The pair is what turns a deletion claim into something an auditor can check for themselves.
+
Destruction receipt
Positive evidence
A signed, append-only record that the subject's encryption key was destroyed at a specific time, under a named key authority. Evidence that an erasure event happened.
−
Non-inclusion proof
Negative evidence
A proof against a signed, published roster root that the subject is absent from current state — checkable by an auditor against that root, rather than against your delete query.
ENFORCED BY KEY DESTRUCTION, NOT BY A DELETE QUERY
Erasure turns on key destruction, not on a delete query someone has to be trusted to have run. It uses only standard AES-256-GCM and a sorted Merkle tree — no novel cryptography.
01
Per-subject key
Each subject's personal data is encrypted under its own random 256-bit key (AES-256-GCM). The bulky ciphertext may live anywhere — backups, replicas, logs.
02
Tiny wrapped key
Only the small data-encryption key sits in a hardened, retention-tight registry, itself wrapped by a workspace master key that is never destroyed and never appears in a receipt.
03
Crypto-shred
Erasure deletes that one registry row. The random key is gone; the ciphertext — wherever copies live — becomes permanently unreconstructable. Nothing is left to leak.
04
Signed roster
Active subjects form a signed, sorted Merkle roster. One inclusion proof over interval leaves shows whether a subject is, or is no longer, in current state — with leaf count and previous root signed in so a roster can't be silently truncated or rolled back.
WHAT IT PROVES — AND WHAT IT DOESN'T
The pair is precise about its own limits. It evidences that erasure happened and that the subject is gone from the current signed roster; it does not pretend to chase down every copy that ever existed.
Proves
Does not prove
REFERENCES
Proof-of-Forgetting is a compliance-management capability, not a law firm. It does not provide legal advice and does not certify compliance. It evidences erasure for the data your Hub workspace manages; you remain responsible for processing that happens elsewhere. Legal review is recommended.