Skip to content
Compliance7 min read

How Long to Keep Candidate Data

How long to keep resumes, scores and interview notes under US rules and the GDPR, what to delete, and a sample retention schedule for hiring teams.

By the HireRabbit.AI team · Published · Last updated

An HR manager sorts candidate folders between a locked filing cabinet with a calendar on top and a shredder, while a colleague checks a schedule on a laptop
On this page
  1. Why candidate data retention cuts both ways
  2. How long to keep resumes under US federal rules
  3. GDPR recruitment data: storage limitation and purpose
  4. AI hiring tools create records of their own
  5. What to keep and what to delete
  6. A worked example retention schedule
  7. Deletion in practice
  8. How this maps to HireRabbit.AI

Without a retention rule, candidate data piles up. Resumes, notes, scores and recordings sit in the ATS, inboxes and spreadsheets, and nobody deletes anything.

This guide covers what US federal rules require you to keep, what the GDPR requires you to delete, the records AI tools add, and a sample schedule.

Why candidate data retention cuts both ways

Keep too little and you cannot defend a decision. If a rejected applicant files a discrimination charge, you need to show what you assessed, against what criteria, and why the person you hired was stronger. A deleted scorecard cannot help you.

Keep too much and every old file becomes risk. A breach of five years of applicant files exposes people who applied once, years ago. In the EU and UK, keeping that data without a reason itself breaks data protection law.

The goal is a schedule: each type of record, kept for a stated period, for a stated reason, then deleted.

How long to keep resumes under US federal rules

This section is general information, not legal advice. Rules vary by jurisdiction, and state law can set longer periods than federal law. Check your schedule with employment counsel.

EEOC: one year, or longer once a charge is filed

The EEOC's recordkeeping rule at 29 CFR 1602.14 requires employers to keep personnel and employment records, including application forms, for one year from the date the record was made or the personnel action was taken, whichever is later.

Once a discrimination charge is filed, the employer must keep all relevant personnel records until final disposition. That covers records about the person who complained, records about others in similar positions, and the application forms or test papers of every other candidate for the same position. A single charge can freeze the whole requisition.

Under the Age Discrimination in Employment Act, 29 CFR 1627.3 says job applications, resumes and records about a refusal to hire must be kept for one year from the personnel action they relate to, and longer once an enforcement action starts.

One year is a floor, not a target. The EEOC says a charge must generally be filed within 180 calendar days of the discrimination, extended to 300 days where a state or local agency enforces a similar law. A one-year schedule leaves little margin.

Federal contractors: the OFCCP rule is gone

Federal contractors used to follow 41 CFR 60-1.12: two years of retention with 150 or more employees and a contract of at least $150,000, otherwise one year.

That rule no longer applies. The Department of Labor's final rule rescinding the Executive Order 11246 regulations, including all of Part 60-1, took effect on October 26, 2026. Separate Section 503 and VEVRAA rules still exist, and Cooley's September 2026 summary says most Section 503 recordkeeping requirements remain, so contractors should confirm their periods with counsel.

Litigation holds override the schedule

A retention schedule says when you may delete. A litigation hold says you may not. Once you reasonably expect a claim, from a demand letter, a charge or a credible threat, suspend deletion for every relevant record, wherever it sits.

Rule 37(e) of the Federal Rules of Civil Procedure lets a court order measures when electronically stored information that "should have been preserved in the anticipation or conduct of litigation" is lost because a party failed to take reasonable steps. If the court finds intent to deprive the other side, it can presume the lost information was unfavorable. Automatic deletion jobs need an off switch for this reason.

GDPR recruitment data: storage limitation and purpose

The GDPR approaches retention from the other side. Article 5(1)(e) says personal data must be kept in identifiable form "for no longer than is necessary for the purposes" it was collected for. Article 5(1)(b) adds that data collected for one purpose must not be reused in a way incompatible with it.

In recruitment, the purpose is filling a specific role and defending that decision. Once the role is filled and any claim period has passed, that purpose is spent.

Article 13(2)(a) requires you to tell candidates, when you collect their data, how long you will keep it, or the criteria used to set that period. "We keep your data for as long as necessary" names neither, so your candidate privacy notice should state the actual period.

Talent pools need their own basis

Keeping a rejected candidate for future roles is a new purpose, so it needs its own lawful basis and notice.

Consent under Article 6(1)(a): the candidate opts in to being kept on file. Article 7(3) says consent can be withdrawn at any time and that withdrawing must be as easy as giving it.

Legitimate interests under Article 6(1)(f): your interest in filling future roles, weighed against the candidate's rights, with a balancing test on file and a clear way to object.

Whichever basis you use, set a limit. France's data protection authority, the CNIL, in its January 2023 guidance for small businesses, says a candidate's CV and cover letter may be kept in a talent pool for in principle no more than two years from the last contact, provided the candidate has been told.

AI hiring tools create records of their own

If software screens, scores or ranks candidates, its configuration and outputs become part of the record. The AI hiring laws guide tracks these as they change.

New York City Local Law 144 requires a bias audit within one year before an automated employment decision tool is used, and notice to candidates at least ten business days before use. The law also requires information about the type of data collected, its source and your data retention policy, either on your website or within 30 days of a written request. Candidates can ask to see your retention policy.

California's Civil Rights Council regulations on automated decision systems took effect on October 1, 2025. Mayer Brown's summary of the final text says records, including automated decision system data, must be retained for at least four years from the later of the record's creation or the personnel action. That is four times the federal floor, and it reaches data used to customize the tool for your company.

What to keep and what to delete

Keep the records that explain the decision:

  • The application: resume, cover letter and answers to screening questions.
  • Screening scores and reasons: the score breakdown, not just the total, plus the criteria and weights in force on that date.
  • Interview notes and scorecards: each interviewer's independent ratings and evidence.
  • The decision record: who decided, when, and the written reason. The hiring audit trail guide covers how to word a reason that holds up.
  • Selection rates by stage: the funnel data behind an adverse impact analysis, held separately from the hiring team's view.

Delete, or never collect, the rest: duplicate resumes in inboxes, unsolicited photos or ID scans sent before an offer, personal notes outside the system, and one-off exported spreadsheets.

A worked example retention schedule

Here is a schedule for a hypothetical 300-person company that hires in New York City and California and occasionally in France. The longest applicable period wins for each record type.

RecordKeep forClock startsDriver
Unsuccessful applicant file (US)4 yearsRejection decisionCalifornia ADS rules, above the federal 1 year
Unsuccessful applicant file (France)Claim period set by counselRejection decisionGDPR storage limitation
Talent pool profile (France)2 years maxLast contactCNIL guidance, with notice
AI screening configuration and outputs4 yearsLast use on a requisitionCalifornia ADS rules
Bias audit and stage outcome data4 yearsAudit dateNYC LL144 audit cycle, California rules
Interview recordingsSame as applicant fileRejection decisionPart of the decision record
Hired candidate's applicationMoves to the personnel fileStart dateEmployment record rules
Any record under a litigation holdUntil counsel releases itHold noticeFRCP 37(e)

The four-year rows apply only where California's rules reach the hire. The France row is left to counsel on purpose: claim periods differ by country and claim type.

Deletion in practice

Three habits turn a schedule into deletions.

Re-consent the talent pool. Before a profile reaches its limit, ask the candidate whether they want to stay on file. Keep those who say yes, with the new date, and delete the rest. Silence is not a yes.

Chase the copies. Candidate data leaks into attachments, shared drives, exports and integrations. Limiting who can see and export records, as the guide to ATS user permissions describes, keeps copies few. For backups, document how long they rotate, so a deleted record is gone once the last backup holding it expires and is never restored into live use.

Log the deletion. Record what was deleted, when, under which schedule line, and who ran it, without keeping the deleted data itself. Under Article 5(2), you must be able to demonstrate that you follow the storage principle, and a deletion log is how you do it.

How this maps to HireRabbit.AI

HireRabbit.AI keeps the decision record together. Each single-candidate move between stages carries a written reason, stored beside the scores, interview reports and panel scorecards behind it, and every overall resume score shows its breakdown.

For deletion, admins can delete candidates and jobs inside the product, so your schedule decides when and an admin carries it out. Uploaded job description files are read and then discarded. Our AI provider does not train on resumes or interviews, and zero data retention is on. A data processing agreement is available for the GDPR, India's DPDP Act and similar laws.

The security page covers access, deletion and data handling in full.

Put this into practice.

Free during invite-only early access. All you need is a work email, and a person reviews every request.