GLOSSARY
Retention
Retention describes which information remains stored and for how long. Conversations, derived summaries, technical logs and backups may follow different periods and processes. Any statement about storage should therefore identify the specific records it covers.
Customer knowledge needs a purpose and a lifetime
The last confirmed negotiating position may be useful during a contract renewal. Keeping every personal remark indefinitely is not necessarily required for that purpose. Larger collections also increase the effort needed for access control, updating and later information requests.
The organisation should decide which information each process needs and who owns retention decisions. Potential legal recordkeeping duties require separate consideration. A useful design distinguishes working data, deliberately stored memory and necessary operational records, with appropriate treatment for each category.
Verify deletion across the processing chain
Acceptance testing should follow a record after expiry or a deletion request. Include caches, exports and involved service providers. Documented periods and exceptions must match the actual configuration. One provider's zero data retention arrangement does not settle the whole question. Evidence should clearly state what was tested, what remains stored for another purpose, and where a deletion delay still applies.