The Otter AI Lawsuit: What It Means for Anyone Using AI in Confidential Meetings

If you use Otter AI in client meetings, there is a federal court case you need to know about. In re Otter.AI Privacy Litigation is pending in the Northern District of California. The first case was filed in August 2025 by a plaintiff who had never signed up for Otter — he was simply in a meeting where another participant had OtterPilot running. The motion-to-dismiss hearing was held May 20, 2026, in Courtroom 7 of the San Jose federal courthouse before Judge Eumi K. Lee. As of May 26, 2026, a ruling has not yet been issued. When it comes, it will be the first federal ruling on whether an AI bot sitting in a video call is covered by wiretap law.

The outcome matters beyond Otter. It will set a precedent for every cloud-based meeting tool in the market.

What the lawsuit actually alleges

The consolidated case bundles four separate suits filed between August and September 2025:

The incident that set everything in motion

Before the lawsuits, there was a tweet. In September 2024, an AI researcher named Alex Bilzerian had a Zoom call with a venture capital firm. Unremarkable while it lasted. A few minutes after it wrapped, Otter emailed him a transcript — including several hours of recording captured after the call formally ended, during which the investors had discussed what Bilzerian later described to The Washington Post as "strategic failures and cooked metrics." The bot had kept listening. The email had gone to everyone on the invite, including him.

Bilzerian posted the story on X on September 26, 2024. It reached over five million views. The VCs apologised. The deal did not happen. Otter's response: "Users have full control over conversation sharing permissions." That framing — the account holder's responsibility, not Otter's — is broadly the argument Otter is now making in federal court.

The core complaint is the same across all four cases. OtterPilot — now rebranded as Otter Meeting Agent — syncs with a user's calendar and auto-joins scheduled calls as a visible participant. According to the complaints, it records audio, transcribes in real time, and captures speaker voiceprints. Participants who have never created an Otter account receive none of this information before the recording begins.

Justin Brewer, the lead plaintiff, had never signed up for Otter. His February 2025 sales call was recorded because another participant on the call had OtterPilot enabled. He did not know the bot was present, had no account, no privacy policy to accept, and no opportunity to decline.

The legal claims run across the federal Electronic Communications Privacy Act (ECPA), California's Invasion of Privacy Act (CIPA), Illinois's Biometric Information Privacy Act (BIPA), and the Computer Fraud and Abuse Act. The damages exposure is significant: ECPA allows for the greater of $10,000 per violation or $100 per day. CIPA runs to $5,000 per violation.

Otter's position, stated in a motion to dismiss reply filed in April 2026, is that no interception occurred — and that its terms of service place responsibility for obtaining participant consent on the account holder, not on Otter itself.

Why this matters more in some meetings than others

For most internal team meetings, the practical risk is low. If you are using Otter to summarise a weekly standup or capture action items from an internal planning session, you are operating in different territory.

The problem concentrates in a specific type of meeting — the ones where confidentiality actually matters.

Client meetings governed by NDAs. Investor conversations before a funding round. Legal discussions protected by attorney-client privilege. Government contractor meetings with data residency requirements. These are the meetings where professionals assumed their content was safe — because they assumed "cloud" meant "private." It does not. Cloud means the audio went somewhere else, processed by someone else's infrastructure, under someone else's terms.

What "consent" actually means here

The lawsuit raises a consent question more complicated than it first appears.

When you sign up for Otter, you agree to their terms of service. Otter argues that covers their data use, and that obtaining consent from other participants is the account holder's responsibility. The plaintiffs argue that a product designed to auto-join and auto-record without affirmative consent from all participants is a problem by design — regardless of what the terms say.

There is also a second consent gap the lawsuit highlights: the people in your meeting who are not Otter users. They never created an account. They never accepted any terms. Their words, and potentially their voiceprints, were captured anyway.

In all-party consent states — California, Illinois, and several others — recording a conversation without the agreement of every participant is legally significant regardless of what the host agreed to. In a remote meeting environment where participants can be dialing in from anywhere, the host rarely knows which consent standard applies.

What this reveals about the underlying architecture

The Otter lawsuit is not really about Otter specifically. It is about a structural tension built into cloud-based meeting tools from the start — it took a lawsuit to make it visible.

Cloud transcription works on a pipeline: audio leaves your device, goes to a server, gets processed, comes back as text. That pipeline is what makes these tools powerful. It is also what makes them incompatible with environments where audio cannot leave the room.

The lawsuit asks the court to rule on whether that pipeline constitutes unauthorised access to private communications under federal wiretap law. But for professionals in NDA-sensitive environments, the question was always more practical: the audio left. The client did not consent. The NDA may have been violated the moment the bot joined the call.

The only architecture that eliminates this risk by design is local-first transcription — where audio is processed on your device, in memory, and never transmitted anywhere. Not a reduced version of the cloud pipeline. A fundamentally different approach.

BarnOwl is built on this architecture — private, local-first meeting transcription for professionals who cannot record meetings. Audio is processed on-device. No audio file is created. No data leaves your machine. No bot joins your call.

Otter is not alone — the wider reckoning

The litigation is expanding beyond Otter. Fireflies.ai now faces two separate BIPA class actions in Illinois, both centred on the same voiceprint capture allegation. Read AI has been banned — by policy rather than court order — from Zoom and Teams environments at the University of Washington, Chapman University, and UC Riverside. The pattern is clear: institutions that used to wave AI notetakers through without question are starting to ask harder ones.

Otter CEO Sam Liang's response to the litigation, in an October 2025 TechCrunch interview, was an argument about inevitability rather than consent: "If they accuse us, then they could accuse everyone else... My view is that we are on the right side of history. We're building this new AI revolution. If you want AI to help, you need to put AI in the meetings." Whether the law agrees is now the question before Judge Lee.

What to do right now if you use Otter in client meetings

You do not need to wait for the court's ruling to make a practical decision.

If you use Otter or any cloud-based meeting tool in meetings governed by an NDA, review what your NDA says about transmitting confidential information to third-party processors. Many standard NDA templates prohibit this. A cloud transcription service is a third party.

If your NDA is silent on the issue, raise it with your legal counsel before the next client meeting — not after.

If your meetings involve confidentiality requirements that cloud tools cannot structurally meet, the alternative category now exists: local-first transcription, running entirely on your device, with nothing leaving the room.

Frequently asked questions

The Otter lawsuit will be resolved by a court. The underlying problem — audio leaving meetings where it should not — is something you can address today, regardless of the outcome.