The AI Notetaker in the Room Heard Everything

The meeting was sensitive. A personnel matter, a pending negotiation, a discussion your counsel joined for a reason. The kind of conversation that happens behind a closed door on purpose.

And a third party heard all of it.

Not a person. A notetaker. A bot that joined the call wearing a participant's name, an AI feature switched on inside the meeting software, or a recorder the size of a phone sitting on the table. It captured the audio, produced a transcript, and stored both on a server somewhere, under an account that may belong to a vendor, a staffer, or a guest who left the meeting twenty minutes in.

I am not against these tools. We use meeting transcription in our own practice, and I will tell you how. The problem is not the technology. The problem is that a decision with real legal and governance weight, the decision to create a permanent record of a private conversation, is being made by default. By whoever installed an app. Not by the people accountable for what happens in that room.

Six questions to answer before the next meeting

Take the last sensitive meeting you held and try to answer these.

Who consented to the recording? Everyone present, on the record? Or did one participant's tool join on their behalf while everyone else assumed the room was closed?

Where do the audio and transcript live, and under whose account? If the answer is "some vendor's cloud, under an employee's personal login," you do not control that record. You may not even be able to find it.

Does the vendor use your content to train its models? The answer lives in terms of service nobody read. If your council discussions or client conversations can become training data, you agreed to that somewhere, whether you know it or not.

How long is it retained, and who can retrieve it? A recording you cannot locate, produce, or delete on your own schedule is not your record. It is someone else's record of you.

Does the transcript undermine privilege or create a discoverable record? When counsel is in the room, the existence of a verbatim transcript changes what may be protected and what may be producible. I am not your lawyer. But this question belongs in front of your lawyer before the recording exists, not after someone requests it.

What happens when a guest brings a notetaker the host never approved? An outside party joins your call and their assistant joins with them. Your sensitive meeting is now stored under their account, governed by their vendor's terms, retained on their schedule.

If you can answer all six, you have a policy. If you cannot, you have a default, and the default was set by a software company.

A transcript is a record

Here is the shift I ask leadership to make. Stop treating these tools as note-taking conveniences and start treating every transcript as a record. A record has an owner and a retention schedule. It can be requested, subpoenaed, discovered. It outlives the meeting and sometimes the people in it.

Once you see it that way, the six questions stop being IT questions. They are governance questions, and they belong to the people who sign, not the people who administer the software.

How we handle it in our own practice

We record and transcribe meetings deliberately, because a good transcript is genuinely valuable. Decisions get captured accurately and commitments do not evaporate on the drive home.

But deliberate is the operative word. We decide before a meeting whether it gets recorded, and some conversations do not. We know where every transcript is stored and under whose account. We know how transcripts are handled afterward and when they age out. Recording is a choice we make meeting by meeting, under rules we set once.

That is the whole counsel. Decide before the meeting, not after. Make recording a policy question, not a default. Treat transcripts as records with retention rules.

For tribal governments, the rules come first

If you lead a tribal government, the stakes are higher.

Council proceedings and executive sessions are sovereign records. Enrollment and health matters carry obligations that do not bend because a tool was convenient. A verbatim transcript of a council discussion sitting in a commercial vendor's cloud, under terms the tribe never negotiated, on retention the tribe does not control, is a sovereignty problem before it is an IT problem.

None of this requires banning AI tools from tribal operations. It requires explicit rules, adopted before any AI tool joins the room: which meetings may be recorded, which never are, where records live, and who holds the keys. Write those rules while things are calm. You do not want to write them in response to an incident.

Decide before the meeting

The notetaker is not going away. More are coming, built deeper into the software you already use and switched on by default. The organizations that handle this well will not be the ones with the strictest bans or the fastest adoption. They will be the ones that decided, on purpose, what gets recorded and what does not.

If you want a second set of eyes on how AI tools are entering your meetings and what your policy should say, that is a conversation I am glad to have.