Washington AI Meeting Recording Laws (2026)

Washington requires all-party consent for AI meeting recorders under RCW 9.73.030. Every participant must be notified before recording begins, and consent is obtained when any party announces recording in a reasonably effective manner. Recordings made without that consent are inadmissible in Washington courts under RCW 9.73.050.

Washington's recording law requires all-party consent, and it creates real problems for AI meeting tools. Under RCW 9.73.030, recording any private communication requires the consent of every participant. Not one party. All of them. That single requirement transforms the legal calculus for tools like Otter.ai, Fireflies.ai, and Zoom AI Companion from a simple activation decision into a compliance challenge for any private meeting recorded in Washington.

The statute does offer one critical mechanism: consent is considered obtained when any party announces "in any reasonably effective manner" that the conversation will be recorded. That phrase carries enormous weight in the AI meeting context. Whether an AI bot's notification banner, chat message, or audio announcement qualifies as "reasonably effective" is the central legal question for every AI recording tool operating in Washington.

And the consequences of getting it wrong are severe. Recordings made without proper consent are not just unlawful; they are inadmissible in any Washington court. That exclusionary rule, codified in RCW 9.73.050, means an illegally recorded conversation cannot be used as evidence in lawsuits, contract disputes, employment proceedings, or criminal cases.

Washington's All-Party Consent Statute: RCW 9.73.030

The Core Prohibition

RCW 9.73.030 prohibits intercepting or recording any private communication transmitted by telephone, telegraph, radio, or other device between two or more individuals. The statute also prohibits recording private conversations by any device designed to record or transmit such conversations without first obtaining the consent of all the participants.

The language is broad. It covers telephone calls, electronic communications (including video conferences and VoIP), and in-person conversations, but only when the communication or conversation is private. Whether a particular meeting is private depends on the facts, such as who attends, what is discussed, and whether participants expect it to stay confidential, so a business meeting is not automatically covered.

A narrow set of wire communications or conversations may be recorded with one party's consent under RCW 9.73.030(2): those of an emergency nature, those conveying threats of extortion, blackmail, bodily harm, or other unlawful requests or demands, those made anonymously, repeatedly, or at an extremely inconvenient hour, and those involving a hostage holder or barricaded person. Any device "designed to record or transmit" falls within the statute's reach, which plainly includes AI meeting recording software.

The "Reasonably Effective Manner" Standard

Under RCW 9.73.030(3), consent is deemed obtained whenever one party has announced to all other parties engaged in the communication "in any reasonably effective manner" that the communication is about to be recorded or transmitted.

The statute further requires that if the conversation is to be recorded, the person making the announcement must actually record themselves making it and then allow the recording to proceed. This creates a verifiable record that notification was given before recording began.

For AI meeting tools, the question is whether newer notification methods satisfy this standard: a bot appearing with a visible name, a chat message in the meeting window, a popup notification, or a brief audio announcement. No Washington court has ruled on whether these AI-specific notification mechanisms qualify as "reasonably effective" as of August 2026.

Penalties: Criminal, Civil, and Evidentiary

Criminal Penalties

RCW 9.73.080 classifies a violation of RCW 9.73.030 as a gross misdemeanor, but it sets no punishment itself. Because RCW 9.73.080 sits in Title 9 rather than Title 9A, the maximum penalty is supplied by RCW 9.92.020, the gap-filler for a gross misdemeanor whose punishment no statute prescribes: up to 364 days in jail, a fine of up to $5,000, or both. A separate, much narrower gross misdemeanor under RCW 9.73.080(2) applies to anyone who knowingly alters, erases, or wrongfully discloses a law-enforcement dash-cam or body-cam audio recording made under RCW 9.73.090(1)(c). That provision governs police vehicle-camera recordings; it does not create separate liability for altering or erasing an AI meeting recording or other private recording.

Civil Damages Under RCW 9.73.060

Any person injured by a violation may recover either actual damages (including mental pain and suffering) or liquidated damages at the rate of $100 per day of violation up to $1,000, plus reasonable attorney fees and costs of litigation.

The Exclusionary Rule: RCW 9.73.050

Any information obtained in violation of RCW 9.73.030 is inadmissible in any civil or criminal case in all Washington courts. There are only two narrow exceptions: when the person whose rights were violated gives permission to use the recording in a damages action, and in criminal cases involving national security.

This means a recording made without all-party consent cannot be used as evidence in employment disputes, contract disagreements, divorce proceedings, personal injury litigation, or criminal prosecutions. The recording is legally worthless as evidence, and its existence may trigger criminal and civil liability.

AI Meeting Tools and Washington's All-Party Consent Requirement

The Central Compliance Challenge

Washington's all-party consent rule, and its requirement that the announcement itself be recorded, make it one of the more demanding states for AI meeting tools. Unlike one-party consent states, where a single participant's consent generally suffices unless the recording is made for a criminal or tortious purpose, Washington requires that every participant in a private conversation be informed and consent before recording begins. Because it is hard to predict in advance whether a court will treat a meeting as private, the safe course is to treat every meeting with a Washington participant as covered.

Does the AI bot's appearance in the participant list constitute notice? Tools like Otter.ai and Fireflies.ai join meetings as named participants. The bot's presence is visible to all attendees. But visibility is not the same as consent. Washington's "reasonably effective manner" standard requires an announcement, not merely a presence.

Does a chat message satisfy the standard? Whether a chat message qualifies depends on whether participants are likely to see it, understand it, and have an opportunity to respond. In a large meeting where chat is active, a single notification message could easily be missed.

The Auto-Join Problem Under Washington Law

Auto-join features are particularly dangerous under Washington law. When an AI tool automatically joins meetings based on calendar integration, scenarios arise where: the user is present but does not announce recording; the user is not present and there is no consenting party; or some participants are unaware because they joined late or are audio-only and miss the notification.

In re Otter.AI Privacy Litigation (N.D. Cal., formerly Brewer v. Otter.ai) raises many of these same issues, alleging that Otter's auto-join feature recorded meetings without participants' consent. On August 13, 2026, the court let the federal Wiretap Act, California privacy, and Illinois biometric claims proceed, but dismissed the Washington Privacy Act claim, with leave to amend, because the Washington plaintiff had not alleged that the recorded conversation was private. The case is now in discovery, and no court has found that Otter broke any law.

Best Practices for Washington Compliance

Organizations with participants in Washington should adopt rigorous notification practices:

1. Verbal announcement at the start of every meeting: State clearly that recording is in progress, identify the tool, and give participants the opportunity to object or leave
2. Record the announcement itself: RCW 9.73.030 specifically requires that the announcement be recorded as part of the conversation
3. Obtain affirmative consent where possible: Rather than relying on implied consent from continued participation, ask participants to confirm they consent
4. Disable auto-join features: Manual activation for each meeting ensures the authorizing user is present and can make the required announcement
5. Document the consent process: Keep records of how notification was provided and whether any participant objected

Popular AI Meeting Tools and Washington Compliance

No tool is automatically compliant in Washington without a clear, affirmative announcement to all participants.

Cross-State Considerations

Washington Participants on Multi-State Calls

Courts have not settled which state's law governs a call that crosses state lines. Washington's own courts generally judge a recording by the law of the place where it is made. In State v. Fowler (2006), following Kadoranian v. Bellingham Police Department (1992), the Washington Supreme Court applied Oregon's one-party rule to calls with a Washington resident that were recorded in Oregon.

Fowler also noted that RCW 9.73.030 can still be violated by a recording made outside Washington if it is made for use as evidence in Washington by an agent of a Washington official or other person. Courts in other states may apply their own rules. The practical effect is that any meeting with a Washington participant should still be treated as requiring all-party consent, because that is the approach that is safe everywhere.

Washington shares borders with Oregon and Idaho. Idaho is a one-party consent state. Oregon is split: ORS 165.540(1)(a) is one-party for telecommunications and radio communications, but ORS 165.540(1)(c) separately bars obtaining any part of a conversation by device unless all participants are specifically informed that their conversation is being obtained, and ORS 165.535(1) defines a conversation to include a communication occurring through a video conferencing program. An in-person, hybrid, or video meeting held in Oregon therefore carries a duty to inform every participant. A participant who records a phone call from Oregon or Idaho with one party's consent may be judged by the law of the place of recording, as in Fowler, but announcing the recording to everyone, and recording the announcement, avoids the question.

Employer and Workplace Considerations

The Tech Industry Factor

Washington is home to some of the world's largest technology companies, including Microsoft, Amazon, and numerous AI startups. Employers in Washington's tech sector should ensure their internal use of AI meeting tools complies with RCW 9.73.030, including training managers on notification requirements and configuring AI tools to provide adequate notice before recording begins.

Remote Work and Distributed Teams

Washington's all-party consent requirement can reach meetings involving Washington-based remote workers. Washington courts generally apply the law of the place where a recording is made, so a recording made in Texas is not automatically governed by RCW 9.73.030. But courts have not settled which state's law governs a multistate meeting, and a recording made in Washington, or made elsewhere for use as evidence in Washington, can fall under the statute. This creates a practical incentive for employers to adopt all-party consent practices company-wide rather than attempting to track which meetings include Washington participants.

This article provides general legal information about Washington recording laws as they apply to AI meeting tools. Washington's all-party consent requirement imposes significant obligations on anyone using recording technology. Laws and their interpretations can change. Consult an attorney for advice specific to your situation.

More Washington Laws

• Washington Data Privacy Laws
• Washington Deepfake Laws
• Washington Employee Monitoring Laws
• Washington Recording Laws

Frequently Asked Questions

Can I legally use AI meeting recorders in Washington state?

You can, but only with the consent of all participants. Washington is an all-party consent state under RCW 9.73.030. Before recording, you must announce to all participants in a 'reasonably effective manner' that the conversation will be recorded. Activating an AI tool to record a private conversation without notifying everyone violates the statute, and because whether a meeting is private depends on the facts, the safe course is to treat every meeting as covered. The announcement must also be recorded as part of the conversation.

Are recordings made without consent admissible in Washington courts?

No. Under RCW 9.73.050, any recording obtained in violation of Washington's consent requirements is inadmissible in any civil or criminal case in Washington courts. There are only two narrow exceptions: when the recorded person gives permission to use it in a damages action, or in a criminal case involving national security.

Does an AI bot appearing in the meeting participant list count as consent notification?

This has not been decided by Washington courts as of August 2026. The bot's visible presence may contribute to notification, but RCW 9.73.030 requires an announcement made in a 'reasonably effective manner.' A bot name alone may not constitute an announcement that recording is occurring. The safest approach is to verbally announce recording at the start of the meeting.

What are the penalties for illegally recording in Washington?

Unlawful recording is a gross misdemeanor under RCW 9.73.080. That section sets the classification only; the maximum penalty comes from RCW 9.92.020, which allows up to 364 days in jail, a fine of up to $5,000, or both. Civil damages under RCW 9.73.060 include either actual damages (including mental pain and suffering) or liquidated damages of $100 per day up to $1,000, plus reasonable attorney fees. Beyond penalties, the recording is inadmissible in court.

How does Washington's law affect remote workers in other states?

Courts have not settled which state's law governs a multistate meeting. Washington's own courts generally apply the law of the place where the recording is made (State v. Fowler, 2006), so a participant recording from a one-party state is not automatically bound by Washington law, but a recording made in Washington, or made elsewhere for use as evidence in Washington, can fall under RCW 9.73.030. Employers with remote workers in Washington should adopt company-wide all-party consent practices rather than trying to track which meetings include Washington participants.