lyre.au/Documentation
Dashboard

Australian Compliance

LYRE is built for Australian regulatory compliance from the ground up. This guide covers the legal requirements for AI voice agents operating in Australia and how LYRE enforces them.

Disclaimer: This guide is informational and does not constitute legal advice. Consult a qualified Australian telecommunications lawyer for your specific use case.

AI disclosure requirement

Under the ACMA Telemarketing and Research Industry Standard 2017 and emerging AI-specific guidance, automated calls must disclose their nature at the start of the conversation. LYRE enforces this by default.

Default behaviour: The agent plays an AI disclosure message before the first message. This is enabled by default and cannot be disabled for outbound calls.
Custom message: You can customise the disclosure text via compliance.ai_disclosure_message.
Inbound calls: AI disclosure is strongly recommended but can be configured to appear as part of the first_message for a more natural flow.

Default disclosure message

"Just so you know, I'm an AI assistant. This call may be recorded
for quality and training purposes. Is that okay with you?"

Custom disclosure in agent config

"compliance": {
  "ai_disclosure": true,
  "ai_disclosure_message": "Hi there! I'm Ava, an AI assistant from Acme Solar. This call is recorded. How can I help?"
}

Recording consent

Australian recording consent laws vary by state and territory. LYRE defaults to the strictest standard — all-party consent— which is legally safe nationwide.

JurisdictionConsent requiredLegislation
NSWSingle partySurveillance Devices Act 2007 (NSW)
VICAll partySurveillance Devices Act 1999 (Vic)
QLDSingle partyInvasion of Privacy Act 1971 (Qld)
WAAll partySurveillance Devices Act 1998 (WA)
SASingle partySurveillance Devices Act 2016 (SA)
TASAll partyListening Devices Act 1991 (Tas)
ACTSingle partyListening Devices Act 1992 (ACT)
NTAll partySurveillance Devices Act 2007 (NT)
Recommendation: Always use all_party consent. Since you typically cannot know which state the caller is in, all-party consent satisfies the strictest requirements (VIC, WA, TAS, NT) and is safe everywhere.

LYRE's recording consent modes:

ModeBehaviour
all_partyAgent asks for explicit verbal consent before recording starts. If denied, call continues without recording.
single_partyAgent announces the call is being recorded. No explicit consent required.
noneNo recording. Audio is processed in real-time only and not stored.

Do Not Call Register (DNCR)

The DNCR is administered by ACMA. Businesses making unsolicited telemarketing calls must wash their call lists against the register. LYRE automates this.

Automatic washing: When dncr_check: true, LYRE checks every outbound phone number against the DNCR before dialling.
Blocking: If a number is on the register, the call is blocked and the status is set to failed with reason dncr_match.
Wash frequency: LYRE maintains a cached copy of the DNCR updated every 30 days, as required by ACMA.
Exemptions:DNCR checks are not required for inbound calls, existing business relationships (within the statutory period), or calls from registered charities. Configure exemptions in your agent's compliance settings.

Calling hours

ACMA restricts the times at which telemarketing calls can be made. LYRE enforces these by default for all outbound calls.

DayPermitted hoursTimezone
Monday to Friday9:00 AM – 8:00 PMRecipient's local time
Saturday9:00 AM – 5:00 PMRecipient's local time
SundayNo calls permitted
Public holidaysNo calls permitted

LYRE determines the recipient's timezone from the area code for Australian landlines or from the registered location for mobile numbers. When uncertain, LYRE defaults to Australia/Sydney (AEST/AEDT).

Custom calling hours in agent config

"compliance": {
  "calling_hours": {
    "timezone": "Australia/Sydney",
    "weekday_start": "09:00",
    "weekday_end": "20:00",
    "saturday_start": "09:00",
    "saturday_end": "17:00",
    "sunday": false
  }
}

Privacy Act and APPs

The Privacy Act 1988 (Cth) and the Australian Privacy Principles (APPs) govern how personal information is collected, used, stored, and disclosed. Key requirements for AI voice agents:

APP 1 — Open and transparent management

Your privacy policy must describe how AI voice agents collect and use personal information, including recordings and transcripts.

APP 3 — Collection of solicited information

Only collect personal information that is reasonably necessary for the agent's function. Do not prompt for unnecessary personal details.

APP 5 — Notification of collection

At or before collection, inform the individual of what is being collected, why, and who it may be disclosed to. The AI disclosure and recording consent prompts help satisfy this.

APP 8 — Cross-border disclosure

If audio or transcripts are processed outside Australia (e.g. via US-based STT providers), you must ensure the overseas recipient handles information in accordance with APPs, or obtain consent. Use sovereign providers to avoid cross-border disclosure entirely.

APP 11 — Security of personal information

LYRE encrypts all recordings and transcripts at rest (AES-256) and in transit (TLS 1.3). Data is stored in Australian data centres. Retention policies are configurable per-tenant.

Penalties

Non-compliance with Australian telemarketing and privacy laws carries significant penalties.

ViolationRegulatorMaximum penalty
Calling DNCR-listed numberACMA$313,000 per call (body corporate)
Calling outside permitted hoursACMA$313,000 per call (body corporate)
Failure to identify callerACMA$313,000 per call (body corporate)
Illegal recording (all-party states)State policeUp to 5 years imprisonment
Serious Privacy Act breachOAIC$50 million, or 3x benefit, or 30% turnover
Notifiable data breach (failure to notify)OAIC$50 million (body corporate)

LYRE compliance defaults

Every new LYRE agent is created with these compliance defaults. They represent the safest configuration for Australian operations.

Default compliance configuration

{
  "compliance": {
    "ai_disclosure": true,
    "ai_disclosure_message": "Just so you know, I'm an AI assistant. This call may be recorded. Is that okay?",
    "recording_consent": "all_party",
    "dncr_check": true,
    "calling_hours": {
      "timezone": "Australia/Sydney",
      "weekday_start": "09:00",
      "weekday_end": "20:00",
      "saturday_start": "09:00",
      "saturday_end": "17:00",
      "sunday": false
    }
  }
}

Compliance checklist

Before going live with outbound AI voice calls in Australia:

1AI disclosure is enabled and plays at the start of every call
2Recording consent mode is set to all_party (safest across all states)
3DNCR checking is enabled for all outbound telemarketing calls
4Calling hours comply with ACMA rules (Mon-Fri 9am-8pm, Sat 9am-5pm, no Sunday)
5Privacy policy updated to describe AI agent data collection and processing
6Data residency requirements met (consider sovereign providers for APP 8)
7Retention policies configured (delete recordings when no longer needed)
8Agent system prompt does not solicit unnecessary personal information
9Webhook configured to log compliance events for audit trail
10Legal review completed for your specific use case and industry