AI Meeting Notes in 2026: Bots, Privacy, Alternatives

A year ago the default way to get AI notes from a meeting was to invite a bot. In 2026 that default is being questioned from several directions at once: the video platforms now build notes in, a group of tools capture audio without joining the call, and courts have started to hear cases about whether a silent note-taking participant has everyone's consent. This is a summary of what is happening, with a source for each point, and a practical guide to what to do about it. We make a transcription tool, so we have a stake in this; we have kept to what the sources say and flagged where they are vendor material.

1. Meeting platforms now ship their own notes

The platforms are no longer leaving notes to third parties.

• Google Meet: per Google's help page, "Take notes for me" requires an eligible Google Workspace edition or Google AI plan, works in English, French, German, Italian, Japanese, Korean, Portuguese and Spanish, supports one language at a time, and "informs all meeting participants that notes are being taken".
• Microsoft Teams: per Microsoft Learn (page updated October 2026), intelligent recap needs a Teams Premium or Microsoft Copilot licence, and transcription must be turned on by an admin; without recording, users get recap without the recording, speakers, topics and chapters.
• Zoom: per Zoom's support page, the meeting summary can be enabled by admins at account, group or user level, or by the host during a meeting, and is shared automatically with the host.

The trade-off is licensing and language. These features sit inside paid editions, and the language lists are shorter than the lists of dedicated transcription tools. Arabic does not appear in Google's list above. In exchange there is no third-party account and no extra bot in the participant list.

2. Bot-free capture is a product category

Several tools now sell the absence of a bot as the feature. Granola says it "uses your computer audio, so doesn't invite a bot" and works across Zoom, Meet, Teams and other apps. Tactiq says it transcribes "in real-time with no bot" through a Chrome extension. Notta advertises a bot-free recorder for Mac and Windows. Our own alternatives guide compares them. Note what bot-free does and does not change: the audience no longer sees a bot, but the recording still happens, and the consent rules for recording still apply.

3. Consent is being tested in court

The case drawing most attention is In re Otter.AI Privacy Litigation in the US District Court for the Northern District of California (Case No. 25-cv-06911). The complaints, summarised in a National Law Review commentary from November 2025, allege among other things that a bot joined meetings and captured people who were not users, and that voiceprints were stored. On 13 August 2026 the court granted Otter's motion to dismiss in part and denied it in part, allowing several claims to proceed, as Bloomberg Law reported. Two things to hold onto:

• The order addresses whether the complaint is sufficiently pleaded. It is not a finding of liability: the allegations are unproven, no court has decided that anything Otter did was unlawful, and the case continues.
• The commentary notes that responsibility for obtaining consent is contested between vendor and account holder, and that default settings may matter. Whatever the outcome, the practical lesson is the same for every tool: you, the person running the meeting, should not assume the vendor has handled consent for you.

We are not lawyers and this is not legal advice. If you record meetings with people in several jurisdictions, ask someone who is.

4. Local and self-hosted transcription

The fourth thread is processing audio on hardware you control. Desktop apps built on OpenAI's open Whisper models, such as MacWhisper and Buzz, run on your own computer, and self-hosting puts the same kind of model on a server you administer. The comparison is in our private-transcription guide. The trade is convenience for control: you give up live bots and calendar magic and keep the audio.

What to use instead of a bot, by situation

A short meeting-notes policy you can adopt

1. Say it at the start. "This meeting is being recorded and transcribed so we can share notes." Ten seconds, and it is what most consent rules ask for.
2. Let people opt out. If someone objects, stop the tool.
3. Know where it goes. Read the vendor's retention and training terms once, and write down the answer.
4. Share the notes, not the audio, unless the audio is needed.
5. Delete on a schedule. Recordings you do not need are a liability.
6. Check the notes. AI summaries can state things nobody said. Read them before circulating, and see how accurate AI transcription is.

Where this is going

We would not predict specifics, but the direction of the evidence above is clear enough: notes are moving into the platforms, bot-free capture is a selling point, consent is a live legal question, and local processing is a real option for people who need it. For ordinary recordings, a file you upload afterwards is the simplest thing that works: you can upload a file without an account to see what that looks like. For how we handle files, see the privacy page; for a recorded meeting turned into minutes, this guide.