The number one question we hear from recruiters who want to record interviews: "Can I get in trouble for this?" The fear is real, but so is the confusion — consent laws are a patchwork of federal requirements, state statutes, and international regulations that don't always agree with each other.
This guide cuts through the noise. We'll cover the federal baseline, the one-party vs. all-party consent distinction that matters most for day-to-day recruiting, what happens when your candidate is in a different state, how GDPR applies to remote interviews with overseas candidates, and a practical compliance checklist you can hand to your TA team. At the end is a quick reference table for the ten states where the most hiring happens.
The Federal Baseline: The Wiretap Act
Federal law starts with the Electronic Communications Privacy Act (ECPA), also known as the federal Wiretap Act (18 U.S.C. § 2511). At the federal level, recording a phone or electronic conversation is legal if at least one party to the conversation consents — and that party can be you, the recruiter. This is the one-party consent rule at the federal level.
So under federal law alone, a recruiter recording their own interview call without informing the candidate is permissible. But federal law is the floor, not the ceiling. States can — and frequently do — require more. The relevant standard is whichever law is most protective for the parties involved.
One-Party vs. All-Party Consent: What It Means in Practice
In one-party consent states, only one participant in the conversation needs to consent to the recording — and the recorder counts as a party. If you're the interviewer and you're recording, you've already consented. You don't need to tell the candidate.
Even in one-party states, best practice is to inform candidates at the start of the interview. It eliminates ambiguity, builds trust, and protects you if the candidate turns out to be in an all-party consent state.
All-party consent states (sometimes called "two-party" states, though it applies to all parties) require that everyone on the call knows and agrees to being recorded. Recording without this consent can be a criminal violation — not just a civil one.
California's statute (Penal Code § 632) is the strictest and most frequently litigated. If a candidate is calling from California and you record without their knowledge, you've potentially committed a misdemeanor — regardless of where your company is headquartered.
Cross-State Interviews: What Law Governs?
This is the question that trips up most recruiting teams. When your interviewer is in Texas (one-party state) and the candidate is in California (all-party state), which law applies?
Courts generally apply the law of the state with the most protective standard when there's a conflict between jurisdictions. In practice: if either party is in an all-party consent state, treat the call as requiring all-party consent. This is the safest and most defensible approach. It also turns out to be operationally simple — if you always inform candidates that the call will be recorded and get verbal acknowledgment, cross-state compliance is automatic.
Some put a bot in the meeting. Others let you manage consent your way.
International Interviews and GDPR
Remote work has made international interviews a daily occurrence for many TA teams. If you're interviewing candidates based in the EU or UK, GDPR applies — regardless of where your company is located.
Lawful basis. You need a documented legal basis for recording. In a hiring context, "legitimate interest" often applies — but you must conduct a balancing test showing your interest doesn't override the candidate's privacy rights. Alternatively, explicit consent at the start of the call is a clean basis that's easy to document.
Inform the candidate. Under GDPR Article 13, you must tell candidates at the time of data collection what you're recording, why, how long you'll keep it, and who may access it. A one-sentence verbal disclosure is insufficient — candidates should receive written notice, typically in the interview invite or scheduling confirmation.
Data retention policy. GDPR prohibits storing personal data longer than necessary. Define how long interview recordings are retained (30, 60, or 90 days is common for candidates who aren't hired) and enforce it. "We keep everything" is not a valid retention policy.
Quick Reference: Consent Requirements by State
The table below covers the ten states that account for the majority of U.S. hiring volume. "All-party" means everyone on the call must consent. "One-party" means the recorder's own consent is sufficient under state law. Always verify current law with counsel — statutes change.
| State | Consent Type | Key Statute | Criminal Penalty? | Practical Guidance |
|---|---|---|---|---|
| California | All-party | Penal Code § 632 | Yes (misdemeanor) | Always disclose; verbal acknowledgment minimum |
| Texas | One-party | Penal Code § 16.02 | Civil only | Legal to record; disclosure still best practice |
| New York | One-party | Penal Law § 250.00 | Civil only | Legal to record; disclose as best practice |
| Florida | All-party | F.S. § 934.03 | Yes (felony) | Strong consent requirement; document it |
| Illinois | All-party | 720 ILCS 5/14 | Yes (felony) | Get consent before recording; document it |
| Pennsylvania | All-party | 18 Pa. C.S. § 5703 | Yes (felony) | Treat as strictest standard; written consent recommended |
| Ohio | One-party | O.R.C. § 2933.52 | Civil only | Legal to record; disclose as best practice |
| Georgia | One-party | O.C.G.A. § 16-11-62 | Civil only | Legal to record; disclose as best practice |
| North Carolina | One-party | N.C.G.S. § 15A-287 | Civil only | Legal to record; disclose as best practice |
| Washington | All-party | RCW § 9.73.030 | Yes (felony) | Explicit consent required; document it |
Practical Compliance Checklist for TA Teams
Legal requirements aside, building a consistent consent workflow protects your company and builds candidate trust. Here's what a solid compliance process looks like in practice.
Interview Recording Compliance Checklist
How QuickScribe Handles Consent
Most recording tools put a bot in the meeting — a visible participant that joins your Zoom or Teams call automatically. The problem: that bot records regardless of whether the recruiter informed the candidate, regardless of which state the candidate is calling from, and regardless of whether anyone mentioned recording at all. The consent workflow becomes an afterthought, not a built-in step.
QuickScribe doesn't use a bot. Recording happens through system audio capture — the recruiter starts the recording, which means the recruiter owns the consent moment. The workflow enforces disclosure because the recruiter has to initiate the recording consciously, typically after the verbal disclosure at the start of the call.
For TA teams that need documented consent, QuickScribe integrates with your scheduling flow — consent acknowledgment can be built into the interview invite before the candidate ever picks up the phone. No bot, no ambiguity, no liability from forgetting the script.
If you're evaluating tools specifically on compliance workflows, the buyer's guide walks through six evaluation criteria — compliance is criterion #3. For the ROI math on what compliant recording actually saves your team, the ROI guide lays it out with real numbers. And if you want a side-by-side comparison of how tools differ on consent handling, the compare page has it.
Time saved on notes, compliance risk reduced, cost per hire. The ROI calculator runs the numbers for your team size.
The Simple Answer
Recruiters who want to record but fear legal exposure almost always overcomplicate this. The practical answer for 99% of hiring situations:
Always tell the candidate you're recording. Always ask if that's okay. This single habit satisfies one-party and all-party consent requirements in every U.S. state, covers you on cross-state calls, and is a meaningful step toward GDPR compliance for international hires. It takes five seconds and eliminates the legal ambiguity entirely.
The companies that run into trouble aren't the ones that recorded — they're the ones that recorded silently, stored everything indefinitely, and had no policy when someone asked. Build the consent habit, define your retention policy, use a tool that supports your workflow rather than working around it, and you're in better shape than most TA teams operating today.
For structured interview best practices that work alongside your recording workflow, see the scorecard templates guide — consistent scorecards plus accurate transcripts is the combination that actually improves hiring decisions.