When an agent sends personal data to several services, each may retain it independently. Distributed memory makes retention and erasure harder: data can remain beyond the main application database, and downstream services may repurpose it. section 5.6.3
Operational safeguards include:
- Set retention timelines for agent data and use deletion scripts to purge old caches. section 5.6.3
- Make working memory, tool-call logs, saved outputs, and longer-term memory searchable and purgeable when handling erasure requests. section 5.6.3
- Apply retention requirements to agents receiving the data, unless it is needed for further purposes. section 5.6.3
Appointment data across services
Booking a doctor’s appointment can send health data to calendar, transit, and insurance services. Each may retain it independently, so erasure must reach every service the agent touched. section 5.6.3
Chat transcript retention
A chatbot that stores transcripts for learning might be configured to delete records older than 60 days. section 5.6.3
