All-Party Consent States in 2026: A Lawyer's Guide to Recording Client Conversations

Recording a client conversation used to be an occasional question. In 2026, with AI notetakers on nearly every laptop and phone, it is a daily one. The technology got cheaper faster than the law adapted, and the intersection of state wiretap statutes, the ABA Model Rules, and emerging AI-specific ethics guidance now catches many well-meaning lawyers off guard.

This guide maps the all-party consent landscape as it stands in 2026, walks through the ethics overlay, and offers a workable consent protocol for attorneys who want to capture client meetings without creating new discovery, privilege, or discipline exposure.

What "All-Party Consent" Actually Means

Every U.S. jurisdiction has a wiretap or eavesdropping statute derived, at least loosely, from the federal Wiretap Act (18 U.S.C. § 2511). Federal law is a one-party consent regime: a participant to a communication may record it without notifying the others. Most states follow that rule. A minority require the consent of all parties to the conversation before a recording is lawful. Those are the all-party (sometimes called two-party) consent states, and they are where careless recording turns into a criminal statute violation and a civil damages claim.

The wrinkle for lawyers: when parties are in different states, the stricter rule usually controls, and several all-party states apply their statute to any call where one participant is physically located inside the state. A California client on a Zoom call with a New York lawyer is, in practical terms, an all-party call.

The 2026 All-Party Consent Map

The list below reflects statutes and controlling case law as of early 2026. It is not a substitute for a jurisdictional check on any specific matter, particularly because several states have narrower rules for in-person versus electronic communications, or carve out recordings made in places without a reasonable expectation of privacy.

Vermont has no wiretap statute and has been treated in case law as effectively all-party for surreptitious in-home recording. Hawaii is one-party for phone calls but all-party for in-person recordings in private places. The safe operating assumption for a multi-state practice is to run every client recording under the strictest applicable rule and to document consent even in one-party jurisdictions.

The Ethics Overlay: Model Rule 1.6 and ABA Opinion 512

State wiretap statutes tell you whether recording is lawful. The rules of professional conduct tell you whether it is proper. The two questions are related but not identical.

ABA Model Rule 1.6 requires lawyers to make reasonable efforts to prevent unauthorized disclosure of information relating to the representation. That obligation reaches every stage of a recording's life: capture, transcription, storage, transmission, and eventual deletion. A recording made lawfully but stored on a vendor server that a lawyer cannot describe is a Rule 1.6 problem regardless of the wiretap analysis.

ABA Formal Opinion 512 (July 2024) applies these duties specifically to generative AI tools. The opinion emphasizes competence, confidentiality, informed client consent where client information is fed to a tool that learns from or retains it, reasonable diligence about vendor practices, and clear communication with clients about how AI is used in their matter. Opinion 512 does not ban cloud AI, but it treats vendor architecture as a matter the lawyer must actually understand and, in many cases, disclose.

The NYC Bar Formal Opinion 2025-6 (December 2025) builds on Opinion 512 with a sharper focus on retention, training data, and client notice for New York practitioners. Both opinions push in the same direction: the lawyer, not the vendor, owns the confidentiality analysis.

Why AI Notetakers Change the Consent Calculus

Before AI notetakers, a lawyer's recording was usually an isolated audio file, sometimes transcribed by a trusted assistant, rarely shared. Modern notetakers often do four things at once: capture audio, transcribe it, summarize it, and send some or all of that content to a third-party cloud where it may be retained, indexed, and, depending on the vendor, used to improve models.

Two 2025-2026 developments made this concrete. First, US v. Heppner (S.D.N.Y. February 2026), an opinion by Judge Rakoff, held that a litigant's chats with a public AI platform were not privileged, drawing an analogy to third-party doctrine cases. The reasoning: once a communication is shared with a third-party service that retains and processes it on its own infrastructure, the litigant cannot credibly claim the confidentiality that privilege requires. The opinion involved a party's own AI chats, not a lawyer's notetaker, but the reasoning travels.

Second, the ongoing Brewer v. Otter.ai litigation (2025) alleges that a widely used transcription service captured conversations of non-users without adequate consent. Whatever the ultimate outcome, the case underscores that when a bot joins a call or a background service captures audio, every non-consenting participant is a potential plaintiff, and the lawyer who invited the tool into the meeting is the closest defendant.

West Technology Group v. Sundstrom (D. Conn. 2024) is the other cautionary tale. The court addressed a party's use of an AI notetaker in a workplace context and reinforced that automated recording without clear consent is not made safer by being automated. If anything, the passive nature of the capture cuts against the recorder.

A Consent Protocol That Works Across Jurisdictions

The cleanest operating rule is to treat every client meeting as if it were governed by the strictest applicable statute and to build a consent record that would satisfy an ethics regulator on a bad day. A protocol along these lines meets that bar in almost every U.S. jurisdiction:

1. Disclose before capture starts. Tell the client, on the record, that the meeting will be recorded and transcribed, name the tool, and briefly describe where the data lives.
2. Get an affirmative response. A verbal yes at the top of the meeting, captured on the recording itself, is contemporaneous evidence of consent. Silence is not consent in an all-party state.
3. Confirm in writing. Include a short recording and AI-tools clause in the engagement letter. Reference the tool, its architecture in one plain sentence, and the client's right to withdraw consent.
4. Log third parties. When opposing counsel, experts, or witnesses join, restate the recording disclosure and capture their consent.
5. Keep a consent log. A per-matter record of who consented, when, and to what tool. In discovery or a bar inquiry, this is the artifact that answers the question quickly.
6. Match retention to the matter. Delete recordings and transcripts on a schedule that matches your file-retention policy, not the vendor's default.

For lawyers who want a deeper walk-through of the engagement-letter language and the mechanics of a per-matter consent record, see our companion piece on AI disclosure clauses in engagement letters.

Cross-Border Calls and the "Strictest Rule" Default

Multi-jurisdiction calls are where lawyers most often trip. Three practical rules cover most fact patterns.

First, if any participant is in an all-party state, treat the call as all-party. California and Pennsylvania courts have both applied their statutes to out-of-state recorders on calls with in-state participants. The Reporters Committee recording guide is a useful cross-check on individual state rules, though it is written for journalists rather than lawyers.

Second, get consent verbally on the recording itself. A recorded "yes" is portable across jurisdictions in a way that a checkbox on a scheduling page is not.

Third, remember that consent is to the recording, not just to the meeting. A client who agreed last month to a recorded intake has not necessarily agreed to today's strategy call being recorded and processed by a new tool.

Privilege, Third Parties, and Vendor Architecture

Recording lawfully is a floor. Preserving privilege is the harder question, and it is where vendor architecture becomes an ethics issue rather than a purchasing preference.

The traditional rule is that disclosure to a third party can waive attorney-client privilege unless the third party is necessary to the representation and understands its confidential nature. Courts have generally treated stenographers, translators, and traditional transcription services as within the tent. The open question in 2026 is whether a cloud AI vendor that retains, indexes, and potentially trains on transcripts fits the same category.

Heppner is a warning shot: at least one federal judge is willing to reason from third-party doctrine to strip privilege from AI-mediated communications. The safer posture, and the one Opinion 512 nudges toward, is to avoid the question entirely by choosing tools whose architecture does not create a new third-party recipient of client content.

Three architectural questions do most of the work when evaluating a notetaker:

• Does audio or transcript content leave the lawyer's device?
• If it does, who holds it, under what contract, and for how long?
• Is a bot joining the call as a visible non-party participant?

A tool that answers "no," "n/a," and "no" to those three questions is architecturally close to the old dictaphone: a device the lawyer uses, not a service the lawyer discloses to.

Common Failure Modes

The recurring patterns in bar complaints and civil suits around recording tools cluster around a few habits worth naming.

Silent bots. A notetaker joins a Zoom call as a named participant, but nobody addresses it. In an all-party state, the presence of a labeled bot is not the same as consent from the other participants. Massachusetts and Pennsylvania courts have been particularly unforgiving on this point.

Auto-record defaults. A calendar integration records every meeting by default. The lawyer forgets which meetings were recorded, and a later discovery request surfaces a recording the lawyer did not know existed.

Shared workspaces. A firm-wide notetaker workspace makes transcripts visible to colleagues who are not on the matter, creating an internal Rule 1.6 problem even if the external analysis is clean.

Training-data ambiguity. The vendor's terms permit use of "aggregated" or "de-identified" content for model improvement. Under Opinion 512 and NYC Bar 2025-6, that is a disclosure the lawyer likely owes the client, and one many clients will decline.

How Basil approaches this

Basil was built by a practicing lawyer specifically to avoid the architectural traps above. Audio capture, transcription, and summarization all run on the Apple Neural Engine on the lawyer's own Mac. Nothing is uploaded, there is no Basil server holding client content, and there are no subprocessors in the data path because there is no data path off the device. In practical terms, there is no server to subpoena and no third-party recipient to argue about under Heppner-style reasoning.

For in-person meetings and virtual calls on Zoom, Teams, or Meet, Basil captures locally in Computer mode rather than sending a bot into the call. That removes the visible-but-unaddressed participant problem that trips up firms in Massachusetts, Pennsylvania, and California.

The Basil for Law edition, arriving August 2026, adds a per-matter consent log, Privileged & Confidential labeling on exports, a privilege attestation on setup, and matter-organized storage. Pricing for the solo tier is $19.99/month or $199.99/year, with a 3-day monthly trial and a 7-day annual trial. Basil signs DPAs and NDAs on request. The general Basil app, with a 60-minute monthly free tier, is available today. This is not a promise of any particular ethics or evidentiary outcome; it is an architecture designed to reduce the risks that Opinion 512, NYC Bar 2025-6, and the 2025-2026 case law have made concrete.

This article is for information only and is not legal advice.

Frequently asked questions

Which states require all-party consent to record a client meeting in 2026?

As of early 2026, all-party consent applies in California, Connecticut, Delaware, Florida, Illinois, Maryland, Massachusetts, Michigan, Montana, Nevada, New Hampshire, Oregon (in-person), Pennsylvania, and Washington, with Vermont and Hawaii treated as effectively all-party in significant contexts. Statutes and case law shift, so verify the current rule in any specific matter.

If my client is in a one-party state and I am in an all-party state, which rule controls?

The safer default is the stricter rule. Several all-party states apply their statutes to any communication with a participant located inside the state, and running every client recording under the strictest applicable rule avoids litigation over choice of law after the fact.

Does an AI notetaker's presence on a call count as consent from the other participants?

No. A visible bot is not a substitute for affirmative consent, particularly in all-party states. Courts and bar authorities have consistently treated automated capture without express consent as equivalent to secret recording, not as a lesser concern.

Can using a cloud AI notetaker waive attorney-client privilege?

It can raise the risk. US v. Heppner (S.D.N.Y. Feb 2026) applied third-party doctrine reasoning to strip privilege from a litigant's public AI chats, and while that case was not about a lawyer's notetaker, the reasoning is available to opposing counsel. On-device tools reduce this exposure by not creating a new third-party recipient of client content.

What does ABA Formal Opinion 512 require for AI notetakers?

Opinion 512 requires competence about the tool, diligence about vendor practices, protection of confidentiality under Rule 1.6, and informed client consent where client information is shared with a tool that retains or learns from it. It does not ban cloud AI, but it puts the confidentiality analysis on the lawyer.

What should an engagement letter say about AI recording tools?

A short clause naming the tool, describing in one sentence where the data lives (for example, on-device only), noting that recordings and transcripts will be captured and retained under the firm's file-retention policy, and preserving the client's right to withdraw consent. Pair it with verbal consent captured on the recording itself.

Keep client conversations on your device

Basil transcribes and summarizes entirely on-device — no cloud, no bot, no server to subpoena. See Basil for Law → · Legal-tool reviews →

This article is for information only and is not legal advice.