The short version
Recording a meeting is useful. Minutes, a replay for whoever was on leave and an AI summary are all real benefits. But in most of Australia you can’t just press record, or let an AI note-taker into the room, without everyone’s consent. The rules differ by state and territory, and the penalties for getting it wrong can be serious. Even where the law lets a participant record, trust is the thing that gets damaged.
My recommendation is simple. Have one official recording, run by the organiser, with consent built into the booking or invite and announced at the start. No personal or third-party recorders, AI bots or wearables unless the organiser has agreed. Sample wording is further down.
This is general information, not legal advice. I’m not a lawyer. If it matters, get advice for your situation.
Why this is everyone’s problem now
AI note-takers have made recording effortless. Microsoft 365 Copilot in Teams, Otter, Fireflies, Zoom recording, phone voice memos and even AI wearables will happily capture a whole conversation and ship it off to a cloud service. In an MSP or small business that covers internal meetings, client calls and the awkward conversations about incidents and mistakes. If someone discovers a bot or a phone quietly recording, that trust goes.
What the law says, state by state
There’s no single national recording law. It’s mostly state and territory surveillance-device legislation, plus Commonwealth rules on telecommunications. Broadly, Victoria, Queensland and the NT let a participant record a private conversation without the others’ consent. SA and WA generally require everyone’s consent. NSW, Tasmania and the ACT generally require consent too, with a narrow exception for recording for your own personal use that isn’t shared. Consent can be express or implied.
| Jurisdiction | Statute | Can a participant record without others’ consent? | Key exception | Penalty (where verified) |
|---|---|---|---|---|
| NSW | Surveillance Devices Act 2007 (s7) | Generally no | Personal use only (not communicated or published to non-parties), or reasonably necessary to protect lawful interests | Up to 100 penalty units or 5 years (individual); 500 penalty units (company) |
| Vic | Surveillance Devices Act 1999 (s6) | Yes – participant recording isn’t caught by s6 | Communicating or publishing a private conversation is regulated separately (s11) | Not verified for publication |
| Qld | Invasion of Privacy Act 1971 (s43) | Yes – s43(2)(a) exempts a party | Publication is regulated separately (ss44-45) | 40 penalty units or 2 years (using a device on a conversation you’re not part of) |
| SA | Surveillance Devices Act 2016 (s4) | No – all principal parties must consent, expressly or impliedly | Reasonably necessary to protect lawful interests; public interest | Up to $15,000 or 3 years (individual); $75,000 (body corporate) |
| WA | Surveillance Devices Act 1998 (s5) | No | Lawful interests and similar exceptions | Up to $5,000 or 12 months (individual); $50,000 (body corporate) |
| Tas | Listening Devices Act 1991 (s5) | Generally no (NSW-style) | Personal use only / lawful interests | 40 penalty units or 2 years (secondary source, not verified) |
| ACT | Listening Devices Act 1992 (s4) | Generally no (NSW-style) | Personal use only / lawful interests | 50 penalty units (secondary source, not verified) |
| NT | Surveillance Devices Act 2007 (s11) | Yes – offence only applies if you’re not a party | Publication is regulated separately (s15) | 250 penalty units or 2 years (non-party recording) |
| Cth | Telecommunications (Interception and Access) Act 1979 (ss6-7) | Not an issue for a party recording at their own end, generally | Interception of a live communication over a telecoms system without the knowledge of the person making it is prohibited | Up to 2 years |
Check these before relying on them. Section numbers and penalties come from secondary sources that summarise the statutes. The Tasmanian and ACT penalties are unverified, and so are the Victorian, Queensland and NT penalties for publishing a recording. Check the current legislation before you rely on any of it.
Two more traps:
- Publishing is a separate issue. Even where you can lawfully record, communicating or publishing the recording to others can be an offence or need consent. Sharing a recording or transcript on LinkedIn, in a Teams chat or with an AI vendor can be the real problem.
- Mixed locations. If you’re in Victoria, someone’s in Perth and someone’s in Sydney, it’s not clear which law applies. The safest approach is to assume the strictest one applies, which means getting everyone’s consent.
In person, online and ‘private conversation’
The surveillance device laws are about ‘private conversations’. Broadly, a conversation isn’t private if all the parties ought reasonably to expect it might be overheard by someone else. A large open session might arguably fall on that side. A small team meeting or a client call almost certainly doesn’t. I wouldn’t rely on that argument. A court looks at the circumstances, and it’s untested for meetings like yours.
The rules apply equally to a phone on the table, a wearable and a bot that joins your Teams call. The device is a ‘listening device’ whatever it looks like.
Commonwealth: the TIA Act and the Privacy Act
- TIA Act: it prohibits intercepting a live communication passing over a telecommunications system without the knowledge of the person making it. A participant recording at their own end isn’t usually treated as interception. Whether a bot that joins a call as a participant is different hasn’t been tested, as far as I know.
- Privacy Act: it applies to ‘APP entities’, which are generally businesses with turnover over $3 million (plus some smaller ones, such as health providers) and government agencies. The small business exemption is still in force as at October 2026 according to secondary sources, though reform has been proposed. Many MSPs are under the threshold, but many of their clients and some vendors aren’t.
- OAIC guidance: it says meeting recordings and AI transcripts are personal information. Collect only what’s reasonably necessary, tell people, consider opt-outs, and destroy or de-identify what wasn’t needed, such as a personal chat or confidential client details.
- Statutory privacy tort: since 10 June 2025 there’s a tort for serious invasions of privacy. I haven’t verified how it applies to small operators or to recordings.
The AI note-taker problem
The recording is only half of it. An AI tool adds questions that an old-fashioned voice memo never did:
- Third-party storage: your colleagues’ and clients’ words now sit on a vendor’s servers.
- Training: does the vendor use the audio or transcripts to train its models? Some do, so check the terms.
- Cross-border: the data is probably processed outside Australia.
- Confidentiality: people discuss client names, incidents and commercial details, which may breach NDAs or client contracts.
- Voiceprints: some tools build speaker profiles, which is biometric-style data.
- Sharing: some tools email a summary to every attendee, or publish a link, automatically.
This is already in the courts overseas. In re Otter.AI Privacy Litigation in the US alleges Otter’s Notetaker recorded meetings without all participants’ consent and used the data for training. In August 2026 a federal court held Otter could plausibly be treated as a third-party eavesdropper because it keeps and uses recordings for its own purposes. That’s US law, not ours, but it shows the risk.
There are workplace consequences too. The Fair Work Commission has accepted covert recording as a valid reason for dismissal (Schwenke v Silcar [2013] FWC 4513). NSW also needs 14 days’ written notice for camera, computer or tracking surveillance of employees, and the ACT has a notice and consultation regime. If you run staff meetings through an AI recorder, check them.
A simple approach for MSPs and small business
The cleanest fix is to separate the organiser’s official recording from everyone else’s. The organiser decides, tells everyone, gets consent and controls where the recording lives and who sees it. An individual’s own recorder or bot has a separate vendor, separate retention and nobody else’s consent. In SA, WA and (mostly) NSW, Tasmania and the ACT that’s where someone can get into trouble, even if they only meant it as private notes.
- Write a short recording policy. Plain English (sample below).
- Get consent in the invite or booking. Say the meeting will be recorded, why, who sees it and how to opt out.
- Announce it at the start. Silence after a clear announcement may amount to implied consent, but express consent, such as a ticked box or a Teams consent prompt, is better.
- Make it visible and offer opt-outs. Use the recording indicator, say it out loud, and let people keep their camera off or ask in chat.
- One official recording. The organiser shares the transcript or summary afterwards, so nobody needs their own recorder.
- Set retention, deletion and access. Where it’s stored, how long it’s kept, who can view it, and how someone asks for deletion.
- Control who joins. See the Teams notes below. Zoom shows participants a consent prompt when recording starts.
- If you find an unauthorised recording, stay calm. Politely ask for it to be stopped, ask what’s been captured and where it’s stored, and ask for deletion and no sharing. Don’t confront anyone publicly or take their device. If it’s serious or has been shared, get advice.
What Microsoft 365 gives you in Teams
If you manage the tenant, two Teams meeting policy settings are worth knowing. Both are admin-level policies, not per-meeting switches, and both match Microsoft Learn.
- Manage external bots and their access to meetings. Teams detects external bots such as note-takers and holds them in the lobby until the organiser explicitly admits them. “When detected, require approval before joining” is the default. Microsoft says some bots may not be detected, so it doesn’t replace a policy. It also suggests letting only organisers and co-organisers admit people from the lobby.
- Require participant agreement for recording and transcription. It’s off by default. Switch it on and, once recording or transcription starts, everyone else is muted with camera and sharing off until they answer Yes or No. A No means a view-only experience. The person who starts the recording is treated as having consented, and the choices appear in the attendance report. It’s the closest thing Teams has to a tick-the-box consent.
Sample wording
(a) Invite or booking notice
This meeting will be recorded (audio, video and chat) by the organiser so that people who can’t attend can catch up and so we can produce notes and an AI-generated summary. The recording is stored in [location], kept for [90 days], and available only to [who]. If you’d prefer not to be recorded, email [organiser] before the meeting and we’ll make arrangements, such as keeping your camera off or asking questions in chat. Please don’t use your own recording tools, AI note-takers or bots without the organiser’s agreement. By attending after reading this notice, you agree to be recorded.
(b) Start-of-meeting script
Before we start: this session is being recorded by us, the organisers, for notes and an AI summary that we’ll share afterwards. If you don’t want to be recorded, please say so now or message [organiser] in chat, and we’ll sort it out. Please don’t run your own recorder or AI note-taker. We’ll share the official transcript and summary. If anyone is uncomfortable at any point, we can pause the recording. Is everyone happy to proceed?
(c) Short recording policy
- Only the organiser makes the official recording of a meeting.
- Attendees must not record audio or video by any means (phone, laptop, wearable, AI note-taker or bot) without the organiser’s agreement and the consent of everyone present.
- Attendees are told about the recording in the invite and at the start of the meeting, and can opt out.
- The organiser shares the transcript or summary with attendees. It isn’t shared outside the meeting without the consent of the people in it.
- Recordings are stored in [location], kept for [period], and deleted on request where practical.
- Unapproved bots will be removed. If an unauthorised recording is found, the organiser will ask for it to be stopped and deleted.
What I haven’t verified
- Section numbers and penalties come from secondary sources, not the statutes themselves.
- The Tasmanian and ACT penalties are unverified.
- The Victorian, Queensland and NT penalties for publishing a recording are unverified.
- Whether a bot that joins a call counts as ‘interception’ under the TIA Act is untested, as far as I know.
- I haven’t verified how the statutory privacy tort applies to small operators or to recordings.
Sources
- DW Fox Tucker Lawyers: When is Consent Required to Record a Conversation (Aug 2026)
- Recording Law: Is It Legal to Record a Conversation in Australia? (secondary; quotes statute text)
- MJA 2021: Overt and covert recordings of health care consultations in Australia
- OAIC: Guidance on privacy and the use of commercially available AI products
- OAIC: APP 3 guidelines (updated 13 May 2026)
- OAIC: Small business
- Microsoft Learn: Manage external bots and their access to meetings
- Microsoft Learn: Manage participant agreement for recording and transcription
- Microsoft Learn: Manage Teams recording policies
- Zoom: Providing consent to be recorded
- Zoom: Modifying recording notification prompts
- NSW Workplace Surveillance Act 2005
- ACT Workplace Privacy Act 2011
- National Law Review: In re Otter.AI Privacy Litigation (N.D. Cal., Aug 2026)
General information only, not legal advice. Laws change and details vary by situation, so check the current legislation or get advice before relying on this.
