Resume Redaction and Candidate Data Privacy for US Recruiters
US hiring teams handle resumes, background check reports, Form I-9 records, and AI screening outputs - each carrying distinct privacy obligations under the FCRA, CCPA, EEOC law, and state ban-the-box statutes. This guide covers what to redact, when, and why.
By RedactProof Editorial Team Β· May 1, 2026
This article is for general informational purposes only and does not constitute legal advice. Privacy and employment law obligations vary significantly by state and change over time. Consult a qualified employment attorney for advice specific to your organization's circumstances.
Hiring documents are some of the most data-dense files an HR team handles. A single resume can contain a candidate's home address, personal email, phone number, and links to social profiles. Add in background check reports, Form I-9 verification records, and interview notes, and you have a collection of personal data that touches federal employment law, state privacy statutes, and EEOC anti-discrimination requirements simultaneously.
Most recruiters think about redaction narrowly - stripping contact details from resumes before forwarding them to hiring managers. That's a reasonable starting point, but it's not the full picture. The privacy obligations that apply to US hiring data are broader, more fragmented by state, and increasingly enforced.
The documents that carry the most risk
Resumes sit at the lower end of the risk spectrum. A missed personal email address is an annoyance - the candidate might get contacted directly, circumventing the agency's placement fee. Not ideal, but not a regulatory breach.
Background check reports are a different matter. These are governed federally by the Fair Credit Reporting Act (FCRA), which applies whenever an employer uses a Consumer Reporting Agency (CRA) to obtain a background screening report. The FCRA imposes strict handling requirements: the report must be provided to the candidate before any adverse action is taken, along with a copy of their rights under the statute. Sharing a background check report more widely than necessary - with a hiring manager who shouldn't see it, for example, or forwarding it to a client in an agency placement - creates exposure under both the FCRA and state equivalents.
Form I-9 records (used for employment eligibility verification under E-Verify) contain document numbers from passports, Permanent Resident Cards, or other identity documents. Employers are generally required to retain completed I-9 forms for three years from the hire date or one year after employment ends, whichever is later. These records should not be co-mingled with the main personnel file, and access should be restricted. When I-9 documentation is shared internally for audit purposes or transferred to a third-party employer-of-record, only the minimum necessary information should travel with it.
Offer letters and compensation documents are the fourth category worth flagging. As pay transparency laws take hold across California, Colorado, New York, Washington, Illinois, and several other states, compensation data in hiring files has become more sensitive - both because it's required to be disclosed in job postings and because its unauthorized disclosure can create pay equity liability.
EEOC law and the bias-blind resume
A resume contains more information about protected characteristics than most hiring managers consciously register. Names that indicate ethnicity, addresses in specific ZIP codes, graduation years that imply age, gaps that might suggest disability or caregiving, school affiliations that suggest religion or socioeconomic background - none of this should influence a hiring decision under Title VII of the Civil Rights Act, the Americans with Disabilities Act (ADA), or the Age Discrimination in Employment Act (ADEA).
The EEOC's Strategic Enforcement Plan 2024-2028 lists recruitment and hiring practices - including AI-assisted screening - as a priority enforcement area. The agency has been actively issuing subpoenas to employers to obtain hiring data and documents as part of discrimination investigations. What you retain, and in what form, is material.
Blind shortlisting addresses this directly. The approach is simple: before resumes reach the hiring manager for the initial screening stage, identifying information is removed - name, address, photo, links to personal social profiles, and any other data that could reveal characteristics irrelevant to the role. What remains is qualifications, employment history, and skills.
Manual editing in Word doesn't reliably achieve this. A candidate's name appears in the filename, in the document header, in body text, and sometimes in the document metadata. Deleting it from one location while leaving it in others is a common oversight. RedactProof applies pixel-burn redaction - permanently destroying the text layer, not just obscuring it - across all instances, including any OCR layer in scanned documents. Documents are processed in your browser and are not uploaded to our servers.
Criminal history and ban-the-box compliance
As of 2025, 37 states and the District of Columbia have some form of ban-the-box law restricting when employers can inquire about criminal history. Fifteen states - including California, Illinois, Colorado, and Massachusetts - apply these restrictions to private employers. In California, criminal history inquiries are prohibited until after a conditional job offer, for any employer with five or more employees. In New York, state law combined with the NYC Fair Chance Act requires employers to weigh seven specific factors before any adverse action based on criminal history, and a written analysis of each factor is required.
Background check reports that include criminal history are particularly sensitive under this framework. The sequence matters: asking too early violates the ban-the-box statute. Acting on a report without completing the FCRA pre-adverse action process - providing the candidate with the report and a waiting period to dispute it before the decision is finalized - violates the FCRA. In practice, many hiring teams get the order wrong under time pressure.
When these reports need to be shared internally (with a second hiring manager, HR, or legal), only the personnel with a clear need to see them should receive unredacted versions. For external sharing - with a staffing agency client, for example - criminal history data generally should not travel at all without explicit legal basis.
State privacy laws and candidate data
The California Consumer Privacy Act (CCPA), as amended by the California Privacy Rights Act (CPRA), applies in full to employment and recruitment data as of January 1, 2023, when the prior employment exemption sunset. The California Privacy Protection Agency (CPPA) has since made clear that candidate data is in scope. Employers covered by the CCPA must provide candidates with a privacy notice at collection, respond to access and deletion requests, and limit data sharing to purposes the candidate would reasonably expect.
California AG enforcement activity in 2025 has included focus on employment services platforms and applicant tracking systems. Penalties run up to $7,500 per intentional violation.
Approximately 19 other states now have comprehensive consumer privacy laws in force or taking effect through 2025-2026, including Virginia (VCDPA), Colorado (CPA), Connecticut (CTDPA), Texas, Florida, and others. Most include employment data within scope or are moving in that direction. The practical implication for HR teams operating across multiple states: candidate data should be treated as privacy-regulated regardless of where the candidate is located, because the state of the employer or the processing location may trigger obligations.
Redaction is part of the data minimization picture here. Before a resume or candidate file is forwarded to a client, a hiring manager in another state, or a background screening vendor, review what personal data is actually included and whether all of it is necessary for the recipient's purpose. Contact details, SSN fragments in document headers, and compensation history that appears in a candidate's previous offer letter are common examples of data that shouldn't travel beyond the initial collection point.
AI screening tools and NYC Local Law 144
If your organization uses automated tools to screen, rank, or select candidates - including ATS resume scoring, AI-driven interview analysis, or algorithmic shortlisting - you may have additional compliance requirements on top of the EEOC and privacy rules above.
NYC Local Law 144, which took effect July 5, 2023, requires employers and employment agencies using Automated Employment Decision Tools (AEDTs) in New York City to commission independent bias audits of those tools on an annual basis and to publish a summary of the results. Candidates must be notified that an AEDT is being used.
A December 2025 audit by the New York State Comptroller found that the NYC Department of Consumer and Worker Protection's enforcement of Local Law 144 had been largely ineffective - 75% of test complaints were misrouted. The DCWP has committed to remediation, and enforcement observers expect a more active posture in 2026, with civil penalties of up to $1,500 per violation per day.
Illinois has its own layer: the Illinois AI Video Interview Act requires employers to notify candidates before using AI to analyze video interviews, obtain consent, and - on request - explain the characteristics the AI evaluated. A separate amendment to the Illinois Human Rights Act (HB 3773, signed 2024, taking effect January 2026) bars employers from using AI in hiring decisions in ways that produce discriminatory outcomes. If your recruiting process touches Illinois applicants, the combination of state AI law, ban-the-box requirements, and CCPA-equivalent protections elsewhere creates a compliance stack that warrants specific attention.
The data generated by AI screening tools - scores, rankings, analysis outputs - can itself constitute personal data under state privacy laws. Retaining it longer than necessary, sharing it with unauthorized parties, or including it in candidate files that are then forwarded without review creates unnecessary exposure.
Practical redaction workflow for US recruiting teams
The documents that most commonly need redaction before onward sharing, and what to remove from each:
Resumes forwarded to clients or hiring managers: Remove name, home address, personal email, direct phone number, links to social profiles (LinkedIn URL often encodes the name), and any photo. Preserve employment history, education, skills, and qualifications.
Background check reports shared internally: Restrict to personnel with a documented need. Do not forward to clients. If excerpting for a hiring committee, redact SSN, date of birth, and any data not relevant to the specific decision being made.
Form I-9 and E-Verify records: Store separately from the main personnel file. When sharing for audit purposes, redact document numbers and expiry dates to the minimum necessary for the audit. Do not send I-9 scans to unauthorized parties under any circumstances.
AI screening outputs and ATS data exports: Before any data export from your ATS is shared externally, review whether scores, demographic flags, or other inferred data fields are included. These should generally be stripped before the candidate file leaves the system.
For teams processing any volume of hiring documents, manual editing is both time-consuming and inconsistent. RedactProof's AI detection identifies 40+ types of personal information automatically - including SSNs, dates of birth, addresses, and phone numbers - across PDFs and scanned documents. Bulk mode processes batches rather than file by file. Tamper-evident verification certificates provide an auditable record that the document was redacted and has not been modified since. Try it free at redactproof.com.
Frequently Asked Questions
Does the FCRA require us to redact background check reports before sharing them?
Which states have ban-the-box laws that affect private employers?
Does CCPA apply to job applicants and candidates?
What is NYC Local Law 144 and does it apply to our recruiting process?
What personal data on a resume should we redact before sending it to a client?
How should Form I-9 records be handled and stored?
See it in action
Upload a document and let RedactProof find the sensitive data. Free to start, no card required.