There is no universal GDPR retention period

The storage-limitation principle requires identifiable information to be kept no longer than necessary for its purposes. UK GDPR does not provide a single period for customer records, CCTV or employee files. Other laws, regulatory obligations and the circumstances may influence how long particular records are needed.

Avoid copying a blanket number from another business. Start with the record’s purpose and identify any relevant external requirement. Distinguish a legally required minimum from a business preference or a period chosen to manage potential claims. Those are different reasons and may justify different access restrictions once day-to-day use has ended.

Define records and triggers precisely

A schedule saying “customer data: six years” leaves important questions unanswered. Does the period run from account creation, the last transaction or contract termination? Does it cover every marketing preference, support note and attachment? Which duplicate copies are included?

Our suggested schedule has a record category, purpose, system, retention trigger, period or review rule, justification, disposal method and owner. Separate records where the purpose differs. An unsuccessful enquiry and a completed contract need not follow the same timetable. Write triggers that the systems can detect, or identify a manual process where automation is not practical.

Make the data map match the schedule

Information often exists in more places than the official system. Include exports, shared drives, email attachments, archived projects, paper storage and relevant suppliers. A deletion rule in the main database may achieve little if a monthly export preserves the same information elsewhere.

A useful exercise is to select one closed matter and trace its copies. Ask who still uses each copy and why. Remove unnecessary duplication before designing elaborate deletion machinery. Establish which record is authoritative and prevent routine workflows from recreating material that has already reached the end of its justified life.

Distinguish deletion from hiding and pseudonymising

Moving a record into an archive or removing it from the normal screen does not necessarily end its retention. Replacing a name with a reversible identifier is generally pseudonymisation, not anonymisation; the information can remain personal data. The legal question depends on whether people are still identifiable in the relevant circumstances.

If retaining aggregate information for business analysis, assess whether the intended result genuinely prevents identification rather than simply removing obvious names. Our practical advice is to define the output before retaining the underlying detail. A small business should not assume that keeping every individual record is necessary merely because it might one day produce a useful report.

Plan for backups and supplier copies

Backups need a documented approach, not an impossible promise that every trace disappears instantly. Understand backup rotation, restoration procedures and whether deleted information could return to active use. Where immediate erasure from a backup is not feasible, appropriate safeguards and restrictions are important while the backup ages out.

Ask suppliers how their deletion controls work in the actual service tier. Check attachments, audit logs, support copies and subcontractors where relevant. Test a harmless sample record rather than relying solely on a button labelled delete. If information is restored after an incident, make sure suppression and deletion decisions are reapplied before ordinary use resumes.

Handle exceptions without creating indefinite holds

A dispute, investigation or other justified need may require relevant information to be preserved beyond the routine schedule. Document the reason, scope, decision-maker and review trigger. A legal hold should not silently suspend deletion across every record the business has ever collected.

Our recommended process separates material under a specific hold from ordinary working copies and restricts access accordingly. When the reason ends, review the record again rather than leaving it permanently exempt. Obtain advice where competing preservation and deletion obligations arise; a general retention policy cannot decide every live dispute.

Give disposal an owner and evidence

The ICO’s records-management framework emphasises responsibility and effective disposal. Translate the schedule into system settings and recurring tasks. For paper, devices and outsourced destruction, consider confidentiality throughout collection, transport and disposal. A certificate is useful evidence only if it relates to the records and process actually used.

Keep proportionate evidence of completed disposal, exceptions and failures. Do not recreate the deleted personal information in a detailed deletion log. A log can usually identify the category, system, scope, date and responsible action without retaining the substance that was meant to be removed.

Review whether the schedule is working

Choose a small sample periodically and test it against the rule. Are expired enquiries still searchable? Do former employees retain access? Has a new integration introduced another copy? Treat failed deletion as a real operational issue to investigate, not merely a missing tick in a compliance checklist.

Update the public privacy information so retention periods or criteria reflect the actual approach. The best schedule is specific enough to operate and flexible enough to reflect justified exceptions. It reduces unnecessary exposure while preserving information the business genuinely needs, with an explanation that can be defended when someone asks why a record is still there.

Sources and further reading

Primary guidance behind this briefing. Requirements depend on the facts; check the current guidance before making a decision.

This is general guidance, not a legal opinion on your circumstances or a guarantee of compliance. An individual assessment may be needed, particularly where sensitive information, disputed rights or regulatory action is involved.