AI August 2026

Nobody rolled these out. That is the interesting part. AI note-takers arrived in most businesses the way good tools usually do: one person tried one, it saved them half an hour, and within a month it was joining meetings nobody had approved. We are not about to tell you to ban them, because we use them ourselves. But there is a short list of things worth knowing before a bot sits in on a client meeting or a difficult conversation with a staff member.

What an AI note-taker actually does

An AI note-taker is a bot that dials into a Teams, Zoom or Google Meet call, listens to everything said, converts the speech to text, and writes up a summary with action items. Some capture the video as well as the audio. The ones you will meet most often are Microsoft 365 Copilot in Teams, Otter, Fireflies and Fathom.

Most of them hook into a calendar so they can turn up on their own. Neither the recording nor the transcript vanishes when the call ends. They are kept, almost always in the cloud, and months later somebody can still search them, forward them or export them. Which cloud, and whose staff can open it, comes down entirely to the tool you used.

The question is not whether the note-taker works. It is where the recording lives afterwards, and who can reach it.

Who can actually see the recording

Start with the obvious group. Many note-takers email the summary to every attendee by default, and some send it to everyone who was invited, including the people who never turned up. If the meeting wandered into a sensitive topic, that distribution list suddenly matters a great deal.

Then there is the vendor. With most third-party note-takers, the file ends up on infrastructure the vendor owns. Their systems, and in some cases their people, can reach it under terms somebody accepted on your behalf, quite possibly an employee clicking through a free sign-up.

And there is the account problem. If the bot joined because a staff member connected it to their own calendar with a personal login, the recording of your client meeting now lives in an account your business does not own, cannot audit, and cannot retrieve when that person leaves. That is the same gap we wrote about in why bad onboarding is the real cause of messy offboarding, wearing a different hat.

For anyone handling legal, financial or health information there is a further wrinkle. Letting a third party access and process a confidential discussion can quietly undermine the confidentiality you are obliged to maintain, and in some professions that is not a small problem.

Does the tool train its AI on your meetings?

This is where the tools differ most, and it is the question almost nobody asks before installing one.

Microsoft documents that Microsoft 365 Copilot does not use your prompts, your responses, or the data it retrieves through Microsoft Graph to train its foundation models, and that the content stays inside your organisation's Microsoft 365 service boundary rather than going anywhere near the public model.

Third-party note-takers vary enormously. Some hold your recordings on their own infrastructure and, depending on the terms accepted, may use that content to improve their models. Others state plainly that they never train on customer data. You cannot tell from the outside, and the only way to know is to read that specific tool's terms.

Two note-takers can look identical during the meeting and treat your data completely differently once it ends.

Consent, and why Australia is not straightforward

Most of the guidance written about AI note-takers is American, and it does not transfer. Australia has no single recording law. Each state and territory has its own, and they do not agree with each other.

Broadly, in Victoria, Queensland and the Northern Territory, a participant in a private conversation may generally record it without asking the other people first. In New South Wales, South Australia and Western Australia, the starting position is that you need the consent of all the principal parties. The rules and their exceptions differ again elsewhere, and none of this is legal advice.

Now put that on a Teams call. Someone in Mornington, someone in Sydney, someone in Perth. More than one rule is in play in the same meeting, and the bot has no idea which. On top of that, a recording of an identifiable person is personal information, so if the Privacy Act applies to your business, obligations attach to how you collect it, store it and pass it on.

Which is why we think "is it legal" is the wrong first question. Being permitted to record someone quietly is not the same as it being a reasonable thing to do to a client. Announce the recording, explain why, and give people a real chance to object. It costs ten seconds and it removes the entire problem. For anything covered by confidentiality or a professional obligation, take proper legal advice before you record at all.

Legal and appropriate are not the same test. Say the meeting is being recorded, and let people say no.

The bot nobody invited

The most common way this goes wrong is not dramatic. Someone signs up to a free note-taker, connects it to their calendar, and leaves on the setting that lets it join meetings automatically. From then on it turns up to everything on the schedule, occasionally including meetings the person who installed it is not even attending.

That is how a client negotiation ends up transcribed into a personal account, or a conversation about someone's performance gets emailed around as a neat summary. Nobody set out to do anything wrong. A default was left switched on, and nobody had said what the rule was.

Six rules that make note-takers safe to use

  • Choose one approved tool and say so out loud. Decide which note-taker the business uses, and ask people not to connect others to company meetings. Recordings then live in one place you control.
  • Turn auto-join off. The bot should record when a person decides to record, not because a meeting appeared on a calendar.
  • Announce it, and get consent. Make it normal to say at the start that the meeting is being recorded, and equally normal to switch it off when someone would rather you did not.
  • Prefer tools that keep the data in your own tenant. A note-taker that writes into the Microsoft 365 environment you already own, and does not train on what it hears, is far easier to govern than one parking everything on infrastructure you have never seen.
  • Check who receives the summary. The default sharing setting is usually more generous than you would have chosen.
  • Keep bots out of sensitive meetings. Legal, HR, financial and confidential client conversations should default to no recording, unless there is a clear reason and everyone in the room agrees.

If you run Microsoft 365, most of this can be decided once and enforced centrally. An administrator can control whether Copilot and meeting transcription are permitted in Teams, which is a great deal more reliable than hoping every person gets it right on the day. It is the same groundwork we described in preparing your Microsoft 365 permissions before a Copilot rollout.

Where we land on this

We use AI note-takers, and we think most businesses should. The time they give back is real, and the summaries are usually better than the notes anyone was taking by hand. What we do not accept is that a tool which records every word of your business should arrive by accident, configured by whoever signed up first.

When we set these up for clients across Melbourne and the Mornington Peninsula, the pattern is the same every time. The recording stays inside the client's own Microsoft 365 tenant. Auto-join is off. Someone says out loud that the meeting is being recorded. None of that is complicated. It is simply decided on purpose rather than by default, which is the same argument we made in it is time to govern your team's AI use.

If you do not know where your meeting recordings are going right now, that is worth half an hour of somebody's attention. Usually it is a quick answer. Occasionally it is not, and those are the ones worth finding early.

Frequently asked questions

Is it legal to record a meeting with an AI note-taker in Australia?

It depends on where the people in the meeting are. Australia has no single recording law. In Victoria, Queensland and the Northern Territory, a participant in a private conversation may generally record it without the consent of the others. In New South Wales, South Australia and Western Australia, the starting position is that all principal parties must consent, and other jurisdictions differ again. On a video call with people in different states, more than one rule can apply at once. This is not legal advice. Wherever you are, the safe practice is the same: say at the outset that you are recording, and give anyone who objects a real chance to say so.

Does Microsoft 365 Copilot use my meeting data to train its AI?

No. Microsoft documents that Microsoft 365 Copilot does not use your prompts, your responses, or the data it retrieves through Microsoft Graph to train its foundation models, and that your content stays within your organisation's Microsoft 365 service boundary rather than going to the public model.

Can an AI note-taker join a meeting without me knowing?

Yes. Once a note-taker has been given access to somebody's calendar it can show up to whatever is scheduled, in some cases to meetings the person who installed it is not even attending. Switching the auto-join setting off restores the rule that a human decides when recording begins.

Where are AI note-taker recordings stored?

In the cloud, but which cloud matters. With Microsoft 365 Copilot, the content stays inside your own Microsoft 365 tenant. Many third-party tools keep recordings on the vendor's own servers, and if a staff member signed up with a personal account, the recording may sit in an account your business does not control. Check the specific tool's terms.

Should we let staff use Otter or Fireflies for work?

You can, provided somebody has set the rules first. Settle on a single approved tool, disable auto-join, make announcing the recording routine, read what that vendor does with the data it stores, and keep the bot away from legal, HR and confidential client conversations. The risk was never the tool itself. It is a tool nobody actually decided on.