Google Meet shows every participant a notification when recording starts, but that notice is not consent, and it does not make your recording GDPR-compliant on its own. Under GDPR you need a lawful basis, and in several EU countries the consent of everyone on the call. Meet's banner tells people what is happening. Getting a defensible legal basis is still your job as the organiser.
What Google Meet actually shows participants
Google documents the behaviour plainly. When a call is recorded, "Participants get a notification when the recording starts or stops." The same Help page adds that people outside your organisation, on the mobile app, or dialling in by phone "get notified when a recording starts or stops, but they can't control the recording." (Google Meet Help, retrieved 2026-07-26.)
Google's AI note-taker works the same way. When "Take notes for me" runs, "Google Meet informs all meeting participants that notes are being taken and the pencil icon appears on all participants' screens." That is a visible notice, not a request for permission. (Google Meet Help, retrieved 2026-07-26.)
A notification is not consent
GDPR separates two obligations that Meet's banner quietly blurs. Transparency under Article 13 means telling people their data is being processed. A lawful basis under Article 6 is the separate ground that makes the processing legal in the first place. Meet's notification helps with the first. It does nothing for the second. Where you rely on consent, that consent has to be freely given, specific, informed, and as easy to withdraw as to give, and a one-way banner cannot deliver any of that.
Google Meet's recording notification is a transparency notice under GDPR Article 13, not consent under Article 6. It informs participants that recording is happening; it does not establish a lawful basis, capture affirmative agreement, or give anyone a way to refuse and stay in the call. Those remain the organiser's responsibility.
Where Germany and other EU states go further
Several EU jurisdictions demand more than a notice. Germany is the sharp example: recording a confidential spoken conversation without the agreement of those speaking can engage section 201 of the Criminal Code (§201 StGB), and where a tool monitors employees a works council (Betriebsrat) usually has a say in how it is introduced. We walk through that in detail in AI notetaker consent, §201 StGB, and the Betriebsrat. A Meet banner does not resolve any of it.
The default-on note-taking change to watch
The consent problem is about to get louder. Google is moving AI note-taking toward opt-out: from 21 September 2026 automatic note-taking becomes on by default for Business Standard and Business Plus meetings with three or more guests, subject to admin control. (Google Workspace Admin Help, retrieved 2026-07-26.) A default-on note-taker means people can be captured before anyone has thought about a lawful basis, which is exactly the failure mode GDPR reviewers look for.
The output has to live somewhere, too. Google states that meeting notes and recordings are saved in "the meeting organizer's Google Drive in the 'Google Meet' folder." (Google Meet Help, retrieved 2026-07-26.) Wherever that Drive is provisioned, the recording, the transcript, and the notes are now personal data you control and must be able to account for.
What a compliant setup looks like on Meet
- Decide your lawful basis before the call, not during it.
- Tell participants the call will be recorded and why, ahead of time, and honour requests to opt out where consent is your basis.
- Use an assistant that joins as a visible participant so the recording is never covert.
- Sign an Article 28 data processing agreement (an AVV) with any processor that handles the audio, transcript, or notes.
- Set a retention limit and delete on schedule.
How Numi handles consent on Google Meet
Numi's meeting bot joins Google Meet calls as a named, visible participant, so attendees can see it and be told before recording begins, which removes the covert-recording problem that silent browser-extension notetakers create. From there the audio streams to an EU-only pipeline, is transcribed on self-hosted models in Frankfurt, and is stored and analysed in the EU under an Article 28 AVV, and your meetings are never used to train AI models. That does not replace your own consent process, but it makes the process straightforward instead of adversarial. If you want the compliance picture end to end, see a GDPR-safe AI notetaker for Google Meet and GDPR-compliant call and meeting recording in Europe.