Data Retention and Deletion Policy template (free, plain-language starter)

Free data retention and deletion policy template for small companies: full text, the controls it supports and the decisions to make. Not legal advice or a certification.

Template · Updated · by the Controlkeep team

In short

How long each kind of record is kept, how deletion requests are handled and how data is destroyed. This free starter covers 3 controls and leaves 9 decisions for you; it is original text, not a standard’s wording, and adopting it is not a certification.

How long each kind of record is kept, how deletion requests are handled and how data is destroyed. Customers and auditors ask for it in privacy regulators and customers asking about deletion; write it before data piles up.

Starter policies are original templates written by Controlkeep. They are a starting point, not legal advice, and adopting them is not a certification or an audit opinion. Adapt every rule to how your company really works, and have a qualified adviser review policies with legal effect (privacy, employment, contracts).

Controls it supports

RefControlStarter framework
TC-CON-02Data is disposed of safelySOC 2-style common criteria starter
IS-PHY-02Equipment and mediaISO 27001-style Annex A starter
IS-ORG-07Legal and contractual requirementsISO 27001-style Annex A starter

Decisions to make before approving

  • [90 days]
  • [30 days]
  • [length required by local tax law, often 5-10 years]
  • [6 years]
  • [6 months]
  • [period required by local law]
  • [12 months]
  • [3 years]
  • [2 years]

The policy text

Purpose

Keeping data longer than needed increases risk and can break privacy law. This policy sets how long [Company] keeps each kind of information and how it is deleted.

Scope

All company and customer information in any system, including backups, exports, email and paper.

Principles

  1. Keep information only as long as there is a business, legal or contractual reason.
  2. When the period ends, delete or anonymise it, including copies.
  3. Legal holds override this schedule: if [Policy Owner] or legal counsel says information must be kept for a dispute or investigation, it is not deleted until the hold is lifted.

Retention schedule

Replace the periods below with those required in the countries where [Company] operates; tax and employment law vary.

InformationKept forThen
Customer account dataWhile the account is active, plus [90 days]Deleted or anonymised
Customer content in the productUntil the customer deletes it or the account closes, plus [30 days]Deleted
Backups[30 days] rollingOverwritten
Invoices and accounting records[length required by local tax law, often 5-10 years]Deleted
ContractsTerm of the contract plus [6 years]Deleted
Job applicant data[6 months] after the role is filled, unless the applicant agrees to longerDeleted
Employee recordsEmployment plus [period required by local law]Deleted
Security and access logs[12 months]Deleted
Support tickets[3 years] after closingDeleted or anonymised
Marketing contactsUntil they unsubscribe or [2 years] without engagementDeleted, keeping only a suppression entry

Deletion requests

  1. Requests from customers or individuals to delete their data are logged and answered within [30 days] (or a shorter legal deadline).
  2. Data is deleted from live systems within that time; copies in backups expire with the backup cycle and are not restored to live systems.
  3. Where data must be kept by law, the requester is told what is kept and why.

How data is destroyed

  1. Digital data is deleted using the system's deletion functions; for devices and storage media, by secure wiping or physical destruction before disposal or reuse.
  2. Paper is cross-cut shredded or placed in secure disposal bins.
  3. Suppliers that hold our data delete it at the end of the contract and confirm in writing where the contract allows.

Responsibilities

System owners make sure their systems follow the schedule, using automatic deletion where available. [Policy Owner] checks compliance at least once a year.

Exceptions

Exceptions to this policy must be requested in writing, approved by [Policy Owner], recorded with a reason and an end date, and reviewed when they expire.

Enforcement

Breaking this policy may lead to loss of access and to disciplinary action in line with employment contracts and local law. Contractors may have their engagement ended.

Review

[Policy Owner] owns this policy and reviews it at least every [Review Period], and after any major incident or change in how [Company] works. Questions go to [Security Contact].

Adopt it

  1. Copy the policy below, or create it from the starter library in Controlkeep, where [Company], [Policy Owner], [Security Contact] and [Review Period] are filled from a form.
  2. Decide the 9 remaining bracketed items so the rules match how you actually work.
  3. Approve it, ask staff to acknowledge it, and link it to the controls it supports so auditors can follow the trail.

Related: collecting audit evidence, policies help, Vendor and Third-Party Management Policy, Information Security Policy.

Questions and answers

How long should we keep data?

As long as there is a reason and no longer. Law, contracts and tax rules set minimums; write each period down as a decision.

Does adopting this data retention and deletion policy make us SOC 2 or ISO 27001 compliant?

No. Policies are one part of a programme; an auditor tests whether you follow them over time. Controlkeep helps you keep the evidence, but it is not a certification or an audit opinion.

Try Controlkeep free

A working control register: owners, evidence, policies and reviews in one place, with exports your auditor can read. The Free plan needs no card; you can export or delete your data any time.