Meeting notes are sensitive data. Handle them that way

Virginia (CPO & CMO)

  • ai-transformation
  • running-the-initiative
  • fluency
  • acceptable-use
  • playbook

Meeting notes are sensitive data. Handle them that way

The bot joined the call. Nobody was asked. The summary went out to everyone on the invite — including the customer who never agreed to be recorded.

That is a Phase 1 problem. Not a chatbot problem. Not a "ban AI notes" problem.

Our Fluency playbook already asks for a one-page acceptable-use note as a Phase 1 exit artifact. Most of those notes say something about pasting confidential data into public models. Few say anything about recordings: who may run a bot, how participants hear about it, where the transcript is stored, who it gets shared with, and when it is deleted.

Start by asking, not banning covered why blanket bans drive shadow use underground. This post is the meetings section of the same note.

Consent before the notetaker is still weak

In a July 2026 U.S. survey of 500 employed adults commissioned by a law firm, about a third said an AI notetaker had been in their work meetings. Among the 167 who had one, only 34.7% said they were always asked first; 25.1% said they were never asked. Treat the subsample as directional. (Kolmogorov Law / Pollfish)

A separate June 2026 survey of 800 Japanese business professionals found only 22.7% obtain participant consent before every recording or transcription, and only 18.6% said their workplace has clear rules for AI minutes — while most respondents already use the tools. Treat as directional; interested-source survey. (MiraLab)

Two countries. Same pattern. The fix is operator habit, not a legal program: one sentence at the start of the meeting, and stop if anyone objects.

Recording-consent rules vary by jurisdiction. Ask your counsel. What follows is operating practice, not legal advice.

Classify the meeting, not the transcript

Notes take on the sensitivity of the most sensitive thing said in the room. Decide the lane before the call:

Meeting type Default practice
HR, performance, compensation, disciplinary No public model. No bot. Human notes with HR.
Health or personal circumstances No public model. No bot.
Counsel present No public model. No bot unless counsel says so.
Active security incidents No public model. No bot.
Customer names, deal terms, pricing Sanctioned tool + human review. Ask the other side before any bot records an external call.
Unreleased product or roadmap Sanctioned tool + human review. Internal only.
Board, M&A, financials before release No public model. No bot.
Routine stand-ups and project syncs Sanctioned tool is fine. Review before the summary leaves the team.

Harvard IT's AI-assistant guidelines are a useful shape for this list — approved tools, announce at the start, stop on objection, keep bots out of sensitive meetings, review before sharing, delete when done — not a standard you must copy. (Harvard HUIT)

When it's their bot

The other case: a partner, customer, or vendor brings a notetaker you don't control. The transcript usually lands in their tenant. You may never see it.

If you host: remove the outside bot and use your sanctioned tool (or the platform's built-in transcription). You do not need the inviter's permission to remove it. Share reviewed notes afterward. A one-line script keeps the relationship intact: "Mind turning the notetaker off for this one? I'll send action items after."

If you're the guest: ask once. If it stays, assume you're being recorded — keep pricing, unreleased product, and personal matters high-level, and put the decisions in a follow-up you control. Platform blocks on your account won't stop someone else's bot in their meeting.

For deal-grade series (M&A, board-adjacent, heavy pricing): ask counsel whether the NDA should name meeting transcription tools and require deletion when information is returned — before the calendar invite goes out.

What fails

Failure What it looks like
Blanket ban, then underground pasting No bots allowed. People paste handwritten notes into a personal chatbot at night. (Ban without alternative)
Auto-summary to every invitee Unreviewed text, including side comments, reaches external guests. Anyone who receives the summary may save and reshare. (Zoom KB0058013)
Silent meeting bots A personal notetaker joins with nobody asked. People may change what they say when a bot is present.
Outside bot you don't control A partner's notetaker joins; the notes stay on their side and you never see them.
Policy covers prompts, not recordings "Don't paste confidential data" — and nothing about transcripts, storage, or retention.
Forever archive, no owner Transcripts pile up with nobody responsible for deletion.

A Meetings section for your acceptable-use note

Add this week:

  1. Approved tools — name the one sanctioned way to record or summarize. If you don't offer one, people will bring their own.
  2. Consent line — "We'd like to use [tool] to transcribe and summarize. Any objection?" If anyone objects, turn it off.
  3. No-bot meetings — HR and performance, health or personal matters, counsel, active incidents, board, M&A, unreleased financials. Accessibility accommodations go through whoever owns accommodations.
  4. Outside bots — in meetings you host, remove theirs and use the sanctioned tool; share reviewed notes. In meetings you join as a guest, ask once; if it stays, keep sensitive points high-level and follow up on your channel.
  5. Where transcripts live — a company-controlled location, not a personal account or a free-tier signup someone made last week. Auto-share is deliberate: team first, after a human review (Play 4's quality bar for anything external), labeled as AI-generated, with a path for corrections.
  6. Retention — delete when the purpose is done; legal holds override.

Name who decides edge cases. Your fluency owner (Play 6) should answer "can I run a bot in this meeting?" — and "what do we do when their bot joins?" — in one message, not a ticket.

What to do Monday

  1. Open your acceptable-use note (or draft the one-pager if it doesn't exist yet).
  2. Paste the Meetings section above and fill in your sanctioned tool and retention default.
  3. Add meeting bots and transcript destinations to this week's shadow-use inventory — without blame.
  4. Practice the consent sentence in the next three meetings you host — and the outside-bot script in the next partner call you host.

Meeting notes are not "just notes." They are a record of what people said when they thought the room was the room. Handle them that way.


This is part of Running the Initiative, our series on operating the AI Transformation Playbook one section at a time. Start with the playbook, or take the Journey Assessment — a mirror, not a score.