CyphrQ
Menu

AI Meeting Notetaker Privacy: Consent, Recordings and Transcripts

Who is told when Zoom, Teams, Google Meet or a bot takes notes, where transcripts are stored and for how long, and what hosts and attendees can do.

By CyphrQ.ai

Written with AI assistance and human editorial review. Every figure linked to its source.

12 min read

Is it safe to let an AI take notes in your meetings? It can be. AI meeting notetaker privacy comes down to two things: everyone in the call knows the notetaker is there, and you know where the notes go. An AI notetaker turns speech into a transcript and a summary. Those files sit in someone's cloud storage, can reach people who were never in the call, and stay until a retention rule removes them.

Every setting below was read on the vendor's help or admin pages on 25 October 2026.

Key takeaways

  • AI notetakers come in two designs: assistants built into the meeting platform, and outside bots that join the call like a guest.
  • Teams and Google Meet keep built-in notes under your organisation's account. An outside bot hands the meeting to another company.
  • Google Meet tells every participant when "Take notes for me" is running. Microsoft warns that outside bots can record or transcribe without people noticing.
  • In Teams, recordings and transcripts expire after 120 days by default, and an admin can change that number.
  • Microsoft and Google say their meeting AI doesn't train generative models on your content, and Zoom said the same in February 2024. Third-party bots set their own terms.
  • The host carries most of the responsibility: announce it, offer a way out, and decide who receives the notes.

Is AI meeting notetaker privacy different for built-in tools and bots?

Yes. There are two designs, and the privacy picture is different for each.

Built into the meeting platform. Zoom AI Companion, Copilot in Microsoft Teams and "Take notes for me" in Google Meet run inside the service you are already using. For Teams and Meet, the transcript and summary stay with Microsoft or Google, under your organisation's account and admin settings.

A bot that joins the call. Third-party notetakers connect to the meeting as a participant and capture it from the inside. Microsoft calls these "external meeting assistant tools (such as transcription or note-taking bots)". With its bot detection switched off, they "appear as any other external participant" (Microsoft Learn). Whatever the bot captures then sits with the bot's provider, under that company's terms rather than your platform's.

Both designs make mistakes. Google says its meeting summary "can be incomplete, inaccurate, or not generated", and that the feature handles one spoken language per meeting (Google Meet Help). Microsoft says generated responses "aren't guaranteed to be 100% factual" (Microsoft Learn). An AI summary is a first draft of the minutes. Check names, numbers and decisions before you forward it.

Who gets told when an AI is taking notes?

That depends on the tool and on your admin's settings.

  • Google Meet: Meet "informs all meeting participants that notes are being taken", and a pencil icon appears on everyone's screen. An administrator can also require every participant to give explicit consent before features like "Take notes for me" run. That setting is off by default (Google Meet Help).
  • Microsoft Teams and outside bots: Microsoft says these bots "may record or transcribe meetings without participant awareness". With bot detection on, which is the default, Teams holds detected bots in the lobby and reminds the organiser of the risk before they admit one (Microsoft Learn).
  • Zoom AI Companion: Zoom's own help pages couldn't be checked for this guide. Ask your Zoom admin which AI Companion features are on and what participants see.

Being notified isn't the same as agreeing. And someone who joins ten minutes late may never hear the announcement.

This isn't legal advice. Recording and privacy laws differ by country. A transcript is a written record of who said what, with names attached, so it is personal information about everyone who spoke.

For the legal side of AI tools at work, see Is It Safe to Use ChatGPT at Work? (including why GDPR comes up) and, for UAE businesses, UAE Data Protection Law (PDPL) and AI Tools.

Whatever your local rules say, three questions are worth taking to your privacy or legal lead before AI notes become routine:

  1. What is our reason for transcribing this kind of meeting, and is a summary enough without a full transcript?
  2. How do we tell people, including guests from outside the company, before the notes start?
  3. How long do we keep transcripts, and who can delete them on request?

Where do the transcript and the summary end up?

Tool Where the files go Who can get them How long they stay
Google Meet "Take notes for me" The organiser's Google Drive, in a "Google Meet" folder, shortly after the meeting ends People on the calendar invite, if the organiser shares it; there is an option to include guests outside the organisation Your organisation's Meet retention policy
Teams recordings and transcripts The organiser's OneDrive for regular meetings; the channel's SharePoint site for channel meetings People the files are shared with 120 days by default, then the recycle bin
Copilot in Teams meetings Stored with your organisation's other Microsoft 365 content, as the user's Copilot activity history The user; admins through Content search or Microsoft Purview Purview retention policies; users can delete their own history
Zoom AI Companion meeting summary Not checked on Zoom's own pages Not checked Not checked
Third-party bot The bot provider's own systems Set by the provider's terms and the account owner Set by the provider

Sources: Google Meet Help, Microsoft Learn: recording expiration, Microsoft Learn: Copilot privacy. Zoom's pages didn't load for checking, so ask your Zoom admin for its storage and retention settings.

When Meet notes are shared, Google says external guests can see that the calendar event has the notes document attached (Google Meet Help). Check the sharing choice before any call with clients or suppliers.

Is your meeting used to train the AI?

Read the vendor's own words, and note the date you read them.

  • Microsoft: "Prompts, responses, and data accessed through Microsoft Graph aren't used to train foundation LLMs." The stored record of Copilot interactions, which covers meetings in Teams, is encrypted and also excluded from training (Microsoft Learn).
  • Zoom: as of its February 2024 update, Zoom said it "does not use any customer audio, video, chat, screen sharing, attachments, or other communications-like customer content" to train its own or third-party AI models (Zoom blog). No newer statement was found on Zoom's own pages, so ask Zoom to confirm it in your contract.
  • Google: for users with Google AI plans, Google says Gemini in Gmail, Calendar, Chat, Docs, Drive, Slides, Sheets, Meet, Vids and Pics "doesn't use your content to train or improve Gemini or other generative AI models". Users enrolled in the Google Workspace Experiments program are covered by separate terms instead (Google Meet Help).
  • Third-party bots: the answer is in each provider's terms and privacy policy. Find it before anyone connects the bot to a work calendar.

Training is only one question. Day to day, the bigger risks are simpler ones: who can open the transcript, and how long it lives.

What should a host do before switching on AI notes?

  1. Say it at the start. "This call has AI notes. Tell me now if you'd rather it didn't." Then pause.
  2. Put it in the invite, so guests from outside know before they join.
  3. Choose who gets the notes before the call, especially when outside guests are invited.
  4. Leave it off for sensitive topics: HR cases, legal advice, health, deals that aren't public.
  5. Admit bots on purpose. If a notetaker you don't recognise is waiting in the lobby, ask whose it is before letting it in.
  6. Review the summary before sending it. Fix errors, and cut anything said off the record.
  7. Delete what you no longer need, rather than waiting for an expiry date.

What can you do as an attendee?

  • Ask whether notes are being taken and who will receive them.
  • Speak up if you're uncomfortable, or ask the host to pause the notes for one part of the discussion.
  • Keep sensitive details for another channel when you know a transcript is running.
  • Question unknown participants. If a participant's name looks like a bot, ask the host. If a person on the call seems off, voice or face, the checks in Deepfake Scams: How to Spot Them apply.
  • Ask for a correction if the summary gets what you said wrong.
  • Don't bring your own bot into someone else's meeting without asking first.

A personal note-taking app connected to a work calendar is one form of shadow AI at work. If you'd rather the processing never left your own laptop, that's a different design, covered in On-Device AI Privacy.

Going deeper: for security and IT teams

Threat model. Four things go wrong with meeting AI. First, an external bot sends meeting content to a processor outside your compliance boundary, meaning the systems where your own retention, eDiscovery, audit and access policies apply. Microsoft lists this risk: bots may "store meeting data in third-party systems outside of the organization's compliance boundaries" (Microsoft Learn).

Second, a presenter admits a bot the organiser never approved. Third, notes are shared with external guests by default. Fourth, retention drifts: transcripts either outlive their purpose or expire before a legal hold catches them. A legal hold is an instruction to preserve records for litigation or an investigation, and it overrides normal deletion.

In practice, regulators already fine organisations over recorded conversations, even without AI. France's CNIL lists a €10,000 fine with an injunction on 16 January 2025 against a remote apprentice-training centre, citing data minimisation and how people were informed, including about telephone recordings. On 17 October 2024 it fined a company handling phone calls for clients €20,000, citing how people were informed, including about telephone recordings, the right to object and data security (CNIL sanctions list). Those cases concern phone calls, not AI notes, but a meeting transcript raises the same questions: were people told, and was keeping it necessary.

Teams: external bot policy. In the Teams admin center, the meeting policy setting "Manage external bots and their access to meetings" sits in the Meeting Join and Lobby section. In PowerShell the attribute is ExternalBotAccessMode: - AllowBots ("Do not detect bots"): bots look like any other external participant. - RequireApprovalWhenDetected (default): detected bots are marked and held in the lobby until someone explicitly admits them, whatever the meeting's lobby configuration says.

Microsoft's tip is to let only organisers and co-organisers admit people from the lobby, so a presenter can't wave a bot through. Its known limitations: some bots aren't detected, and humans are sometimes flagged as bots, which the organiser fixes with "This is not a bot". One thing to test in a lab tenant: the page's text names Set-CsTeamsMeetingPolicy, but its sample commands use Set-CsTeamsEventsPolicy (Microsoft Learn).

Teams: recording and transcript retention. Under Meetings > Meeting policies > Recording & transcription, the setting "Recordings and transcriptions automatically expire" controls deletion. The PowerShell parameter is -NewMeetingRecordingExpirationDays on Set-CsTeamsMeetingPolicy. Changes apply only to new recordings and transcripts (Microsoft Learn).

In practice, the documented numbers to build retention around:

Item Figure Microsoft documents
Default expiry, recordings and transcripts 120 days
Configurable range 1 to 99,999 days; -1 (PowerShell only) means never expire
Maximum default expiry for A1 users 30 days
Published recordings for Teams events 30 days, extendable to 90
Recycle bin after expiry, work or school accounts Deleted automatically after 93 days unless an admin changed it

Source for every figure in the table: Microsoft Learn: recording expiration. Once an expired recording is purged from the recycle bin, Microsoft says it can't be recovered.

Copilot interactions and eDiscovery. Microsoft stores the user's prompt and Copilot's response as Copilot activity history, including for meetings in Teams. Admins can search it with Content search or Microsoft Purview, set Purview retention policies for it, and use the Teams Export APIs for Teams chats with Copilot.

Copilot respects the usage rights in Purview Information Protection encryption, applied through sensitivity labels, and only surfaces content the user can at least view. That makes over-broad sharing of recordings and transcripts a Copilot exposure as well. For EU tenants: as of 25 October 2026, Microsoft's page says Anthropic models offered as a subprocessor "are currently excluded from the EU Data Boundary" (Microsoft Learn). Re-check that line before you rely on it.

Google Workspace. The explicit-consent requirement for "Take notes for me" is off by default, so switching it on is a deliberate admin decision. Notes follow your Meet retention policy (Google Meet Help).

Vendor statements change. In practice: Zoom published its post on how its terms of service apply to AI features on 7 August 2023, and the editor's note shows an update on 7 February 2024 (Zoom blog). Store the exact wording and the date you read it in your vendor file, and re-check it at each renewal.

Detection and testing. - Invite a known third-party notetaker to a test meeting. Confirm it lands in the lobby, flagged as a bot, and that a presenter can't admit it. - Microsoft's own best-practice list includes monitoring audit logs for unusual participant activity. Review external participants joining meetings held by sensitive groups. - Sample a few recordings each quarter and confirm the expiry date matches the policy assigned to the organiser.

What to ask a third-party notetaker vendor. - Where are recordings and transcripts hosted, and which subprocessors touch them? - What's the default retention, and can we enforce deletion centrally? - Is customer content used for training, and where is that stated contractually? - Can the bot join meetings the connected user doesn't organise? - Can we see an admin audit log of which meetings the bot joined?

A checklist for your next meeting with AI notes

  • [ ] Everyone was told at the start, and guests saw it in the invite.
  • [ ] The notes go only to the people who need them.
  • [ ] No bot in the call that the host didn't approve.
  • [ ] Sensitive items were discussed with notes off.
  • [ ] Someone checked the summary before it was sent.
  • [ ] You know where the transcript is stored and when it will be deleted.
  • [ ] For any third-party bot: you've read its training and retention terms.

Sources