Meeting Recording Laws by State: The Compliance Map Nobody Cares About (But Should)
One-party or all-party consent? What each state's law says about recording meetings, the 2026 Otter.ai ruling, and how meeting tools handle consent.
Corrected October 3, 2026: the state table had errors. It listed Oregon and Connecticut as all-party for all communications, cited Delaware's one-party statute as all-party, and listed Michigan and Missouri as one-party states. We rebuilt the table from the Reporters Committee for Freedom of the Press state guides, linked each state, and added the August 2026 Otter.ai ruling. See our corrections page.
The rules on recording calls are knowable. The tools just do not make compliance easy.
Your sales rep in California records a Zoom call with a prospect in Illinois. California requires all-party consent. Illinois does too. Both states agree, so no problem. Now move that prospect to New York (one-party consent) while your rep stays in California. The rules conflict. California says your rep needs everyone's permission. New York says one party is enough. Which state's law governs the call?
Most companies recording meetings have never asked this question. They turned on the recording feature, maybe saw a notification pop up, and assumed that was enough. It may not be. The rules vary state by state, and a single call between two states can create liability.
This guide lays out what the law says so you can make informed decisions about your recording setup. It is not legal advice. Consult counsel for your specific situation.
One-party vs all-party consent
Federal law (18 U.S.C. 2511) sets the floor: you need the consent of at least one party to record a conversation. If you are a participant, you count as that one party. This is called one-party consent, and it means you can record your own calls under federal law without telling anyone.
States can be stricter. According to the Reporters Committee for Freedom of the Press (RCFP), about 11 states primarily require the consent of all parties, and four more require it for either phone calls or in-person conversations but not both. Despite the common label "two-party consent," all-party means every participant must know about and agree to the recording. A five-person call in California needs five people's consent, not two.
The consequences range from misdemeanors to felonies. In Pennsylvania, illegal recording is a felony punishable by up to seven years in prison. In Illinois, it is a felony with one to three years and fines up to $25,000. In California, a first criminal offense carries a fine up to $2,500, and the civil statute lets each person recorded sue for $5,000 per violation. Plaintiffs have used these statutes against companies, including AI notetaker vendors (see the Otter section below).
About 11 states primarily require all-party consent
California, Delaware (statutes conflict), Florida, Illinois, Maryland, Massachusetts, Michigan (at least for non-participants), Montana, New Hampshire, Pennsylvania, Washington
Split rules: Connecticut and Nevada require all-party consent for phone calls only. Missouri requires it for private in-person conversations only. Oregon allows one-party consent for phone calls but requires that all participants be told before an in-person or video-conference conversation is recorded.
If any participant is in one of these states, the safest approach is to get everyone's consent. Source: RCFP.
States that require all-party consent
The table below covers the 11 primarily all-party states plus the four with split rules. Each state links to its RCFP guide, which quotes the statute. The remaining states follow one-party consent.
| State | Consent Type | Key Statute | Notes |
|---|---|---|---|
| California | All-party | Cal. Penal Code 632, 637.2 | Covers confidential communications. Criminal fine up to $2,500 for a first offense. Civil damages of $5,000 per violation or three times actual damages (637.2), the remedy most lawsuits use. |
| Connecticut | Mixed | Conn. Gen. Stat. 52-570d; 53a-187, 53a-189 | Phone calls: all-party consent to avoid civil liability (52-570d). The criminal statutes require only one party. In-person: one-party. |
| Delaware | Conflicting | Del. Code tit. 11, 1335(a)(4); tit. 11, 2402 | The statutes conflict: the privacy law (1335) requires all-party consent, the wiretap law (2402) allows one-party. RCFP advises following the stricter rule. |
| Florida | All-party | Fla. Stat. 934.03 | Felony, up to 5 years and $5,000, with lighter penalties for some first offenses. |
| Illinois | All-party | 720 ILCS 5/14-2 | Felony, 1 to 3 years and up to $25,000. Illinois also has BIPA, which governs voiceprints. |
| Maryland | All-party | Md. Code, Cts. & Jud. Proc. 10-402 | Felony, up to 5 years and $10,000. |
| Massachusetts | All-party | Mass. Gen. Laws ch. 272, 99 | Bans secret recording. Affirmative consent is not needed when all parties know about the recording. |
| Michigan | All-party* | Mich. Comp. Laws 750.539c | All-party for eavesdropping by a non-participant. A 1982 appeals court ruling (Sullivan v. Gray) held that a participant may record without others' consent; the state supreme court has not settled it. |
| Missouri | Mixed | Mo. Rev. Stat. 542.402 | Phone calls: one-party. Private in-person conversations: all-party, per RCFP. |
| Montana | All-party | Mont. Code 45-8-213 | All-party knowledge or consent for in-person, phone and electronic communications, with some exceptions. |
| Nevada | Mixed | Nev. Rev. Stat. 200.620, 200.650 | Phone calls: all-party. In-person: one-party. |
| New Hampshire | All-party | N.H. Rev. Stat. 570-A:2 | Felony, but a misdemeanor if the person recording was a party or had one party's consent. |
| Oregon | Mixed | Or. Rev. Stat. 165.540 | Phone calls: one-party. In-person conversations, and conversations held through a video conferencing program (165.535(1)): all participants must be specifically informed before recording (165.540(1)(c)). The Ninth Circuit, sitting en banc, upheld this rule in Project Veritas v. Schmidt (Jan. 7, 2025). Opinion. |
| Pennsylvania | All-party | 18 Pa. C.S. 5703 | Felony, up to 7 years and $15,000. |
| Washington | All-party | Wash. Rev. Code 9.73.030 | A recorded announcement that the conversation is being recorded counts as consent. |
All other states and D.C. (Alabama, Alaska, Arizona, Arkansas, Colorado, D.C., Georgia, Hawaii, Idaho, Indiana, Iowa, Kansas, Kentucky, Louisiana, Maine, Minnesota, Mississippi, Nebraska, New Jersey, New Mexico, New York, North Carolina, North Dakota, Ohio, Oklahoma, Rhode Island, South Carolina, South Dakota, Tennessee, Texas, Utah, Virginia, West Virginia, Wisconsin, Wyoming) follow one-party consent. (Hawaii and Maine require all-party consent for recording in private places.) Vermont has no recording statute, so federal one-party consent applies. Table checked against the RCFP state guides (last updated by RCFP between 2019 and 2023) on October 3, 2026. Laws change. Always verify current law with legal counsel.
Your SDR in Portland records a phone call with a CFO in Miami. Oregon allows one-party consent for phone calls, but Florida requires all parties to consent, and Florida treats most violations as felonies. If nobody announced the recording, the Florida side of the call is the exposure. Sales teams that record by default run into this whenever a prospect sits in a stricter state.
Cross-state calls: which rule applies?
This is where it gets messy. When a caller in Texas (one-party) joins a meeting with someone in California (all-party), which state's law governs the recording?
The short answer: it depends on the court. Some courts apply the law of the state where the recording was made. Others apply the law of the state where a participant is located.
In Kearney v. Salomon Smith Barney (2006), the California Supreme Court held that California's all-party consent law applied to a Georgia firm's recording of calls with California clients, even though Georgia requires only one-party consent. The ruling had a limit: California law governed going forward (injunctive relief), but the court declined to impose damages for the past recordings. The message for out-of-state companies was clear anyway: if you call Californians, plan to follow California's rule.
The practical takeaway: if any participant on the call is in an all-party consent state, treat the entire call as if all-party consent is required. This is the conservative approach. Getting consent from everyone costs little. Getting it wrong can cost you a lawsuit.
For companies with distributed teams, this often means every call should be treated as an all-party consent situation. If you have employees or customers in California, Florida, Pennsylvania, Illinois, or any of the other all-party states, your recording policy needs to account for that.
AI notetakers in court: the Otter ruling
The biggest legal development for meeting recording in 2026 is not a new statute. It is a court ruling about who counts as the eavesdropper.
On August 13, 2026, Judge Eumi K. Lee of the U.S. District Court for the Northern District of California granted in part and denied in part Otter.ai's motion to dismiss in In re Otter.AI Privacy Litigation (No. 5:25-cv-06911), a consolidated class action. The claims under the federal Wiretap Act, the California Invasion of Privacy Act (CIPA section 631) and the Illinois Biometric Information Privacy Act (BIPA) survived. The court dismissed the computer-fraud claims (CFAA and California's CDAFA) and the Washington Privacy Act claim, with leave to amend.
The key point: the court found the plaintiffs had plausibly alleged that Otter itself is a third-party eavesdropper, not just a tool acting for the meeting host, because it allegedly retained conversation data and used it for its own purposes, including training models (UC Today summary). That theory matters for every notetaker user. Under it, the host's consent may not cover the vendor, and the people being recorded may have claims against the vendor directly. A ruling on a motion to dismiss is not a finding of liability; the case continues.
A second suit followed. On July 30, 2026, a class action filed in the same court accused Granola of designing its app to capture meeting audio from the user's computer without disclosure to other participants, in violation of CIPA's all-party rule (Computerworld, Aug 6 2026). These are allegations in a complaint, not findings.
How meeting tools handle consent
Recording tools vary widely in how they notify participants. Some make compliance easy. Others leave it entirely to you. The summary below draws on each vendor's documentation. If you are also weighing the privacy trade-offs of free tools, we covered that in our analysis of free notetaker privacy policies.
Zoom shows a notification to all participants when recording starts. Zoom also offers a recording consent disclaimer that prompts participants to consent to stay or leave. Customizing the disclaimer text requires a Business, Education, API or Enterprise account with 100 or more licenses, plus owner or admin rights. If you qualify and work with all-party states, adding explicit consent language is worth the five minutes.
Microsoft Teams displays a recording indicator and notifies participants when recording starts. Teams now also detects third-party bots and holds them in the lobby. A meeting policy setting, ExternalBotAccessMode, defaults to requiring approval when a bot is detected (Office 365 for IT Pros, Aug 24 2026); general availability is due to finish by the end of October 2026 (MC1251206). That makes bots more visible, but visibility is not the same as consent.
Google Meet notifies participants when a recording starts or stops. Admins can also turn on a setting that requires all participants to give explicit consent before recording, transcription or "take notes for me" runs. The setting is off by default, so check whether your admin has enabled it.
Gong offers configurable consent profiles. Admins can combine a pre-call email to external invitees, a consent page participants must accept (if they decline, the recording is canceled) and an audio prompt that announces the recording. Different profiles can apply to different users, so teams that sell into stricter states can use stricter settings. For revenue teams in regulated industries, this level of control matters.
Otter.ai, Fireflies.ai, and Fathom join meetings as bot participants. The bot's name typically signals recording (e.g., "Otter.ai Notetaker" or "Fireflies.ai Notetaker"), and participants can see it in the attendee list. Relying on a bot name for legal consent is thin, and the Otter ruling shows a second problem: the bot's vendor may count as a separate party that needs consent of its own. Check each vendor's current consent and announcement settings before relying on them.
Krisp, Bluedot, and Jamie record locally without joining as a bot participant. Other attendees have no way to know the recording is happening unless the user tells them. These tools put the consent burden entirely on the person recording, and the Granola complaint shows plaintiffs are now targeting this design. If you use desktop-level recording, your team needs clear training on when and how to announce it.
The pattern: platform-native recording (Zoom, Teams, Meet) generally handles notification better than third-party tools. Third-party bots provide some visibility through their presence in the meeting. Desktop-based tools provide none. The compliance burden shifts to you as the tools become less visible.
What to do about it
Here are five concrete steps to reduce your legal risk around meeting recordings.
1. Map your states. List every state where your team members work. List every state where your customers and prospects are located. If any of those states require all-party consent, your recording policy needs to account for it. For most companies with remote employees, this means at least one all-party state is in the mix.
2. Configure your recording tool to announce itself. Turn on every notification and consent feature your tool offers. In Zoom, enable the recording consent disclaimer. In Meet, ask your admin to turn on explicit consent. In Teams, ensure recording notifications are active (they are by default, but check). If you use a tool like Gong, configure the pre-call consent emails and audio prompt. Do not rely on default settings.
3. Add a recording notice to meeting invites. For recurring meetings and any meeting that will be recorded, add a line to the calendar invite: "This meeting will be recorded and transcribed. By joining, you consent to the recording." This is not bulletproof legally, but it establishes a paper trail of notification. Name the notetaker vendor too, since the Otter ruling treats the vendor as a possible separate party.
4. Train your team. Your sales reps, customer success managers, and anyone who records calls needs to know the rules. The training does not need to be long. Cover: which states require all-party consent, how to announce recording at the start of a call, and what to do if someone objects. A five-minute briefing and a one-page reference sheet are usually enough.
5. Audit your tool's compliance features. Every six months, review what your recording tool offers for consent management and what its terms say about using your recordings for model training. Platforms change their bot and consent controls often, as Teams did in 2026. Court decisions shift the rules. A quick review twice a year keeps you current.
The goal is not to stop recording meetings. Recording is valuable for training, accountability, and documentation. The goal is to record legally, with informed consent from everyone on the call. In most cases, that means saying "I'm going to record this meeting" at the start and giving people a chance to object. It takes five seconds.
Disclaimer: This article is for informational purposes only and does not constitute legal advice. Recording consent laws are complex, vary by jurisdiction, and change over time. Consult a qualified attorney for guidance on your specific situation.