Resource
The removal itself is one click. The reasons it comes back are a team setting that overrides yours and an app that stays installed after you stop using it. Below: the in-call step, the uninstall on both the personal and admin side, the Fireflies settings that matter, and the three Zoom controls that keep any vendor’s bot out.
Open the participant list, click More next to Fireflies Notetaker, and choose Remove. Fireflies states that if the notetaker is removed before 3 minutes, no transcript or notes will be created.
Two footnotes. Fireflies’ pages label the bot slightly differently, as Fireflies Notetaker in one article and Fireflies.ai Notetaker in another, so look for either. And the three-minute claim is about transcript and notes creation only; Fireflies does not say what happens to audio from those minutes.
If you are not the host: Fireflies does not document what a non-host can do, and Zoom’s technical library describes removal as the host’s action. Fireflies’ own FAQ says the bot may request permission when you are not the host and that a host must admit it if there is a waiting room. In practice, ask the host to remove it or to leave it waiting.
Turn off auto-record. In Fireflies, open Settings, then Recording & Privacy, and toggle off Auto-record meetings.
Or join on invitation only. From the dashboard Upcoming panel, open Calendar meeting settings. The default is all meetings with a web-conference link; change it to Only when I invite fred@fireflies.ai.
The setting that overrides yours
On a team workspace, Fireflies documents an admin control under Settings, then Team, then Recording & Privacy, where the Auto-record meetings dropdown can be left at Allow teammates to choose or forced to a choice such as Record all calendar events with a meeting link or Only when invited. Fireflies describes this as letting admins control which meetings Fireflies can join and record for the entire team. If your personal toggle appears to do nothing, this is why, and the fix is a conversation with whoever administers the workspace.
Recording Rules are the other reason. They target meetings by keyword, email, or domain and take precedence over auto-join, which our Fireflies auto-join guide covers in full.
Stopping the bot and uninstalling the app are separate. The Fireflies app can sit in your Zoom library indefinitely after you stop using it.
Your own account. Zoom documents the path: sign in to the Zoom Workplace desktop app, open the Marketplace tab, then My Library, find the app, click More under Actions, choose Remove, and confirm.
For the whole Zoom account. An admin or owner signs in to the Zoom App Marketplace, opens Manage, then Apps on Account, then the Added Apps tab, selects the app, opens Manage app, and uses Remove App. Zoom says removing an app deactivates it for all users on the account and that it would need to be added again by a user or admin. Neither Zoom article states that removal revokes OAuth tokens, so do not assume it does.
From the Fireflies side. Fireflies documents Settings, then Integrations, then Zoom, then Disconnect, after which Fireflies says it will stop sending data to Zoom. Note the direction: that disconnects the integration that pushes notes into Zoom. It is not the same as revoking calendar access, which Fireflies documents only as account deletion under Settings, then Delete Account, with adjusting auto-join settings as the lighter alternative.
None of the Fireflies settings above touch a bot that somebody else’s account invited. Zoom documents three host-side controls that do, and its technical library confirms that automated tools joining as participants are visible to these features and that a host may remove or report an uninvited one.
For organizations, Zoom also documents an admin setting to allow or block specific SDK apps from joining as participants, under Admin Center Settings, then General, then Security, which Zoom describes as controlling unauthorized SDK apps from joining and accessing meeting content. Our general anti-bot guide covers the same controls on Meet and Teams.
All of this exists because a cloud notetaker needs your audio on its servers and sends a participant into the call to collect it. Capture on your own machine and there is nothing to remove, nothing to uninstall, and no domain to block.
Minutes records device-side and transcribes locally with whisper.cpp, writing markdown to your own disk. No bot joins and no audio is uploaded. Conversation content leaves your machine only when you send it somewhere, such as a summarizer you configured or an AI agent you connect; out of the box neither is happening, and the full list is on our security page. The direct comparison is at Fireflies and Minutes. And as with any recording, tell people; the consent rules are in recording consent law by state.
Next step
The Fireflies settings and recording rules, in full.
The Otter version, if that is the other bot in your calls.
The same bot on Teams, where roles decide who can remove it.
Every vendor and platform in one place.