Call Recording Laws by State (2026): All 50 States

Not legal advice. This guide is general information, not legal advice. Confirm the rule for your situation with a licensed attorney before you rely on it.

New to the terminology? Read our plain-English explainer on one-party vs two-party consent states first, then come back here for the state-by-state detail.

This resource is structured for fast lookup and deep reference. Use the state directory table below to check the rule for any state you sell into. For the ten highest-volume B2B sales markets (California, New York, Texas, Florida, Illinois, Pennsylvania, Massachusetts, Washington, Georgia, Virginia) we provide full compliance write-ups including statute citations, fines, exceptions, federal interaction, and practical guidance for sales teams. The remaining 40 states and DC include consent type, statute, and a one-line summary for fast classification. If you operate across multiple states, jump to the compliance playbook for a step-by-step deployment plan.

Verification note: Statute citations, fine amounts, and case references are drawn from publicly available sources and standard legal references current as of 2026. Before relying on any specific figure (especially civil damage amounts, sentencing maxima, and individual case citations), verify against the primary statute text and consult counsel for your jurisdiction. Laws change and individual circumstances vary. The authoritative sources are listed at the end of this guide.

One-party consent (38 states plus DC)

In one-party consent jurisdictions, only one participant in the call must consent to the recording. Because the rep is a participant, their own consent is legally sufficient under both federal law (18 U.S.C. 2511(2)(d)) and state law. Disclosure is not legally required, although it remains the recommended best practice. Examples include Texas, New York, Georgia, Ohio, and most southern and midwestern states.

All-party (two-party) consent (12 states)

In all-party consent states, every participant on the call must consent before recording begins. The phrase "two-party consent" is the older term and is technically inaccurate when more than two people are on a call; "all-party consent" is the correct legal terminology. The 12 commonly cited all-party consent states are California, Delaware, Florida, Illinois, Maryland, Massachusetts, Michigan, Montana, Nevada, New Hampshire, Pennsylvania, and Washington. For a side-by-side breakdown of the two regimes, see one-party vs two-party consent states.

Edge cases worth knowing

A few states do not fit neatly into either list, so the count of 12 comes with footnotes:

• Connecticut is one-party under its criminal statute, but Conn. Gen. Stat. 52-570d makes recording a phone call without everyone's consent a civil wrong. It is not counted in the 12, but disclose on every Connecticut call.
• Oregon is one-party for phone calls, but ORS 165.540 requires that all parties be informed before an in-person conversation is recorded. It is not counted in the 12.
• Michigan is counted in the 12 because its statute reads all-party, but a 1982 Court of Appeals ruling (Sullivan v. Gray) lets participants record their own conversations. Treat it as all-party until the state supreme court settles the point.
• Nevada is counted in the 12 for phone calls (Lane v. Allstate, 1998); in-person conversations are one-party.
• Delaware is counted in the 12: its wiretap statute has a participant exception, but its separate privacy statute requires consent of all parties.

The safe operational rule for every edge case: treat the call as all-party and disclose at the start.

The federal Electronic Communications Privacy Act (ECPA), codified at 18 U.S.C. 2511, is the floor for US call recording rules. ECPA permits recording when at least one party to the conversation consents, making the federal standard one-party consent. Violations carry up to five years imprisonment plus civil damages. The one-party rule itself sits in Section 2511(2)(d). Critically, ECPA does not preempt stricter state laws, so states remain free to require all-party consent. When state law is more privacy-protective than federal law, state law governs.

This is why California Penal Code 632 controls calls into California even though federal law alone would permit one-party recording. For interstate calls, most courts apply the law of the state with the strongest protective interest, which means an all-party state will override a one-party state whenever any participant is located in the stricter jurisdiction. The operational implication: your prospect's location, not your rep's, determines the applicable rule.

Every US jurisdiction, its consent rule, the primary statute, and a one-line practical note. Federal law (18 U.S.C. 2511(2)(d)) sets a one-party floor everywhere; the 12 states marked all-party are stricter. A sales rep on the call is a participant. The same table appears in our one-party vs two-party consent states guide.

These ten states represent the highest volume of B2B sales activity in the United States. We provide a full compliance write-up for each, including statute citation, fines, exceptions, federal interaction, and practical guidance for multi-state sales teams.

California (CA): all-party

All-party consent under California Penal Code 632. Every participant must consent before recording. The most aggressively litigated recording statute in the US.

• Statute: California Penal Code 632 and 632.7 (cellular)
• Fines and damages: Up to $2,500 per violation criminal fine. Civil damages of $5,000 per violation or 3x actual damages (whichever is greater) under Penal Code 637.2. No proof of harm required.
• Exceptions: Public communications with no reasonable expectation of privacy; law enforcement acting under a warrant; emergency situations involving threat to life; communications recorded by a party in response to an immediate threat.
• Federal interaction: California law overrides the federal one-party consent standard because it is more privacy-protective. ECPA does not preempt stricter state law.
• Practical guidance: Treat every California prospect as all-party consent without exception. Announce the recording verbally and capture explicit affirmative consent at the start of every call. The civil cause of action under Penal Code 637.2 is the largest class-action exposure for any SaaS company recording California users.

New York (NY): one-party

One-party consent under N.Y. Penal Law 250.00 and 250.05. Class E felony for non-participant eavesdropping.

• Statute: New York Penal Law 250.00 and 250.05
• Fines and damages: Class E felony with up to 4 years imprisonment for non-participant eavesdropping. Civil damages also available under common law and statutory privacy torts.
• Exceptions: Party consent (the rep is a participant); law enforcement with a warrant; communications conducted in public with no reasonable expectation of privacy.
• Federal interaction: New York aligns with federal one-party consent. The eavesdropping statute applies primarily to recordings made by a non-party to the communication.
• Practical guidance: New York-based sales reps may record without disclosure as a participant. However, professional norms in the financial services and enterprise software sectors strongly favor disclosure. FINRA Rule 3170 requires registered broker-dealers to retain recordings for at least 3 years, layering federal industry rules on top of state law.

Texas (TX): one-party

One-party consent under Tex. Penal Code 16.02. Civil damages of $10,000 per occurrence plus actual damages under Civ. Prac. & Rem. Code 123.001.

• Statute: Texas Penal Code 16.02 and Texas Civil Practice & Remedies Code 123.001
• Fines and damages: Second-degree felony with up to 20 years imprisonment for criminal violation. Civil damages of $10,000 per occurrence plus actual damages, punitive damages, and attorney fees.
• Exceptions: Party consent (the rep is a participant); law enforcement with a warrant; communications recorded with the consent of any party.
• Federal interaction: Texas aligns with federal one-party consent. A participant may record without notifying other parties under both Texas and federal law.
• Practical guidance: Texas is one-party for criminal purposes, but the civil practice code creates a private right of action with statutory damages. Sales teams that record Texas prospects without disclosure face limited criminal exposure but real civil litigation risk. Disclose anyway as a best practice. The combination of Austin and Dallas as major SaaS hubs means professional disclosure norms are increasingly expected.

Florida (FL): all-party

All-party consent under Florida Statutes 934.03. Recording without consent is a third-degree felony. Heavy class-action litigation environment.

• Statute: Florida Statutes 934.03
• Fines and damages: Third-degree felony with up to 5 years imprisonment and $5,000 fine. Civil damages include actual damages, punitive damages, and attorney fees.
• Exceptions: Law enforcement with a warrant or court order; consent of all parties; communications uttered in public where no reasonable expectation of privacy exists; emergency communications involving threat to life or limb.
• Federal interaction: Florida law overrides federal one-party consent because it is stricter. ECPA permits states to impose more protective rules. When a rep outside Florida calls a Florida prospect, Florida law applies.
• Practical guidance: Florida is one of the most active class-action jurisdictions for recording violations. Always obtain explicit verbal consent before recording any Florida-based prospect. Document consent in the CRM. The combination of felony criminal exposure and easy civil litigation makes Florida the second-highest risk state after California.

Illinois (IL): all-party

All-party consent under 720 ILCS 5/14-2. Eavesdropping is a Class 4 felony for a first offense, Class 3 for repeat offenses.

• Statute: 720 ILCS 5/14-2 (Illinois eavesdropping statute)
• Fines and damages: Class 4 felony for a first offense (1 to 3 years imprisonment, fines up to $25,000). Class 3 felony for repeat offenses (2 to 5 years). Civil damages also available.
• Exceptions: Law enforcement with a warrant or court order; consent of all parties to the communication; public communications where no party has a reasonable expectation of privacy; recording of certain illegal activity as defined by statute.
• Federal interaction: Illinois law overrides federal one-party consent. After the People v. Clark (2014) decision struck down the original overbroad statute, the legislature narrowed the rule to apply to private communications, but private B2B sales calls clearly qualify.
• Practical guidance: The post-Clark statute focuses on communications where any party has a reasonable expectation of privacy. Sales calls involving deal terms, financial information, or strategic discussion clearly fall within the protected category. Always obtain consent from Illinois prospects before recording.

Pennsylvania (PA): all-party

All-party consent under 18 Pa.C.S. 5703 and 5704. Third-degree felony for recording without consent. Aggressively enforced.

• Statute: Pennsylvania Wiretap Act, 18 Pa. C.S. 5703 and 5704
• Fines and damages: Third-degree felony with up to 7 years imprisonment and $15,000 fine. Civil damages of $100 per day of violation or $1,000 (whichever is greater), plus punitive damages and attorney fees.
• Exceptions: Law enforcement with a court order; consent of all parties to the communication; certain telephone company employees acting in the ordinary course of business; business-extension exception for monitoring service quality with prior notification.
• Federal interaction: Pennsylvania law overrides federal one-party consent. For interstate calls, assume Pennsylvania's all-party rule applies whenever even one participant is in Pennsylvania.
• Practical guidance: Pennsylvania is one of the most aggressively enforced two-party consent jurisdictions. Even brief unrecorded conversations can trigger felony liability if any portion of the call is recorded without disclosure. Treat any call with a participant in Pennsylvania as requiring all-party consent.

Massachusetts (MA): all-party

Strict all-party consent under M.G.L. c. 272 s. 99. Up to 5 years state prison plus $10,000 fines. One of the strictest recording regimes in the US.

• Statute: Massachusetts General Laws Chapter 272 Section 99
• Fines and damages: Felony with up to 5 years in state prison and fines up to $10,000. Civil damages available under the same statute. Class action exposure for SaaS companies recording Massachusetts users.
• Exceptions: Law enforcement acting under a warrant; certain federal investigations; Office of Inspector General investigations; public broadcast or transmission with the actual knowledge of parties.
• Federal interaction: Massachusetts law overrides federal one-party consent. The statute requires actual knowledge of all parties, which courts have interpreted as a higher bar than implied consent.
• Practical guidance: Massachusetts requires explicit verbal consent. Implied consent through continued participation may not be sufficient under the actual knowledge standard. Use a recording tool that clearly announces it is recording, and follow up with a verbal disclosure script. Federal litigation over recording public officials (Project Veritas Action Fund v. Rollins, 1st Cir. 2020) did not change the rule for private sales calls.

Washington (WA): all-party

All-party consent under RCW 9.73.030. Gross misdemeanor for a first offense, civil damages of $100 per day or $1,000 minimum.

• Statute: Revised Code of Washington 9.73.030
• Fines and damages: Gross misdemeanor for a first offense. Civil damages of the greater of $100 per day of violation, $1,000, or actual damages, plus punitive damages and attorney fees under RCW 9.73.060.
• Exceptions: Emergency communications; law enforcement with a warrant; consent of all parties to the communication; recording of communications threatening unlawful demands or extortion.
• Federal interaction: Washington law overrides federal one-party consent. The statute applies to private communications and is read narrowly by Washington courts.
• Practical guidance: Washington is the home of major SaaS and cloud companies. Sales teams calling into Seattle-area prospects must default to all-party consent. The statute makes the recording itself the violation, and consent is interpreted narrowly. Announce the recording verbally and capture explicit consent at the start of every call.

Georgia (GA): one-party

One-party consent for telephone calls under O.C.G.A. 16-11-66. A participant may record without notification.

• Statute: O.C.G.A. 16-11-62 (eavesdropping), 16-11-66 (telephone recording)
• Fines and damages: Felony with up to 5 years imprisonment plus civil damages. The eavesdropping statute carries harsher penalties for non-participants than the one-party rule for participants.
• Exceptions: Party consent (the rep is a participant); law enforcement with a warrant; public communications with no reasonable expectation of privacy.
• Federal interaction: Georgia aligns with the federal one-party standard. ECPA permits the recording by a participant without notification.
• Practical guidance: Although Georgia is one-party, disclosure remains the recommended practice for enterprise sales. Many corporate buyers require disclosure as part of their own compliance posture, and disclosure reduces friction with privacy-conscious prospects. The Atlanta-based SaaS market expects professional disclosure norms.

Virginia (VA): one-party

One-party consent under Va. Code 19.2-62. Class 6 felony for non-participant recording.

• Statute: Virginia Code 19.2-62
• Fines and damages: Class 6 felony with up to 5 years imprisonment for non-participant interception. Civil damages of the greater of actual damages, $100 per day of violation, or $1,000.
• Exceptions: Party consent (the rep is a participant); law enforcement with a court order; public communications with no reasonable expectation of privacy.
• Federal interaction: Virginia aligns with federal one-party consent. A participant may legally record without notifying other parties.
• Practical guidance: Virginia hosts a significant federal contracting market in the DC suburbs. Sales calls involving federal government employees or federal contractors may be subject to additional rules under federal acquisition regulations. Default to disclosure for any call into the DC metro area, and consult counsel for federal-contract-specific recording requirements.

Multi-state compliance is a process problem: a rep dialing 30 calls a day across a dozen states cannot be expected to recall the right consent rule from memory, and one mistake can create criminal exposure. The fix is a single all-party disclosure habit, applied on every call, before anyone presses record.

Nimitai works on the preparation side of that habit. The Researcher Agent builds a one-page pre-call brief on the buyer before the call, and the Preparation Agent turns it into a call plan, so the prospect's location is in front of the rep before they dial. During the call, the Live Meeting Co-pilot (in early access) gives the rep private on-screen guidance. No bot joins the Zoom, Google Meet, or Teams meeting; audio is captured on the rep's own device, so the prospect sees a normal call.

No bot does not mean no consent rules. Consent and recording laws still apply to any recording you make, whether or not a bot is visible. Follow the rule for every state on the call (in practice, disclose and get consent at the start), and check with counsel for regulated industries. Nimitai is $149/seat/month with no seat minimum.

The simplest defensible operational policy is to default to all-party consent disclosure on every call. The cost of universal disclosure is one extra sentence at the start of the call. The cost of getting it wrong in California, Florida, or Pennsylvania is a six-figure class action or a felony charge against the rep who pressed record. The math is obvious.

Sample consent script

Use this script verbatim at the start of every recorded call:

"Just to let you know, this call is being recorded for quality and coaching purposes. By continuing, you consent to the recording. Is that okay with you?"

Wait for an affirmative response before proceeding. The "coaching purposes" wording also covers later review of the call in your sales coaching software, so say it every time. Document the consent in your CRM under a dedicated field. For Massachusetts, where actual knowledge of all parties is the standard, this explicit affirmation is essential.

When to confirm in writing versus verbally

For routine sales calls, verbal consent captured in the recording itself is sufficient. For regulated industries (financial services, healthcare, insurance) or high-stakes enterprise deals, follow up with a written confirmation via email referencing the recording policy. This creates a double audit trail in case the verbal consent is later disputed.

Multi-state team protocol

Build a single global policy that defaults to all-party consent. Train every rep on the same disclosure script. If your recording tool shows a platform recording indicator, treat it as a supplement to the verbal script, not a replacement. A no-bot AI meeting assistant keeps an extra participant out of the room, but it does not remove the duty to disclose when you record. Capture prospect state in your CRM so you can audit compliance by jurisdiction, and fold the consent step into your AI sales meeting prep checklist so reps see the prospect's state before dialing. Review the policy annually with counsel. These five steps deliver compliance with the vast majority of US state laws plus GDPR and PIPEDA simultaneously.

Nimitai prepares the rep before the call and, through the Live Meeting Co-pilot (early access), gives private guidance during it, with no bot in the meeting. Your consent obligations stay the same: follow your state's rule for any recording you make. Nimitai is $149/seat/month with no seat minimum.

• Federal: 18 U.S.C. 2511 (Electronic Communications Privacy Act)
• Wikipedia: Telephone recording laws (overview)
• California Penal Code 632 (official text)
• Justia: 50-state survey on recording conversations
• EU GDPR Article 6 (lawful processing)
• Canada: PIPEDA