Under the UK GDPR, organisations should not keep personal data for longer than necessary. Retention periods should be based on the purpose of the processing, legal requirements, business need, and the accountability principle.
Under the UK GDPR, organisations should only keep personal data for as long as they need it for a clear purpose. There is no single retention period that applies to every organisation or every record. The right period depends on why the data is held, legal or regulatory requirements, operational need, and whether keeping it can still be justified under the accountability principle.
Should be
Limited to what is necessary for a clear purpose
Should involve
Documented retention periods and review points
Should allow
Secure deletion, anonymisation, or archive decisions
The UK GDPR does not usually tell organisations exactly how many months or years to keep each type of record. Instead, organisations need to decide and document retention periods that are reasonable for the purpose. Keeping data indefinitely because it might be useful one day is unlikely to be enough.
A retention period should connect back to the reason the data was collected or used. Customer records, staff records, marketing lists, and complaint files may all need different periods.
A retention schedule helps show that the organisation has thought about necessity, legal duties, limitation periods, operational need, and privacy risk.
Retention periods should be reviewed when systems, services, laws, or business processes change, especially where large volumes of personal data are involved.
Retention decisions also connect to transparency, because people should usually be told how long their data will be kept or how that period will be decided.
A sensible retention period is usually based on a mixture of legal requirements, business need, limitation periods, sector expectations, and the risk to individuals. The key is to make a reasoned decision rather than keeping everything by default.
Some records need to be kept for a minimum period because of tax, employment, financial, contractual, or regulatory requirements. Those duties should be identified before data is deleted.
Organisations may need data to deliver services, manage accounts, handle disputes, evidence decisions, support audits, or maintain operational records.
If data may be needed to bring or defend a legal claim, the relevant limitation period can influence how long certain records are retained.
The more sensitive, detailed, or high-risk the data is, the stronger the reason should be for keeping it and the more carefully access should be controlled.
A retention period is only useful if people inside the organisation can actually follow it. That usually means having a retention schedule, clear ownership, review dates, and a process for secure deletion or anonymisation.
A retention schedule should identify the record categories an organisation holds, why it holds them, how long each category is needed, and what should happen at the end of that period.
At the end of a retention period, data should usually be deleted, anonymised, or moved into a restricted archive if there is a clear reason to preserve it.
For marketing records, organisations may need to keep limited evidence of consent, objections, or communication preferences so they can explain past decisions and respect future opt-outs. Keep only what is needed for that purpose, and consider whether a minimal suppression record is needed to prevent unwanted contact. PECR may also apply to the marketing activity itself; see Direct Marketing and GDPR for the wider overlap.
Common retention problems include keeping information “just in case”, applying one period to every record, overlooking copies in different systems, and failing to review whether the original purpose still applies. Organisations should also check whether a law or a live claim justifies retaining particular records.
Keeping personal data indefinitely “just in case” is unlikely to be justified. Set a period linked to the purpose and any relevant legal requirement, then review the data and delete or anonymise it when it is no longer needed.
Data is often copied into spreadsheets, inboxes, downloads, shared folders, and old systems. Those copies still count and should be covered by retention controls.
A retention schedule is a working control, not a document to set and forget. Assign responsibility for reviewing it, check that it reflects current purposes and legal duties, and make sure deletion or anonymisation happens across the systems and copies the organisation actually uses.
Retention periods depend on the purpose and type of record. Legal duties, business need, possible legal claims, relevant sector guidance, and the privacy impact can all inform the decision. A commonly used period is a starting point, not an automatic rule for every organisation.
Keep customer records for as long as they are needed to manage the relationship and meet relevant legal duties. When the relationship ends, review which records still have a clear purpose, such as accounting records or evidence needed for a claim, and delete or anonymise the rest.
Recruitment data should not normally be kept indefinitely. Organisations should decide how long to keep unsuccessful applicant data and explain this clearly.
Review marketing records regularly. When someone objects or unsubscribes, stop the relevant marketing and retain only the minimal information needed to respect that preference and prevent future unwanted contact.
Keep complaint and dispute records while they are needed to investigate and resolve the matter, and for any further period that can be justified for follow-up or possible legal claims. Restrict access and delete or anonymise the records when that need ends.
If personal data is kept longer than needed, more information remains exposed to loss, misuse, unauthorised access, and data breaches. It also increases the amount an organisation may need to locate and assess if someone makes a data rights request. Good retention reduces unnecessary data and supports stronger governance.
This article is based on ICO guidance on storage limitation, retention, deletion, and accountability under the UK GDPR, together with the UK GDPR provisions on storage limitation. These generally require identifiable personal data not to be kept longer than necessary for its purpose, subject to limited provisions for qualifying archiving, research, or statistical purposes with appropriate safeguards. This article also connects to wider duties around accountability, privacy notices, lawful basis, and individual rights such as subject access requests.
Use the glossary for key terms, or download the checklist if you want a practical starting point for reviewing retention periods, deletion routines, privacy notice wording, old records, supplier files, marketing data, and internal retention schedules.
We use cookies and similar technologies to make our website work and to provide optional features such as live chat.
Some cookies are strictly necessary for the website to function. Optional cookies support tools such as live chat and will only be used if you choose to allow them.
We also use privacy-friendly, cookieless website analytics to understand aggregated website usage. This does not use cookies or track you across websites.
You can choose to accept all cookies, reject non-essential cookies, or manage your preferences.