Start with the purpose
An enquiry inbox or customer management system can accumulate information long after a conversation ends. Before setting a deletion rule, list the kinds of information you hold and why. A current request, a signed contract, an invoice and a marketing preference may need different treatment because they serve different purposes.
The ICO says personal data should not be kept longer than necessary for its purpose. There is no single universal enquiry retention period in the UK GDPR: the appropriate period depends on the circumstances. Identify the person responsible for the decision and document the reasoning rather than copying a number from another business.
Map where information is stored
Follow a message from the contact form through the delivery service to the team inbox, any spreadsheet, customer system and shared files. A copy may also exist in an export, an attachment or a backup. Record which providers are involved, who has access and why each copy exists. The aim is to understand the actual process, not draw an idealised diagram.
If staff forward enquiries to personal accounts or download lists onto shared devices, the business may struggle to review or remove them later. Agree approved storage locations and access arrangements, and check how suppliers handle information on your behalf. Do not put customer details into an unapproved tool simply to consolidate a report.
Define categories and review points
Create categories that reflect real purposes, such as an open request, a declined project, an active agreement and a completed invoice. Decide what event starts the review: receipt, last contact, completion or the end of an obligation may each be relevant depending on the record. Make the criteria understandable enough for another person to apply them consistently.
For each category, document the reason, owner, review interval and the decision to keep, erase or genuinely anonymise. If a legal or contractual obligation requires a particular record to remain available, identify it rather than retaining everything indefinitely. A review date can flag a decision; it is not necessarily a command to delete without checking context.
Plan a retention review
- PurposeWhy is each record held?
- LocationWhere are its copies?
- ReviewWhen and by whom?
- ActionKeep, erase or anonymise
Be precise about deletion and anonymisation
Moving an old record to another folder or taking it offline does not automatically make it anonymous or deleted. A coded record may still identify someone when combined with other information. Ask how your systems remove information from active storage, exports and backups, and how long any retained copy remains accessible.
If you use an anonymised aggregate for reporting, check that individuals cannot reasonably be identified from small groups or a separate key. The team may need only counts by broad service type rather than original messages. Follow the provider's documented process and keep enough evidence of the review without retaining the data you meant to remove.
Explain the approach and protect access
Make privacy information clear about the purposes for using personal information and the retention period or criteria that apply. It should reflect what the business actually does and be accessible where information is collected. Check that the contact route for privacy questions works and that someone knows how to respond to requests.
Limit access to people who need it, review supplier permissions and protect accounts appropriately. Retention is not only a schedule in a policy: it affects day-to-day inboxes, exports and shared workspaces. An operational owner needs time and access to carry out the review.
An illustrative review
Imagine a business has an open quote request, an unrelated old enquiry and a completed project with an invoice. It records the purpose of each, identifies the applicable review point and checks whether any additional obligation affects the completed project. The open request is handled by the assigned person; the old enquiry is reviewed against the documented criteria.
This is a hypothetical example, not a prescribed retention schedule or legal advice for every business. The team should check the actual facts and obtain appropriate advice if obligations conflict. It should not use the existence of one invoice as a reason to retain every unrelated message forever.
Build a retention table by record type
Create one row each for an open enquiry, a closed or declined enquiry, an active contract and a financial record. For each row record the purpose, system, responsible person, event that triggers review and criteria for the next decision. Do not put an actual customer's name in the template; it is a process document rather than a second database.
A hypothetical open enquiry may need to remain accessible while the team replies. A declined enquiry should be reviewed under the business's documented criteria. A financial record may have a separate reason to be retained. These examples deliberately do not prescribe a number of months or years: the business must assess its own purposes and any other applicable obligations.
Test how the chosen system implements the decision. Ask whether deletion affects attachments, shared inboxes, exports and supplier-held copies, and how backup retention is handled. If the tool only archives a record, that may not be deletion. Document unresolved issues and assign an owner rather than assuming a policy sentence changes every system automatically.
When a person asks about their information, the team also needs to know which systems and suppliers may hold it. Keep a reliable contact for each processor and an internal route for requests, without promising that every record can be erased immediately in every circumstance. Check the facts, any applicable obligations and current ICO guidance, then record the decision and the action taken.
A repeatable checklist
For each type of record, ask: what is it for, where are its copies, who can see it, what event triggers review, and what happens when the purpose ends? Check the privacy notice against the same answers. Record who approved the schedule and when it will be revisited.
Test a small set of records to see whether the process works in practice, without exposing details to people who do not need them. Include backups and provider-held copies in the assessment. Revisit the schedule when a service, supplier, purpose or legal requirement changes.
