On 12 November 2026 Anthropic opened the beta of Claude Meetings. Claude can join a Google Meet call as a visible participant, introduce itself with a notice in the meeting chat, and take notes. It is available on the Team and Enterprise plans, and Google Meet is the first supported platform.
The feature is interesting, but it is not the point of this article. Once one note-taking bot gets into a company, other brands follow. So the rules on who may record, which meetings are off limits, and how long the results are kept should belong to your company, not be inherited from one product's defaults.
What is actually stored
According to Anthropic's Help Center, Claude saves a transcript, a summary, and descriptions of what appeared on screen. Audio is not kept. Notes and action items sit on a meeting page that members of the organization on the invite can open, edit, and share.
The audio detail is often read as good news, as if there were no recording. But a full transcript holds the same things a recording does: who said what, including numbers, names, and complaints. In risk terms the two are equivalent.

On how long this is kept, the three sources we opened are equally silent: the Claude Help Center, VentureBeat, and UC Today. UC Today in fact advises companies to set a retention policy for meeting outputs, in Claude and in other systems, and to decide who is authorized to allow the bot to take part. That advice is sound, and nobody will write the policy for you.
The built-in controls exist, and they help
Owners can choose a setting called "Meetings with external guests": internal meetings only, or allowed. If outside guests are not allowed, Claude stays out of calls that invite people from outside the organization, and leaves by itself if an outside guest joins mid-call. If they are allowed, the Help Center says Claude listens and takes notes without replying in chat, and guests do not receive the meeting page or the recap email.
The default is worth checking yourself. The Help Center says that on Team plans Claude can join calls with outside guests by default and an owner can turn that off, while on Enterprise plans an owner must allow it first. VentureBeat writes that by default Claude stays out of calls with outsiders. Two sources, two readings. Do not guess. Open your admin panel and look.
Then there is auto-join. According to the Help Center, each user chooses it in their own settings, and owners cannot set it for users. So who brings the bot into a meeting is not one person's decision in an admin console. It is the decision of dozens of people, every day.

Four things that must be written down
One page is enough:
- Who may call the bot, and who may switch on auto-join.
- Meetings that are off limits. Salary talks, performance reviews, internal legal matters. Client and vendor meetings need written approval each time.
- Retention. How long transcripts and summaries may exist, and who is responsible for deleting them.
- Who may read and share the results, given that everyone on the invite can open them.
Two variables decide most of it: how sensitive the content is, and whether outsiders are present. A salary meeting stays sensitive even if only employees attend. A product webinar has many outsiders, but its content is meant to be public. The map below is an example of where to start, not a standard to copy.

Look at the top right cell. Client and vendor meetings are where a bot is most tempting and most risky: prices, discounts, and objections end up in your company's account, and outsiders only learn about it from a notice in the meeting chat. That is why the approval should be written and per meeting, not one blanket consent.
Start before it becomes a habit
The best time to write the policy is before a team member switches the bot on in a client meeting. Four weeks is enough for a small or mid-sized company:

Week one covers two cheap steps: opening the admin panel, and asking who already has a note-taking bot on their calendar. The answer is often a surprise, because use usually starts before any policy exists.
If next week someone turns the bot on in a call with a client, you should already have a written answer on whether that is allowed, instead of asking IT afterwards. Change the bot's brand and its default settings change with it. Your company's written policy stays the same.
If you want help drafting and testing this policy, contact us at bisnis@xetup.id or WhatsApp +62 822 6515 7644.
