All insights
Privacy

Does Your Privacy Policy Need an Automated Decision-Making Update?

4 Oct 2026 · 6 min read

A computer may already influence decisions in your business without anyone calling the process artificial intelligence. A booking platform may rank requests, software may flag an application for review, or a system may recommend whether a customer qualifies for a service. From 10 December 2026, some Australian organisations must include specified information about certain computer-assisted decisions in their privacy policies.

This does not mean every small business needs a new AI paragraph. The obligation has defined conditions, and the first question is whether the business is covered by the Privacy Act and Australian Privacy Principles.

What you should take away

Do not start by rewriting your privacy policy. First list the decisions your software makes or materially informs, identify the personal information used, and check whether any decision could significantly affect a person's rights or interests. If all relevant conditions may apply, use the OAIC's flowchart and obtain appropriate privacy advice before publishing changes.

Start by checking whether the Privacy Act covers you

Most businesses with annual turnover of more than $3 million are covered by the Privacy Act. Some smaller businesses are also covered regardless of turnover, including certain health service providers, businesses that trade in personal information, Commonwealth contractors, residential tenancy database operators, credit reporting bodies, and reporting entities under anti-money-laundering legislation.

That list is not a complete legal test. Use the OAIC's small-business privacy checklist or seek appropriate advice if your position is unclear. Coverage can change as a business's activities or turnover change.

The obligation is about decisions, not AI labels

The new transparency requirement can apply when an APP entity has arranged for a computer program to make a decision, or do something substantially and directly related to making one. A human being involved at the end does not automatically place the process outside the requirement. The OAIC says relevant factors include where the program sits in the process, the information it uses, and how much its output influences the human decision-maker.

The decision must also be reasonably expected to significantly affect an individual's rights or interests, and the program must use personal information about that individual. Routine drafting raises different questions from software influencing access, eligibility, pricing, employment, credit, insurance, housing, health, or another important outcome.

Run this five-question workflow check

Create one row for every system that ranks, recommends, approves, rejects, routes, scores, flags, or personalises an outcome. Then answer:

  • Decision: what decision is made or informed?
  • Program: what software produces the output, recommendation, score, or action?
  • Personal information: what information about an identifiable person does it use?
  • Impact: could the outcome significantly affect that person's rights or interests?
  • Human role: who reviews the output, and how much do they rely on it?

Record the system owner and vendor too. This inventory will not decide the law, but it stops important automated steps remaining invisible during a privacy review.

What an affected privacy policy needs to explain

Where the conditions apply, the OAIC says the policy must describe the kinds of personal information used and the kinds of relevant decisions made by, or substantially and directly assisted by, computer programs. Information may be grouped into meaningful categories, but it still needs to be clear enough for a reasonable person to understand.

Describe what your business does in plain terms, not vendor marketing language. Keep internal records covering the system, purpose, information used, human review, owner, and review date. Collection notices may need separate attention; changing a website policy alone does not resolve every privacy obligation.

Use a cautious review path

Assign one person to own the inventory. Check the OAIC flowchart against each potentially significant workflow. Ask vendors what information their recommendations or scores use, then verify the answer against your configuration. Have an appropriate privacy professional review uncertain or high-impact cases before 10 December.

Review new systems before launch too. A current policy can fall behind when someone connects a new chatbot, scoring service, recruitment tool, or customer platform to personal information.

Takeaway

The practical job is not adding the words "artificial intelligence" to a privacy policy. It is knowing which programs influence meaningful decisions about people, what personal information they use, and whether your organisation is covered. Build that inventory first. It gives an adviser something concrete to assess and gives customers a clearer explanation if an update is required.

Source note: This article is based on public guidance from the Office of the Australian Information Commissioner published on 30 September 2026. It provides general information for Australian small businesses and is not legal advice or a complete assessment of Privacy Act obligations. AI-assisted research and drafting were reviewed, edited, and adapted by Maud Digital.

General information to help you decide, based on public sources at the date shown. For legal, tax or compliance questions about your business, speak with a qualified adviser.

let's talk

Want technology decisions like these made for you?

book a discovery call