Published: 11 June 2025 · Last updated: 19 November 2026

AI phone agents in Australia: privacy and call recording

Plain-English guidance on privacy, consent, and call recording for AI phone agents in Australia. Includes disclosure lines, vendor questions, and controls.

By Matthew WalkerFounder, Valory AI
GovernanceRisk review7 min read
Secure office door with padlock icon representing privacy and call recording controls for AI phone agents in Australia

Tell callers when they are speaking with an AI receptionist. If you want to record a call, first work out which recording rules apply, how you will ask for permission and where the caller can go if they decline. Check what the service keeps even when audio recording is off, including transcripts, summaries and callback details.

If the Privacy Act applies to your organisation, its rules about collecting, notifying people and protecting personal information can apply separately from rules about recording a conversation. Start with the OAIC’s guidance on collection, collection notices and security and retention.

What “good” transparency sounds like

You want disclosure that is short, calm, and practical. It should happen early.

Example disclosure lines (pick one)

AI disclosure + help

  • “Hi, you’re speaking with our AI receptionist. I can help with bookings, changes, and general questions.”

Ask before recording

  • “May we record this call so the team can review what was agreed? If you’d prefer to go ahead without a recording, I can give you another way to reach us.” Use this wording only if your setup can deliver that alternative.

Transcript disclosure

  • “We’ll keep a short summary so the team can follow up.” If you keep a transcript too, explain that in your notice.

If your business is covered by the Privacy Act, you generally need to take reasonable steps to ensure people are aware of key collection matters, including why you are collecting information. (OAIC)

Which call recording rules should we check?

There is no single consent rule for every Australian call. For example, section 7 of the NSW Surveillance Devices Act sets out restrictions and exceptions for recording private conversations. Queensland addresses use and subsequent sharing separately in sections 43–45 of the Invasion of Privacy Act. Check the rules that apply to your service, including calls across borders, before relying on any exception. This guide provides general information only. For legal advice on your setup, speak with an Australian lawyer familiar with the rules that apply to your calls.

Test how a caller can decline

As a practical starting point, explain the purpose, ask for express agreement before recording and provide another way to reach the team. Have your adviser review the greeting and route. A privacy notice explains collection and use. It does not settle whether recording itself is permitted.

Call the test number and decline the recording. Check when recording starts, whether any transcript is still produced and whether the promised route works. If your setup cannot deliver that choice, resolve it before enabling recording. Decide who can retrieve each record, why they need it and when the business should remove it.

Data minimisation: what to collect, what to avoid

The safest AI phone agent is boring. It captures only what it needs and moves on.

Collect (most businesses)

  • first name
  • callback number
  • reason for the call (booking, change, quote, enquiry)
  • preferred time window
  • any operational constraint (for example, “needs wheelchair access”)

Avoid (unless you have a deliberate secure process)

  • Medicare numbers, licence numbers, and similar identifiers
  • full date of birth
  • detailed medical symptoms or history
  • payment card details over voice
  • anything you would not want read out loud in a busy office

Health service providers are covered by the Privacy Act even if they are small businesses, so data minimisation is especially important in clinics. (OAIC)

Storage, access, retention: vendor questions checklist

You are not just buying a voice. You are buying a data pathway.

Use this checklist when assessing any AI phone agent vendor or your own build.

Storage and residency

  • Where are recordings and transcripts stored?
  • Is data encrypted in transit and at rest?
  • Can you choose where data is hosted?

Access controls

  • Who can access recordings and transcripts?
  • Is access role-based?
  • Do you get audit logs for access and changes?

Retention and deletion

  • What is the default retention period?
  • Can you set different retention for recordings vs transcripts?
  • Can you delete specific calls and transcripts on request?
  • What happens to backups?

Under APP 11, covered organisations must take reasonable steps to secure personal information and to destroy or de-identify it when it is no longer needed (subject to other legal obligations). (OAIC)

Incident response

  • How are incidents detected and reported?
  • What is the notification process and timeframe?
  • Do you support the customer if a breach is likely to cause serious harm?

If an organisation is covered by the Privacy Act, the Notifiable Data Breaches scheme can require notification to affected individuals and the OAIC for eligible breaches. (OAIC)

The “do not guess” principle: accuracy and escalation

Most trust failures come from overconfidence.

Build the rule:

  • If the agent is not sure, it does not improvise.
  • It captures details and escalates to a person.

This matters for:

  • clinic enquiries that drift into clinical questions
  • pricing edge cases
  • cancellations and refunds
  • anything sensitive or emotional

A safe line:

  • “I want to make sure I get that right. I can take your details and have the team confirm it.”

Practical controls that make this safe in real life

You do not need a compliance program. You need operational discipline.

1) Change log

  • Record what changed, when, and why (hours, pricing posture, policies, scripts).
  • Tie changes to a named owner.

2) Weekly QA

  • Review a sample of calls.
  • Tag failures: wrong answer, unclear next step, over-collection, missed escalation.
  • Update scripts and knowledge in small increments.

3) Incident handling

  • Define what counts as an incident (wrong disclosure, wrong info, unauthorised access).
  • Define who is called, what is paused, and how issues are documented.
  • Have a “kill switch” that routes calls to a safe fallback.

4) Collection notice consistency

  • Keep your phone disclosures aligned with your website privacy policy and onboarding messages.
  • People should not be surprised later about what was collected and why. (OAIC)

Implementation checklist

  • Not completed: Write your disclosure lines (AI, recording, notes) and test them out loud
  • Not completed: Define the scope: what the agent will handle vs never handle
  • Not completed: Decide whether you record calls, store transcripts, or both
  • Not completed: Set retention periods and deletion processes
  • Not completed: Confirm access control, encryption, and audit logs with your vendor
  • Not completed: Add “do not guess” escalation rules
  • Not completed: Start with after-hours and overflow only
  • Not completed: Run weekly QA and keep a change log

CTA

If you want, we can share a privacy-first rollout checklist and run a short workshop to define your disclosures, boundaries, escalation rules, and retention settings before you pilot.

FAQ

Do we have to disclose AI?

There is no single one-line rule that fits every scenario. From a trust and risk perspective, clear disclosure is the safer approach. If you are collecting personal information, you generally need to take reasonable steps to ensure people understand what is being collected and why. (OAIC)

Check the rules that apply to the call. For a routine setup, explain the purpose and ask before recording. If the caller declines, use the alternative you have tested. See the NSW and Queensland provisions above for examples of how the rules differ.

Can we delete transcripts?

Often, yes, but it depends on your systems and any record-keeping obligations you have. Under APP 11, organisations covered by the Privacy Act should take reasonable steps to destroy or de-identify personal information when it is no longer needed. (OAIC)

What about clinics and patient privacy?

Clinics and health service providers are covered by the Privacy Act even if they are small businesses. Treat health-related call content as sensitive and collect only what you need for booking and follow-up. (OAIC)

Do we have to record calls to run an AI phone agent?

No. You can run without recording, or keep only minimal metadata and outcomes. Recording can help QA, but it increases privacy and security obligations.

What should we ask a vendor before we start?

Ask about encryption, access control, audit logs, retention, deletion, backups, and incident response. If they cannot answer clearly, do not proceed.

What is the simplest safe way to pilot?

Start with after-hours and peak overflow, handle only FAQs and logistics, collect minimal details, and escalate anything uncertain. Then review calls weekly and tighten.