Otter.ai Lawsuit: Recording Consent Class Action Explained (2026 Buyer's Guide)

The Otter.ai lawsuit recording consent class action most people are searching for is In re Otter.AI Privacy Litigation, case number 5:25-cv-06911 in the Northern District of California — a consolidated proposed class action alleging that Otter's OtterPilot bot joined Zoom, Microsoft Teams, and Google Meet calls, recorded participants without all-party consent, and used the audio to train Otter's AI models. On August 13, 2026, Judge Eumi K. Lee let the core federal Wiretap Act, California Invasion of Privacy Act (CIPA) §631, and Illinois BIPA voiceprint claims proceed toward discovery. No class is certified, no court has ruled Otter broke the law, and Otter denies wrongdoing. If you are a PR agency owner, CPA, in-house counsel, or lawyer vetting an AI notetaker under ABA Formal Opinion 512, this page gives you the case facts, the state-by-state consent exposure, and a buyer's framework for picking a tool that actually survives security review.

What the Otter.ai lawsuit actually alleges

The lead case, Brewer v. Otter.ai, Inc., was filed on August 15, 2025 in federal court in the Northern District of California. According to NPR's reporting on the complaint, the suit accuses Otter.ai of "deceptively and surreptitiously" recording private work conversations and using those recordings to train its transcription service without permission from the people being recorded.

The named plaintiff, Justin Brewer of San Jacinto, California, has never held an Otter account. He joined a Zoom meeting on February 24, 2025 where another participant was running OtterPilot, and alleges he discovered Otter had recorded a confidential conversation he never agreed to share. The complaint pleads that "if the meeting host is an Otter accountholder who has integrated their relevant Google Meet, Zoom, or Microsoft Teams accounts with Otter, an Otter Notetaker may join the meeting without obtaining the affirmative consent from any meeting participant, including the host," according to the same NPR writeup.

Between August and September 2025, three more putative class actions followed. The court consolidated them into In re Otter.AI Privacy Litigation before Judge Eumi K. Lee. Courthouse News summarized the resulting posture: the lawsuit claims Otter.ai illegally records and transcribes meetings without obtaining all participants' consent, as required in states including California, Illinois, and Washington.

The August 13, 2026 ruling: what survived, what didn't

Otter.ai moved to dismiss the consolidated complaint. On August 13, 2026, Judge Lee granted that motion only in part. According to the RecordingLaw analysis of the order, the court held that "plaintiffs plausibly alleged Otter acts as a third-party eavesdropper," and let the federal Wiretap Act claim, the CIPA §631 claim, both Illinois BIPA voiceprint claims, unjust enrichment, and the Unfair Competition Law claim proceed toward discovery.

CFAA, CDAFA, and Washington Privacy Act claims were dismissed with leave to amend. Mealey's Litigation Report noted that the court ruled plaintiffs failed to sufficiently plead unauthorized computer access and, for several plaintiffs, a reasonable expectation of privacy, but allowed the claims grounded in real-time interception, third-party eavesdropping, and biometric voiceprint collection to continue.

The practical significance: this is the first federal order that treats an AI meeting bot as potentially a separate, third-party eavesdropper under the Wiretap Act, rather than an invited participant acting through the host. BIPA alone, as RecordingLaw observes, allows statutory damages of "$1,000 to $5,000 per violation without proof of actual harm," which scales rapidly across a class.

Current status (as of October 31, 2026)

Per the Scribbl case tracker, no court has ruled that Otter broke the law. Otter filed its answer denying the claims on September 17, 2026, and the case is now in discovery with a class certification motion due by May 13, 2027. Our earlier walkthrough of the May 20, 2026 motion-to-dismiss hearing is here: In re Otter.AI Privacy Litigation: What the May 2026 Hearing Means.

Why California's all-party consent rule is the real engine of this lawsuit

The reason OtterPilot's "silent participant" architecture is dangerous isn't that it's new technology — it's that California wiretap law was already strict. The Privacy Rights Clearinghouse CIPA overview explains that California is an "all-party consent" state: every participant in a confidential communication must consent before it can be recorded or monitored, which makes CIPA stricter than federal law and most other states.

The statute, codified at Cal. Penal Code §§ 630–638.55, dates to 1967. RecordingLaw's CIPA explainer describes the Otter ruling as the clearest example yet of CIPA's all-party rule being applied to an AI tool that a meeting host invites, rather than to the host's own recording decision — because "the court held Otter is a third-party eavesdropper under CIPA Section 631, not an invited participant, because it independently retains and uses the recordings for its own commercial purposes."

Prior consent must be real. In Javier v. Assurance IQ, LLC, the Ninth Circuit held that §631(a) requires prior consent of all parties, and that retroactive consent — such as agreeing to a privacy policy displayed after the recording has begun — does not ratify the violation. That's bad news for any notetaker whose "consent" lives in a terms-of-service click by one account holder.

What this means for buyers: PR, CPAs, lawyers, and in-house counsel

If you run a PR agency handling crisis calls and embargoed launches

• Any cloud notetaker that uploads audio to a vendor server creates a disclosable third-party processor you may have to name to clients.
• Your clients likely have NDAs covering embargo material. A "de-identified" training pipeline — which Otter asserts in its policies — is not the same as not retaining the content.
• Pick a tool that keeps audio on the host's device and give clients a one-line disclosure: "This call is being transcribed on my device; nothing is uploaded."

If you're a CPA on tax-season calls

• IRS §7216 restricts disclosure or use of tax return information. A cloud transcription vendor is a disclosure risk unless you have specific written consent.
• On-device tools eliminate the §7216 "auxiliary services" question for the transcription itself. See our guide to Section 7216 and AI notetakers for CPAs.

If you're a lawyer vetting under ABA Formal Opinion 512

• Opinion 512 requires you to understand how a generative AI tool handles client information, including training use, retention, and third-party access.
• The due-diligence surface for an on-device app that never leaves your Mac is dramatically smaller than for a cloud vendor like Otter or Fireflies. Our walkthrough: ABA Opinion 512 and AI meeting recording.

If you're in-house counsel and IT banned Otter and Fireflies

• Push for "no network access during recording" as a hard requirement, not just SOC 2.
• SOC 2 Type II tells you the vendor manages their own controls — it does not tell you the audio never leaves your device.

Comparison: Otter, Fireflies, Zoom AI Companion, and on-device Basil AI

The question most buyers ask after reading about the lawsuit is: "what should I use instead?" Here is a fair-to-competitors comparison of the four architectures AI shoppers evaluate most often.

Fair-to-competitors note: Otter has publicly argued that it does not initiate recordings on its own, and that its Terms of Service require users to obtain any necessary permissions, per statements covered by UC Today's coverage of CEO Sam Liang's defense. The court will decide whether that is enough.

The ABA Opinion 512 due-diligence question (and why on-device is easier to vet)

If you're a lawyer, your state bar and ABA Formal Opinion 512 require you to vet any generative AI tool before using it with client information. Jackson Lewis's Workplace Privacy Report notes that the Brewer complaint underscores "consent gaps are a liability" and warns that single-consent models are risky in all-party states like California.

Due diligence on a cloud vendor like Otter or Fireflies requires you to evaluate:

• Where audio is stored and for how long
• Which sub-processors can access it (and from which countries)
• Whether the vendor can use your audio to train models
• How breach notification works
• Whether consent can satisfy CIPA, BIPA, and your own state wiretap statute

Due diligence on an on-device app is shorter: audio never leaves the device, so most of those questions are N/A. That's the practical reason legal and compliance teams are increasingly looking at local-first notetakers after the Otter ruling.

Private alternatives: the fair landscape

Several categories of "private" or local AI notetaker now exist. Buyer-oriented review sites covering this space include Meetily, open-source projects referenced by developers, and roundups like Mumble's guide to local AI meeting notetakers on Mac. Each has trade-offs. Honest comparison:

• Hyprnote / Granola / Fathom — record locally but still send transcripts or summaries to a cloud LLM in most configurations. Read our Hyprnote buyer guide for pricing details.
• MacWhisper / Aiko / open-source Whisper — fully offline transcription, but no built-in meeting workflow, summaries, or Apple Notes export.
• Basil AI — on-device recording and transcription using Apple Speech Recognition, with summaries, speaker labels, and Apple Notes integration.

For the broader category, see our deep dive: Bot-free AI meeting notes with on-device processing.

How Basil AI solves this

The thing the Otter lawsuit is really about is architecture: a cloud notetaker depends on sending audio to a vendor, and that vendor becomes a third party for wiretap purposes. Basil AI is built so that question never comes up.

• 100% on-device processing. Recording and transcription run locally on your Mac or iPhone using Apple's on-device Speech Recognition. See Apple's Speech framework documentation and Apple's privacy overview.
• No bot joins the call. You record on the host side, so there is no visible third-party participant like OtterPilot — and no vendor server retains or trains on the audio.
• No training on your data. There is no cloud pipeline to send audio to; the question of whether "de-identified" training applies simply does not arise.
• Host-controlled consent workflow. You can announce the recording and log the response in the meeting itself. For an all-party consent state, that is the standard way to establish implied consent at the start of a call.
• Works offline. If your laptop is on an airplane or inside a corporate network with no outbound internet, Basil still records and transcribes.

None of this is a legal claim about Otter or any particular user's situation. It is an architectural fact: on-device audio has no vendor server to subpoena, breach, or litigate over.

Practical checklist before you record your next call

1. Confirm whether any participant is in California, Illinois, Florida, Washington, Oregon, Pennsylvania, or another all-party consent state. If yes, assume all-party consent is required.
2. Announce the recording verbally at the start of the call: "I'm using an on-device transcription tool to take notes. Is everyone okay with that?"
3. Wait for a verbal yes. Under Javier v. Assurance IQ, retroactive consent doesn't satisfy §631(a).
4. If anyone objects, stop recording.
5. Keep the transcript on your device. Do not forward it to vendors who may use it for training.

Download Basil AI

Basil AI is a privacy-first, on-device AI voice recorder and meeting notetaker for iPhone, iPad, and Mac. 8-hour continuous recording, real-time transcription using Apple Speech Recognition, Apple Notes integration, speaker labels, and "Hey Basil" voice activation — all without any audio leaving your device.