Part 10 of 12 · 1 min read
Quick notes
- An agent system copies personal data in many places: prompts, tool arguments and results, traces, memory, summaries, embeddings, eval sets and provider logs. Privacy engineering is knowing every copy.
- Order of preference: do not send it, then hide it, then protect it. Minimise the fields, pseudonymise with stable tokens kept in a vault, and redact logs and traces.
- Detection is imperfect. The example's regex rules found about three quarters of the labelled items and missed obfuscated or spelled-out values; a Luhn check is what stopped order numbers being redacted as card numbers.
- Reversible tokens keep the agent useful: the same value always maps to the same token, and detokenisation happens only where a tool genuinely needs the real value.
- Erasure must follow lineage. Deleting the raw record left the summary, embedding and log line behind; following derivation links removed all of them. None of this is legal advice.