TTL policy and retention periods

Shared by Pavel · Updated 2026-11-12

Memory systems should assign retention by data class, expire ordinary memories automatically, and keep safety, review, or legal records on separate, purpose-limited schedules.

Retention by data class

Data classRetention approach
User-facing memoriesGive each class a defined TTL; consider expiring memories that have not been accessed for a long time. Deletion from the user-facing memory should not itself control separate safety, review, or legal records.
Raw source data and derived memoriesTrack which source records each summary, embedding, or other derived item depends on, so deletion can propagate through copies and replicas. A tombstone can signal that deletion; dependency-aware handling avoids removing a fact that also rests on other sources.
Safety and review recordsUse a distinct retention schedule tied to those purposes; restrict access and keep the records separate from user-facing memory. Some products retain reviewed chats disconnected from the account for up to three years, illustrating that product-specific schedule—not a universal period—is needed.
Legal recordsApply a hold only to defined records; pause their ordinary deletion, log the hold, and end it when it no longer applies.

Deletion and holds

Treat ordinary deletion as a request to remove user-facing memory and its dependent copies, not as an automatic instruction to erase records subject to a separate lawful retention basis or active hold. Make exceptions scoped and auditable, and resume deletion when a hold ends.

The New York Times case illustrates why retention state must be explicit: a May 2025 order required preservation of output logs; on 9 October 2025, the going-forward duty was lifted, while some previously saved data remained preserved.

Choose periods by purpose and obligation

There is no single retention number for every system: SOC 2 does not set one, while HIPAA requires six-year retention for specified policy documentation. Apply the actual rule to the relevant record class rather than extending it to all user-facing memory.