Skip to main content

    AI risk and compliance

    Who should review an ADM privacy policy in Australia

    Reviewing an automated decision-making (ADM) privacy policy in Australia takes 3 people. Operations confirms that the workflows are real. Privacy counsel confirms that the wording meets Australian Privacy Principle (APP) 1.7. The executive owner confirms that the organisation will publish that wording. An operational review can prepare the first part, and it cannot replace the second.

    In short

    Three reviewers: privacy counsel, operations and an executive

    • Privacy counsel should sign off the APP 1.7 wording, and operations should sign off the workflow list that the wording describes.
    • A vendor cannot make your privacy policy compliant by reviewing it, because the customer reads your policy.
    • An operational review can map decisions, test likely gaps and draft material that helps counsel write the disclosure.
    • The executive who owns publication is the third reviewer. Without one, approved text can sit unpublished.

    Detail

    No single adviser can do the whole review

    People searching for who can review an APP 1.7 privacy policy usually want a single professional. No single adviser can do the whole job alone.

    Start with the facts. Someone who runs hiring, claims, credit, fraud, rostering or customer operations has to confirm which computer programs influence outcomes about people. That person also confirms which kinds of personal information those programs use. If they are not part of the review, counsel is drafting without the facts.

    Then come the privacy lawyers. They may be internal counsel, a panel firm or a specialist privacy practice. The title matters less than whether they will take responsibility for the APP 1.7 analysis and the final sentences in the policy. Ask them to work from the workflow map in place of a generic AI addendum. Ask them to state in writing what they have not verified.

    An operational adviser sits between those 2 roles. A Rapid Review is one example. The job is to find the workflows, test whether the current policy mentions the relevant kinds of decisions and give counsel a usable map. That work maps decisions and analyses governance. It does not determine whether you are covered, and it does not replace counsel's approval of the public wording.

    Some parties should not be the only reviewer. They include the vendor whose software runs the workflow and the agency that rewrote the website. They also include an AI steering committee that has never opened the privacy policy. Each can contribute facts. None of them is the APP entity whose policy the customer reads.

    Commercial impact

    Readers compare the policy with what happened to them

    A privacy policy is a public statement about how the organisation handles personal information. From 10 December 2026, APP 1.7 and APP 1.8 set privacy policy disclosure rules for some automated decisions. Our article on what APP 1.7 requires sets out the test in full.

    With the wrong reviewers, you get fluent text about AI in general that misses the collections scorer. Or you get a legal opinion with no inventory behind it.

    Regulators and affected people will not read your internal responsibility chart. They will read the policy and compare it with what happened to them. The review structure exists so that the comparison holds no surprises.

    Timing matters as well. Counsel booked in November cannot invent a workflow map, and operations briefed in November cannot get a careful legal review. Name the reviewers while there are still weeks left.

    In practice

    Illustrative cases of right and wrong reviewer choices

    Illustrative composite: one company sent its privacy policy to its marketing agency, because the agency managed the website. The agency added a paragraph about using AI to improve services. None of the live decision kinds were in it. The website owner was the wrong reviewer for APP 1.7.

    Illustrative composite: another company asked its HR technology vendor to certify that the hiring tool was compliant. The vendor sent a white paper. The organisation's own policy still said nothing about automated ranking of candidates, and the candidate reads the organisation's policy.

    Illustrative composite: a general counsel asked for an operational map before working on the draft, which is the right order. An operational review produced the workflow list and the likely gaps. Counsel then wrote and approved the disclosure sentences, so 2 signatures covered 2 different jobs.

    Illustrative composite: in one organisation no executive would own publication, so the approved text sat in a legal folder.

    What to do

    Steps to split the policy review and name reviewers early

    • Split the review: operations signs off the map, privacy counsel signs off the wording and an executive signs off publication.
    • Do not treat the vendor or the website agency as the APP 1.7 reviewer.
    • Use an operational Rapid Review to prepare the map and supporting drafts, then hand them to the legal team.
    • Name the reviewers while there is still time before 10 December 2026.
    • Give counsel the workflow list before they review the policy.

    Last reviewed

    Map the decisions before 10 December 2026.