Your memory, yours to take with you
Why this matters right now
After China's Interim Measures for the Administration of Generative AI Anthropomorphic Interaction Services took effect in July 2026, a major LLM product deleted all users' conversation history outright, with no migration path offered. Memories people had built up stopped being theirs, without warning — that's not a hypothetical, it already happened.
We chose a different principle
You can export your complete memory graph at any time, and delete it permanently at any time. This is a product commitment we made on our own, not the minimum required by regulation.
Full export — the "memory passport"
One call exports your complete personal knowledge graph: every entity, every relation, every memory's source and timestamp, in an open JSON-LD-style format inspired by two early open standard drafts (MIF/PAM) covering semantic/episodic/procedural memory classification and source provenance. It's not a proprietary format and it's not locked to our product — an independent script can read the exported file and rebuild the full graph structure.
Technical basis:
export/schema.py + docs/export_format.md; tests/test_export.py::test_export_round_trips_without_information_loss verifies the exported file is self-consistent with no information loss.
True delete — not just "out of sight"
Deleting is a physical removal from underlying storage, not a status flag left sitting in a database. You get a before/after record-count comparison, and the deletion itself is recorded in an audit log — the act of deleting is logged, but what was deleted is not.
Technical basis:
export/exporter.py::delete_all(); tests/test_export.py::test_delete_all_is_physically_verifiable_at_the_storage_layer queries the underlying SQLite file directly to confirm the data is actually gone, not just unreachable at the application layer; audit.py logs an unfalsifiable deletion record.
These two capabilities are permanently free
Export and delete aren't premium features behind a paywall — they're product principles, not a lever to monetize. Putting them behind a paywall would be an admission that "memory sovereignty" is just marketing language.
Told straight: the limits of this claim
- No authoritative standards body (W3C, IETF) currently defines a formal standard for AI memory portability — MIF/PAM, which we drew on, are early drafts from individual developers, not yet adopted by major vendors.
- We don't claim to be "GDPR compliant" or "legally mandated" — this is a product principle we chose ahead of where regulation currently stands, not an existing compliance benefit we're claiming credit for.