The Tuesday client call starts. Four people from your company, two from the client, and a seventh participant called something like “Notetaker” or “Assistant,” which nobody remembers inviting. It records everyone. Forty minutes later a transcript, a summary, and a list of action items land in one person’s inbox. Sometimes that inbox is a personal Gmail account.
Nobody else on the call agreed to any of this. Most of them did not notice. And if the client’s lawyer asked next month for the transcript of that call, nobody at your company could say whether one exists, where it is, or who can read it.
Most owners have not decided anything about this yet. This guide is about the decision, not the technology.
What a note-taker actually does
An AI note-taker is a service that joins a video meeting as if it were a person, records the audio, turns it into a transcript, and writes a summary. The recording and the transcript are stored on the vendor’s servers, under the account of whoever set it up. Teams, Zoom, and Google Meet all have built-in versions, and dozens of companies sell outside ones, many with a free tier.
The outside ones get into your meetings through a calendar. When an employee signs up, the service asks for permission to read their calendar, and from then on it sees every meeting with a video link and joins on its own. That permission request is a consent screen, the same kind of screen that approves any app’s access to a Microsoft 365 or Google account, and an employee can approve it in two clicks without anyone else at the company knowing.
So there are two ways a bot ends up on your call. Someone on your side signed up for one, or someone on the other side did and their bot joined a meeting you host. The second case means the recording of your call lives with a vendor your company has no relationship with, under an account you cannot reach.
Five questions follow from that, and most companies cannot answer any of them today:
- Who owns the transcript? The vendor’s terms usually say the account holder does. If that is an employee’s personal account, it is not the company.
- Where is it stored, and for how long? On the vendor’s servers, in a country you did not choose, for as long as the account exists.
- Does the vendor learn from it? Some business tiers say no. Free tiers often say something else, in a document nobody read.
- What was on the recording? A client’s finances. A patient’s history. A negotiating position. Whatever anyone said, assuming the room was private.
- Who invited it? Usually nobody can say. That is the answer that should stop an owner.
What went wrong this year
Two incidents from the summer of 2026 made this concrete, and neither involved a hacker breaking anything.
The database that was open. In August 2026, Dark Reading reported that a security researcher had found a misconfigured database behind tl;dv, a widely used note-taker. The database was missing the rule that keeps one customer’s records separate from another’s, so any signed-in user could read everyone’s. The researcher counted about 182,000 meeting records belonging to roughly 84,000 users across 35,000 organizations, including government bodies in more than twenty countries. The exposed records were the map of who was meeting whom, when, and on which link; around a thousand meetings were live at any given moment, and the researcher was able to join some of them uninvited. The company says recordings and transcripts themselves were not reachable, and the researcher’s account centers on the meeting data rather than the audio. Take the company at its word and the lesson is unchanged: the schedule of every call your company has, with the links to join them, was readable by strangers for months, because of a vendor your employee picked.
The court that called it eavesdropping. On August 13, 2026, a federal judge in California ruled on a motion to dismiss a class action against Otter.ai, one of the best-known note-takers. The court let the federal Wiretap Act claim and the California privacy claim proceed, on the reasoning that a note-taker which joins a call and keeps the recordings for its own purposes, including improving its own product, is plausibly an outside eavesdropper rather than an extension of the person who invited it. That is a ruling on what the plaintiffs alleged, not a finding that anyone broke the law, and the case continues. A similar suit against Fireflies.ai was dropped by the plaintiff in March 2026. The point for an owner is narrower than the headline: a court has now said the obvious thing out loud. The bot is not your colleague taking notes. It is a company, on the call, with its own interests.
The decision, which costs nothing
The question is not whether note-takers are good. They are useful, which is why your staff are already using them. The question is which one, under whose account, and with whose knowledge. Three positions are defensible. Pick one and write it down.
Use the built-in one. If your company lives in Microsoft 365, Teams can already record and transcribe a meeting. The files are saved to the organizer’s OneDrive, inside your own tenant, where the retention rules you set apply, the backup you have or do not have covers them, and they stay with the company when the employee leaves. Participants see that recording has started, and an administrator can make Teams ask each person to agree before they unmute. For most companies this is the whole answer.
Approve one outside tool, on its business tier. If your team prefers a particular product, buy the business version under a company account, read the two paragraphs of its terms about retention and training, and name it in your AI acceptable use policy as the only one allowed. The free tier of the same product is a different product, with different terms, and it is the one your staff will sign up for if you say nothing.
Say no to the rest. Whichever position you take, every other note-taker is unapproved, including the ones other people bring. The rule for those is spoken, not technical: the organizer asks for the bot to be removed, or accepts it knowingly and says so.
And whichever tool records, the organizer says so at the start of the call. New York lets a participant record without telling anyone; your client in California is covered by a stricter law, and no client anywhere enjoys learning afterward.
Two settings for your IT provider
Both of these are configuration, not purchases, and both are the kind of thing that takes an afternoon.
Refuse outside bots automatically. Since September 2026, Teams has a setting that refuses identified external bots at the door, with no decision left to the meeting organizer. It is off by default. The honest caveat is that Teams can only block bots it recognizes as bots; a note-taker running inside a participant’s own meeting app is invisible to it. Turning it on removes the common case and leaves the spoken rule to cover the rest.
Stop apps from getting calendar access without approval. This is the one that matters more, because it is how every outside note-taker gets in. Microsoft 365 can be set so that employees cannot approve an app’s access to their calendar or mailbox on their own; the request goes to an administrator instead, who says yes or no. It is the same setting that closes the door on a much nastier category of attack, where a phishing email tricks an employee into approving an app that then reads their mailbox for months. One setting, two problems.
Ask your provider for a third thing while they are in there: the list of apps that already have access to your staff’s calendars and mailboxes. It is usually longer than anyone expects, and it is where the forgotten note-taker from the employee who left in March still lives.
What a well-run approach to note-takers looks like
- One approved tool is named, and it is either the built-in one or a business-tier product under a company account.
- Recordings live inside the company, in a place the retention policy and the backup both cover, not in an employee’s personal account.
- Every recorded call is announced at the start, in one sentence, by the organizer.
- Outside bots are refused by default, and the organizer knows to ask when one appears anyway.
- Staff cannot grant apps access to their calendar or mailbox without an administrator seeing the request.
- Someone can produce the list of apps with access to company calendars and mailboxes, and has read it this quarter.
- The AI policy has two lines about it, and the team has heard them read aloud once.
Where this leaves you
Two questions for this week. “If a client’s lawyer asked for the transcript of last Tuesday’s call, who here would know whether one exists and where it is?” And: “Which apps have access to our calendars today, and who approved them?” If the first answer is a shrug and the second is “I would have to ask,” you have your finding, and it is the most common one.
Setting the two controls above, pulling the list of apps that already have access, and making the built-in recording the easy default are Microsoft 365 configuration work. Deciding what your staff may record and where it goes is the policy half, which sits inside a security program. Get in touch and we will start with the list of what has access to your calendars now.