When someone asks to be forgotten, Lethe Delete removes them from your vector store, RAG index, and caches — verifies the embeddings are actually gone — and hands you a signed certificate proving it. Runs inside your own infrastructure.
01 The problem
GDPR Article 17 covers personal data in AI memory — including embeddings. Delete the database row and the vector is still there, still searchable, still returning the person you were told to forget. And no vector database can prove a deletion happened.
If you sell AI to enterprises, you’ve hit the sharper version: a customer’s security review asks “prove you can delete a user’s data from your AI,” and you can’t. That’s a stalled deal, not an abstract fine.
02 We measured it
A reproducible, neutral benchmark of whether AI-memory systems can actually forget a person — run against each store’s native API, not ours.
| System | Deletes | Identifies a subject | Proves deletion |
|---|---|---|---|
| pgvector | yes | yes | no |
| Qdrant | yes | yes | no |
| Chroma | yes | yes | no |
| Pinecone | yes | yes | no |
Provability is the universal gap — exactly what the signed certificate fills. Read the benchmark → “Can Your AI Forget?”
03 The artifact
Tag personal data as it’s written. On request, delete the subject across your stores, verify the records and embeddings are gone, and emit a certificate showing exactly what was deleted, when, and confirmed absent — the thing you paste into a security questionnaire or hand a regulator. Scoped honestly: “deleted across these layers and verified absent,” never “perfectly erased everywhere.”
Independently verify a certificate in your browser →04 New · for AI agents
Lethe Delete ships an MCP server, so autonomous agents handle a deletion request end-to-end and verify the proof machine-to-machine. No human in the loop; the destructive step is guarded instead.
A two-step confirm token binds the exact blast radius the agent previewed — a hallucinated id or mid-flight change can’t delete the wrong person.
A second agent runs in verify-only mode with no database and confirms the certificate against the operator’s pinned key. One machine proves, another checks.
05 Integration
Wrap your vector store and declare which field names the data subject.
Every write tags itself for deletion — nothing to remember later.
Call forget(subject) on request; get the certificate back.
Connectors for Postgres/pgvector, Pinecone, and LangChain / LlamaIndex today.