Australian businesses covered by the Privacy Act face a new disclosure obligation from 10 December 2026 when computer programmes use personal information in significant decisions about individuals. The Office of the Australian Information Commissioner, or OAIC, says privacy policies must explain the kinds of information used and the kinds of decisions involved.1
The requirement is conditional. The entity must have arranged for the programme to make a decision, or do something substantially and directly related to making it. The outcome must reasonably be expected to significantly affect an individual's rights or interests, and personal information must be used. This is a test of the programme's role in decision-making, rather than a requirement triggered simply by buying software.1
Suppliers need to explain their products
IAB Australia, the digital-advertising trade body, addressed the coming change in a briefing published on 21 October. Its public explanation says the scope extends beyond artificial intelligence to rules-based processes, software, apps and third-party tools. It identifies personalised pricing, recruitment software and some advertising for significant goods or services as relevant examples.2
The industry body says software providers should give clients clear information so they can update their privacy policies. For an overseas vendor selling into Australia, that creates a practical connection between product documentation and the customer's compliance work. Purchasing an external service does not remove the customer's need to understand what the programme does.2
The commencement date belongs to a staged reform
Japanese law firm Nagashima Ohno & Tsunematsu's February review places the obligation within Australia's staged privacy-law amendments. Its table separates the automated-decision requirement from earlier enforcement changes and the civil claim for serious invasions of privacy that commenced in June 2025. The firm describes the coming disclosure duty as requiring:3
所定の情報をプライバシーポリシーに明記して開示
Disclosure of specified information in the privacy policy.3
That account helps distinguish the specific December obligation from the wider reform programme. A business cannot assume that every privacy change has the same commencement date, or that preparing for this disclosure alone addresses every existing privacy responsibility. The Japanese review describes several different legal mechanisms with separate implementation stages.3
Overseas processing remains a separate question
Existing OAIC guidance on cross-border disclosures generally requires reasonable steps to ensure an overseas recipient handles personal information consistently with the applicable privacy principles, subject to exceptions. It says supplying customer information to an overseas service contractor is usually a disclosure. The Australian entity can remain accountable for the recipient's handling of that information.4
The guidance distinguishes limited storage arrangements where the Australian entity retains effective control. This means the location of a server alone does not settle the legal analysis. As the disclosure deadline approaches, the separate issue for cross-border software contracts is who can access the information and what the contracted service is authorised to do with it.4