How to Run a Data Retention Clean-Up
A step-by-step approach to finding personal data you no longer need, agreeing what to keep, and deleting the rest safely and with a record.
Most organisations keep personal data far longer than they need it. Old customer records, applications for roles filled years ago, exports from finished projects, test databases copied from production. None of it is useful any more, but all of it is still a risk.
A retention clean-up reduces that risk. Data you no longer hold cannot leak, cannot be misused and does not need to be searched when someone asks what you have about them.
Why it matters
- Less risk. Every record you delete is one less record exposed in a breach.
- Easier requests. Finding and handling a person’s data is simpler when there is less of it.
- Lower cost. Storage, backups and tooling all cost more as data grows.
- Cleaner systems. Teams work faster with less clutter.
Step 1: Get agreement on who decides
A clean-up needs people with authority to say “we can delete this”. Usually that means:
- Business owners, who know what each type of data is used for.
- Legal, who confirm how long data must or may be kept.
- IT and security, who know where data lives and carry out deletion.
Name one person to coordinate. Without that, clean-ups stall the moment a question comes up.
Step 2: Find what you hold
You cannot decide what to delete without knowing what exists. Build or update an inventory of where personal data lives, including databases, file shares, SaaS tools, exports and test environments. For a method, see how to find the personal data hiding across your systems.
Step 3: Group data into types
Instead of deciding record by record, group data into types such as:
- Customer accounts
- Billing and invoices
- Support conversations
- Job applications
- Employee records
- Marketing contacts
- Logs and analytics
Each type gets one retention decision.
Step 4: Agree a retention period for each type
For each type, record:
| Field | Example |
|---|---|
| Data type | Job applications |
| What it is used for | Assessing candidates for a role |
| Retention period | Agreed with legal |
| What happens at the end | Delete |
| Owner | Head of talent acquisition |
The period itself should come from the business need and your legal team’s advice. This guide cannot tell you what it should be.
Step 5: Decide what happens at the end
The usual options are:
- Delete the data entirely.
- Archive it somewhere with tighter access, if it must be kept for longer but not used day to day.
- Anonymise it for statistics, if that is genuinely possible and your legal team agrees it is appropriate.
Step 6: Clean up, carefully
Start with the low-risk, high-volume wins: old exports, abandoned test databases, systems nobody uses. Then move to live systems.
- Test deletion on a small batch first.
- Check that integrations and reports still work.
- Keep a record of what was deleted, when, by whom and under which retention rule. Record the action, not the data itself.
Step 7: Do not forget vendors and copies
Personal data you send to vendors is still part of your footprint. Ask them to delete data in line with your rules, and get confirmation. Check shared drives and email attachments too; they often hold the most forgotten copies.
Step 8: Make it ongoing
A one-off clean-up drifts back to clutter within a year. To keep it clean:
- Build automatic deletion into systems where you can.
- Run a review on a regular schedule.
- Add a retention decision to the checklist for every new system or project.
Start small
Pick one data type that is clearly over-retained, such as old job applications, and take it all the way from decision to deletion. The first clean-up teaches you where the obstacles are, and the next one goes faster.
For the wider picture, see our DPDP compliance checklist.
Arbor Lens finds the personal data in your systems from inside your own perimeter, read-only.
Explore Arbor LensQuestions people ask
Who decides how long we keep data?
The business owner of each data type proposes a period based on what it is needed for, and your legal team confirms it against any legal or regulatory requirements. IT and security then make sure the decision is carried out.
What about backups?
Deleting individual records from backups is usually impractical. Many organisations let backups expire on a fixed schedule instead, and make sure deleted data is not restored into live systems. Agree the approach with your legal and security teams.
Is anonymising data the same as deleting it?
Not always. Data that can be linked back to a person may still count as personal data. Ask your lawyer before relying on anonymisation in place of deletion.