AI meeting notetaker privacy involves more than the person who enables the tool. Other participants may have no account with the service, yet their voices and contributions can become part of a stored meeting record. The questions I would settle first are who is informed, what is captured, who can stop it, and where the result goes.
I use none of the products examined here, so this is a documentation review rather than a hands-on comparison. I also cannot reliably say whether I have attended a call with someone else’s notetaker running. That uncertainty is a reason to ask at the start of a meeting; it is not evidence that a tool recorded me secretly.
AI meeting notetaker privacy starts with separate permissions
Otter’s June 2026 privacy policy asks users to obtain necessary permissions before providing recordings containing other people’s personal information. That is an obligation the policy places on its users. It does not establish that Otter has no duties of its own, or that a host’s permission satisfies every applicable law.
The policy describes speaker-identification information and possible automatic screenshots in virtual meetings. Its service-improvement clause includes training on de-identified audio and transcripts that may contain personal information. The transcript wording should not be collapsed into a promise that all training material is anonymous.
Scope matters here too. The policy separately addresses Business or enterprise service agreements under which Otter processes information on the customer’s instructions. Check the agreement and controls for the account hosting your meeting before applying a general-policy clause to every plan.
Notification, consent, and authority to stop capture are separate questions. A visible indicator can provide notice without resolving whether a particular participant agreed or has a stop button. A privacy policy also does not describe every in-product notification.
What the Otter meeting privacy order decided
The order dated 13 August 2026 in In re Otter.ai Privacy Litigation, case 25-cv-06911-EKL, partly granted a motion to dismiss and denied it in other respects. Some dismissed claims could be amended; withdrawn claims required a further showing before being reasserted. The order did not determine liability.
For a California interception claim, the court considered allegations that Otter retained and used conversations for its own commercial purposes. It found the allegations sufficient at that pleading stage to treat Otter as a possible third-party interceptor. That is not a general ruling that every vendor training on meeting data violates the law.
The original August 2025 Brewer complaint alleged inadequate participant consent and limitations on who could disable the notetaker. Those are historical allegations, not a verified description of every current account. This discussion explains the cited order and original complaint, rather than reporting the latest docket or identifying the currently operative pleading.
For a product review, the lesson I draw is to examine what the provider does for its own purposes as well as what it does for the meeting organizer. A promise about obtaining permission does not answer a separate question about training or retention.
Fireflies can store meetings despite its processor retention promise
Fireflies’ privacy policy says meeting content is not retained by third-party vendors after processing and is not used to train internal or external AI models. Its product guide makes the distinction explicit: external processors operate under Zero Data Retention, while Fireflies offers stored meeting records and deletion controls.
Those promises can coexist. No retained copy at an external AI processor is not the same as no saved meeting in your account.
The auto-delete guide describes an Enterprise feature controlled by the meeting owner’s or workspace’s retention settings. It says enabling that setting applies to future meetings, not the existing meeting history. Check old records separately rather than assuming a new retention setting has already removed them.
The policy also says providers may derive voice characteristics to distinguish speakers. It states that those providers do not use that Voice Data to identify or authenticate people and that Fireflies does not receive or process that derived information on its own servers. That limit concerns the defined Voice Data, not all audio recordings or transcripts.
Uploading company data to AI covers the broader review. Here the distinction to carry into it is between the service storing your meeting and a processor handling it temporarily.
Google Meet notes stay in the organizer’s account
Google Meet’s “Take notes for me” produces summary notes, which should not be described as a verbatim transcript. Google says the document is saved in the meeting organizer’s Drive. The organizer may belong to another company, and Drive is itself a cloud service; this is not a guarantee that the notes remain in your organization’s account.
The documented controls are specific:
| Question | Google Meet documentation |
|---|---|
| Is capture visible? | Participants receive notice; a pencil icon indicates note-taking. |
| Who can start or stop notes? | Organizer and internal participants; host controls restrict this to organizer, hosts, and co-hosts. |
| What about Quick Stop? | An internal user can use it when an admin enables it and host controls are off. |
| Does a Calendar attachment grant access? | No. Document sharing permissions determine access. |
These roles matter more than a blanket claim that guests can or cannot stop capture. Ask which role you have and what controls the particular meeting exposes.
Zoom and Read: meeting capture modes change the controls
Zoom My Notes: meeting controls differ from device capture
Zoom describes My Notes as personal notes that can be enhanced with a transcript. They are not automatically shared with the other participants. For supported in-meeting use, Zoom documents visible indicators and host controls; participants can request that transcription stop, and the host can approve or decline. Full management functionality has client-version requirements.
Device-audio capture is different. For third-party apps and certain out-of-meeting uses, Zoom says My Notes uses system and microphone audio and instructs the user to meet applicable notice requirements. Muting in the third-party meeting app does not necessarily stop My Notes from transcribing the local microphone. Use the My Notes pause or stop control for that.
Therefore, the absence of a separate bot in the participant list is not proof that no software is capturing audio. It also does not prove that capture is occurring.
Read: stopping capture is different from deleting it
Read’s current help says that when its web assistant joins as a visible participant, any attendee can send Read Stop to end capture while keeping a report of the earlier portion. Opt Out ends capture and deletes the session’s measured data; when Read supplies an opt-out link, use that link instead of the chat command.
The same commands do not work the same way for local capture through its desktop or mobile app. This is a concrete example of why a vendor-wide answer to “can I stop it?” can mislead: the answer depends on how the tool joined or captured the meeting.
Set the meeting privacy rules before capture starts
For my own meeting policy, I would settle these points with the organizer:
- Name the tool and capture mode. Specify whether it uses a meeting participant, native platform feature, or local audio capture. Identify who will provide notice and handle an objection.
- Separate the outputs. Ask whether audio, video, screenshots, transcripts, and summaries are retained. They are different records with different sharing implications.
- Identify the account and audience. Name the organization controlling the stored copy and check who receives links or access. “In Drive” does not identify the owner.
- Set retention and training expectations. Check the account’s agreement and actual settings. Confirm whether deleting a meeting also addresses exports, shared copies, and other retained outputs.
- Test the stop path before sensitive discussion. Decide who can stop capture and whether that also deletes material already collected. Offer a way to continue without the tool where needed.
These questions apply to the host as well as the other participants. The host may control the meeting while still depending on a provider or another attendee for access to the resulting records.
FAQ
QCan my employer see the AI transcript of a meeting I was in?
Can my employer see the AI transcript of a meeting I was in?
QDo I have to tell people an AI notetaker is running?
Do I have to tell people an AI notetaker is running?
QIs a meeting transcript used to train the AI?
Is a meeting transcript used to train the AI?
QCan I stop a notetaker that someone else turned on?
Can I stop a notetaker that someone else turned on?
QWhat is the Otter lawsuit about?
What is the Otter lawsuit about?
Sources
- Otter.ai Privacy Policy
- Fireflies.ai Privacy Policy
- Fireflies: Responsible meeting notetaking
- Fireflies: Auto-delete meetings
- Google Meet: Take notes for me
- Brewer original complaint, filed August 2025
- Court order of 13 August 2026, reproduced by FindLaw
- Zoom: Using My Notes
- Read: Stop or opt out of a recording
Vendor documentation checked in October 2026; features and agreements can change. The court discussion is limited to the dated records cited, and complaint statements are allegations. This is a documentation review, not product testing or legal advice.