Skip to content

Consulting and recruiting

How long should recruiting firms keep candidate data?

By SourceX Editorial · Reviewed by Noah Loul ·

Short answer

Recruiting firms should keep candidate data at least as long as the longest legal minimum that applies to each record type, and no longer than the purpose stated in their privacy notices. Set the period per record type rather than for the whole ATS, and let a pending charge, lawsuit or audit suspend deletion until it ends.

Key takeaways

  • Candidate data retention is set per record type: applications, interview notes, background checks, EEO data and payroll records follow different rules.
  • Federal anti-discrimination recordkeeping rules set minimums, and federal contractors may face longer ones under OFCCP rules.
  • Privacy laws push the other way, so keeping every resume forever carries its own risk.
  • A pending discrimination charge, lawsuit or audit generally suspends deletion for the records involved.
  • When retention ends, delete or properly de-identify; never extend retention of personal data in order to license it.

What sets the candidate data retention period?#

The candidate data retention period is set by two forces pulling in opposite directions: legal minimums that require you to keep certain hiring records, and privacy rules that expect you to keep personal information no longer than needed. A sound policy finds the window between them for each record type.

Minimums come mainly from federal anti-discrimination recordkeeping rules, federal contractor rules, wage and hour law, background check rules and state employment laws. Upper limits come from privacy laws, your own privacy notices, client contracts and the practical risk old data creates in a breach or a dispute.

Staffing firms carry a double load. They hold applicant records like any employer, and for temporary workers on their own payroll they also hold employee records such as timesheets, payroll and onboarding documents.

Retention by record type#

Retention rules differ by record type, so a single ATS-wide rule is almost always wrong. The table shows where minimums may come from and what to confirm with counsel. It deliberately gives no periods, because the right period depends on your firm's size, contracts, client programs and the states where candidates live.

Retention by record type
Record typeRules that may set a minimumWhat to check
Applications and resumes for a specific openingEEOC recordkeeping under Title VII, the ADA and the ADEA; OFCCP rules for federal contractorsWhether you or your client is the federal contractor, and state rules
Unsolicited resumes and talent pool profilesUsually privacy law and your own notices rather than a hiring minimumWhat candidates were told about how long you keep them
Interview notes, scorecards and client feedbackSame rules as the application they relate toWhether notes sit in the ATS, in email or in a client VMS
Assessments and test resultsAnti-discrimination recordkeeping and any test validation recordsAssessment vendor contracts and where results are stored
Background check reportsFCRA disposal rules and state consumer reporting lawsSecure disposal method and access limits
EEO self-identification dataEEOC and OFCCP rules, kept apart from hiring filesRestricted access and separate storage
Form I-9 and onboarding documents for placed workersFederal I-9 rules, which use their own retention formulaWhich entity is the employer of record
Timesheets and payroll for temporary workersFLSA recordkeeping and state wage lawsWhether payroll lives in a separate back-office system
Video interview recordingsHiring recordkeeping plus state laws on recordings and biometricsConsent records and the video vendor's retention settings

Federal minimums and state caveats#

Federal minimums for candidate data come from several overlapping rule sets. EEOC regulations require covered employers to keep applications and other hiring records for a minimum period, a staffing firm may be covered both as an employer and as an employment agency, and federal contractors and subcontractors may have longer obligations under OFCCP rules. Check the current text of each rule with counsel rather than relying on a summary, including this one.

Two further principles apply across the board. When a discrimination charge, lawsuit or government audit is pending, the records relevant to it generally must be kept until the matter is fully resolved, whatever the normal schedule says. And background check reports carry their own disposal requirements under the FCRA, which address how records are destroyed as well as when.

States add their own layer. Some set longer periods for employment records, some regulate recordings, biometrics or automated hiring tools, and state privacy laws such as the CCPA may give California applicants rights to know about and delete their data. Because staffing firms recruit across state lines, map where your candidates live, not only where your offices are.

Why keeping everything forever is also a risk#

Keeping every candidate record forever creates risk because old personal data still counts in a breach, still answers to access and deletion requests, and can be pulled into disputes long after it stopped being useful. Privacy laws such as the GDPR, for any candidates in the EU, and the CCPA expect a defined purpose and retention period for personal information.

Old records are also less accurate. A resume from many years ago describes a different person in a different market, and recruiters who rely on it waste time on stale contact details and outdated skills. Deleting on schedule is good hygiene as well as good compliance.

Writing a retention schedule your ATS can enforce#

A retention schedule works only if your ATS and back-office systems can apply it, so write it in terms the software understands: record type, trigger event and action. A policy that lives only in a handbook tends to be ignored until a request or a breach forces the issue.

  • Classify records into the types in the table above, including those held outside the ATS.
  • Set a trigger event for each type, such as application date, last candidate activity or end of placement.
  • Agree each period with employment and privacy counsel and record the reason behind it.
  • Configure automated purges or scheduled review lists in the ATS and the payroll system.
  • Add a legal hold flag that stops deletion for records tied to a charge, lawsuit or audit.
  • Cover copies outside the ATS: email, shared drives, VMS downloads and vendor backups.
  • Log deletions so you can show the schedule was followed.

What happens to value when the retention period ends?#

When the retention period ends, personal candidate data should be deleted or de-identified, and that decision should never be bent to keep records for licensing. De-identification has to meet the standard of the laws that apply, which counsel should confirm; removing names alone is rarely enough when work history, employers and locations remain.

Some records keep value without any candidate identity. Job orders, the sequence of submission stages, the time between steps, client feedback categories and placement outcomes can describe how recruiting work flows without describing a person. Those workflow records can support internal benchmarks and, after rights and privacy review, may be licensed for AI development.

Illustrative: a deletion request arrives while a charge is pending#

Illustrative: a fictional staffing firm with clerical and light industrial desks receives a deletion request from a California applicant who was not placed. Its privacy lead finds the applicant's profile, resume, interview notes and a background check report in the ATS, plus copies in recruiter email and a client's VMS.

Counsel confirms that an EEOC charge filed by a different applicant for the same opening is still open, so records for every candidate on that requisition, including this applicant's application, interview notes and scorecards, sit under a legal hold. The firm deletes only what counsel confirms no hold or minimum covers, such as stray copies in recruiter email, explains in writing what it must keep and why, and sets the held records to return to the normal schedule once the matter is fully resolved.

The episode also exposes a gap: the ATS had no legal hold flag. The firm adds one, along with trigger-based deletion rules, so the next request can be answered from the system rather than by searching recruiters' inboxes.

How SourceX treats candidate records#

SourceX treats candidate personal data as material to remove or exclude, not as the asset being licensed. Any review starts from records inside the firm's retention schedule, and preparation removes names, contact details and other identifying details; resumes and background check material are typically left out altogether.

Rights and privacy questions are handled within the SourceX five-step transaction: Supply, Rights, Preparation, Approval and Delivery. The SourceX Evidence Packet records the privacy record and permitted use for each package, and the laws that may apply are assessed deal by deal with the firm's counsel.

Frequently asked questions

Does a candidate's deletion request override our legal minimums?

Generally no. Privacy laws that grant deletion rights usually include exceptions for records you must keep under other laws or for legal claims. Respond to the request, delete what you can, and explain what you must retain and why. Counsel should review your response template, because the exceptions differ from law to law.

Can we keep resumes if a candidate joined our talent pool?

Joining a talent pool can support keeping a profile for future roles, but only for the purpose and period your notice described. Confirm interest periodically and delete profiles that go stale. A talent pool is not a reason to keep every resume indefinitely.

Do email, exports and backups count?

Yes. Copies of candidate data in email, shared drives, exported spreadsheets and vendor backups are part of what you hold. Your schedule should say how each is handled, accepting that backups may expire on their own cycle rather than being edited record by record.

What about candidates outside the US?

Candidates in other countries may bring their own laws with them, such as the GDPR for people in the EU. Those laws can set stricter purpose and retention limits than US rules. If you recruit internationally, include each region in your schedule and confirm the approach with counsel.

Who is responsible for candidate data inside a client's VMS?

Records held in a client's vendor management system are usually governed by the client's or MSP's terms, not by your schedule alone. Keep your own copies under your schedule and follow the program agreement for anything held inside the VMS.

Related resources

See if your company qualifies

A short company assessment. No data uploads are needed.

See if you qualify