How long to keep business email: retention and the GDPR
There's no single retention period for business email. What the GDPR says about storage limits and backups, what the EDPB advises, and how to set a policy.
- Published
- 5 min read
There is no single legal retention period for “email”. What sets the period is what an email contains and why you keep it: invoices and contracts fall under tax and commercial record-keeping rules that can require several years, while the GDPR says personal data must not be kept longer than you need it. You satisfy both with a written retention policy by type of email, and a backup you can actually find, open and restore.
This isn’t legal advice. It’s a summary of public rules and guidance to help you get started. Retention periods depend on your country, your sector and your contracts, so confirm yours with a lawyer, an accountant or your data protection officer.
The content sets the clock, not the mailbox
A business mailbox holds a bit of everything: supplier invoices, customer conversations, job applications, shipping notices, newsletters. Each of those has its own reason to be kept, or not. Asking “how many years do we keep email?” tends to produce one number that is too long for some messages and too short for others. A better question is: what kinds of email do we receive, and what is each one kept for?
What the GDPR actually says
The General Data Protection Regulation doesn’t set a number of years. It sets principles, and two of them matter most here.
Storage limitation. Article 5(1)(e) says personal data must be kept in a form that identifies people “for no longer than is necessary for the purposes for which the personal data are processed”. Almost every email contains personal data: names, addresses, signatures, phone numbers and often far more.
Accountability. Article 5(2) says the controller must be able to demonstrate compliance. In practice that means writing your retention decisions down.
The European Data Protection Board turns this into plain advice in its SME data protection guide: personal data “must be deleted or anonymised once this data is no longer necessary”, your organisation “should have an internal policy in place regarding data retention periods per different purpose, as well as a procedure for deleting data”, and national legislation “may oblige you to keep certain data (i.e. for tax reasons)”.
That last point is the key. The GDPR sets the ceiling (“no longer than necessary”), and other laws often set the floor.
The GDPR also expects you to be able to restore
Article 32 asks for security measures that include “the ability to restore the availability and access to personal data in a timely manner in the event of a physical or technical incident”, and “a process for regularly testing, assessing and evaluating” those measures. A backup nobody has ever tried to restore doesn’t tick that box.
Does it apply to you?
The GDPR covers organisations established in the EU, and Article 3(2) extends it to organisations elsewhere that offer goods or services to people in the EU or monitor their behaviour there. If you’re unsure whether that includes you, that’s a question for your lawyer.
The floor: record-keeping rules
Retention minimums come from national law, and they vary a lot. Two examples show how different they can be:
| Example | What it covers | Period | Source |
|---|---|---|---|
| United States (IRS) | General tax records | 3 years in most cases | IRS |
| United States (IRS) | Unreported income over 25% of gross income | 6 years | IRS |
| United States (IRS) | Claims for worthless securities or bad debt | 7 years | IRS |
| United States (IRS) | Employment tax records | At least 4 years | IRS |
| Spain (Commercial Code, art. 30) | Business books, correspondence and receipts | 6 years | BOE |
The Spanish rule is a good reminder that “correspondence” can be a record in its own right: email exchanged with customers and suppliers about the business counts. Sector rules (healthcare, finance, employment, anti-money-laundering) can add longer periods on top. Where one applies, it wins over the general rule.
Putting it into practice
- Take inventory. List the mailboxes you have: personal ones, shared ones like invoices@ or info@, and those of people who have left. Note what usually arrives in each.
- Give each purpose a period. Billing and contracts get the tax and commercial period that applies to you. Job applications get whatever your hiring policy says. Newsletters and notifications don’t need keeping at all.
- Write it down. One page is enough. It’s your evidence for Article 5(2).
- Separate what has to last. A dedicated mailbox or folder for business correspondence means the long-term copy covers what it should and little else.
- Keep a copy outside your provider. If an account is closed, suspended or wiped by someone who got into it, don’t count on the provider giving it back. We covered this in cloud email is not a backup and what happens if your account is suspended or hacked.
- Review once a year. Delete or anonymise what has expired, and test that the backup restores.
Employee mailboxes
A staff member’s work mailbox holds their personal data and other people’s. Tell your team in writing what is backed up, who can access those backups and how long a mailbox is kept after someone leaves. Local employment law may add rules about when an employer can look at that content.
Keeping and deleting without contradicting yourself
“Keep it for years” and “don’t keep more than you need” sound like they pull in opposite directions. In practice you separate the two. Business records are kept whole and unchanged for their period, and everything else goes when its purpose is done. For the first part you want a copy that is hard to alter. For the second, you need to know where everything is.
Where Arca Mail Backup fits
Arca backs up email over IMAP (Gmail and Google Workspace, Outlook.com and Microsoft 365, or your hosting provider’s mail) to a disk, a NAS or S3-compatible storage that you choose. Each message is stored byte for byte as it arrived, in standard mbox files (one per folder and month) with a manifest.json. Closed months never change, so they work with versioning and Object Lock on your bucket. Mail deleted on the server stays in the backup, marked as deleted. Nothing passes through servers of ours.
What it doesn’t do yet: Arca keeps everything it backs up, and “versions and retention” in Pro is listed as coming soon. For now, you apply your deletion schedule yourself. It doesn’t back up calendars or contacts either.
It’s free for one account on a disk of your computer, and Pro yearly covers 1 to 100 accounts (see pricing). It’s in the Microsoft Store for Windows and the Mac App Store for Mac, with Arca Pro on sale in both.