PolicyForge
All posts
5 min

How to write a data retention policy

A data retention policy defines how long you keep data and when you delete it. Here is what to include — retention periods, deletion, GDPR — with a free template.

Why keeping data forever is a liability

Every record you keep is data you must protect — and, under GDPR, data you must justify keeping. A data retention policy defines how long each category of data is kept and how it is securely deleted, reducing both your breach exposure and your compliance risk.

What to include

  1. Scope — data categories covered (customer, HR, financial, logs, backups).
  2. Retention periods — how long each category is kept, tied to legal, contractual and business needs.
  3. Legal basis — the obligation or justification behind each period (GDPR storage-limitation principle).
  4. Deletion — secure, documented deletion when the period ends, including backups.
  5. Holds — how legal holds suspend deletion when required.
  6. Responsibilities — who owns retention decisions and enforcement.
  7. Review — periodic update as obligations change.

Common mistakes

  • "Keep everything forever," which maximises breach impact and breaches GDPR.
  • Retention periods with no legal basis recorded.
  • Forgetting backups, where data lives on after deletion from production.

Framework alignment

Supports ISO 27001:2022 Annex A 5.33 (protection of records) and 8.10 (information deletion), the SOC 2 criteria, and the GDPR storage-limitation principle.

Generate it in minutes

See a sample data retention policy or generate yours free.