Nevada AI Meeting Recording Laws (2026)

Nevada requires all-party consent to record wire communications under NRS 200.620, and virtual meetings such as Zoom and Microsoft Teams calls are most likely covered. Despite statutory language that could suggest one-party consent, the Nevada Supreme Court interpreted the law to require consent from every participant. Violations are a Category D felony.

Nevada's recording consent laws create a legal trap for users of AI meeting recording tools. The state applies two different consent standards depending on how the conversation takes place, and getting it wrong can result in felony charges. Wire communications, including phone calls and VoIP calls, require the consent of all parties under NRS 200.620, and virtual meetings over platforms like Zoom or Microsoft Teams are most likely covered. In-person conversations, by contrast, require only one-party consent under NRS 200.650.

This distinction matters enormously for AI meeting tools. A Zoom call recorded with an AI notetaker is most likely a wire communication. Every participant on that call must consent before the recording begins. An in-person meeting recorded with a voice recorder on the table requires only the consent of one participant. The same AI tool used in two different settings triggers two entirely different legal standards.

The penalties for getting it wrong are severe. Illegal wiretapping in Nevada is a Category D felony carrying 1 to 4 years in state prison. Civil liability adds another layer of exposure, with minimum damages of $1,000 per violation plus punitive damages and attorney fees.

Nevada's Recording Consent Framework

Wire Communications: All-Party Consent (NRS 200.620)

NRS 200.620 prohibits any person from intercepting or attempting to intercept any wire communication unless the interception is made with the prior consent of all parties to the communication. The statute's text references consent from "one of the parties," but the Nevada Supreme Court has interpreted this provision to require the consent of all parties.

This judicial interpretation is critical. Reading the statute in isolation might suggest that Nevada follows a one-party consent rule for wire communications. It does not. Nevada courts have consistently held that NRS 200.620 demands all-party consent for the lawful recording of telephone and electronic communications. Any reliance on the statute's literal text without accounting for the Supreme Court's interpretation would be a serious legal error.

NRS 200.610(2) defines a "wire communication" as the transmission of writing, signs, signals, pictures and sounds of all kinds "by wire, cable, or other similar connection between the points of origin and reception of such transmission." That plainly covers traditional telephone calls and wired VoIP.

Whether it also covers an internet video meeting is less settled than it may appear. NRS 200.610(3) puts transmission "by radio or other wireless methods" into a separate "radio communication" category, and NRS 200.620 reaches only wire communications. It is NRS 200.630, the disclosure ban, that covers wire and radio communications alike. No Nevada appellate decision has classified Zoom, Teams, or Google Meet traffic under NRS 200.610(2); the handful of Nevada cases construing NRS 200.620 all predate modern video conferencing or involve ordinary telephone calls.

The practical answer does not change: assume a virtual meeting is a wire communication and obtain all-party consent. But treat that as the safe working assumption rather than a settled holding, particularly where a participant joins over Wi-Fi or a cellular connection.

Where the Recording Happens: Ditech Financial v. Buckles

NRS 200.620 does not follow a Nevada participant everywhere. In Ditech Financial LLC v. Buckles, 133 Nev. Adv. Op. 64 (Sept. 14, 2017), the Nevada Supreme Court answered a certified question from the U.S. District Court for the District of Nevada and held "that NRS 200.620 does not apply when the act of interception takes place outside Nevada." Quoting the Washington Supreme Court's decision in Kadoranian v. Bellingham Police Department, it added that "interceptions and recordings occur where made."

The facts show why this matters. Ditech was a mortgage servicer whose call centers in Arizona and Minnesota recorded calls with a Nevada resident. The court held that the lawfulness of those recordings "is determined according to the laws of Arizona and Minnesota, the places where the conversations were intercepted and recorded, not according to the laws of Nevada where the calls were received."

Cloud AI notetakers sit squarely inside this problem. When Otter.ai, Fireflies.ai, or a platform's own server-side recorder captures a meeting, the act of capture happens on the vendor's infrastructure, which is rarely in Nevada. Under Ditech, that location is what decides whether NRS 200.620 applies at all. No Nevada court has yet applied Ditech to a cloud recording, and pinning down where a distributed recording is "made" is genuinely difficult, so neither side should treat the question as resolved. All-party consent remains the sound practice, but because of that uncertainty and because of other states' laws, not because NRS 200.620 automatically reaches every call a Nevadan joins.

In-Person Conversations: One-Party Consent (NRS 200.650)

NRS 200.650 addresses eavesdropping on private, in-person conversations. The statute prohibits surreptitious listening to, monitoring, or recording of any private conversation "unless authorized to do so by one of the persons engaging in the conversation." Unlike NRS 200.620, this provision genuinely operates as a one-party consent rule.

The one-party exception under NRS 200.650 means a participant in a face-to-face meeting can legally record the conversation without informing the other participants. An employee who activates an AI voice recorder during an in-person meeting in a Nevada conference room needs only their own consent.

The key limitation: NRS 200.650 applies only to private conversations. If a conversation takes place in a public setting where the participants cannot reasonably expect privacy (a crowded restaurant, a public sidewalk, an open office floor), the eavesdropping statute may not apply. Privacy expectations depend on the circumstances.

The Critical Split: Why It Matters for AI Tools

The divide between NRS 200.620 and NRS 200.650 creates a practical problem for AI meeting tools. Most modern AI notetakers (Otter.ai, Fireflies.ai, Fathom) are designed for virtual meetings, which are wire communications under Nevada law. That means every deployment of these tools in a Nevada meeting triggers the all-party consent requirement.

An employer who legally records in-person meetings under the one-party rule of NRS 200.650 cannot assume the same rules apply when the team switches to Zoom. The moment a meeting moves to a virtual platform, the consent threshold jumps from one party to all parties. Companies transitioning between in-person and remote work must adjust their recording policies accordingly.

What Constitutes "Consent" in Nevada

Nevada law does not specify a particular form of consent (written, verbal, or electronic). Courts have recognized that consent can be inferred from the circumstances. If a meeting participant is informed that recording is taking place and chooses to remain in the meeting, a court may find implied consent.

For AI meeting tools, practical consent mechanisms include verbal announcement at the start of the meeting that recording is active, a meeting platform's built-in notification banner (Zoom's "Recording" indicator, Teams' notification), written disclosure in the meeting invitation, and a separate consent form signed before the meeting. The safest approach in an all-party consent state like Nevada is to combine multiple methods: send written notice in advance, announce recording verbally, and use the platform's notification features.

AI Meeting Recorders and Nevada Law

How AI Meeting Bots Interact with NRS 200.620

AI meeting bots typically join virtual meetings as a separate participant. Otter.ai's OtterPilot, for instance, appears in the Zoom participant list as "Otter.ai Notetaker." Fireflies.ai's bot joins under a similar identifier. These bots record the meeting audio, generate transcripts, and in many cases analyze the conversation for action items, sentiment, and key topics.

Under NRS 200.620, the presence of a visibly named bot in the participant list may provide notice that recording is occurring, but notice is not the same as consent. All participants must affirmatively agree to the recording. A participant who does not notice the bot's name in a large meeting, or who does not understand what the bot does, has not consented.

The class action lawsuit against Otter.ai (In re Otter.AI Privacy Litigation, N.D. Cal., No. 5:25-cv-06911) centers on this exact issue. Plaintiffs allege that Otter's bots joined meetings and recorded participants who never consented. While the case was filed under California law, the same factual pattern would raise NRS 200.620 questions in Nevada whenever the recording is made in the state.

The Auto-Join Problem

Many AI meeting tools offer an auto-join feature that connects to meetings automatically based on the user's calendar. Otter.ai's default settings, for example, allowed the bot to scrape calendar invitations and join meetings without any manual activation by the host.

In an all-party consent state like Nevada, auto-join features create significant legal risk. The meeting organizer may not realize the bot is joining, and other participants certainly have not consented. Even if the organizer intended to record, the auto-join bypass removes the opportunity for consent to be obtained at the start of the meeting.

Nevada users of AI meeting tools should disable auto-join features, manually activate recording at the start of each meeting, and confirm consent from all participants before the AI tool begins capturing audio.

Voiceprint and Biometric Concerns

Several AI meeting tools use speaker identification technology that creates voiceprint profiles to distinguish between speakers and attribute text to the correct participant. Nevada has no comprehensive biometric privacy statute comparable to Illinois' BIPA, and no BIPA-style private right of action for the collection of a voiceprint.

Nevada does regulate biometric data in a narrower setting. NRS 603A.415 defines "biometric data" to include a person's "voiceprint," and NRS 603A.500 bars a regulated entity from collecting or sharing consumer health data without the consumer's "affirmative, voluntary consent." That scheme is limited in two ways that matter here: it turns on consumer health data specifically, and NRS 603A.425 excludes "a natural person acting in an employment context" from the definition of "consumer," so it will rarely reach an ordinary workplace meeting transcript.

Nevada's consumer privacy law (SB 220, codified at NRS 603A.300 to 603A.360) governs the sale of covered information and is likewise a poor fit for meeting voiceprints. For AI meeting tools, the consent rules in NRS 200.620 and NRS 200.650 remain the operative constraint, not Nevada's data privacy statutes.

Popular AI Meeting Tools and Nevada Compliance

No AI meeting tool is automatically compliant in Nevada for virtual meetings. The all-party consent requirement under NRS 200.620 means that every participant must agree to the recording before it begins. Platform notification banners provide notice but do not guarantee consent. The safest practice is to verbally confirm consent from every participant at the start of the meeting.

For in-person meetings recorded with AI voice recorders (not conducted over a wire), the one-party consent rule of NRS 200.650 applies, and the recording party's own consent is sufficient.

Penalties for Violations

Criminal Penalties

Violations of NRS 200.620 through NRS 200.650 are punished under NRS 200.690. Illegal wiretapping or eavesdropping in Nevada is a Category D felony.

Nevada's felony scale runs from Category A (most severe) to Category E (least severe); Category D sits one tier above Category E, not at the bottom. Unlike Category E felonies, which carry a statutory presumption of probation under NRS 193.130, a Category D conviction carries mandatory state prison exposure. A conviction creates a permanent felony record that affects employment, housing, and professional licensing.

Civil Damages

NRS 200.690 also establishes civil liability for illegal wiretapping. A person whose wire or oral communication is intercepted without consent can recover actual damages or liquidated damages of $100 per day of violation (with a minimum of $1,000, whichever is greater), punitive damages at the court's discretion, and reasonable attorney fees and litigation costs.

The $100-per-day structure creates escalating exposure for AI meeting tools that record over extended periods. An AI bot that records daily meetings without consent for 30 business days would face a minimum of $3,000 in liquidated damages per affected participant, before punitive damages and attorney fees.

Exclusion of Evidence

Communications intercepted in violation of Nevada's wiretapping statutes are generally inadmissible in court proceedings. This applies to AI-generated transcripts, meeting summaries, and any derivative work product based on an unlawfully recorded conversation. An employer who records workplace meetings without all-party consent cannot use those transcripts in disciplinary proceedings, litigation, or arbitration.

Employer and Workplace Considerations

All-Party Consent in the Nevada Workplace

Nevada employers must obtain consent from every meeting participant before deploying AI recording tools in virtual meetings. This requirement applies regardless of whether the participants are employees, contractors, clients, vendors, or other third parties. The employer's status as a party to the meeting does not exempt them from the all-party consent requirement for wire communications.

Practical steps for Nevada employers include adding recording consent language to meeting invitations sent through calendar systems, verbally confirming consent at the start of every recorded virtual meeting, providing a clear option for participants to leave without penalty if they decline recording, documenting consent in meeting records, and training employees on Nevada's all-party consent requirement for virtual meetings.

In-Person vs. Virtual Meeting Policies

The split between NRS 200.620 (all-party consent for wire communications) and NRS 200.650 (one-party consent for in-person eavesdropping) creates a policy challenge for Nevada employers. An employer can legally record an in-person conference room meeting without notifying all participants, but the moment that same meeting is conducted over Zoom or Teams, all-party consent becomes mandatory.

Employers should implement a single, unified recording consent policy that applies to all meeting types. Even though in-person meetings require only one-party consent, applying an all-party consent standard across the board simplifies compliance, reduces confusion, and eliminates the risk of accidentally applying the wrong rule.

Remote and Hybrid Work Complications

Nevada employers with remote employees in other states must account for cross-state consent requirements. When a Nevada-based employee joins a virtual meeting that is recorded from outside Nevada, Ditech Financial LLC v. Buckles indicates that NRS 200.620 may not reach the recording at all, because the statute applies to interceptions made in Nevada. The employee's location is not the trigger; the location of the recording is.

Conversely, when participants from other all-party consent states (California, Washington, Illinois) join a Nevada meeting, those states' laws may impose additional requirements or penalties. Because the place of recording is hard to pin down for a cloud tool, and because the strictest applicable state law effectively governs any multi-state call, obtaining consent from everyone remains the practical rule.

Employer Monitoring and Surveillance

The Nevada Employers Association has noted that employer monitoring of workplace communications must comply with NRS 200.620. Secret recording of employee phone calls or virtual meetings without all-party consent violates the statute, even when conducted for quality assurance, performance monitoring, or loss prevention purposes.

Employers who wish to monitor or record employee communications must provide clear notice and obtain consent. The "normal course of business" exception that exists in some states' wiretapping laws does not override Nevada's all-party consent requirement for wire communications.

Cross-State Meeting Considerations

Nevada's all-party consent requirement for wire communications has extraterritorial implications. When a Nevada resident participates in a virtual meeting with people in other states, the analysis depends on the other states' consent laws.

A Nevada participant's presence on the call is not by itself what triggers NRS 200.620. Under Ditech Financial LLC v. Buckles, the statute applies to an interception made in Nevada, because "interceptions and recordings occur where made." A recording captured entirely outside the state falls outside NRS 200.620 even though a Nevadan was on the line.

That does not make cross-state recording safe. Where a cloud recording is "made" is often unclear, since audio may be captured on vendor servers in one state, processed in another, and stored in a third, and no Nevada court has applied Ditech to that pattern. Other states' laws also apply on their own terms: if any participant is in California, Washington, or another all-party consent state, that state's requirements must be satisfied regardless of Nevada's reach. And a recording made in Nevada, for example on a Nevada host's own device, sits within NRS 200.620 directly.

Given the complexity of multi-state consent analysis, the safest practice for any meeting involving a Nevada participant is to obtain explicit consent from everyone on the call. This approach satisfies Nevada's all-party requirement and avoids the need for a state-by-state legal analysis of every participant's location.

The Otter.ai Litigation and Nevada Exposure

The consolidated class action against Otter.ai (In re Otter.AI Privacy Litigation, N.D. Cal., No. 5:25-cv-06911) has direct relevance for Nevada. The lawsuit alleges that Otter's AI bots recorded meetings without proper consent. While filed under California law, the same conduct could support an NRS 200.620 claim in Nevada if the recording were made in Nevada. Under Ditech Financial LLC v. Buckles, a recording captured on Otter's out-of-state servers would be tested under the law of the place of capture rather than Nevada's.

Key allegations from the Otter.ai litigation that intersect with Nevada law include the bot's auto-join feature recording participants without affirmative consent (an NRS 200.620 concern where the recording itself is made in Nevada), the use of recorded audio to train machine learning models without disclosure, and the collection of speaker identification data (voiceprints) without notice.

The Ambriz v. Google "capability test," established in a California court in February 2025, adds another dimension. The court ruled that an AI vendor's mere capability to use intercepted data for its own purposes supports a privacy claim, regardless of actual use. While this is a California precedent, Nevada courts evaluating NRS 200.620 claims against AI meeting tools may find the reasoning persuasive.

The case remains pending. On August 13, 2026, Judge Eumi K. Lee granted Otter.ai's motion to dismiss in part, and the litigation is continuing on the claims that survived. The outcome will likely influence how courts nationwide, including Nevada courts, evaluate AI meeting recording tools under state wiretapping statutes.

This article provides general legal information about Nevada recording laws as they apply to AI meeting tools. Laws and their interpretations can change. Consult an attorney for advice specific to your situation.

More Nevada Laws

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