Nobody in your business decided to start recording meetings. Someone connected an AI note taker to their calendar because it saved them writing notes, it worked, and a colleague asked what they were using. Two months later an AI note taker joins most calls, transcripts land in inboxes, and no one has asked the question that matters: where does the recording go, and who can reach it afterwards?

The time saving is real, which is why these tools spread without a decision being made. But every word of a meeting gets captured, including the parts nobody would put in writing, and it is stored somewhere under terms that somebody accepted on your behalf.

The AI note taker question nobody asked before it joined

An AI note taker joins a Teams, Zoom, or Google Meet call, records the audio and sometimes video, converts speech to a transcript, and produces a summary with action items. Microsoft 365 Copilot, Otter, Fireflies, and Fathom are the ones you will meet most often.

Two behaviors matter more than the feature list. Most connect to a calendar, and many will auto-join anything scheduled unless that setting is turned off, including meetings the person who installed it is not attending. And the recording does not end when the call does. It is stored in the cloud, searchable, shareable, and exportable, for as long as the account exists.

Which account, and whose cloud, is the whole question.

Where the recording actually goes

Three groups can reach an AI note taker recording, and only the first is obvious.

• Everyone on the distribution list. Many an AI note taker will email the transcript to every attendee by default, and some send it to people who were invited but never joined. If the meeting covered a salary, a client dispute, or a supplier problem, that default has just widened the audience considerably.
• The vendor. With a cloud-based AI note taker, the recording sits on the vendor’s servers. Their systems, and in some cases their staff, can reach it under the terms someone accepted at signup. A law firm review of the legal risks of AI note takers goes further, warning that letting a vendor access or use transcripts for its own purposes can risk waiving attorney-client privilege for businesses handling legal matters.
• Whoever owns the account the bot came from. If the AI note taker auto-joined from an employee’s personal calendar connection, the recording may live in an account your business does not control and cannot audit. When that person leaves, the recordings do not necessarily leave with them, or they might, which is the other half of the problem.

Whether your AI note taker trains on your meetings

This is where tools diverge most sharply, and where two products that look identical behave completely differently.

Microsoft states that Copilot in Teams does not use your prompts, responses, or meeting content to train its foundation models, and that the content is processed inside your organization’s Microsoft 365 service boundary rather than on the public model. That position is set out in Microsoft’s Copilot privacy documentation.

Third-party tools vary. Some store recordings on their own infrastructure and, depending on the terms accepted, may use that material to improve their models. Others state plainly that they do not train on customer data. There is no way to tell from the interface, the pricing page, or the marketing. The only reliable method is reading the specific tool’s terms, and checking again after any major product update.

The practical shortcut: an AI note taker that keeps recordings inside your own Microsoft or Google tenant is far easier to govern than one holding everything on infrastructure you have no relationship with.

Four questions that separate one AI note taker from another

Vendor terms change, so a list of which tool does what would be out of date within months. These four questions do not go stale, and they can be answered from any tool’s documentation in about ten minutes.

• Where is the recording stored? Inside your own Microsoft or Google tenant, or on the vendor’s infrastructure? This single answer determines how much control you have over everything that follows.
• Is our content used for training? Look for an explicit statement, not an absence. “We take privacy seriously” is not the same as “we do not train on customer data.”
• Who can access it on the vendor’s side? Support staff, engineers, subprocessors. Reputable vendors document this; if you cannot find it, treat that as the answer.
• What happens when we cancel? Can you export everything, and is it actually deleted afterwards, on what timescale? An AI note taker holding two years of your meetings is a hard thing to walk away from if there is no clean exit.

If a tool cannot answer all four from published documentation, that is useful information in itself. It does not necessarily disqualify it, but it should keep that AI note taker out of any meeting on the no-record list below.

The consent problem, and where Texas actually sits

Recording a conversation is not always your decision alone, and the rule depends on where every participant is sitting.

Texas is a one-party consent state. Legally, if you are on the call, you can record it without asking the others. That sounds like the end of the problem for a business in League City or Webster, and it is not, for two reasons.

The first is that around a dozen states require every participant to consent, and California is one of them. A League City engineering firm on a call with a client in San Diego is exposed to the stricter rule, not the friendlier one. The same applies to any call with participants in Florida, Illinois, Washington, or the other all-party states, and the state-by-state survey of recording law is worth a look before you assume Texas rules apply to your whole client list. If your business serves clients outside Texas, the safe default is to behave as though every call is all-party.

The second is that legality is not the same as trust. A client who discovers after the fact that an AI note taker was quietly transcribing your conversation will not be reassured to learn it was lawful. For professional services firms around the Bay Area, such as accountants, law practices, and engineering consultancies, the relationship cost of that discovery is far larger than the compliance question.

Announcing the recording, explaining why, and letting people object costs about eight seconds and removes both problems at once.

The meetings that should never have a bot in them

Some conversations should stay off any AI note taker regardless of consent, because the existence of a transcript is itself the risk. Once a recording exists it can be subpoenaed, leaked, exported by a departing employee, or simply read by someone it was never meant for.

• HR matters. Performance conversations, complaints, investigations, terminations. A transcript of a disciplinary meeting is a discoverable document.
• Legal discussions. Anything touching privilege, per the concern above.
• Financial and strategic decisions. Pricing, acquisitions, redundancies, anything commercially sensitive that becomes damaging out of context.
• Client conversations under confidentiality. If your engagement letter promises confidentiality, an AI note taker on the vendor’s servers may quietly breach it.
• Anything involving a third party’s personal data. Patient details, client financials, employee records.

The practical rule most businesses land on is simple: recording is the default for internal working meetings, and off by default for anything in that list, restored only by deliberate agreement.

A one-page AI note taker policy you can put in place this week

This does not need a project. Six decisions, written down and communicated once, cover most of the exposure.

• Name one approved AI note taker. Pick it, say so, and ask staff not to connect anything else to company meetings. One tool means one place to audit, one set of terms to read, one export to run if you ever need to.
• Turn off auto-join. An AI note taker should record because someone chose it at the start of a call, not because it was the default on every calendar entry.
• Announce and offer the opt-out. Make it normal to state that the meeting is being recorded and to skip recording if anyone objects.
• Fix the sharing default. Check where summaries go automatically. Change it so transcripts do not reach people who were invited but never attended.
• Write the no-record list. HR, legal, financial, confidential client work. Put it in writing so nobody has to make the judgment call under pressure.
• Set a retention period. Decide how long AI note taker recordings are kept and delete them on schedule. Indefinite retention is a decision by default, and usually the wrong one.

If you run Microsoft 365, most of this is enforceable centrally rather than left to individual habit, since an administrator can control whether Copilot and transcription are permitted in Teams meetings. That is the difference between a policy people remember and a setting that holds regardless. Getting those controls configured properly is part of running Microsoft Teams as managed infrastructure rather than as an app everyone happens to have, and the same admin console is where the compliance side of retention and consent gets handled.

Two related problems usually surface at the same time as this one. The first is that staff adopt AI tools before anyone approves them, which is worth auditing properly, and we covered how in our guide to running a shadow AI audit. The second is that turning on Copilot exposes whatever the user already has permission to reach, which is usually far more than anyone expects, and that needs handling before a Copilot rollout rather than after.

Frequently Asked Questions

Can I record a meeting in Texas without telling the other person? Legally yes. Texas is a one-party consent state, so your participation is enough. That stops being true the moment someone on the call is in an all-party state such as California, and it says nothing about whether a client will be comfortable when they find out.

Does Microsoft Copilot use my meeting data to train its AI? Microsoft states it does not. Meeting content, prompts, and responses stay inside your Microsoft 365 environment and are not used to train the foundation models.

Can an AI note taker join a meeting I didn’t invite it to? Yes, and this surprises people. Many tools connect to a user’s calendar and auto-join everything on it, sometimes including meetings that user is not attending. Turning auto-join off is the single highest-value setting change available.

An employee left. Do they still have our meeting recordings? If they connected the tool under a personal account, quite possibly. This is the strongest argument for one approved, company-controlled tool rather than whatever each person found useful.

How long should we keep transcripts? Long enough to be useful, which for most working meetings is weeks rather than years. Set a retention period and enforce it, because a recording you no longer need is pure liability.

An AI note taker is genuinely useful and worth keeping. The exposure comes almost entirely from an AI note taker arriving without a decision behind it, and the fix is a handful of settings plus one page of written policy. If you are not sure which tools are already connected to your meetings, or where those recordings are sitting right now, an IT health check is a straightforward place to find out.

Featured Image Credit: Pexels