Brewer v. Otter.ai started with one sales call. The whole category is watching how it ends.
By Kyle Nelson, Founder, Fazit
Brewer v. Otter.ai is the case people mean when they search for the Otter AI lawsuit: the first of four 2025 class actions, now consolidated as In re Otter.AI Privacy Litigation, and the closest thing the AI notetaker category has to a test of its default architecture. This page is the case file in plain language: what was filed, what it became, what happened at the August hearing, and what has actually been decided, which is nothing yet.
Last updated August 11, 2026. Case status checked against the public docket and courtroom reporting on that date.
The filing
In February 2025, Justin Brewer, a California resident who has never held an Otter account, joined a sales call. Another participant was running OtterPilot, Otter’s meeting bot. The complaint he filed that August in the Northern District of California alleges the call was recorded, transcribed, and transmitted to Otter’s servers, and from there into the training pipeline for Otter’s speech-recognition models, all without his knowledge or consent.
The legal claims stack four ways: the federal Wiretap Act and the Computer Fraud and Abuse Act on the federal side, and the California Invasion of Privacy Act and Unfair Competition Law on the state side. California is an all-party consent state, which is why one participant clicking “agree” is the entire dispute rather than the end of it.
Three more putative class actions followed within weeks. On October 22, 2025, Judge Eumi K. Lee consolidated all four as In re Otter.AI Privacy Litigation, No. 5:25-cv-06911, and a consolidated complaint landed on December 5. The full docket is public at CourtListener.
Where the case stands
BREWER v. OTTER.AI, AS A TIMELINE
Feb 2025 the sales call the complaint is built on
Aug 2025 Brewer v. Otter.ai filed, N.D. Cal.
Sep 2025 three more putative class actions follow
Oct 22 2025 all four consolidated before Judge Eumi K. Lee
as In re Otter.AI Privacy Litigation,
No. 5:25-cv-06911
Dec 5 2025 consolidated complaint filed
May 20 2026 motion to dismiss argued, taken under submission
Aug 4 2026 further hearing; Judge Lee "not persuaded"
plaintiffs lack standing
Today still no ruling. Nothing decided, either way.Otter moved to dismiss the consolidated complaint, arguing no unlawful interception occurred and that the plaintiffs had not plausibly pleaded their claims. The motion was argued on May 20, 2026 and taken under submission. At a further hearing on August 4, 2026, MLex reported that Judge Lee said she was “not persuaded” the plaintiffs lacked standing to sue.
Read that carefully for what it is: a judge signalling doubt about one of the defendant’s dismissal arguments, in open court, before ruling. It is not a finding that Otter did anything unlawful, and it does not predict the outcome on the substantive wiretap questions. But standing was one of the cleaner exits available to Otter, and the court sounded unconvinced by it.
What a complaint does not establish
Every sentence in the filings above is an allegation. Otter denies the claims, no court has ruled on them, and the motion to dismiss could still end the case before discovery opens. A complaint is a theory told entirely from one side, drafted to survive exactly the motion now pending. Treat every “Otter did X” in coverage of this case, ours included, as “the plaintiffs allege Otter did X.”
What the case has already established is different, and it does not need a ruling: the default architecture of a cloud notetaker, where the vendor ends up holding a recording that only one participant agreed to, is now the explicit subject of federal litigation. The same is true of the Granola case filed in July 2026, which runs a similar theory against a notetaker that sends no bot at all. Together they mark out the category's real question: not whether the note is good, but who else ends up holding the conversation.
The part that applies beyond Otter
The plaintiffs in this case are meeting participants suing over a tool a counterparty used. That framing should stop every professional who points a notetaker at client calls, because it puts the user of the tool, not only the vendor, inside the consent question. We walked through that exposure, including the $5,000-per-recording statutory damages figure under California Penal Code § 637.2, in the AI notetaker legal risk post, and the broader safety review of Otter itself is in Is Otter.ai Safe?
The structural point is the one worth carrying out of the courtroom: every claim in the consolidated complaint attaches to an artifact, the stored recording on a vendor’s server. An architecture that never creates that artifact, where audio stays in RAM on your own machine, is transcribed locally, and is destroyed when the session ends, has nothing for this kind of case to attach to. That is Fazit’s design, documented invariant by invariant on the security page. Consent and candour with your counterparties still apply to note-taking of any kind; the stored voice recording put to uses nobody agreed to is the specific thing that structurally cannot exist.
Frequently asked questions
What is the Otter AI lawsuit?
In re Otter.AI Privacy Litigation (N.D. Cal. No. 5:25-cv-06911) is a consolidated putative class action built from four 2025 suits, the first of them Brewer v. Otter.ai. It alleges Otter’s meeting bot recorded participants without all-party consent and that recordings fed Otter’s model training, claiming violations of the federal Wiretap Act, the Computer Fraud and Abuse Act, the California Invasion of Privacy Act and California’s Unfair Competition Law. Otter denies the claims; no court has ruled on them.
Who is the plaintiff in Brewer v. Otter.ai?
Justin Brewer, a California resident with no Otter account. His complaint alleges a February 2025 sales call he joined was recorded and transcribed by OtterPilot because another participant ran the tool, and that the conversation reached Otter’s servers and training pipeline without his consent.
What happened at the August 2026 hearing?
At an August 4, 2026 hearing on Otter’s motion to dismiss, Judge Eumi K. Lee said she was “not persuaded” that the plaintiffs lacked standing to sue, per MLex’s courtroom reporting. That is a signal about one dismissal argument, not a ruling. The motion, first argued May 20, 2026, remains under submission.
Has the court ruled on the Otter.ai motion to dismiss?
No. As of August 11, 2026 the motion is under submission and nothing has been decided either way. Dismissal, survival into discovery, and settlement all remain open outcomes, and each would land differently on the rest of the cloud notetaker category.