Skip to content
Compliance updates, all guides

Automated decision-making privacy policy rules explained

From 10 December 2026, your privacy policy must explain any automated decision-making that affects people. Here is what to include.

Notebook checklist of five steps to update a privacy policy for automated decisions before 10 December 2026.

If your business uses software to make decisions about people, or to help make them, your privacy policy has a new job. On 30 September 2026 the Office of the Australian Information Commissioner (OAIC) published resources to help businesses get ready for the new automated decision-making rules for privacy policies, which start on 10 December 2026.

In short: if the Privacy Act 1988 (Cth) covers your business, and you use a computer program to make, or substantially help make, decisions that could significantly affect someone's rights or interests using their personal information, your privacy policy must say so from 10 December 2026.

What is changing on 10 December 2026?

The change comes from the Privacy and Other Legislation Amendment Act 2024. It adds new requirements to APP 1, the Australian Privacy Principle about managing personal information openly and transparently. APP 1 is also where the existing list of what a privacy policy has to include lives.

The new parts are APP 1.7 and APP 1.8. APP 1.7 sets out when the rule applies to you. APP 1.8 sets out what you then have to add to your policy.

This is a transparency rule. It does not ban automated decisions or tell you how to run your software. It requires you to be upfront about it in your privacy policy. For other changes in the pipeline, see our Privacy Act reform tracker.

When do the automated decision-making rules apply to you?

All three of these have to be true:

  • A computer program is involved in the decision. You have arranged for a program to make the decision, or to do something substantially and directly related to making it.

  • The decision matters. It could reasonably be expected to significantly affect a person's rights or interests.

  • Personal information is used. The program uses personal information about that person to make the decision, or to do the related thing.

Two things worth noticing in the wording. First, the law says "computer program", not "AI", so don't assume it only catches the newest tools. Second, it says you have "arranged for" a program to do this, so a tool you subscribe to may count just as much as one you built yourself.

If only one or two of the conditions apply, the new requirements are not triggered. Whether a particular decision is "significant" is the part most likely to depend on your circumstances.

What does your privacy policy need to say?

If all three conditions are met, APP 1.8 says your policy must describe:

  • The kinds of personal information used in the operation of those programs.

  • The kinds of decisions made solely by the program, with no person making the call.

  • The kinds of decisions where the program does something substantially and directly related to making the decision, such as scoring, sorting or recommending, with a person involved as well.

Notice the word "kinds" throughout. The law asks you to describe types of information and types of decisions, so plain language categories will usually do a better job for your customers than technical detail.

What the OAIC requires you to disclose

The OAIC has updated its APP 1 Guidelines and published three resources:

The OAIC says the resources reflect feedback from 90 written submissions made during its consultation, from academia, civil society, government and industry.

How to get your privacy policy ready

1. List the tools that decide things about people

Think beyond anything labelled AI. Include booking, application, screening, approval, pricing and fraud tools, and anything that automatically accepts, declines, ranks or flags a customer, applicant or staff member.

2. Run each one through the OAIC flowchart

Use the APP 1.7-1.9 Transparency Obligation Flowchart to check each tool against the three conditions. Keep a note of your reasoning, including for tools you decide are out of scope.

3. Sort decisions into two groups

For the tools that are in scope, separate the decisions the program makes on its own from the ones where it helps a person decide. Your policy needs to cover both groups.

4. Update your privacy policy

Add a plain English section describing the kinds of personal information used and the kinds of decisions involved. Make sure it matches what you tell people at the point of collection, too. To check what your policy must include overall, see our guide, or start from our Australian privacy policy template.

5. Get it done before 10 December 2026

Then add it to your annual review, and revisit it whenever you add or change a tool that touches customer data. The OAIC is already checking privacy policies against APP 1, so this is not a section to leave for later.

If your privacy policy needs a refresh anyway, Savira's privacy policy tools can help you keep it current as your systems change.

This is general information, not legal advice. Every business handles information a bit differently, so if you're not sure how this applies to yours, it's worth checking with a lawyer or privacy adviser.

FAQ

Common questions

Can't find your answer? Get in touch

What must a privacy policy say about automated decisions?

When do the automated decision-making rules start?

When do the automated decision-making rules start?

10 December 2026.

Does this ban automated decision-making?

No. It is a transparency rule: you must say in your privacy policy that you use it.

What if a human reviews every automated decision?

If the program still substantially shapes the decision, it is likely covered. Describe it in your policy anyway.

Get the foundations in place today

© Savira 2026. All rights reserved.Savira is operated under the registered business name savira.com, ABN 53 273 071 022.PO Box 2045, Hornsby Westfield NSW 1635

Savira provides consent management tools, templates and general information to help you manage privacy compliance. It is not legal advice and does not guarantee compliance. You remain responsible for your own compliance.