The Privacy and Other Legislation Amendment Act 2024 changed how Australian privacy failures are punished, litigated and investigated, and the last of its first-tranche changes lands on 10 December 2026. The Act (No. 128, 2024) received Royal Assent on 10 December 2024. It added a tiered civil penalty regime, infringement notices, an explicit "technical and organisational measures" element in APP 11, a statutory tort for serious invasions of privacy, doxxing offences, data breach declarations, Commissioner-led public inquiries and a transparency duty for automated decisions. This guide explains what changed, when each part commences, what it means for security and breach planning teams, and why automated decisions matter for organisations running AI agents. It builds on the Australian Privacy and Cyber Rules Guide, which covers the wider Privacy Act and the Notifiable Data Breaches scheme, and does not repeat it.
Status checked 27 October 2026 against the Federal Register of Legislation (Act No. 128, 2024 as made, and the Privacy Act 1988 compilation dated June 2026). Further "tranche 2" reforms flowing from the Privacy Act Review had not been located in enacted form on the official sources checked. This page is not legal advice.
Key takeaways
- Penalties now come in three tiers. Section 13G covers serious interferences, a new section 13H covers any interference with privacy (2,000 penalty units for individuals, with a higher maximum for bodies corporate), and section 13K covers specified APP and notification breaches, with infringement notices of 200 penalty units per contravention for listed corporations.
- APP 11 now names technical and organisational measures. New APP 11.3 states that reasonable security steps include technical and organisational measures, which links security control evidence directly to privacy compliance.
- Automated decision transparency starts 10 December 2026. Privacy policies must describe the personal information used and the kinds of decisions made solely or partly by computer programs where the decision could significantly affect an individual.
- Individuals can now sue. Schedule 2 creates a statutory tort for serious invasions of privacy, covering intrusion upon seclusion and misuse of information, with exemptions for journalists, intelligence and law enforcement bodies and people under 18.
- Breach response has new government levers. The Minister can make eligible data breach declarations that permit specified sharing of breached data for up to 12 months, and the Commissioner can run public inquiries on direction.
Scope: who and what is covered
The amendments sit inside the Privacy Act 1988, so they apply to the same "APP entities" as before: Australian Government agencies and private sector organisations, with the Attorney-General's Department stating that the APPs apply to organisations with annual turnover of $3 million or more. The small business exemption was not removed by the 2024 Act. The statutory tort in Schedule 2 is different: it is a cause of action between individuals and whoever invades their privacy, and it is not limited to APP entities.
| Part of the 2024 Act | What it covers | Who it affects |
|---|---|---|
| Schedule 1, Part 2: APP codes | Minister can direct the Commissioner to develop an APP code (s 26GA) and the Commissioner can make temporary codes of up to 12 months (s 26GB) | Entities or classes named in the code |
| Schedule 1, Part 3: Emergency declarations | Changes to the emergency declaration regime for sharing personal information | Agencies and organisations in an emergency |
| Schedule 1, Part 4: Children's privacy | Commissioner must develop and register a Children's Online Privacy Code within 24 months of Royal Assent | Online services likely to be accessed by children (as the code defines) |
| Schedule 1, Part 6: Overseas data flows | Regulations may prescribe countries or binding schemes whose laws are substantially similar to the APPs, for APP 8.3 | Entities disclosing personal information overseas |
| Schedule 1, Part 7: Eligible data breaches | Ministerial eligible data breach declarations (ss 26X to 26XC) | Breached entities and the recipients named in a declaration |
| Schedule 1, Part 8: Penalties | Serious interference test and factors (s 13G), new mid-tier (s 13H), low-tier and infringement notices (s 13K, s 80UB) | All APP entities |
| Schedule 1, Parts 10 and 11 | Commissioner public inquiries; wider determination remedies under s 52 | Sectors or practices under inquiry; entities subject to determinations |
| Schedule 1, Part 15: Automated decisions | New APP 1.7 to 1.9 privacy policy content | APP entities using computer programs in significant decisions |
| Schedule 2 | Statutory tort for serious invasions of privacy | Anyone, subject to exemptions |
| Schedule 3 | Doxxing offences in the Criminal Code | Individuals who release personal data menacingly or harassingly |
Key obligations
Security of personal information (APP 11.3)
APP 11.1 and 11.2 already required reasonable steps to secure personal information and to deal with information no longer needed. The new APP 11.3 states that, for those subclauses, "such steps include technical and organisational measures". In practice this means the regulator and a court can examine both controls (encryption, access control, logging, credential management) and governance (policies, training, ownership, supplier oversight). A security programme that cannot show both will struggle to argue that its steps were reasonable.
Automated decisions (APP 1.7 to 1.9)
- Trigger: a computer program makes, or substantially contributes to, a decision that could reasonably be expected to significantly affect the rights or interests of an individual, and personal information about the individual is used in the operation of the program.
- Policy content: the APP privacy policy must describe the kinds of personal information used in the program and the kinds of decisions made solely by the program and those where it contributes substantially.
- Scope of "decision": APP 1.9 confirms that refusing or failing to make a decision counts, and that the effect may be adverse or beneficial.
Penalty-exposed conduct
- Serious interference (s 13G): now requires an interference with privacy that is serious. New s 13G(1B) lists factors a court may consider: the kind and sensitivity of the information, the consequences for the individual, the number of individuals affected, whether an individual is a child or experiencing vulnerability, whether conduct was repeated or continuous, and failure to implement adequate privacy practices, procedures and systems.
- Any interference (s 13H): a civil penalty of up to 2,000 penalty units for an individual (law firm summaries put the body corporate maximum at 10,000 penalty units; check the compiled Act) for an interference with privacy that is not shown to be serious; under s 13J a court that finds an interference but not a serious one can make a s 13H order instead.
- Administrative breaches (s 13K): civil penalties for specified APP contraventions and non-compliant eligible data breach statements, with infringement notices under s 80UB. The OAIC states that a single contravention by a listed corporation attracts an infringement notice of 200 penalty units; check the compiled Act for the court-imposed maximums.
Eligible data breach declarations
Under new s 26X the Minister may make a written declaration after an eligible data breach where it is necessary or appropriate to prevent or reduce a risk of harm from misuse of the information. The declaration specifies the kinds of information, the entities that may handle it, the recipients and the permitted purposes, and cannot name media organisations. It ends at the earliest of a specified time, repeal or 12 months (s 26XA). Onward disclosure of information received under a declaration is an offence unless an exception applies, (s 26XC); check the compiled Act on the Federal Register of Legislation for the penalty. For breach planners this means banks, identity document issuers and government bodies may lawfully receive breached data to protect customers, and your incident plan should anticipate requests that rely on a declaration.
Timeline and current status
| Date | Event | Source provision |
|---|---|---|
| 13 December 2022 | Earlier amendments increased maximum penalties and OAIC enforcement powers | Attorney-General's Department privacy page |
| 16 February 2023 | Privacy Act Review Report publicly released | Attorney-General's Department privacy page |
| 10 December 2024 | Royal Assent to Act No. 128, 2024 | Section 2 commencement table |
| 11 December 2024 | Schedule 1 Parts 1 to 7 and 9 to 14, items 48 to 58 (penalties), Schedule 3 doxxing offences commence | Section 2 commencement table |
| No later than 10 June 2025 | Schedule 2 statutory tort: commences on Proclamation, or the day after six months from Royal Assent if not proclaimed | Section 2 commencement table |
| By 10 December 2026 | Children's Online Privacy Code to be developed and registered (24 months from Royal Assent) | Schedule 1, Part 4 |
| 10 December 2026 | Schedule 1 Part 15 automated decision transparency (APP 1.7 to 1.9) commences | Section 2 commencement table |
| Not enacted at time of checking | "Tranche 2" reforms from the Privacy Act Review (for example changes to exemptions and broader fairness obligations) | Treat as proposals until a Bill is introduced |
Tranche 2 is the label commonly used for the Review Report proposals not included in the 2024 Act. Because their content and timing depend on future legislation, do not build controls around specific tranche 2 wording. Build around the direction of travel: more accountability for how data is used, stronger security evidence and fewer gaps between Australian and GDPR-style obligations. The Global Privacy Regulatory Map tracks how Australia compares with other regimes.
Enforcement and penalties
| Tier | Provision | Maximum or mechanism | Typical security scenario |
|---|---|---|---|
| Serious interference | s 13G (as amended) | Highest tier; the maximum is the greatest of the amounts set out in s 13G(3) | Large breach of sensitive data after known control gaps were left unaddressed |
| Interference | s 13H | 2,000 penalty units for individuals; higher for bodies corporate (check the compiled Act) | Breach caused by inadequate APP 11 steps where seriousness is not proven |
| Administrative | s 13K | Infringement notices of 200 penalty units per contravention for listed corporations (s 80UB), per the OAIC; court maximums in the compiled Act | Non-compliant privacy policy, defective breach statement |
| Compliance notice | s 80UC(4) | Infringement notice of 200 penalty units for listed corporations, per the OAIC | Ignoring a Commissioner notice to fix a privacy policy |
| Determination | s 52 (as amended) | Can now require steps to prevent or reduce reasonably foreseeable loss or damage | Ordering credit monitoring or document replacement after a breach |
| Onward disclosure offence | s 26XC | Criminal offence; check the compiled Act for the penalty | Misuse of data received under a breach declaration |
| Statutory tort | Schedule 2 | Remedies including damages, subject to defences, exemptions and time limits | Individual claim for misuse of leaked records |
The value of a penalty unit is set under the Crimes Act 1914 and indexed, so convert units to dollars on the date that matters rather than relying on a figure in an old memo. The serious interference factors in s 13G(1B) are the most useful planning tool: every one of them (sensitivity, number affected, vulnerable individuals, repetition, missing systems) is something a security team can reduce in advance.
What it means for AI agents and non-human identities
Two changes reach directly into machine-driven processing.
- Automated decisions: an AI agent that approves refunds, flags accounts for closure, scores credit or triages claims using personal information is a computer program that may make or substantially contribute to significant decisions. From 10 December 2026 the privacy policy must describe the information used and the kinds of decisions. You cannot write that description without an inventory of which agents and workflows make which decisions, with which data. See the AI and Privacy Guide.
- APP 11 and machine credentials: service accounts, API keys and agent tokens with broad read access to customer data are the access path in many large breaches. Under APP 11.3 the technical measures (vaulting, rotation, least privilege, logging) and organisational measures (named owners, reviews, offboarding) for those identities are part of what "reasonable steps" will be judged against. See the Non-Human Identity (NHI) Guide.
- Seriousness factors: a single over-privileged integration that exposes every customer record raises the "number of individuals" and "inadequate systems" factors at once. Scoping agent and integration access to the minimum dataset lowers both.
- Evidence: logs that show which non-human identity accessed which records are what lets you scope an eligible data breach quickly and limit the affected population. See Audit Readiness for AI Agents and NHIs.
Compliance steps
- Map the commencement dates to owners. Assign the APP 11.3, penalty, tort, declaration and automated decision changes to named owners in legal, security and product, with 10 December 2026 as the hard date for APP 1.7 to 1.9.
- Inventory automated decisions. List every program, model and AI agent that makes or substantially contributes to decisions about individuals. For each, record the decision type, the personal information used and whether a human reviews the output.
- Draft the privacy policy text. Write the APP 1.8 descriptions by decision type, test them with the product owners for accuracy, and set a change control so new agents cannot go live without a policy check.
- Re-baseline APP 11 evidence. Pair each technical control with its organisational counterpart (for example, a secrets vault with an NHI ownership and rotation standard) and keep evidence that both operate.
- Reduce seriousness exposure. Use the s 13G(1B) factors as a risk lens: remove unneeded sensitive data, segment access to children's and vulnerable customers' records, and fix repeat findings first.
- Update the breach plan. Add handling for breach declarations (who verifies a recipient's request, what is shared, how disclosures are logged), the possibility of tort claims, and determinations that require harm-reduction steps. Test it in a tabletop exercise.
- Track the Children's Online Privacy Code and tranche 2. Assign someone to monitor the OAIC code consultation and any new Bill, and review this plan when either is published.
Common failure patterns
- Treating APP 11.3 as wording only: strong tools with no ownership, review or training evidence leave the organisational half of the test unmet.
- Missing the agent estate in the decision inventory: teams list the credit model and forget the support agent that can close accounts or the workflow bot that denies claims.
- Retaining data "just in case": over-retention raises the number of affected individuals and the sensitivity factor in any later s 13G assessment.
- Over-privileged integrations: a single service account with read access across the customer database turns a small compromise into a population-wide breach.
- Planning only for the OAIC: breach plans that ignore declarations, tort exposure and determinations under s 52 underestimate the follow-on work.
Practitioner checklist
- Record the commencement date of each part of Act No. 128, 2024 in your compliance register.
- Build and maintain an inventory of automated decision systems, including AI agents.
- Publish APP 1.7 to 1.9 privacy policy content before 10 December 2026.
- Map APP 11 controls to both technical and organisational evidence.
- Assign owners, rotation and least privilege to every non-human identity that can reach personal information.
- Score data stores against the s 13G(1B) seriousness factors and reduce the worst first.
- Add breach declaration and determination handling to the incident response plan.
- Monitor the Children's Online Privacy Code and any tranche 2 Bill.
Standards and references
- Federal Register of Legislation: Privacy and Other Legislation Amendment Act 2024
- Federal Register of Legislation: Privacy Act 1988 (latest compilation)
- Attorney-General's Department: Privacy
- NIST: SP 800-53 Rev. 5
- NIST: Cybersecurity Framework 2.0
- OWASP: Top 10 for LLM Applications 2025
Related NHI Mgmt Group resources: Australian Privacy and Cyber Rules Guide · Australia Cyber Security Act 2024 Guide · Breach Notification Laws by Country Guide · Global Privacy Regulatory Map. This guide summarises the Privacy and Other Legislation Amendment Act 2024 and is not legal advice.