Somewhere in your business, an AI is probably taking notes right now. Someone on your team connected Otter or Fireflies or Read AI to their calendar, and now a little bot slips into meetings, records every word, and emails around a tidy summary afterward. It's genuinely useful — nobody misses the days of scribbling half a page and forgetting the rest. But it arrived without anyone deciding it should, and it's quietly recording your customers, your staff, and your confidential conversations onto someone else's servers. That's the part worth stopping to look at. The tools are fine. The defaults are the problem.
What these tools actually do with your meetings
Under the hood, an AI note-taker connects to your calendar, joins the meeting as a participant, and records the audio — not on your computer, but on the vendor's servers, where the transcript and summary are generated and stored under the vendor's terms of service. And most of them default to collecting as much as possible unless someone goes into the settings and dials it back. That means the recording of your pricing conversation, your staff's performance discussion, or your client's confidential situation lives on a third party's infrastructure, governed by a policy nobody on your team has read.
This isn't hypothetical hand-wringing. As of 2026, Otter is facing consolidated lawsuits in federal court over recording people without their explicit consent, and Fireflies is fighting biometric-privacy suits in Illinois alleging it captured and stored the unique voice characteristics of meeting participants — including people who never signed up for the tool or agreed to anything. The common thread in every one of these cases is the same: people ended up recorded without a real chance to say no.
The Florida wrinkle: consent isn't optional here
This matters more in Florida than in a lot of the country. Florida is an all-party-consent state — as a rule, you need the consent of everyone in a conversation to record it, not just one person. So when an AI bot silently joins a call with a customer, a vendor, or a job candidate and starts recording, you may be on the wrong side of that line before anyone's said a word about it. The fix is simple and free: announce that the meeting is being recorded, and give people a genuine chance to decline. But it has to actually happen — a setting buried three menus deep that nobody checks isn't consent.
The questions nobody asked before turning it on
You don't need to ban these tools — they earn their keep. You need to answer a few questions you skipped when they showed up on their own:
- Where does the recording live, and for how long? Whose servers, under whose terms, and is there a retention limit — or does it sit there forever by default?
- Who can see the transcripts? Just the person who ran the meeting, the whole workspace, or anyone the tool auto-shared the summary with?
- Is it training an AI on your conversations? Several tools use your recordings to improve their models unless you turn that off — and the switch is rarely front and center.
- Did the people in the room agree to be recorded? Especially your customers and candidates, who never signed the tool's terms and, in Florida, need to consent.
- Is it in rooms it has no business being in? HR conversations, legal discussions, anything privileged or highly sensitive — those should never have a bot quietly transcribing them.
What to actually do about it
This is a fifteen-minute fix, not a project — it just needs someone to actually do it:
- Set a consent habit. Announce recording at the top of any external meeting, and give people room to opt out. Make it normal, not awkward.
- Fix the settings once. Turn off model training, set a reasonable retention period so transcripts don't pile up forever, and limit who transcripts get shared with by default.
- Draw a line around sensitive rooms. Agree, out loud, that the note-taker stays out of HR, legal, and confidential conversations.
- Pick tools that don't train on your data. When you're choosing or renewing, favor vendors whose default is "your content is yours." It's a real differentiator now.
- Write a one-page AI-tools policy. Which tools are approved, what they can and can't touch, and the consent rule. One page makes it stick and gives your team a clear answer instead of a shrug.
The bigger pattern
AI note-takers are just the first of many tools that will walk into your business the same way — adopted by a well-meaning employee, useful on day one, and quietly making decisions about your data that nobody signed off on. The answer isn't to lock everything down; it's to have a light-touch way of saying yes on purpose instead of by accident. That's exactly the kind of sensible, bank-grade-but-right-sized governance behind controls and compliance readiness — controls that fit a business your size rather than a Fortune 500's. If your team has adopted a pile of AI tools and nobody's sure what they're all doing with your data, a quick readiness look sorts it out — book a discovery call and we'll get your AI tools working for you without quietly working against you.
Common questions
- Are AI meeting note-takers a privacy risk?
- They can be. Tools like Otter, Fireflies, Read AI, and Fathom join your meetings, record the audio on the vendor's servers, and generate transcripts stored under the vendor's terms — and most default to maximum data collection unless you change the settings. In 2026 both Otter and Fireflies are facing lawsuits over recording people who never consented, including capturing voice characteristics without permission. The tools are useful, but the defaults are not built around your privacy.
- Do I need everyone's consent to record a meeting in Florida?
- In Florida, yes. Florida is an all-party-consent state — recording a conversation generally requires the consent of everyone in it, not just one person. That makes an AI note-taker quietly joining and recording a call legally risky if participants haven't agreed. The safe practice is to announce the recording and give people a real chance to decline before it starts.
- Will these tools train their AI on my meetings?
- Some will, unless you tell them not to. Several note-takers use recordings and transcripts to improve their models by default, and turning that off is buried in the settings. If your meetings touch customer data, financials, or anything confidential, check each tool's data-use and training settings before you rely on it — and prefer vendors that don't train on your content.
- What should a small business actually do about this?
- Three things: set a simple ground rule for announcing and consenting to recordings, configure the tool's settings for privacy (turn off model training, set a sensible retention period, limit who can access transcripts), and keep the note-taker out of sensitive conversations entirely — HR issues, legal matters, anything privileged. A short written AI-tools policy makes all of that stick.