Privacyboard

Data retention: how long to keep customer, employee and invoice data

By the Privacyboard teamPublished 15 November 20268 min read
Short answer

The GDPR sets no fixed retention periods. You keep personal data only as long as each purpose needs it, then delete or anonymise it. Other laws set minimums for some records, such as 6 years for UK company accounts, 8 years for invoices in Germany and 10 years for accounting records in France. Everything else needs a period you can justify and write down.

The GDPR does not tell you how many years to keep anything. It says you may keep personal data in a form that identifies people "for no longer than is necessary" for the purpose you collected it for, then you delete or anonymise it. Tax, accounting and employment laws add minimum periods for some records, and those set the floor.

So a retention schedule has two kinds of lines: periods the law imposes (invoices, payroll), and periods you choose and justify (customer accounts, prospects, CVs). This guide gives starting points for both in France, Germany, the UK and the US, as of 15 November 2026. It is general information, not legal advice; check your own country's rules and sector.

#What does the GDPR actually require?

Four provisions do the work.

  • Article 5(1)(e), storage limitation. Personal data is kept in identifiable form no longer than the purpose needs. Longer storage is allowed only for archiving in the public interest, research or statistics, with safeguards.
  • Article 13(2)(a) and 14(2)(a), transparency. Your privacy notice must state the retention period, or the criteria used to set it.
  • Article 30(1)(f), the register. Your record of processing activities lists, where possible, the time limits for erasing each category of data.
  • Article 17, erasure. Once data is no longer needed, people can ask you to delete it, and you should have done so already.

The UK regulator, the ICO, sums it up plainly: the UK GDPR "does not set specific time limits for different types of data". You set them, you document them, and you must be able to justify them. Keeping data "just in case" is not a reason.

#Is there a standard retention period for each type of data?

No single list applies across Europe, because the minimums come from national tax, company and labour laws. The table below gives common starting points from official sources. Periods usually run from the end of the year, contract or relationship, not from the day you collected the data.

RecordFranceGermanyUKUS (federal tax)
Invoices and accounting vouchers10 years for accounting records (CNIL, citing the accounting obligation)8 years for vouchers and invoices since 2025 (§ 147 AO, § 14b UStG)6 years for company records; VAT records up to 6 years3 years by default, longer in some cases
Books and annual accounts10 years10 years6 years from the end of the financial year3 years by default
Payroll6 years for payslip data after filing (CNIL HR guide)Set by tax and social security rules3 years from the end of the tax year (PAYE)At least 4 years for employment tax records
Customer data used for marketingEnd of relationship + 3 years (CNIL)Your justified periodYour justified periodNo federal rule
Prospects (never customers)3 years from collection or last contact (CNIL)Your justified periodYour justified periodNo federal rule
Rejected job applicantsTime of recruitment, then 5 years archived as evidence (CNIL HR guide)Your justified periodYour justified periodNo federal rule in this list

Two points about this table. First, a legal minimum covers the record the law names, not everything you hold about the person. An invoice must be kept; the customer's browsing history next to it does not. Second, "your justified period" is not a blank cheque. Write down the reason, such as the limitation period for claims, and stick to it.

#How long can you keep customer and prospect data?

The CNIL's guidance for commercial activities, which many teams outside France also use as a reference, splits customer data by purpose:

  • To run the contract: for as long as the contract lasts.
  • After the contract: only what you must keep for accounting or tax, or what you need as evidence for a possible dispute, moved to a separate archive and kept within the limitation period.
  • For marketing to customers: during the relationship, then 3 years after it ends (from a purchase, the end of a warranty or contract, or the customer's last contact).
  • For prospects who never bought: 3 years from collection or from the prospect's last contact. The CNIL says a click on a link in your email counts as contact; simply opening an email does not.

At the end of those 3 years, you can ask the person whether they still want to hear from you. Without a clear yes, delete the data or archive only what a law requires.

The CNIL also says the card security code (CVV) must be deleted as soon as the payment is complete.

#How long should you keep employee and candidate data?

Employee data falls under the strictest mix of rules, because labour, tax and social security law each set their own periods. In April 2026, the CNIL published a dedicated retention guide for HR. Some of its periods:

  • Personnel file: for the duration of employment; after departure, only what a law requires or what you need as evidence, archived.
  • Payslip data: 6 years after the social security filing; payslips made available to employees, 5 years.
  • Register of staff: 5 years after the employee leaves.
  • Badge access logs: 3 months.
  • CCTV footage: 1 month.
  • Rejected candidates: for the time of the recruitment, then up to 5 years archived from when the post was filled, as evidence in case of a discrimination claim. A talent pool, kept with the person's agreement or unless they object, is limited to 2 years from the last contact.

In the UK, HMRC requires payroll records for 3 years from the end of the tax year. In the US, the IRS asks employers to keep employment tax records for at least 4 years after the tax is due or paid, whichever is later. Neither sets a period for CVs or performance reviews, so you set and justify those yourself.

#What does "delete" mean in practice?

The ICO's test is that data must be put "beyond use". A few practical consequences:

  • Moving data to an offline drive is not deleting it. It is still personal data and still needs a justification.
  • Backups count. The ICO says data deleted from live systems should also be deleted from backups. If a backup cannot be edited, let it expire on a fixed cycle and never restore the deleted records into live systems.
  • Anonymised data is outside the GDPR, but only if people can no longer be identified. Pseudonymised data (with an ID replacing the name) is still personal data.
  • Archives are a separate step. Records kept for a legal obligation belong in a restricted archive that only a few people can reach, not in your live CRM.

#How do you build a retention schedule?

Work from your record of processing activities: one retention line per activity and data category.

  1. List each activity (selling, invoicing, payroll, recruiting, newsletter, support).
  2. Check for a legal minimum in your country for each record type, and note the article.
  3. Set a period where there is none, linked to the purpose and to the limitation period for claims if you keep data as evidence.
  4. Name the starting point: end of contract, last contact, end of tax year.
  5. Say what happens at the end: delete, anonymise or archive.
  6. Copy the periods into your privacy notice and register so they say the same thing.
  7. Automate or schedule the deletion, and review once a year.

In Privacyboard, each activity in the processing register has its own retention field, the register flags activities still missing one, and the privacy policy lists the periods from the same record.

#Retention checklist

  • Every processing activity has a retention period or a clear criterion.
  • Each legal minimum is tied to the record it covers, with its legal reference.
  • Periods have a start point (end of contract, last contact, end of tax year).
  • Privacy notice and register state the same periods.
  • Prospects and inactive customers are cleaned at least once a year.
  • Rejected candidates' files are deleted or archived after the period you set.
  • Card security codes are never stored after payment.
  • Archives are separate from live tools and access is restricted.
  • Backups expire on a fixed cycle and deleted data is never restored.
  • Vendors who hold your data delete or return it at the end of the contract, as your DPA says.
  • An erasure request triggers a check of every tool, not just the CRM.

#FAQ

#Does the GDPR say how long to keep personal data?

No. It only requires that data be kept no longer than the purpose needs, and that you state the period or its criteria in your privacy notice. Fixed periods come from other laws, such as tax and company law, or from regulator guidance like the CNIL's.

#Can I keep customer data forever if they might come back?

No. "They might come back" is not a purpose. Keep what the contract and the law need, then delete or anonymise. For marketing, the CNIL's reference is 3 years after the relationship ends, after which you ask the person whether they still want to hear from you.

#Do I have to delete an invoice if the customer asks for erasure?

No, not while a legal obligation requires you to keep it. Article 17(3)(b) of the GDPR makes an exception for data you must keep to comply with a legal obligation. You can delete the rest of the customer's data and keep the invoice in a restricted archive until the period ends.

#How long can I keep a CV after rejecting a candidate?

It depends on the country. In France, the CNIL allows keeping the file for up to 5 years after the post is filled as evidence in a discrimination claim, archived, and up to 2 years in a talent pool from the last contact if the person agrees or does not object. Elsewhere, set a period tied to the time limit for claims and tell candidates.

#Do retention periods apply to backups?

Yes. The ICO says data deleted from live systems should also be deleted from backups, or at least put beyond use until the backup expires. Short, fixed backup cycles make this manageable.

#Sources

Privacyboard is a guidance tool, not legal advice. This article explains general rules in plain language and was accurate on the date above; laws and guidance change. For an unusual situation, ask a qualified professional. Spotted a mistake? Write to hello@privacyboard.io.

Keep reading