Using an AI meeting recorder is legal in most of the US under one-party consent β if you’re a participant in the call, your own consent is enough, and roughly 38 states work this way. The complication is that at least five widely cited 2026 legal guides disagree on exactly which states require everyone’s consent instead, with counts ranging from 11 to 14 states and different names on each list. None of the guides are lying β they’re categorizing two genuinely unusual hybrid states differently. Here’s what’s actually settled, what isn’t, and the one habit that keeps you safe regardless of which list turns out to be right.
Why the State Lists Don’t Agree
Five current guides on all-party (two-party) consent states, checked side by side, produce five different lists:
| Source | States listed as requiring all-party consent | Count |
|---|---|---|
| itsconvo.com | California, Delaware, Florida, Illinois, Maryland, Massachusetts, Montana, Nevada, New Hampshire, Pennsylvania, Washington | 11 |
| recordmeeting.com | California, Florida, Illinois, Pennsylvania, Washington, Connecticut, Delaware, Maryland, Massachusetts, Michigan (list continues) | ~12+ |
| recordinglaw.com | Not fully enumerated; states 13 total states require all-party consent | 13 |
| legaloverview.com | Not fully enumerated; states roughly 38 states use one-party consent, implying 12 elsewhere | ~12 |
| kenznote.com | California, Connecticut, Delaware, Florida, Illinois, Maryland, Massachusetts, Michigan, Montana, Nevada, New Hampshire, Oregon, Pennsylvania, Washington | 14 |
Two states explain part of the gap on their own: Connecticut requires all-party consent for phone calls but only one-party consent for in-person conversations, and Oregon runs the opposite way β all-party consent in person, one-party consent for electronic communications. A guide focused on video calls might reasonably drop Oregon since electronic communication there only needs one-party consent, while a guide covering all recording scenarios would include it. That accounts for some of the variation between an 11-state list and a 14-state list, but not all of it β Michigan and Montana appear on some lists and not others without an obvious hybrid-law explanation in what’s covered here. The honest takeaway is that the exact state count is a genuinely contested number across current legal-guide publishers, not a single settled fact, and treating any one list as definitive is the mistake, not picking the “wrong” list.
The Safe Default Regardless of Which List Is Right
Every source agrees on the fix that sidesteps the counting problem entirely: announce the recording out loud at the start of the call, in every state, regardless of which consent tier applies. A simple statement β “I’m going to record this call for reference, does anyone have an objection?” β followed by no objection, creates a strong record of implied consent in essentially every US jurisdiction, one-party or all-party. This costs nothing and makes the state-by-state disagreement above irrelevant to your actual practice.
The Newer Question Nobody’s Settled: Is a Bot’s Announcement Enough?
Beyond the state-list disagreement sits a genuinely unresolved question specific to AI notetakers. When a tool like Otter or Fireflies joins a call as a visible bot with a generic name and posts an automated notice that the meeting is being recorded, does that satisfy all-party consent law in a state like California? California Penal Code Section 632 requires that all parties to a confidential communication consent β and legal commentary on this is split on whether a bot’s generic name and automated message counts as adequate disclosure, or whether it needs to come from an actual human host, by name, for a participant to meaningfully understand and agree to it. This hasn’t been definitively settled through the sources reviewed here, which means teams relying on the bot’s own announcement as their compliance mechanism are relying on an interpretation, not a confirmed legal safe harbor.
Bot-Based vs Bot-less Recording: Different Disclosure Problems
The disclosure mechanics differ meaningfully depending on how the tool actually captures the call, and 2026 brought a new variant worth understanding.
| Recording method | Disclosure mechanism | Risk |
|---|---|---|
| Zoom/Teams native recording | Platform shows a visible recording banner to every participant automatically | Lowest β disclosure is built into the platform itself |
| AI notetaker bot (e.g. Otter, Fireflies) | Bot joins visibly and posts an automated notice | Unresolved whether a generic bot announcement meets all-party consent standards |
| Browser or system-audio capture with no visible bot | None built in β no banner, no bot, no automatic notice to other participants | Highest β verbal or written disclosure from the host becomes the only compliance mechanism |
Tools that capture system audio without a bot joining the call are being marketed as more discreet and less disruptive, but that discretion is exactly what removes the automatic disclosure a visible bot at least attempts. If you’re using this kind of tool, the burden to actually tell participants shifts entirely onto you, verbally, at the start of the call β the same habit recommended above becomes non-optional rather than merely a good practice.
What Actually Changes the Analysis
State consent law isn’t the only layer. Employment and labor rules often require documented disclosure for performance reviews or disciplinary meetings specifically, regardless of whether the state is one-party or all-party consent, because a recording used later as evidence in an employment dispute faces a different standard than a casual work call. This is a real consideration for anything covered in HR and recruiting workflows that use AI β a documented, written disclosure in the meeting invite or employment agreement is the safer approach for these specific meeting types, independent of the general state consent question above.
Cross-State Calls: Which Law Applies
If participants join from different states, the strictest applicable state’s law governs the whole call, consistently across every source reviewed. A host in a one-party consent state recording a call that includes participants from an all-party consent state should treat the entire call as requiring everyone’s consent β the location where you personally sit doesn’t protect you from a stricter state your participants are sitting in.
A Practical Checklist
| Situation | Recommended action |
|---|---|
| All participants confirmed in one-party consent states | Verbal disclosure still recommended, not strictly required |
| Any participant location unknown or mixed states | Announce recording out loud and get explicit acknowledgment before starting |
| Performance review, disciplinary meeting, or other employment-sensitive call | Written disclosure in the invite or employment agreement, regardless of state |
| Using a bot-based AI notetaker | Don’t rely solely on the bot’s automated notice β add a verbal announcement |
| Using a bot-less, system-audio capture tool | Verbal disclosure is mandatory β no platform-level notice exists at all |
Who Should Get Real Legal Advice Instead of Following This Guide
This is general information synthesized from multiple current legal guides, not legal advice, and the guides themselves don’t agree on every detail. Anyone recording calls involving healthcare information, legal privilege, minors, or international participants outside the US should treat this article as a starting point for questions to bring to an actual attorney, not as a compliance checklist to rely on directly β the same caution this site has applied when covering AI disclosure obligations under the EU AI Act, where the specific rule matters more than the general principle.
Frequently Asked Questions
Is it legal to use an AI notetaker without telling everyone on the call?
In roughly 38 US states, one-party consent applies, meaning your own participation and consent is legally sufficient. In the remaining states, every participant’s consent is required, though legal guides disagree on the exact count and list of those states.
How many US states require all-party consent for recording?
Current guides disagree, with counts ranging from 11 to 14 states depending on the source and how they categorize two hybrid states, Connecticut and Oregon, whose rules differ between phone, in-person, and electronic communication.
Does an AI notetaker bot announcing itself count as legal consent?
This is genuinely unresolved. Some legal commentary questions whether a bot joining with a generic name and an automated notice meets the disclosure standard required in all-party consent states like California, versus a clear, human-delivered announcement.
What’s the safest way to record a meeting regardless of which state’s law applies?
Announce the recording verbally at the start of the call and ask if anyone objects. Proceeding without objection creates a strong record of implied consent in essentially every US jurisdiction, sidestepping the state-by-state disagreement entirely.
Are bot-less, system-audio AI recorders more legally risky than bot-based ones?
They remove the automatic, if imperfect, disclosure a visible bot provides. Without a bot or a platform recording banner, there’s no built-in notice to other participants at all, which shifts the entire disclosure burden onto the host.
Does recording a performance review or disciplinary meeting have different rules?
Employment and labor rules often require documented, written disclosure for these meeting types specifically, separate from general state consent law, because such recordings may later be used as evidence in an employment dispute.