For personal agents

When a personal agent forgets something, is it gone?

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.

Checking the live service…
Without forgetproof

Pim says it forgot

  • John"Forget Alice." Pim deletes her records and confirms.
  • Pim's storesKeep every byte: the write log, the index tombstones, the page slack, the history table, the backup copy.
  • John's optionsTrust Pim, or open the files with a hex editor.
Deleted in the API. Readable on disk.
With forgetproof

The files say what happened

  • ScanReads the store files directly and names what's still recoverable, store by store, as counts.
  • ForgetRebuilds, vacuums and zeroes until Alice's exact values are in no byte of any store, live records untouched.
  • ReceiptBefore, after, actions, file hashes, signed. Checked in the browser, against a key the signer publishes.
Gone, and John can see that it's gone.
01 / How a forget works

Five steps. The stores' own files are the evidence, so the receipt is about the files.

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.

1 · Pim deletes

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 notes
2 · Scan the files

forgetproof 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.slack
3 · Erase

Collections 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 …
4 · Rescan, then sign

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 · signature
5 · Check

John, 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) → ok

A 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.

02 / The stories

Each story runs live on fresh stores. Run one yourself.

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.

03 / The receipt

Check the latest receipt yourself, in this browser.

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.

No live run yet.

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.

04 / Your agent

The same thing, for the agent you actually run.

MCP server

Any MCP client

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
Desktop app

Memory Hygiene

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
Hosted agents

The forget-me extension

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))
05 / What it is

What this is, and what it isn't.

What this is

  • A working demo of forgetproof 0.2: the scanner and eraser for Chroma, mem0, Qdrant local, LanceDB, SQLite, Postgres/pgvector and text files, the MCP server, the desktop app and the provider SDK, all from one codebase.
  • John and Pim are fictional. Pim is a scripted agent that uses the stores' real APIs, in its own process, the way a real agent does.
  • Pim Cloud is a fictional hosted provider built on the SDK. Its receipts are signed with its own key, published at /.well-known/forgetproof.json under each run.
  • Every check reads the files. "Gone" means the exact values are in no byte of any store file after erasing, and the stores still open with every live record intact.

What it isn't

  • Not an integration with any real hosted agent. Instinct, Hello Haven, Wajo and Muse haven't adopted the extension. The hosted story shows what a provider gets when it does; the "without the extension" story shows what you get until then: an honest UNVERIFIABLE.
  • Not semantic forgetting. A memory that is about Alice without any of her exact values isn't matched. That needs the provider to tag records at write time.
  • Not forensic erasure. On an SSD an overwrite doesn't defeat wear levelling. forgetproof removes data from the logical files, which is what copies, syncs, backups and other programs read; full-disk encryption covers the rest.
  • Not proof of honesty. A signature shows which key signed a receipt and that it hasn't changed, not that the signer did what the receipt says.
  • Not independently tested. One team built the agent, the stores' setup, the eraser and the checks.
06 / Resources

The code, the extension, and the protocols around it.