Data retention policy template

List each kind of record your business keeps, with its purpose, how long you keep it, when the clock starts and why that long. The builder flags any line the GDPR’s storage limitation rule or California’s retention disclosure would find thin, then writes the schedule into a short policy you can print or copy. It starts from a worked example and runs entirely in your browser.

Photocopy-style paste-up of a filing cabinet with an open drawer of manila folders under a blank clock face

What the rules ask of a period

Storage limitation
no longer than is necessary for the purposes, GDPR Art. 5(1)(e)
Tell people the period
the period, or the criteria used to set it, Arts 13(2)(a) and 14(2)(a)
Record of processing
time limits for erasure, where possible, Art. 30(1)(f)
California notice
how long for each category, or the criteria, § 1798.100(a)(3), regs § 7012(e)(4)
California request records
at least 24 months, regs § 7101(a)
California risk assessments
while the processing continues or five years after completion, whichever is later, regs § 7155(c)

Rule texts read 22 Oct 2026.

What it works out

A retention policy answers one question per kind of record: how long do we keep it, counted from when, and why that long. This builder keeps the answers as a schedule, one line per category, and checks each line for the three things the rules lean on: a purpose, a period (or the criteria for one) and a reason a reviewer can test. A line missing any of them is flagged with the rule that asks for it.

The Policy tab wraps the schedule in eight short clauses: purpose, scope, the storage rule, the schedule, what happens at the end of a period (backups included), holds, telling people, and review. Switch the GDPR or CCPA clauses on or off and the wording follows. The periods you set here are the same ones your notice at collection and privacy notice must state, and the “time limits for erasure” column of a data map or Art. 30 record.

What it does not do

It does not pick your periods for you. Only a law that reaches your business can set a minimum; everything else is your call, and the schedule shows which is which. Nothing you type leaves this tab: it is not sent to us or stored, and closing the tab clears it. Information, not legal advice.

Where fixed periods come from

Neither the GDPR nor the CCPA gives a number of years for ordinary records. They ask you to keep data no longer than its purpose needs, and to say how long that is. The fixed numbers come from other rules: tax, employment and immigration law, and California’s own record-keeping regulations. These are the ones the example firm uses, each read on the owner’s page.

Record periods set by US federal and California rules
RecordPeriodSource
Most tax records3 years from filing; 6 or 7 years in the cases listedIRS, How long should I keep records
Employment tax recordsat least 4 years after the tax is due or paid, whichever is laterIRS, same page
Personnel and employment recordsone yearEEOC, Recordkeeping requirements
Personnel file after an involuntary terminationone year from the date of terminationEEOC, same page
Payroll records (ADEA, FLSA)three yearsEEOC, same page
Form I-93 years after hire or 1 year after employment ends, whichever is laterUSCIS, M-274 Handbook, retaining Form I-9
CCPA request recordsat least 24 monthsCPPA, regs § 7101(a)
CCPA risk assessmentswhile the processing continues or five years after completion, whichever is laterCPPA, regs § 7155(c)
Federal and California rules, read 22 Oct 2026. A charge or lawsuit extends the EEOC periods. State law can add longer periods. Check the ones that reach you.
“In order to ensure that the personal data are not kept longer than necessary, time limits should be established by the controller for erasure or for a periodic review.”
GDPR, Recital 39

That is why the builder offers “review, then delete or extend” as an end action: where a period hangs on something you cannot see in advance, such as a tax case, a set review date is the time limit.

Worked example: the firm in the pre-filled schedule

The builder opens on a 30-person software firm in Colorado that sells subscriptions to businesses in the EU and California. Its ad pixel on the marketing site shares visitor data, which is why it keeps California risk assessments; our privacy impact assessment template covers that document. 7 of its 13 periods come from a named rule; the other 6 are its own decisions, each with one line of reasoning.

The example firm's retention schedule
CategoryKept forWhy this long
Customer accounts90 days after the account is closedcontract or claims
Invoices and payment records3 years after the tax return they support is filedset by law
Payroll and employment tax records4 years after the tax becomes due or is paid, whichever is laterset by law
Personnel files of former staff1 year after employment endsset by law
Job applicants not hired1 year after the hiring decisionset by law
Form I-9 (US hires)until 3 years after the date of hire or 1 year after employment ends, whichever is laterset by law
Support tickets and emails24 months after the ticket is closedour decision
Newsletter listuntil the person unsubscribes or withdraws consentconsent
Product usage analytics14 months after the event is recordedour decision
Server and security logs90 days after the log line is writtenour decision
Privacy request records24 months after the request is closedset by law
Risk assessments (California)as long as the processing continues or for five years after the completion of the risk assessment, whichever is laterset by law
Trade-show leadsnot setour decision
Example answers as pre-filled. Rules read 22 Oct 2026. Information, not legal advice.

One line is left unfinished on purpose. The trade-show leads have no purpose and no period, the most common gap in a real schedule: data collected by one team and never claimed by anyone. The builder flags it and the result reads 12 of 13. Give it a purpose (“follow up with people who asked for a demo”) and a short period from the event, and it is ready.

Two lines also feed the firm’s request handling. Request records are kept for at least the 24 months California asks for, and our DSAR deadline calculator gives the dates those records should show. Deleting on schedule also shrinks what a subject access request has to search.

Jurisdiction notes

EUCA

EU: the GDPR

Storage limitation (Art. 5(1)(e)) is the rule; Art. 5(2) makes the business able to show it follows it. The period, or the criteria for it, goes in the notice whether the data came from the person (Art. 13(2)(a)) or from somewhere else (Art. 14(2)(a)), and in the record of processing where possible (Art. 30(1)(f)). Once data is no longer needed for its purpose, a person can ask for it to be erased (Art. 17(1)(a)), unless keeping it is needed to meet a legal obligation (Art. 17(3)(b)) or for legal claims (Art. 17(3)(e)). Those two exceptions are what the “set by law” lines and the hold clause rest on. Processor contracts must make the processor delete or return the data at the end of the service, so the schedule reaches into the data processing agreement too.

California: the CCPA and its regulations

The notice at collection must say how long each category is kept, or the criteria, and the business may not keep personal information for longer than is reasonably necessary for the purpose it disclosed (Civ. Code § 1798.100(a)(3); regs § 7012(e)(4)). Request records are kept for at least 24 months (§ 7101(a)), but the regulations add that a business is not required to keep personal information only to answer a future request (§ 7101(e)). A risk assessment must record how long each category is kept (§ 7152(a)(3)(B)) and is itself kept while the processing continues or five years after completion, whichever is later (§ 7155(c)). For businesses that owe a cybersecurity audit, the audit looks at retention schedules and disposal (§ 7123(c)(16)).

Other US states

The newer state privacy laws carry their own data-minimisation and notice rules. Check the ones that reach you with which privacy laws apply, then read their texts through our guide to the US state privacy laws before you rely on this schedule there.

Questions

Does the GDPR say how long I can keep personal data?

No. It sets no number of years. Article 5(1)(e) says data that identifies people is kept no longer than the purpose needs, and Recital 39 asks the controller to set time limits for erasure or for a periodic review. The numbers in your schedule come from your purposes and from other laws, such as tax and employment rules.

What if I cannot give a fixed period?

Give the criteria instead. GDPR Articles 13(2)(a) and 14(2)(a) and California’s § 1798.100(a)(3) each accept “the criteria used to determine that period” where a period is not possible. In the builder, choose “until an event” and name it: “until the person unsubscribes” is a criterion; “as long as needed” is not.

Can we keep data just in case we need it later?

Not as a purpose of its own. Once data is no longer needed for the purpose it was collected for, the GDPR lets the person ask for erasure (Art. 17(1)(a)), and California caps keeping at what the disclosed purpose reasonably needs. Keeping records for a known claim, investigation or legal duty is different: that is what the hold clause and the “set by law” lines cover.

Do deletions have to reach our backups?

Neither law text mentions backups. The approach this template writes is common: backups are not edited record by record; deleted data drops out as each backup copy expires on its own cycle, and is never restored into live systems. State your backup cycle in the schedule as its own line so the longest real period is visible.

How long should we keep records of privacy requests?

Under the CCPA regulations, at least 24 months (§ 7101(a)), with the date, nature and manner of the request and how it was answered (§ 7101(b)). The record is about the request; it is not a reason to keep the person’s other data, which § 7101(e) says a business need not keep only to answer a request.

Is a written retention policy required?

Neither law names a document called a retention policy. But the GDPR expects you to be able to show you meet storage limitation (Art. 5(2)) and to list erasure time limits in your record where possible (Art. 30(1)(f)), and California expects the periods in your notice. A written schedule is the simplest way to do all three from one place. Information, not legal advice.

Related