Advanced / Minimization worksheet

Privacy Controls

The strongest privacy control is not writing sensitive data in the first place. What you do store must be exportable and removable on request.

Worksheet

Check what you are about to store

Stated preferences and working stylefineThe core use case for memory.
Decisions and constraints for a projectfineDurable and useful to recall.
Direct identifiers (full name, email, phone)avoidReference your own user record instead of copying identifiers in.
Health, financial, or other special-category dataavoidDo not write it unless you have a lawful basis and an approved design.
Passwords, keys, or tokensavoidNever. Rotate anything that has already been written.

Reasonable scope. Preferences and decisions are what memory is for. Keep identifiers in your own database and reference them.

Obligations

Support export and deletion

Whatever you do store, your application must be able to hand it over or remove it on request. Both paths are explicit API calls that you authorize yourself.

# export what is readable in the current scope
bundle = ms.export_all()          # { user_id, memories, generated_at }

# remove specific records after your own authorization check
ms.forget([4821, 4822], reason="user_request")

Authorize the requester in your application before calling either operation.
Scope matters: export returns what the current key and end-user scope can read.
Record who requested it, what was returned or removed, and when.

Copy and run

Copy a working example

bundle = ms.export_all()
print(bundle.user_id, len(bundle.memories), bundle.generated_at)

removed = ms.forget([4821, 4822], reason="user_request")
print("removed", removed)

Was this page helpful?

← Previous

Resilient Fallbacks

PII-safe Memory