ChatGPT meeting notes: a consent and data policy for teams
This research library uses AI-assisted source research and drafting. Linked sources support product claims; analysis and proposed exercises are our interpretation. Unless an article documents a test and its results, do not read it as a hands-on review or an independently verified benchmark.
ChatGPT meeting notes now come from a Meetings plugin in the ChatGPT desktop app on macOS that listens through your own microphone and system audio, with no bot joining the call. OpenAI launched it on 29 September 2026 as a beta for all Pro and Business users. The Meetings help article states that you must tell participants and get their consent, and that the in-app reminder does not notify anyone else. That one sentence moves a privacy decision from the tool to every person who clicks record, which is why teams need a written policy before the plugin spreads.
This guide is for engineering leads, workspace admins and whoever owns your data policy. It covers what the plugin does with audio and notes, which decisions are yours, and a policy you can adapt. It is not legal advice. Recording and consent rules differ by country and by company, so involve your legal or privacy owner.
Should your team allow ChatGPT meeting notes?
Many teams will want it for internal working sessions. Decide the conditions as a team rather than leaving them to individuals. The benefit is real: decisions and action items land on a page instead of in one person's memory. The risk is also concrete. Because nothing visible joins the call, a participant can be recorded without noticing, unless the note taker tells them.
A reasonable default is to allow ChatGPT meeting notes for internal meetings where every participant has agreed, and to exclude categories where consent is harder or the content is more sensitive. The sections below turn that default into rules.
Where meeting audio and notes go
| Data | What the help article says | Decision for your policy |
|---|---|---|
| Audio | Streamed to OpenAI, deleted from the Mac and servers once notes are ready | Accept that there is no recording to replay |
| Transcript | Not included when a page is shared | Who may see the full notes page |
| Summary and action items | Saved to a page in ChatGPT Space, private by default | When a page may be shared, and with whom |
| Calendar | Optional, through the Google Calendar or Outlook Calendar plugin | Whether calendar access is allowed at all |
Two consequences follow. First, the summary page becomes the record of the meeting, so its accuracy and sharing need an owner. Second, a dispute about what was said cannot be settled by replaying audio. If a decision matters, the notes should be checked by someone who was there, soon after the meeting.
Consent is the note taker's job, so write it down
The plugin gives the note taker a reminder, and nothing more. Your policy should make the ask specific:
- Ask at the start, out loud, before notes begin: "I'm taking AI notes with ChatGPT. The audio is deleted afterwards and I'll share the summary. Is everyone OK with that?"
- If anyone declines, take no AI notes in that meeting. Do not negotiate in front of the group.
- For people who join late, ask again.
- In calendar invites for recurring meetings, add a line that AI notes may be taken, so people can raise concerns before the call.
The invite line helps, but it does not replace asking in the meeting.
Meetings to exclude by default
Some meetings carry more risk than they are worth. We suggest excluding these unless a named owner approves an exception:
- Performance reviews, HR conversations and one-to-ones about personal matters.
- Legal, security incident and vulnerability discussions.
- Calls with customers, candidates or external partners, unless your legal owner has approved a consent process for them.
- Any meeting where participants cannot see or hear the consent request, such as large webinars.
Admin controls on Business and Enterprise
On Business, Space and Meetings must be enabled by a workspace admin before anyone can use the plugin. Use that switch as your gate: publish the policy, then enable the feature. Enterprise access is an alpha through your account manager, so larger organizations have time to agree the rules before broad availability.
The plugin is also separate from the older Record feature. If you already have a policy for Record, check it against Meetings rather than assuming it covers both. Windows, iOS and Android versions are listed as coming soon, so plan to revisit the policy when they arrive and more people can take notes.
A one-page policy checklist
- Allowed meeting types, and the default exclusions above.
- The exact consent sentence, when to say it, and what happens if someone declines.
- Who may share a notes page, and whether external sharing is ever allowed.
- Who checks the summary for accuracy, and by when.
- Whether calendar plugins may be connected.
- The admin who enables Space and Meetings, and the date the policy was published.
- A review date for when Windows and mobile versions arrive.
What to measure after launch
Keep it light. Track how many notes pages needed a correction to a decision, how often someone declined consent, and any case where a page was shared more widely than the policy allows. Those three numbers tell you whether the policy is followed and whether the notes can be trusted. Our guide to measuring an AI workflow before scaling it covers how to keep such a pilot honest.
The pattern matches our Delegate, Review, Own method: the plugin drafts the notes, a person reviews them, and the meeting owner owns what gets shared. This week, write the consent sentence, agree the exclusions with your privacy owner, and only then ask your admin to enable Meetings.