John tells Pim, his personal agent, to forget Alice: her email, her number, everything. Pim deletes her through its memory APIs and says so. But deletes in the stores agents use are logical. Her email is still in Chroma's write log, flagged-but-present in the vector index, and sitting in the free pages of a SQLite file. Anyone with the files can read it. Pim can't tell, and John can't check.
forgetproof reads the files themselves, finds what was deleted but is still there, rewrites the stores so it isn't, and signs a receipt that says what it found before and after. John can check the receipt in his browser. A hosted agent can embed the same thing and publish its key.
Pim runs on John's laptop with four stores: a Chroma collection, a mem0 history, a SQLite notes table and a knowledge-graph file. Every store here is real; nothing is mocked.
John asks. Pim removes Alice through each store's API, the way a well-behaved agent does. The APIs say she's gone.
collection.delete(ids) · DELETE FROM notesforgetproof opens the files read-only and compares what the raw bytes hold with what the store still returns. The difference is residue.
chroma.write_log · hnsw_tombstones · mem0.history_deleted · sqlite.slackCollections are rebuilt from live records, files vacuumed with secure delete, unused index memory zeroed, history rows of deleted memories removed. No copy is kept.
forgetproof forget --subject …The files are scanned again and every exact value is searched for in every byte. The receipt records both scans, the actions, and the SHA-256 of each file, and is signed with Ed25519.
verdict: CLEAN · signatureJohn, or anyone he hands the receipt to, verifies the signature against the published key. The receipt holds counts and hashes: never a value, never a hash of one.
verifyReceipt(receipt) → okA store Pim has open can't be rewritten; the erasure is queued and finishes when Pim restarts. A value that is still part of a live record stays, and the receipt says RESIDUE_REMAINS instead of CLEAN.
Every run builds a new world for John and Pim in a temporary directory, runs the story, checks what the files actually contain, and deletes the world. Below is the latest live run of each story.
This page verifies the signature itself with the dependency-free verifier (WebCrypto when available, pure JavaScript otherwise). It doesn't ask the server whether the receipt is valid.
A valid signature proves that this key signed exactly this receipt and that nothing changed since. It doesn't prove the signer ran forgetproof honestly. For the hosted story the key is the one Pim Cloud publishes at its /.well-known/forgetproof.json; for the others it is this site's own.
For the technically minded: the receipt is canonical JSON (keys sorted, no whitespace, UTF-8), signed with Ed25519; the public key is raw bytes, base64url. Format forgetproof-receipt/0.2, schema in the repository.
Finds the stores Claude Code, mem0, Letta, the memory MCP server and Obsidian keep on your machine. "Forget Alice's number" in conversation ends with a receipt id.
claude mcp add forgetproof -- \ forgetproof mcp --home --owner --allow-fix
macOS and Windows. Every store on your machine, what it still remembers about a value, one-click forget everywhere, receipts, a daily sweep. Nothing leaves the machine.
pip install 'forgetproof[desktop,chroma]' forgetproof desktop
A provider — Instinct, Hello Haven, Wajo, Muse, a Poppy company — mounts the SDK, publishes its key, and its users' "forget me" ends in a receipt their browser can check.
provider = Provider("Pim Cloud", stores, …)
app.mount("/forgetproof", provider.asgi(subject_of))/.well-known/forgetproof.json under each run.The scanner, the eraser, receipts, the MCP server, the desktop app, the SDK, this site and its stories.
What a hosted personal agent publishes and serves: the well-known document, the endpoints, the subject rule, the receipt.
The dependency-free JavaScript this page uses: canonical JSON, Ed25519, file hashes, the well-known check.
The Personal Agent Protocol: how a personal agent works with a company. The extension is written in its style.
When a personal agent stops mid-booking, the next one finds out whether it went through. Same format, same John.
Research on non-membership proofs and memory erasure for AI agents, where forgetproof comes from.