How to Turn Off Otter AI

You're in a meeting. A bot you didn't invite just joined. The participant list now includes "Otter.ai Notetaker," and it's recording everything you say. You need to know how to turn off Otter AI right now, not after the meeting, not after filing a support ticket. This guide is written for you, the person being recorded, not the admin who configured it. The steps are concrete, platform-specific, and ordered by speed.

Key Takeaways

• On Zoom, typing stop otter in the meeting chat removes the bot immediately, even if you don't have an Otter account.
• On Google Meet and Microsoft Teams, you can remove the bot from the participant panel, but you may need host or co-host permissions to do so.
• Removing the bot from one meeting is often temporary. If someone in the meeting has Otter connected to their calendar, auto-join will bring it back for the next one.
• To stop it permanently, you (or your admin) need to disconnect Otter's calendar integration or revoke its third-party access from your Google/Microsoft account settings.
• A federal class action is currently challenging whether Otter's visible-bot model constitutes informed consent. No court has ruled yet. Your right to remove the bot is the one control you have right now.

What Is the Otter Bot, Exactly?

It's a cloud-based participant that joins your video call, records the audio, and generates a transcript. The branding has shifted over time. Otter renamed "OtterPilot" to "Otter Notetaker," so you might see either name in the participant list depending on how recently the account owner's software updated. In litigation filings, it's called "Otter Meeting Agent." Same thing. It joins as an attendee, sits in the call, and captures everything.

The important structural detail: the bot doesn't require your permission to join. If someone else in the meeting has Otter connected to their calendar, the bot can auto-join without asking other participants for consent. It typically notifies the host. It does not, by default, ask you.

How Do I Remove Otter from a Zoom Meeting Right Now?

You have two options, and the fastest one doesn't require any special permissions.

Option 1: Type "stop otter" in the Zoom chat

Open the Zoom meeting chat and type stop otter. That's it. This removes the notetaker immediately, and it works even if you don't have an Otter account. No host permissions needed. The bot leaves.

This is the fastest path. If you're reading this mid-meeting, do this first and read the rest later.

Option 2: Remove it from the Participants panel

Click the Participants icon in Zoom's toolbar. Find "Otter.ai Notetaker" in the list. Hover over it and click Remove. This works if you're the host or co-host. If you're neither, the Remove option may not appear, and you'll need to fall back to the chat command above or ask the host to do it.

How Do I Remove Otter from a Google Meet Call?

Click the people icon to open the participant panel. Find the Otter bot. Open the three-dot menu next to it and select Remove. Otter's own help center confirms this works, though it may require host permissions depending on your organization's Google Workspace settings. If you're a regular attendee in a meeting someone else organized, you might not have the authority to remove participants. In that case, ask the host directly.

How Do I Remove Otter from a Microsoft Teams Meeting?

The process mirrors Google Meet. Open the participant roster, locate the Otter bot, and use the contextual menu to remove it. Otter documents this as a supported removal path across Zoom, Google Meet, and Teams, with the same caveat: your ability to remove a participant depends on whether the meeting organizer or your Teams admin has granted you those permissions.

Teams admins can also block third-party bot participants at the org level. If you're hitting a wall as an individual attendee, flagging it to your IT team is the faster route to a permanent fix. The same applies to Zoom admins, who can disable AI notetaker bots at the account or group level.

Why Does Removing It from One Meeting Not Fix the Problem?

Because auto-join runs off the calendar, not the individual meeting. Removing the bot from one call rarely stops it for good. If the person who connected Otter to their calendar still has that integration active, the bot will show up again at the next scheduled meeting. You're playing whack-a-mole.

Disabling auto-join in Otter's settings stops the bot from joining automatically, but Otter still retains access to the calendar. It can see your upcoming events. It just won't act on them until someone toggles auto-join back on or manually sends the bot to a specific meeting. To remove calendar visibility entirely, the calendar integration itself needs to be disconnected.

This is the core frustration. The person who connected Otter may not be you. It may be a colleague who set it up months ago, forgot about it, and now the bot arrives at every recurring standup like an uninvited guest who knows the door code.

How Do I Permanently Stop Otter from Accessing My Meetings?

There are two layers: what the Otter account owner can do, and what you can do from your own accounts regardless of who set Otter up.

If you are the Otter account owner

Log into Otter. Go to settings. Disable auto-join for meetings. Then go further and disconnect your calendar integration entirely. Disconnecting the calendar removes Otter's access to all future events, not just the auto-join behavior.

If someone else connected Otter and you want to cut off access from your side

You can revoke Otter's third-party access at the account level. For Google accounts, go to your Google account security settings, find Otter.ai under "Third-party apps with account access," and remove it. The path is: Google Account → Security → Your connections to third-party apps & services → Otter.ai → Remove Access. For Microsoft accounts, the equivalent is in the Microsoft Account privacy or app permissions dashboard.

This doesn't stop someone else's Otter from joining meetings you're invited to. It stops Otter from using your calendar as a source of meeting links. The distinction matters. If your colleague's Otter account is the one auto-joining, revoking your own access won't help. You'd need to ask them to disconnect, or ask your org admin to block the bot at the platform level.

What If I Can't Remove the Bot and Don't Have Admin Access?

This is the scenario nobody wants to talk about. You're in a meeting. The bot is recording. You don't have host permissions. The chat command doesn't work (it's platform-specific to Zoom). The meeting organizer doesn't respond when you ask them to remove it.

Your options at that point are limited to the social and the procedural. You can state on the record that you do not consent to being recorded. You can leave the meeting. You can escalate to your organization's IT or legal team afterward.

None of these are great. They all involve friction, awkwardness, or a delay. And that's the point worth sitting with for a moment: the product's architecture puts the burden of opting out on the person who didn't opt in.

Why Does This Require So Many Steps?

Because the system was designed around the preferences of the person who subscribes to Otter, not the people in the meeting. The subscriber connects their calendar. The bot auto-joins. The host gets a notification (sometimes). Everyone else gets a new participant in the call they didn't expect.

To fully disentangle yourself, you potentially need to: remove the bot from the live meeting, disable auto-join in someone else's Otter settings, disconnect the calendar integration, revoke third-party app access from your own Google or Microsoft account, and confirm the bot hasn't already captured a transcript of the current session. That's five distinct actions, spread across three or four different interfaces. Multiple independent guides exist precisely because no single step is sufficient.

The number of steps is itself a design finding. Consent-by-default systems that require multi-step opt-out from the uninvited party have the relationship backwards.

Is There a Legal Issue with Otter Recording Without My Consent?

There's an active, unresolved one. A consolidated federal class action, In re Otter.AI Privacy Litigation (N.D. Cal.), alleges that Otter records audio and captures biometric data without participant consent. The case centers on how the Otter Meeting Agent integrates into calendars to log audio, transcripts, and voiceprints. Plaintiffs from eleven two-party-consent states argue that a visible bot in the participant list is not the same as informed consent.

Otter's position, as reported, is that the bot's visible presence in the meeting constitutes sufficient notice. A motion-to-dismiss hearing was held before Judge Lee on May 20, 2026, and no ruling had been issued as of late June 2026. As of July 2026, the motion to dismiss is fully briefed with oral argument set for August 2026. No court has found Otter's practices either lawful or unlawful. The question is genuinely open.

This matters for you practically because it means the legal framework hasn't established clear protections yet. Your ability to remove the bot mid-meeting is the one concrete control you have while the law catches up.

What Happens to the Data Otter Already Captured?

Removing the bot stops the recording going forward. It does not retroactively delete what was already captured. If the bot was in your meeting for ten minutes before you noticed it, those ten minutes are in Otter's system.

Otter's privacy policy permits users to grant Otter and third parties permission to use conversations for training and product improvement via a checkbox that many overlook. This means the data question extends beyond "was I recorded" to "what happens to my recording after." If data use for training is a concern, that's a separate conversation to have with whoever in your organization holds the Otter subscription.

Can My Organization Block AI Notetaker Bots Entirely?

Yes, and an increasing number are doing so. Reporting from 2026 describes a broader "bot fatigue" backlash, with enterprises banning cloud-based AI bots over data security and consent concerns. The objection is structural: bots that record without explicit, verifiable consent from every participant and store audio on third-party servers create liability that many organizations aren't willing to accept.

Zoom admins can disable AI notetaker bots at the account or group level, which prevents them from joining any meeting in the organization. Google Workspace and Microsoft Teams admins have similar controls. If you're not the admin, the best path is to surface the issue to whoever is, ideally with a reference to the pending litigation so it gets prioritized appropriately.

What About Otter's Support Process?

It may not be fast. One user reportedly waited five months for a response from Otter's support team after trying to disconnect the service, eventually deleting everything and unsubscribing. That's a single secondhand account, not a systematic finding, but it's consistent with the general pattern of consumer AI tools that are easy to connect and harder to fully remove.

Don't rely on support as your primary removal path. Use the direct technical steps outlined above. If those fail, escalate through your organization's IT.

A Quick Reference: What to Do, in Order

1. Right now, in Zoom: type stop otter in the meeting chat.
2. Right now, in any platform: open the participant panel, find the Otter bot, remove it (requires host/co-host permissions).
3. After the meeting, if you're the Otter subscriber: disable auto-join in Otter settings, then disconnect your calendar integration.
4. After the meeting, if someone else set it up: revoke Otter's third-party access from your Google or Microsoft account security settings.
5. For a permanent org-wide fix: ask your Zoom/Meet/Teams admin to block third-party AI notetaker bots at the platform level.

Why This Problem Shouldn't Exist

The fact that "how to turn off Otter AI" is a search query at all says something about the consent model. A recording tool that requires guides, chat commands, and multi-step revocation procedures for the people being recorded has the power dynamic inverted. The subscriber gets convenience. Everyone else gets a participant they didn't invite, capturing audio they didn't agree to share, with data policies they didn't review.

There's a simpler model. Recording happens on the device of the person who wants the transcript. Nothing joins the call. No bot appears in the participant list. No one else needs to learn a chat command to protect themselves. The recording party owns their own data. Everyone else is left alone.

We built Selina around a different premise entirely: your data stays yours, memory is encrypted at rest, and nobody else's meeting gets a surprise participant because of your settings.

If that sounds worth trying: start a free 7-day trial, no card required.

Michael C.

Founder & Principal Engineer, Selina Labs

Michael builds Selina, a privacy-first AI that remembers you across conversations. He ships security-sensitive AI in production — real attacks, real fixes, measured in minutes and dollars — and writes about privacy, security, and LLMs from that seat. Top Rated Plus and expert-verified on Upwork.

• www.upwork.com
• x.com
• medium.com
• selinalabs.io