Pro free for 30 days.No card.Start free →

Data Retention and Deletion Policy for Small Business: How to Write One

What to keep, for how long, and how to destroy it. A five-step guide to writing a short data retention and deletion policy, with an example schedule, disposal methods and common mistakes.

By WorkBOS Content Desk8 min read
Shredded paper strips piled together, some showing printed words (Photo by campbellstogether on Pixabay)
Photo: campbellstogether / Pixabay

Most small businesses are good at collecting information and bad at getting rid of it. Old customer lists, former employees' files, abandoned spreadsheets and years of email attachments pile up because nobody is sure when it is safe to delete them. That habit has a cost: the more personal information you hold, the more there is to lose in a breach, to search through when a customer makes a request, and to explain to a regulator.

A data retention and deletion policy fixes this. It is a short document that says what you keep, why, for how long, and how you destroy it. This guide shows how to write one in an afternoon. It is general information, not legal advice; some records must be kept for set periods, so check the rules for your industry and location.

Why a retention policy matters

Three reasons usually matter to a small business:

  • Less risk. The US Federal Trade Commission's guide for businesses tells companies to keep personal information only as long as there is a business reason or legal requirement, then dispose of it securely. In its words, data that is not in your system cannot be stolen from it.
  • Easier requests. Privacy laws give people the right to see or delete their data. A smaller, tidier data set is quicker to search.
  • Legal compliance. Privacy rules such as GDPR include a principle called storage limitation. The UK regulator explains that personal data should be kept in identifiable form only for as long as necessary for your purposes, and that holding it "just in case" is not a reason. California's privacy agency says collection, use and retention must be reasonably necessary and proportionate to the purposes people would expect or agreed to.

Keeping is not the same as being required to keep, and deleting is not the same as being allowed to delete. A policy sorts out which is which.

Step 1: take stock of what you hold

You cannot set a period for data you have not found. Make a simple inventory:

  1. List every place personal information lives: email, accounting, CRM, shared drives, spreadsheets, HR files, paper, laptops, phones, backups and every online tool your team uses.
  2. Note what types of data are in each place: customers, prospects, employees, applicants, suppliers.
  3. Flag the sensitive items first: Social Security numbers, bank details, ID documents, health information.
  4. Record who can access each store.

The FTC's own advice follows this same pattern: take stock, scale down, lock it, pitch it and plan ahead. The inventory is the "take stock" step.

Step 2: decide how long to keep each type

There is rarely one correct number. The ICO notes that data protection law sets no fixed time limits, because it depends on your situation. Its small-business guidance says to base the period on why you collected the data and your lawful basis, to be able to justify it, and to follow any other law that requires a record to be kept for a set period, such as payment records for tax returns.

Use these questions for each category:

  • Why did we collect this, and is that purpose still active?
  • Does a law, contract or insurer require us to keep it?
  • Could we need it to defend a complaint or claim, and until when?
  • Could we keep less detail, or an anonymised version?

An example schedule

The periods below are placeholders to show the structure. Replace them with periods you have checked for your own situation.

| Data type | Why you hold it | Keep until | What happens next | |---|---|---|---| | Active customer records | Deliver the service | Relationship ends plus a review period you set | Delete or anonymise | | Invoices and payment records | Tax and accounting rules | The legal period for your location | Secure deletion | | Unconverted sales leads | Follow up on enquiry | A short window you set, such as a year of no contact | Delete | | Job applicant files | Hiring decisions | Only as long as a claim could arise, then delete | Secure deletion | | Former employee files | References, payroll, legal duties | Per employment and tax rules | Keep the required items, delete the rest | | Website enquiry forms | Answer the question | Until answered, plus a short follow-up | Delete | | Support tickets | Resolve and improve service | A period you can justify | Delete or anonymise |

For legal minimums on financial documents, our guide to small business record keeping is a good starting point. Employee and applicant records often have their own rules, and the ICO gives examples such as keeping unsuccessful applicants' records only for the period in which a claim could be brought.

Step 3: write the policy

Keep it to one or two pages. The FTC suggests a written policy covering what to keep, how it is secured, how long it is kept and how it is disposed of. A workable outline:

  1. Purpose and scope: which data and systems the policy covers.
  2. Owner: one named person responsible for it.
  3. The schedule: your table from step 2.
  4. Legal holds: if a dispute, audit or investigation is possible, pause deletion for the relevant records until a professional says otherwise.
  5. Disposal methods: how each format is destroyed (see below).
  6. Review rhythm: how often you review the schedule and the data.
  7. Exceptions: who can approve keeping something longer, and how that is recorded.

The ICO adds that small organisations doing occasional, low-risk processing may not need a documented policy, but you still need to review data regularly and delete what you no longer need. A short written policy is usually easier than defending the absence of one.

Step 4: delete properly

Deleting a file is not always deleting the data.

  • Paper: the FTC says to shred, burn or pulverise records, with shredders placed throughout the workplace.
  • Old computers and drives: the FTC says to use wipe utilities that overwrite the whole drive, because normal deletion leaves data recoverable.
  • Live systems and backups: the ICO says that if you delete from a live system you should also delete it from backups. Plan for backups to roll off on a schedule so old data does not live on indefinitely. Our guide to backing up business data is a useful companion on keeping backups.
  • Offline is not deleted: the ICO notes that taking data offline does not remove it from your duties.
  • Remote workers: home offices need the same disposal habits.
  • Anonymise where useful: data that can no longer identify anyone can often be kept for analysis. Pseudonymised data, such as key-coded records, can still identify people, so it does not count.

Step 5: build deletion into the routine

A policy that lives in a folder does nothing. Put dates on the calendar.

  • Quarterly: review lead lists and old project folders.
  • When someone leaves: collect devices, close accounts and move needed records into the right archive.
  • When a project closes: archive what you must keep and delete the rest.
  • When a customer asks: treat the request as a trigger to review what you hold, as the ICO recommends.
  • If you close your business: the ICO advises a plan covering what you must keep, where and how it is stored, who can access it, and when it will be destroyed.

Automation can help. The ICO notes that automated systems can flag records for review or delete them after a set period.

Common mistakes

  • "Keep everything forever" as a policy. It feels safe and creates the biggest exposure.
  • Deleting what you must keep. Check legal minimums before you purge.
  • Forgetting backups, exports and personal devices. Deleted data often survives there.
  • No owner. If everyone is responsible, nobody deletes anything.
  • Copying another firm's schedule. Your purposes and laws differ.
  • Skipping the record of deletions. Note what you deleted and when, so you can show your process.
  • Deleting during a dispute. Pause deletion if a claim or investigation is possible.

Where WorkBOS fits

A retention policy is easier to follow when records sit in a few known places. WorkBOS keeps CRM contacts, projects, invoices, HR files and documents in one system, uses roles and permissions to control who can see them, and has automations that can help with routine tasks such as review reminders. A person still decides what is deleted. See the docs for setup, pricing for plans, and the Academy for short lessons.

Frequently asked questions

Q: How long should I keep customer data? A: Only as long as you need it for the purpose you collected it, plus any legal retention period. No law gives a single number, so set periods per category and be able to explain them.

Q: Do I need a written retention policy? A: Regulators generally expect one where practical. The UK regulator says small organisations with occasional, low-risk processing may not need a documented policy, but they must still review and delete unneeded data.

Q: Is deleting from my live system enough? A: No. Copies in backups, exports and old devices also need to be dealt with on a schedule.

Q: What if a customer asks me to delete their data but I need the invoices? A: You can usually keep records you are legally required to hold. Delete the rest, keep the required items, and tell the person what you kept and why.

Q: Should I delete or anonymise? A: Either can work. Anonymised data cannot identify a person, while pseudonymised data can, so treat the latter as personal data.

This is general information and not legal advice. Sources are linked in the text above: UK Information Commissioner's Office (storage limitation, data storage advice), California Privacy Protection Agency FAQ, and the US Federal Trade Commission's guide Protecting Personal Information.

Run it all from one place

Projects, clients, finance, people and AI employees in one system. Start free, no card needed.

Start free →