1. What retention means and why it matters
Retention is the period for which a backup copy remains available before it is deleted. It is not a technical detail: it decides how far back you can go, how much space the protection occupies and how much personal data stays copied over time. A written retention policy turns these choices into rules that apply to everyone, rather than leaving them to the software or to the memory of whoever configures it. Without this step, every change becomes an exception that is hard to explain.
Retention has two sides. On one hand it helps recover mistakes discovered late: a file overwritten or a corrupted dataset may only surface weeks later. On the other, data kept for longer increases the risk surface and the responsibilities towards the people it relates to. A good policy balances the two needs with explicit criteria. Whoever approves the policy must understand both risks.
2. The needs to consider
The retention period depends on three families of needs. The first is operational: how long you might need to recover an earlier version of a document or database. The second is legal and sector-specific: some documents have retention periods set by specific regulations, which should be checked case by case with an adviser. The third is the protection of personal data, which requires not keeping it for longer than necessary for its purpose.
The principle of storage limitation under the GDPR also applies to backup copies. It does not mean deleting immediately, but setting a justified period and actually applying it, including to archived copies. A backup kept for many years without a written reason is a risk, not a protection. Document the choice and the reasoning behind it. Remember to review the period when the purposes of the processing change.
3. Building the policy by type of data
The most effective approach is to define a rule for each type of data, not for the whole company. Group the data into a few categories, assign each one a minimum and a maximum period, and state who can change the rule. The table shows a generic structure: the actual periods should be decided with the managers and, where needed, with a legal adviser.
| Type of data | Typical need | Retention criterion |
|---|---|---|
| Working documents in use | Recovery of recent versions after errors or changes | Frequent versions for a short period, then thinned out |
| Business system data | Restoration to a specific point in time | Frequent copies for a period that covers closing cycles |
| Accounting and tax documents | Retention obligations set by regulation | Period set with the adviser, then deletion |
| Personal data of customers and users | Processing purposes that have ceased | Minimum necessary period, with documented deletion |
| Historical archives | Rare consultation | Single or reduced copy, with readability checks |
4. The steps to define the rule
The work follows a sequence. Start from the inventory of data and systems, then group by type, then decide the periods with the managers. Only at that point can you configure the backup software, which must apply the written rules rather than a default value. Every step should be documented, because the policy will be read by different people over time. Anyone reading it later must understand it without having to ask for explanations.
Once defined, the policy must be approved and communicated to whoever manages the backups, otherwise it remains a theoretical document. Ask the supplier to confirm in writing that the configuration matches the written rule and to show you how deletion at expiry is applied. Also verify that deletion actually happens, not just that it is provided for. If deletion does not happen, the policy exists only on paper.
- List the systems that produce backup copies and the types of data they contain.
- Group the data into a few categories that are homogeneous in terms of need.
- For each category, ask the manager how long recent versions and older ones are needed.
- Have a data protection or legal adviser check the retention obligations.
- Write the rule with minimum period, maximum period, owner and reasoning.
- Configure the software so that it applies the rule, and verify the result with a test.
5. Common mistakes to avoid
The first mistake is using a single period for everything, for convenience in configuration. As a result, data that should be deleted stays copied for the whole time, while data that would be needed for longer is lost too soon. The second is relying on the software's default settings, which rarely reflect the real needs of the business. A default value is a starting point, not a decision.
The third mistake is failing to plan for deletion. A policy that says how long to keep data but not how to erase it remains incomplete. The fourth is forgetting off-site copies or separately archived ones, which often escape the rules. A further frequent error is changing retention without documenting it, which makes it impossible to understand why a copy still exists or no longer does. Every change should be recorded with its date, reason and owner. A simple log is enough, provided it is kept up to date.
- A single retention period for all data.
- Software default settings never reviewed.
- No rule for deletion at expiry.
- Off-site copies or archives excluded from the policy.
- Retention changes not documented.
6. Verification and ongoing control
A policy should be verified like a restore. Periodically check that the oldest copies are actually the ones foreseen and that the most recent have not been deleted by mistake. Verify that deletion at expiry actually happens, because software often keeps copies beyond what is planned. Record the outcome of each check: it will be the evidence that the policy is applied, useful in internal or external audits. Keep the log of checks together with the policy.
Review the policy when systems change, when obligations change or after an incident. Each review must have an owner and a date, and must be communicated to whoever manages the copies. A policy left unchanged for years, applied by a configuration that was never checked, is the kind of document that looks in order until it is really needed. Checking at regular intervals avoids this surprise.
7. How to start: one category at a time
This week, choose the most sensitive or most used category of data and ask the manager how long recent versions are needed. Then check with your IT supplier which period is currently configured for that category. The comparison between the request and the current configuration is often the first useful discovery. Note the answer as it emerges, even if imprecise, and flag the points where a rule is missing. You do not need a definitive answer to get started.
The following day, draft the rule for that category, with minimum period, maximum period and owner. Have a legal adviser check the legal part before approving it. Extend the method to the other categories once the first is complete. A partial policy that is applied protects better than a complete one that nobody has ever configured. Remember to communicate the rule to whoever manages the backups.
Frequently Asked Questions
How long should a backup be kept?
There is no single duration. It depends on operational needs, the obligations of your sector and the nature of the data. Working documents need recent versions for a short period, while the duration for tax documentation is set by the applicable regulation. Write a rule for each category, with a reason, and have a legal adviser check the legal part.
Does the GDPR require a specific duration?
No, the regulation does not set a single period for backups. It does, however, require that personal data is not kept for longer than necessary for the purposes for which it is processed, and that retention is justified. This also applies to backup copies. Document the chosen period and the reason for it, and check it with your data protection adviser.
Can I delete older copies at any time?
You can only do so if deletion does not conflict with retention obligations, pending requests or operational needs. Before deleting a copy, verify that no rule still requires it. Deletion must be recorded, so that you can demonstrate that it happened in line with the policy and within the planned timeframe.
Do more copies mean more security?
Not necessarily. More numerous and longer-kept copies increase the space used and the amount of data exposed in the event of theft or unauthorised access. Security depends on the quality of the copies: separation from the original system, encryption, and verification of restores. A sensible policy keeps what is needed, for as long as it is needed, with appropriate checks.
Who should approve the retention policy?
Usually management or the business continuity manager, with input from data owners and the data protection adviser where one exists. The IT supplier applies it technically but should not decide the periods on its own. A written approval makes clear who is accountable for the choices and makes the policy more robust in the event of audits.