Memory Compliance & Interview Prep
GDPR and privacy compliance for agent memory, plus FDE interview scenarios and deep-dive questions.
Last updated
After this section you can
- Translate GDPR data-subject rights into operations a memory store must support
- Design an erasure that reaches rows, embeddings, derived data, backups and processors, and prove it with a test
- Set retention and write-time controls, and take a memory system through a pre-ship checklist
19
Memory Compliance & Interview Prep
Once an agent remembers people, its memory is a store of personal data. Each right a user has becomes an operation you must be able to run, across every copy, and prove you ran.
Key idea
Design memory so that, for any person, you can find everything held about them, export it, correct it, stop using it and delete it from every copy, including embeddings, summaries and backups. Those five operations must exist before launch; retrofitting them onto a running store is where teams fail.
One erasure request, six places to delete from. It is done when every store has confirmed.