Your client joins the call. So does their AI notetaker. You never consented to being recorded, but the transcript is already being written.
That is the quiet reality of AI notetakers in 2025. Tools like Otter.ai, Fireflies, and Notion AI Meeting Notes have made it trivially easy for one person in a meeting to capture everything said by everyone else. The person who invited the bot gets the summary. Everyone else gets nothing, not even a heads-up in most cases.
This is not a hypothetical risk. It is a structural one baked into how these tools work.
The Consent Gap Nobody Talks About
Most AI notetakers join a call as a named participant, sometimes with a label like 'Notetaker' or 'AI Assistant', sometimes with a name indistinguishable from a real attendee. The host knows it is there. The other participants may not notice, or may not understand what it means if they do.
Once it is in the room, it records. It transcribes. It summarises. And that data sits on a third-party server, tied to the account of whoever invited it.
If you are a lawyer discussing a client matter, a founder sharing unannounced product plans, or a recruiter running a confidential interview, you have just handed sensitive information to a platform you have no relationship with and agreed to no terms with.
US News reported in July 2026 that professionals across industries are starting to question this practice, but 'starting to question' is doing a lot of heavy lifting. The tools are already widely deployed. The questioning is lagging badly behind the adoption.
The Risk Mechanism Is Simple
Here is how the exposure actually works, step by step.
First, the meeting host enables an AI notetaker on their account. This takes about 30 seconds in most tools.
Second, the bot joins the call automatically for every meeting on that person's calendar, often without them actively thinking about it each time.
Third, everything said in the meeting, by every participant, is processed by the notetaker's platform. That processing happens on external servers under the vendor's data policy, not yours.
Fourth, the transcript and summary are stored, potentially indefinitely, in the host's account. If that account is ever breached, or if the vendor's data practices change, your words go with it.
You had no input into any of those four steps. You were just in the meeting.
Why SMBs Are Especially Exposed
Enterprise teams have legal and IT departments that can push back, negotiate data processing agreements, or ban certain tools outright. Most small and mid-sized businesses do not.
If you run a small firm and your clients or partners are using AI notetakers, your conversations are being captured by tools your own IT policy has never evaluated. You are inheriting their risk profile without knowing it.
The asymmetry is real. A solo operator or small team almost certainly lacks the bandwidth to audit every tool a meeting guest might bring into a call. But that does not mean the exposure disappears. It just means it accumulates quietly.
What You Should Actually Do
None of this means AI notetakers are categorically bad. Used transparently, with consent, they are genuinely useful. The problem is the default behaviour, not the technology.
Three things worth doing now:
State your policy at the start of sensitive calls. A simple 'we ask that no recording tools be active for this conversation' is a legitimate professional request. Most people will respect it.
Check your own calendar integrations. If you have connected an AI notetaker to your calendar, audit which meetings it is joining automatically. You may be the one creating this problem for your own guests.
Read the data retention terms before you enable any tool. Most people skip this. The question to answer is: where does the transcript go, who owns it, and how long does it live?
The tool that saves you ten minutes on meeting notes could cost you a client relationship or a confidentiality obligation. That trade-off is worth a few minutes of scrutiny before you hit enable.
Know what is in your meetings before you decide what belongs there.