How to Set Data Retention Periods Properly

How to Set Data Retention Periods Properly

A former employee’s mailbox, an old customer spreadsheet and years of CCTV footage can all create the same problem: data that no one actively needs, but no one has felt confident enough to remove. Knowing how to set data retention rules gives your organisation a sensible way to keep what is needed, delete what is not and respond confidently when a security or compliance question arises.

Data retention is not simply an IT housekeeping task. It affects privacy, storage costs, cyber risk, backups and your ability to find reliable records when you need them. The right policy is practical enough for staff to follow and specific enough to stand up to scrutiny.

What data retention means in practice

A data retention policy sets out what information you hold, why you hold it, where it is stored, how long it should remain available and what happens when that period ends. It should cover digital records, paper files where relevant, cloud platforms, shared drives, email and data held by third-party suppliers.

For a small business, this may include customer contact records, invoices, HR files, email, Microsoft 365 documents, support tickets, call recordings and security logs. A home user may apply the same principle more simply, such as deciding how long to retain old device backups, scanned documents or CCTV clips.

The objective is not to delete data as quickly as possible. Some records must be retained for legal, contractual, tax, warranty or operational reasons. Equally, keeping personal data indefinitely because it might be useful one day is rarely a good justification. The longer unnecessary data remains in your systems, the more information could be exposed if an account is compromised, a laptop is lost or ransomware reaches a file share.

How to set data retention around real business needs

Start with the information your organisation actually uses rather than copying a generic policy. A retention schedule should reflect the type of data, the purpose for holding it and the risks of keeping or deleting it too soon.

Map the data before choosing a timescale

Make a straightforward inventory of your main data sets. Ask which team owns each set, where it lives and whether it contains personal, financial, confidential or commercially sensitive information. Do not overlook data held outside the main server or cloud tenant, including staff laptops, mobile phones, email archives, USB drives, accounting software, VoIP systems and supplier portals.

For each category, identify the business purpose. For example, customer contact details may be needed to deliver an ongoing service; project documents may be required during a contract and warranty period; and financial records may need to be retained to meet statutory obligations. If there is no clear purpose, that is a strong prompt to remove the data or stop collecting it.

This exercise also reveals duplication. The same customer list may exist in a CRM system, an old spreadsheet and several mailboxes. Retention controls are far easier to manage when there is a recognised source of truth.

Set periods using evidence, not habit

There is no universal retention period that suits every type of record. UK GDPR requires personal data to be kept no longer than necessary for the purpose it was collected, but it does not provide one standard number of years for every business record. Other requirements, including tax, employment, insurance, contractual and industry rules, may set or influence retention periods.

Write down the reason for every period you choose. A useful schedule records the data category, purpose, retention period, legal or business basis, storage location, owner and disposal method. This turns a vague instruction such as “delete old files regularly” into an action that can be checked and applied consistently.

Be careful with inactive customer data. A person who has not bought from you recently may still have an active service agreement, an unresolved query or a valid reason for you to retain limited records. On the other hand, marketing lists should not be allowed to grow indefinitely without reviewing consent, legitimate interests and engagement.

Where there is genuine uncertainty, get advice from a qualified data protection professional or legal adviser. IT support can implement the technical controls, but it should not be expected to make legal retention decisions on your behalf.

Separate retention from backup

Backups protect you from loss. Retention determines how long information should exist. They overlap, but they are not the same thing.

A deleted file may remain in backup copies for a defined backup cycle, and that can be appropriate where the backup is secure and access is controlled. However, a backup system must not become an unmanaged archive containing every piece of data your business has ever created. Define how long daily, weekly and monthly backup versions are retained, who can restore them and when older copies are securely removed.

This distinction matters during a subject access request, a data breach investigation or a deletion request. You need to know whether data is live, archived or held temporarily in a protected backup, and whether restoring it would reintroduce information that should no longer be processed.

Put the policy into your everyday systems

A policy only reduces risk when it becomes part of normal working practice. The best approach is to apply automated rules where possible, then support them with clear staff processes.

Microsoft 365, email platforms, document management systems, cloud storage and security tools can often apply retention labels, archive rules and deletion policies. For instance, you might retain invoices for an agreed period, archive completed project folders after handover and automatically remove temporary files after a shorter period. Automation reduces reliance on someone remembering a yearly clean-up, but test every rule before applying it across the business.

Email requires particular care. Retaining every mailbox forever makes searching harder, increases storage costs and creates unnecessary exposure. A sensible email policy may keep business correspondence for a defined period while allowing certain records, such as contractual approvals or finance evidence, to be saved in the correct controlled location. Staff should not use personal inboxes or local downloads as an informal archive.

CCTV, call recordings and system logs also need explicit periods. These records can be valuable when investigating an incident, but they can contain personal data and become difficult to manage when retained without a clear reason. Keep them for a period that reflects the likely time in which an issue would be reported or investigated, unless a specific incident requires preservation for longer.

Define exceptions and legal holds

There will be times when normal deletion must pause. This may happen because of an insurance claim, employment matter, customer dispute, audit, regulatory enquiry or suspected security incident. Record who can authorise a retention hold, which data it covers, why it was applied and when it will be reviewed.

Without this process, staff may either delete relevant evidence automatically or keep everything permanently “just in case”. Neither approach is well controlled. A hold should be targeted, documented and lifted once the matter is resolved.

Make secure deletion part of the plan

At the end of a retention period, data should be deleted or anonymised in a way that matches the risk. Removing a file from a desktop is not always enough if copies remain in recycle bins, shared folders, cloud sync locations, devices or backups.

For ordinary business information, managed deletion rules and normal secure disposal procedures may be sufficient. For sensitive data on retired laptops, servers or storage drives, use verified wiping or certified physical destruction where appropriate. Keep a record of disposal for higher-risk information and equipment, particularly where it contains customer or employee data.

Anonymisation can be useful when you need to retain statistics or trends without retaining identifiable personal data. It must be genuinely irreversible. Simply removing a name while leaving a combination of unique details may not be enough to prevent identification.

Review retention rules at least once a year

Your retention schedule should change when your business changes. New software, a move to cloud services, a merger, a new product, revised contracts or a cyber incident can all expose gaps in an old policy. Review the schedule at least annually and whenever a significant change occurs.

Check whether automated rules are working, whether staff understand where records belong and whether old systems still hold forgotten data. It is also worth testing a restore from backup and confirming that retention settings do not conflict across connected systems.

For many organisations, the practical challenge is not writing the policy but applying it across email, cloud files, endpoints, servers and backups without disrupting work. A managed IT partner can help map the systems, configure controls and keep the process under review, while your leadership team retains ownership of the decisions.

Good data retention should make your business lighter on its feet: less clutter, less exposure and clearer records when they matter most. Start with one high-risk area, document the reason for each decision and build a process your team can maintain with confidence.