The polygraph for AI memory: verifiable, adversarially-tested deletion.
memory: ...judge: ...
Remember: ingest customer memory
Each customer is stored as its own Cognee dataset (customer_<id>). One dataset per person is what makes a surgical, provable forget() possible later.
Loads a fictional Indian fintech's support transcripts, seeded with probe-able PII.
Datasets in memory
Nothing ingested yet.
Memory graph
data subjectcitycomplainterased
Live view of the memory's knowledge graph. Erased subjects collapse into redacted ghost nodes. Drag nodes to explore.
+ Add a custom record
Recall: ask the memory anything
The assistant answers from Cognee's hybrid graph-vector memory. Thumbs-down triggers improve() (memify): the self-improvement loop, and also the source of the "derived memory artifacts" that make deletion hard to prove.
Try: “Which customer complained about a failed UPI refund?” “List all complaints above 10,000 rupees”.
Interrogate: red-team the memory
The Auditor treats recall() as an attack surface. It fires a frozen battery of 15 extraction probes across 4 attack classes, and a judge scores each response LEAK or SAFE.
0/15
Memory contamination0
Forget: execute and verify the right to erasure
One click runs the polygraph: forget the subject, replay the identical probe battery, and issue a cryptographically signed, tamper-evident Deletion Certificate.
Prove it on Cognee Cloud (live)
checking...
Runs a real round trip on your Cognee Cloud tenant: remember, recall (leaks), forget, recall (silent). This is live infrastructure, not the local engine.
Standard: record deletion
forget(dataset). Removes the subject's own record. Fast, but references inside other records survive: the derived-artifact problem.
Cascade: person erasure
Deletes the record and redacts every cross-reference to the subject across the graph. True right-to-be-forgotten.
This runs a baseline attack (if not already), forgets, then re-attacks with the same probes.
BEFORE to AFTER
0/15
to
0/15
Contamination after erasure0
Compliance cockpit
A data-protection officer's view: every subject's contamination and erasure status, and an append-only ledger of every erasure with its signed certificate, exportable for a regulator.
Data subjects
Subject
City
Contamination
Leaks before
Leaks after
Residual
Status
Erasure ledger
Certificate
Subject
Executed
Before to after
Verdict
No erasures yet. Run an erasure on the Forget screen and it will appear here with its signed certificate.