liveBook · Manning

Retention policy

As explained in Think Like a CTO

A retention policy specifies how long data must be kept and when or how it may be deleted or archived.

A retention policy sets how long each data bucket is kept, where it is held, and when it may be moved or deleted. Account for operational stores and backups, and confirm that the organization has the right to retain the data. section 8.5.2 section 8.5.2

For each data bucket, decide:

  • How long data stays in each location, and when it ages into longer-term storage. section 8.5.2
  • Which business events trigger deletion, including deletion from backups. section 8.5.2
  • Whether ownership permits retention and whether special compliance requirements apply. section 8.5.2

A client leaves

If a client leaving is a deletion trigger, define whether that event removes the client’s data from both operational stores and backups. section 8.5.2

Include retention policies when mapping company data alongside security and visibility. A clear policy helps make data handling deliberate rather than leaving storage and deletion decisions implicit. section 8.10 section 8.5.2

How Think Like a CTO covers it

How deep it goes
Explains durations across operational stores and backups, storage aging, and deletion triggers without specifying exact periods.
Examples
Uses a client leaving as a business event that may trigger deletion, including from backups.
What it assumes
Assumes data is grouped into buckets and requires distinguishing owned data from data merely stewarded.
What you can do after
Operate data handling by assigning retention periods, aging rules, and deletion triggers to data buckets.
How it connects
Connects retention to data ownership, backups, storage aging, data mapping, visibility, and compliance.

Also explained in

Compare how 10 books explain retention policy →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a CTO. The section links point to the parts of the book it draws on.