Inherited capture: on someone else's call, the note-taker runs on their defaults

Overview

On 16 July 2026 Google published how Meet’s “Take notes for me” will be set when admin defaults take effect for end users — “no sooner than September 21, 2026”. The split runs the opposite way to intuition. Business Standard and Business Plus default on. Enterprise Standard, Enterprise Plus, Frontline Plus and AI Pro for Education default off. The tiers with a compliance function are the quiet ones; the tiers without are the ones taking notes. Nothing bites before that date — Google is explicit that “there will be no impact to the end user experience on any plan before September 21, 2026” — which makes this the rare case of a capture default you can go and ask about before it starts applying to you.

The reflex this prompts is to go and check your own settings. Do — it takes two minutes. But it covers the smallest part of your exposure.

The content

The obvious read is that meeting AI is a setting you manage. Find the toggle, decide your posture, done.

The overturn is that a meeting has only one capture posture, and it isn’t yours. It belongs to whoever convened the call, and from your seat it is usually invisible and rarely yours to change. Call it inherited capture: on any call you didn’t host, you are running on someone else’s defaults, chosen by an admin you’ve never met, under a plan tier you can’t see.

The vendor documentation is unusually blunt about this. Zoom’s support page lists among its limitations that “Only the meeting host and co-host can start or stop the Meeting summary through the in-meeting controls”; the participant signal it describes is a diamond icon changing colour. Microsoft’s Teams admin guide notes that the transcription setting “is on by default for new policies”, with speaker attribution and voice and face enrolment likewise enabled org-wide by default — while meeting recording is off by default, so “not recorded” and “not transcribed” are two different questions. Otter’s notetaker joins from your calendar, and one of its auto-join options covers every calendar event carrying a Zoom, Meet or Teams link. Google has built a real explicit-consent gate — but it’s set by admins at domain, OU or group level, it’s off by default, there is no end-user setting for it, and as of the vendor’s 17 June 2026 update the rollout is paused “while we make improvements to the feature”.

And the documentation lags the product, which is the trap underneath all of this. Since 26 January 2026, by every institutional account, Zoom participants have met an AI Companion policy disclaimer when a host switches the feature on: agree to stay, or leave the meeting — and if you do nothing, your microphone and camera are disabled until you do. That is a working consent gate, shipped, while Google’s sits paused — and the Zoom support page above still doesn’t mention it, which is why the accounts of it are universities’ rather than the vendor’s. So the vendor you’d have called the weakest on consent last year is currently the strictest. Don’t carry a league table around in your head; it will be out of date, and you can’t check it from inside the call.

What each vendor offers a participant differs, then, and it moves. What doesn’t move is the shape underneath: the decision sits above the meeting, and the person with the most at stake in the conversation has the least say over it.

This is also where the legal weather is turning. Courts are working through whether an AI note-taker is a party to the call or an unauthorised third party listening in — Recording Law’s April 2026 survey points to the “capability test” from Ambriz v. Google, which held that alleging the vendor had the capability to use intercepted data for its own purposes was enough to establish third-party status at the pleading stage. It counts four Otter.ai suits filed across August–September 2025 and since consolidated. Thirteen US states require every party to consent on that page’s own count — its table lists fourteen — and Illinois’ biometric statute runs $1,000–$5,000 per violation where a recorder builds voiceprints to identify speakers without written consent. Australian and UK rules differ again. The vendors are the named defendants; the awkward conversation lands on whoever convened the call.

One precision worth holding, because the scare version of this story is wrong: capture is not uniformly on. It is plan-specific and admin-specific, and the regulated tiers frequently default off. The claim is narrower and more useful — the default was set for you, above you, it differs by plan, and you cannot read it from inside the call.

Try it

Two minutes on your own tenant, then one line you keep.

1. YOUR DEFAULT — open your meeting tool's settings and find the
   AI notes / transcription / summary entry. Write down which of
   these you actually are:
     ON and I can change it  ·  ON and greyed out  ·  OFF  ·  can't find it
   "Can't find it" is a real answer, and it's the ask to your admin:
   "what's our meeting-AI default, and does it gate on consent for
   external guests?"

2. THEIR DEFAULT — for calls you don't host, write the opener you
   will actually say, before the sensitive part:
     "Before we get into it — is anything recording or taking
      notes on this call?"

3. THE SEQUENCE — for a genuinely confidential conversation,
   turn capture off BEFORE people join, not after.

Where it breaks, deliberately: step 1 tells you nothing about step 2. Auditing your own workspace can leave you more confident on exactly the calls where you have no control — the external ones. And expect the answer to step 2 to be “I don’t think so?”, because the host often doesn’t know their own default either; that uncertainty is the finding, not a failure of the question. Two harder limits. Where all you get is an icon changing colour, that’s a disclosure, not consent — noticing is not the same as being able to decline. And where there is a real gate, as on Zoom now, the offer is agree or leave the meeting, which at a call you’re expected at is a thin sort of choice. Either way, stopping capture partway through doesn’t unmake the transcript of the part you already said.

Additional reading

• New Google Meet “Take notes for me” settings for admins and end users — Google Workspace Updates (16 July 2026) — the plan split (Business Standard/Plus on; Enterprise Standard/Plus, Frontline Plus, AI Pro for Education off), the effective date for admin defaults reaching end users (Google’s wording is “no sooner than” 21 September 2026, on a gradual rollout), and the new admin option to enable automatic note-taking only for meetings with three or more people.
• Require explicit consent for “Take notes with Gemini”, recordings and transcripts in Google Meet — Google Workspace Updates (posted May 2026; last updated 17 June 2026) — the consent gate: admin-set at domain/OU/group level, off by default, no end-user setting. Read the banner at the top before relying on it — the rollout has been paused since that June update.
• Admin guide to Copilot in Teams — Microsoft Learn (page metadata updated 29 April 2026; the date displayed to readers is 12 December 2025) — transcription “on by default for new policies”; voice and face enrolment enabled for all users by default; speaker attribution on at org level; meeting recording off by default. The page is scoped to Teams Rooms, but the transcription-policy setting it describes is org-wide.
• Using Meeting Summary with AI Companion — Zoom Support — the host-only control, verbatim, and the colour-changing diamond. Worth reading alongside the next entry as a live example of vendor documentation trailing the product.
• Zoom AI Companion: policy disclaimer — Stanford University IT — the participant-facing gate in force since 26 January 2026: agree to stay or leave the meeting, with microphone and camera disabled if you don’t respond, and the desktop prompt disappearing after 90 seconds. An institutional IT page rather than a Zoom-authored one; the same wording appears across several universities, but treat it as corroborated rather than vendor-confirmed.
• Automatically add Otter Notetaker to your meetings — Otter.ai Help Center — the auto-join options, including the one that joins every calendar event carrying a Zoom, Meet or Teams URL. (The page blocks direct fetching; the settings above are quoted via its search-indexed text.)
• AI meeting recording laws — Recording Law (3 April 2026) — the Ambriz v. Google capability test, the four Otter.ai suits filed August–September 2025 and consolidated as In re Otter.AI Privacy Litigation, all-party-consent states and the Illinois biometric exposure. Treat the state tally as indicative: the page says thirteen and its table lists fourteen, which is a fair signal of how unsettled the area is.

Editor’s note

I have always treated every meeting as having the potential to carry a perfect record, whether or not I know about it. Jurisdiction matters too — where you are and where the other participants sit will change what is permitted — though I would not lean on that as a control. The difference now is that the record can be automated by someone who is not in the meeting at all. It no longer takes a decision by anyone in the room.