Is Otter.ai Safe? What the 2026 Class Action Means for Everyone on the Call

If you've never created an Otter account, you might assume the lawsuit against Otter.ai has nothing to do with you.

The plaintiffs would disagree.

In August 2025, a class-action complaint was filed in the Northern District of California against Otter.ai, alleging that its OtterPilot feature violates the federal Wiretap Act and the California Invasion of Privacy Act (CIPA). The case is now consolidated under In re Otter.AI Privacy Litigation. A motion to dismiss was heard on May 20, 2026. As of this writing, the court has not yet issued a ruling — the matter is still under submission.

The central claim isn't about a data breach or a rogue employee. It's about a product working exactly as designed: an AI bot that joins your meetings and records everyone in them, including people who never agreed to be recorded by a third-party service.

What OtterPilot Actually Does

Otter.ai's core product is AI transcription — you record a meeting, upload the audio, and receive a searchable transcript. OtterPilot is the feature that automates the recording step: connect your Google Meet, Zoom, or Microsoft Teams calendar, and OtterPilot can automatically send a bot to join meetings on your behalf.

That automation is the product's value proposition. You don't have to remember to start a recording. You don't have to be present in the meeting for the transcript to happen. OtterPilot attends, records, and delivers.

According to the lawsuit's complaint, the problem is how that bot functions once it's in a meeting. The complaint alleges that OtterPilot joins calls and captures the audio of everyone present — not just the Otter subscriber who set it up. If the meeting host has OtterPilot connected to their calendar, the bot can join without requiring affirmative consent from any other participant, including those who have never used Otter and have no agreement with the company.

The complaint goes further: it alleges that Otter uses the audio captured in those meetings to train its machine-learning systems, deriving commercial value from conversations that third-party participants didn't consent to share.

No court has found these allegations proven. Otter disputes them. But the legal question they raise — does automatically recording meeting participants without their individual consent violate federal wiretap law? — is precisely what the pending ruling will address.

The Consent Question

The federal Wiretap Act prohibits the intentional interception of wire or electronic communications without the consent of at least one party to the communication. Many states, including California, go further and require the consent of all parties before a conversation can be recorded. These are often called "two-party consent" or "all-party consent" laws.

When someone invites OtterPilot to a meeting, the Otter subscriber has consented to being recorded. Under federal law, that might be sufficient — one party's consent can make a recording lawful. Under California law, it isn't enough.

But the lawsuit argues that the consent question runs deeper than one-party vs. all-party. The plaintiffs contend that the people being recorded — attendees who never agreed to Otter's terms, never connected their calendars, and may not have known a third-party service was present — can't be said to have consented to something they didn't know was happening. They aren't parties to the Otter agreement. Their audio is being captured and potentially used by a company they've never interacted with.

Whether that constitutes an actionable wiretap violation is a novel question that federal courts haven't conclusively resolved — which is exactly why this case is being watched closely by the legal and HR communities. HR Executive called it something every HR leader should have on their radar. Jackson Lewis, a major employment law firm, published an analysis calling it a case study in the legal risks of AI note-takers.

Why You May Already Be Affected

If any of the following describe you, you may have been recorded by OtterPilot without your knowledge:

• You've had a video call with someone who uses Otter.ai and has OtterPilot connected to their calendar.
• You've met with a recruiter, hiring manager, or HR professional who uses Otter for candidate interviews.
• You've been on a client call, vendor meeting, or internal sync where the other party had OtterPilot set to auto-join.

Otter reported over 19 million users as of late 2024. OtterPilot is actively promoted as the primary enterprise feature. If you've had meetings with a meaningful number of knowledge workers over the past two years, the probability that at least one of those meetings was captured by OtterPilot without your direct knowledge is not small.

You may not remember seeing a bot in the participant list. OtterPilot typically appears as "Otter.ai Notetaker" — but in a large meeting, an unfamiliar participant name often doesn't register. And if OtterPilot auto-joined because the host's calendar was integrated, the host may not have actively sent it for that specific call.

What It Means for the Note-Taker Industry

Otter is not the only service that works this way. Fireflies.ai, tl;dv, and most other bot-based meeting recorders operate on the same architecture: a bot joins your call, captures audio, processes it in the cloud, and returns a transcript. The consent question the Otter lawsuit raises applies equally to all of them.

That's why the case is significant beyond Otter's own user base. If a federal court finds that automatically recording meeting participants without their individual consent violates the Wiretap Act, it isn't only Otter that faces pressure to change its product. It's every service that sends a bot into a meeting someone else organized.

A visible market shift is already underway. A growing segment of the note-taker category has moved toward what the industry calls "bot-free" recording — tools that capture audio directly from the local device using the microphone and system audio, rather than sending a third party into the call. From the other participants' perspective, no one new enters the meeting. The recording is happening on the device of someone who is already a party to the conversation.

This design significantly narrows the legal exposure. There's no third party joining without consent — just one of the participants making a record of a call they're already in. Whether that recording is lawful still depends on jurisdiction and disclosure practices, but it sidesteps the specific allegation at the center of the Otter case.

What to Check If You Use a Note-Taker

Is your note-taker bot-based or bot-free? The distinction matters legally. If your tool sends a bot into meetings, your participants may be affected by consent requirements even when you're the one who set up the account — and you may bear the compliance responsibility.

Is auto-join enabled? The lawsuit's most specific allegations concern meetings where OtterPilot joined automatically, without the host manually dispatching it for that call. Review your calendar integration settings and know what's running by default.

What does your jurisdiction require? California, Florida, Connecticut, Washington, and several other states require all-party consent for recorded conversations. If your meetings include participants from those states, a single-party federal standard doesn't govern — even if you're the account holder.

What does the tool do with recorded audio? The Otter complaint specifically alleges that audio is used for AI training. This is worth verifying in the terms of any tool you use. Transcription for your own notes is one use; training a commercial AI model on your participants' words is another — and most users haven't examined what their tool's terms permit.

Do your participants know? Clear disclosure at the start of a recorded meeting is both sound professional practice and, in all-party consent jurisdictions, a legal requirement. Don't assume the tool handles this for you.

The Architecture That Avoids This Entirely

The Otter lawsuit is, in part, a case about a tool doing exactly what it was built to do. The problem isn't deception — it's that the product's design creates legal exposure for people who aren't Otter's customers.

There's an alternative architecture for AI in meetings that sidesteps this entirely: tools that run as overlays on the local device rather than bots joining the call from outside. Meeting Copilot operates as a desktop application that captures audio from the user's own device — mic and system audio — and provides real-time suggestions in a window only they can see. No bot enters the call. No third-party service is recording other participants. The session is started and stopped deliberately by the user and exists only on their machine.

For anyone using AI assistance in job interviews, sales calls, or high-stakes negotiations, that architecture doesn't just reduce legal risk — it changes the basic relationship. You're not putting the other people in your meetings inside a system they didn't agree to. You're getting help for yourself, in a window only you can see, in the conversation you're already in.

An Open Question Getting a Legal Answer

In re Otter.AI Privacy Litigation is one of the first federal tests of whether wiretap law applies when an AI bot joins a meeting and records participants who never agreed to be recorded. The ruling — whenever it arrives — will establish precedent that shapes how the entire industry operates.

Settlement discussions have begun in at least one proceeding related to the case, suggesting some parties see meaningful exposure regardless of how the motion to dismiss resolves. Whatever the outcome, the litigation has already changed how HR departments, legal teams, and compliance professionals think about AI recording tools. The calendar integrations and auto-join defaults that seemed unremarkable two years ago are now receiving scrutiny they weren't designed to withstand.

The question of whether you've been recorded in a meeting you thought was private may already have an answer you don't know. Whether that recording violated the law is what the court is deciding. What you choose to use going forward is up to you.