Job applicant privacy is the set of obligations an employer owes to candidates regarding the personal information collected during recruiting. It is a relatively new area of exposure for most employers, because candidates were historically treated as outside the scope of privacy frameworks — and in California, that changed on January 1, 2023.
The practical consequence is that people an employer never hired, and has no ongoing relationship with, may now hold enforceable rights over data the employer is still holding.
For covered California employers, applicants hold substantially the same rights as consumers: to know what personal information is held and how it is used, to have inaccurate information corrected, to request deletion subject to exceptions, and to limit the use of sensitive personal information.
A notice at collection is generally required at or before the point of collection, describing the categories collected, the purposes, and the retention period or the criteria for determining it. Many employers still operate career pages with no such notice, or with a customer-facing privacy policy that never contemplated candidates.
The obligation that causes the most operational difficulty is the right to know. Answering it requires enumerating every place a candidate's data resides — and applicant data is characteristically scattered across an applicant tracking system, individual hiring managers' inboxes, referral threads, interview notes in personal documents, and spreadsheets built to track a search.
Employers face genuinely competing obligations. Anti-discrimination record-keeping rules require retaining application and selection records for defined periods. Privacy principles push toward not keeping data longer than necessary. Recruiting teams want to retain promising candidates for future openings.
The defensible position is a documented schedule that satisfies the mandatory minimum, sets an outer limit, and applies deletion automatically. Retaining candidates for future consideration is legitimate, but it should be a decision with a stated period — ideally disclosed to the candidate — rather than the byproduct of nobody ever deleting anything.
Indefinite retention is the weakest posture available. It maximizes breach exposure, makes deletion requests difficult to honor, and is hard to justify under any privacy framework.
Privacy exposure begins before storage, at the point of collection. Several categories create risk simply by being requested.
Salary history inquiries are restricted or prohibited in a number of jurisdictions, California among them. Questions touching protected characteristics — age, marital or family status, national origin, disability, religion — create discrimination exposure independent of any privacy rule, and application forms designed years ago sometimes still contain them.
Criminal history timing is separately regulated. Many jurisdictions restrict when it may be requested, and California generally requires waiting until after a conditional offer for covered employers, followed by an individualized assessment before any adverse decision.
Demographic data collected for reporting purposes should be voluntary, separated from the application materials the hiring team sees, and used only for its stated purpose.
Interview notes occupy an awkward space. They are records — potentially discoverable in a discrimination claim — but they typically live in notebooks, personal documents, and email rather than in any managed system.
That informality creates two problems at once. The notes are not retained properly when they would help the employer, and they are not deleted when they should be. They also frequently contain observations that read badly out of context, because interviewers writing privately are less careful than they would be writing into a system.
Keeping notes inside the applicant tracking system, and training interviewers on what belongs in an evaluation record, addresses both the privacy exposure and the discrimination exposure simultaneously.
Employers increasingly use automated tools to screen or rank candidates. This is an area of active regulatory attention, with requirements emerging around notice, bias auditing, and in some jurisdictions the ability to request alternative evaluation.
Employers using such tools should confirm current obligations in the jurisdictions where they recruit, understand what the tool actually evaluates, and be able to explain the basis of a decision if asked. A vendor's assurance that a tool is unbiased is not a substitute for the employer's own diligence, since the obligation remains with the employer.
Testing the rights-request process matters more than writing it. An employer that has never attempted to locate and produce everything held about one candidate will discover the gaps during a live request, on a statutory clock.
Employer's Guardian helps employers structure recruiting records, notices, and retention through onboarding documentation compliance.
This article provides general educational information, not legal advice. Requirements vary by jurisdiction and change over time. Consult qualified counsel before changing recruiting practices.