The Australian Privacy Principles explained for business websites and web applications
For owners, managers and technical leads whose business has met the Privacy Act 1988 in a contract, a customer questionnaire or a complaint.
This guide sets out the thirteen principles from the Act's own text, shows where each one meets a website's forms, analytics, chatbots, customer accounts and portals, and gives you a touchpoint map of what a targeted test can and cannot evidence.
In this guide
Australian Privacy Principles website checklist: a thirteen-principle touchpoint map
One row for each Australian Privacy Principle in Schedule 1 to the Privacy Act 1988, as Compilation No. 104 (compilation date 4 June 2026) prints it, with APP 1.7 to 1.9 noted from the amending Act. Each row reads left to right: the principle as the Schedule names it, what it asks in short form with the Schedule's clause numbers, where a website or web application meets it, what to record or test, the evidence the result can supply, what the result cannot show and who decides, and the limits for that row.
How to use itHide the instructions
Start with row 1, the system list, because later rows rely on it. Rows 1, 5, 8 and 9 read pages, documents and settings and send no test requests. Rows 2, 3, 4, 6, 7, 10, 11, 12 and 13 send requests, submit forms or sign in, and each carries its own limits: run them only on systems your business owns or is authorised in writing to test, on a staging copy where one exists, with test accounts and invented people and never a real customer, and with every message a test triggers going to an inbox or phone number the business controls. A row that shows another person's real information stops at that point, with the request and the response written down. A vendor's platform is tested only as far as its terms allow, so read them and ask the vendor in writing first. A result is evidence about the build, accounts and records tested, never a finding that a principle is met. Whether the business is an APP entity, and whether it meets each principle, is for the business to establish with its adviser.
13 rows
Principle (Schedule 1)
What it asks, in short
1. APP 1: open and transparent management of personal information
- What it asks, in short
- APP 1.2: reasonable steps to implement practices, procedures and systems that will ensure compliance and enable the entity to deal with inquiries and complaints. APP 1.3 and 1.4: a clearly expressed and up-to-date APP privacy policy containing the information APP 1.4 lists, including the kinds of information collected and held, how and why, access and correction, complaints, and likely overseas disclosure. APP 1.5: reasonable steps to make it available free of charge and in an appropriate form. From 10 December 2026, APP 1.7 to 1.9 add privacy policy content about certain decisions that a computer program makes, or does a thing substantially and directly related to making.
- Where a website or app meets it
- The privacy policy page and the link to it from each page template. Every form, sign-up, analytics or advertising tag, chat window, customer account area and portal, because the policy describes what they collect and hold. Any computer program on the site that makes, or helps make, decisions about people.
- What to record or test
- Read-only. Build the system list that later rows draw on: for each system that collects or holds personal information through the site, such as the form tool, mailing platform, analytics, chat, customer database, portal, hosting and backups, record who runs it, what it receives and what its vendor's terms say about security testing. Then read the privacy policy beside that list, mark where it answers each APP 1.4 item, note the date it says it was last updated, and record whether each page template links to it. List any program that makes or helps make decisions about people, for the APP 1.7 question.
- Evidence the result can supply
- A dated system list, and a side-by-side record of what the policy says against what each system on the list receives. Differences between the two are facts an adviser can work from.
- What it cannot show, and who decides
- Whether the policy is clearly expressed and adequate, whether the practices are reasonable steps under APP 1.2, and whether APP 1.7 will capture a program: for the business and its adviser.
- Limits and conduct
- Reads pages, documents and settings only, and sends no test requests. Opens no screen that displays a password, key or secret. A vendor's answer on testing is kept with the list and covers only what it says.
2. APP 2: anonymity and pseudonymity
- What it asks, in short
- APP 2.1: individuals must have the option of not identifying themselves, or of using a pseudonym, when dealing with the entity in relation to a particular matter. APP 2.2: not where the entity is required or authorised by or under an Australian law, or a court/tribunal order, to deal with individuals who have identified themselves, or where dealing with them unidentified or under a pseudonym is impracticable.
- Where a website or app meets it
- General enquiry forms, chat windows, newsletter sign-ups, quote requests, and any form that marks a name field as required.
- What to record or test
- Read-only first: list which fields each form and chat requires before it will send, and for each matter note whether the business has recorded a reason to require identity. Then submit one general enquiry as an invented person, using a pseudonym and leaving every optional field blank, and record whether the form accepts it.
- Evidence the result can supply
- A record of what each collection point demands before it will submit, and what one pseudonymous enquiry produced on the build tested.
- What it cannot show, and who decides
- Whether APP 2.2 applies to a matter, such as a law that requires identification or a dealing where anonymity is impracticable: for the business and its adviser.
- Limits and conduct
- Own site only, using a staging copy where one exists. One submission with invented details and a reply address the business controls, no load. Stop and record if the response shows another person's real information.
3. APP 3: collection of solicited personal information
- What it asks, in short
- APP 3.2: an organisation must not collect personal information, other than sensitive information, unless it is reasonably necessary for one or more of its functions or activities (APP 3.1 sets the agency test). APP 3.3: sensitive information only with consent and the same necessity test, or where APP 3.4 applies. APP 3.5: only by lawful and fair means. APP 3.6: only from the individual, unless an exception in APP 3.6 applies.
- Where a website or app meets it
- Every form field, hidden fields and file uploads included; sign-up and checkout forms; any value stored with a submission that the person did not type, where the site records one; questions a chatbot asks.
- What to record or test
- Read-only first: list every field each form collects as built, hidden ones included, mark any that falls into a category of the section 6(1) definition of sensitive information, and write beside each the function or activity it is collected for. Then submit one form as an invented person and ask the developer for the stored record of that submission, to compare what was stored with what the screen showed.
- Evidence the result can supply
- A field list as built and as stored for one invented submission, showing any stored value that no screen displays, and which fields touch sensitive categories.
- What it cannot show, and who decides
- Whether a field is reasonably necessary, whether consent was given, and whether a collection is lawful and fair: for the business and its adviser.
- Limits and conduct
- Own systems only, using a staging copy where one exists. One submission with invented details and no real health or other sensitive information, confirmations only to an inbox the business controls, no load. Stop and record if a real person's record appears in what the developer returns.
4. APP 4: dealing with unsolicited personal information
- What it asks, in short
- APP 4.1: within a reasonable period after receiving personal information it did not solicit, the entity must determine whether it could have collected it under APP 3. APP 4.3: if the entity determines it could not have collected it, and the information is not in a Commonwealth record, destroy it or ensure it is de-identified as soon as practicable, but only if it is lawful and reasonable to do so. APP 4.4: otherwise APPs 5 to 13 apply as if it had been collected under APP 3.
- Where a website or app meets it
- Free-text message boxes, chat transcripts, file uploads and replies to form notification emails: places where a person can volunteer more than the business asked for.
- What to record or test
- Send one chat message and one form message, each containing an invented marker phrase and no real personal details. Then, read-only, search for the marker to trace where each landed, such as form entries, the notification inbox, connected services, the chat transcript store and any log the vendor's documentation describes, and record who can read each copy and whether staff can find and delete that one item.
- Evidence the result can supply
- A map of where volunteered text goes on the systems tested, and whether a single item can be found and removed from each place, shown with the marker.
- What it cannot show, and who decides
- Whether any information was solicited under the section 6(1) definition, and what the APP 4.1 determination should be: for the business and its adviser.
- Limits and conduct
- Own systems only, using a staging copy where one exists, and a vendor's chat or form platform only within its terms (row 1). Two messages, invented marker only, any confirmation only to an inbox the business controls, no load. Search for the marker only and keep every other entry out of the evidence. Delete only the test items. Stop and record if another person's real message appears.
5. APP 5: notification of the collection of personal information
- What it asks, in short
- APP 5.1: at or before collection or, if that is not practicable, as soon as practicable after, take such steps (if any) as are reasonable in the circumstances to notify the individual of the APP 5.2 matters that are reasonable in the circumstances, or otherwise ensure they are aware. The APP 5.2 matters include identity and contact details, purposes, the main consequences of not collecting, usual disclosures, that the privacy policy contains information about access, correction and complaints, and likely overseas disclosure with the countries where practicable.
- Where a website or app meets it
- The notice or link beside each form, sign-up, checkout, chat start screen and account registration, and any banner that explains analytics or advertising cookies.
- What to record or test
- Read-only. For each collection point on the row 1 list, capture what a person sees at or before submitting: the notice text, any link and where it sits. Mark which APP 5.2 matters it addresses. Submit nothing.
- Evidence the result can supply
- Dated screenshots of each collection point with its notice, and a matter-by-matter record of what each notice says.
- What it cannot show, and who decides
- Which matters are reasonable in the circumstances, and whether the steps taken are reasonable: for the business and its adviser.
- Limits and conduct
- Reads public pages only, submits no form and sends no test requests.
6. APP 6: use or disclosure of personal information
- What it asks, in short
- APP 6.1: personal information held for a primary purpose must not be used or disclosed for a secondary purpose unless the individual consents or APP 6.2 or 6.3 applies. APP 6.2 covers, among other cases, a related secondary purpose the individual would reasonably expect (directly related, for sensitive information) and a use or disclosure required or authorised by or under an Australian law or a court/tribunal order.
- Where a website or app meets it
- Form data sent on to a customer database, mailing platform or automation service; analytics and advertising tags on pages that collect personal information; chat conversations passed to an outside service.
- What to record or test
- Submit one form as an invented person while the developer or tester records the requests the page makes to outside hosts. Record each host and which submitted fields, if any, appear in a request to it, leaving out any key, token or cookie value. Then, read-only, list the integrations the form tool sends submissions to and the stated purpose of each.
- Evidence the result can supply
- A list of outside hosts that received a typed value on the build tested, with the field each received, beside the configured integrations and their stated purposes.
- What it cannot show, and who decides
- What the primary purpose was, and whether a secondary use or disclosure is permitted or reasonably expected: for the business and its adviser.
- Limits and conduct
- Own site only, using a staging copy where one exists. One submission with invented details, confirmations only to an inbox the business controls, no load. Host and field names only in the evidence. Stop and record if a real person's details appear.
7. APP 7: direct marketing
- What it asks, in short
- APP 7.1: an organisation must not use or disclose personal information for direct marketing unless an exception in APPs 7.2 to 7.5 applies. APP 7.2 and 7.3 require, among other things, a simple means by which the individual may easily request not to receive direct marketing communications. APP 7.4: sensitive information may be used or disclosed if the individual has consented. APP 7.7: no charge for such a request, and effect given within a reasonable period. APP 7.8: the principle does not apply to the extent the Spam Act 2003, the Do Not Call Register Act 2006 or the other laws it lists apply.
- Where a website or app meets it
- Newsletter and offer sign-ups, marketing consent boxes on forms and at checkout, unsubscribe links and preference pages.
- What to record or test
- Sign up once with an invented name and an email address the business controls, recording what the sign-up form says and whether any consent box is ticked in advance. Receive one marketing email, use its unsubscribe link or preference page once, then, read-only, look up the test address in the mailing platform and record when it shows as unsubscribed.
- Evidence the result can supply
- A dated record that the opt-out took effect for one test address on the system tested, and how long it took to show.
- What it cannot show, and who decides
- Whether an exception in APPs 7.2 to 7.5 applies, what period is reasonable, and whether the Spam Act 2003 or another law listed in APP 7.8 applies instead: for the business and its adviser.
- Limits and conduct
- Own sign-up form only, using a staging copy where one exists. One test address the business controls, one sign-up and one opt-out, no load, no real subscriber touched. Treat the unsubscribe link as one that may work for whoever holds it: open it only for the test address and keep it out of the evidence. The mailing platform is the vendor's, so act only within its terms (row 1). Remove the test subscriber afterwards. Stop and record if any other subscriber's details or status appear changed.
8. APP 8: cross-border disclosure of personal information
- What it asks, in short
- APP 8.1: before disclosing personal information to an overseas recipient, take such steps as are reasonable in the circumstances to ensure the recipient does not breach the principles (other than APP 1) in relation to it. APP 8.2 lists cases where APP 8.1 does not apply, and in the circumstances section 16C sets out, the recipient's act or practice is taken to be the entity's and a breach by it.
- Where a website or app meets it
- Hosting, form tools, mailing platforms, analytics, chat and AI services, customer databases and support desks that receive personal information from the site, and the overseas statements in the privacy policy (APP 1.4(f) and (g)) and collection notices (APP 5.2(i) and (j)).
- What to record or test
- Read-only. Using row 1 and the host list from row 6, record for each service where its vendor's own documentation or contract says it stores or processes data, then compare that with what the privacy policy and notices say about overseas disclosure.
- Evidence the result can supply
- A list of the services that received data from the site on the build tested, each with the location its vendor states, beside the policy's and notices' overseas statements.
- What it cannot show, and who decides
- Whether a flow is a disclosure, whether an APP 8.2 exception applies, and whether the steps taken are reasonable: for the business and its adviser. The APP 8 guide covers those questions.
- Limits and conduct
- Reads documents, contracts and settings only, and sends no new requests. Leaves unopened any account page that displays a key or secret.
9. APP 9: adoption, use or disclosure of government related identifiers
- What it asks, in short
- APP 9.1: an organisation must not adopt an identifier assigned by an agency, a State or Territory authority or another assigner in the section 6(1) definition as its own identifier of the individual, unless required or authorised by or under an Australian law or a court/tribunal order, or APP 9.3 applies. APP 9.2: it must not use or disclose one unless an exception applies, such as where reasonably necessary to verify the individual's identity for its activities or functions.
- Where a website or app meets it
- Any form or account field that asks for a number or code an agency or a State or Territory authority assigned, and any account number, customer reference or link built from one.
- What to record or test
- Read-only. Ask the developer, in writing, whether any such identifier is collected, stored, used as an account key, or appears in page addresses, exports or emails, and list the fields that hold one.
- Evidence the result can supply
- The developer's written answer and field list. Where an identifier appears in an address or export, the access tests in row 11 cover who can reach it.
- What it cannot show, and who decides
- Whether a value is a government related identifier as section 6(1) defines it, and whether an exception in APP 9.1 or 9.2 applies: for the business and its adviser.
- Limits and conduct
- Read-only. Enter no real identifier anywhere for testing.
10. APP 10: quality of personal information
- What it asks, in short
- APP 10.1: such steps (if any) as are reasonable in the circumstances to ensure personal information collected is accurate, up-to-date and complete. APP 10.2: the same for personal information used or disclosed, having regard to the purpose of the use or disclosure, adding relevant.
- Where a website or app meets it
- Profile screens, form validation, and the copies the site keeps in step with other systems, such as a customer database or mailing list.
- What to record or test
- As an invented customer, change one detail, such as a phone number, in the account area. Then ask the developer to confirm, read-only, whether and when the change reached each connected copy named in row 1.
- Evidence the result can supply
- A record of whether one change made through the site reached each connected copy on the build tested, and when.
- What it cannot show, and who decides
- Which steps are reasonable, and whether the information held is accurate overall: for the business and its adviser.
- Limits and conduct
- Own systems only, using a staging copy where one exists. One invented account and one change, no load, any notification only to an inbox the business controls. Stop and record if a real customer's record changes or appears.
11. APP 11: security of personal information
- What it asks, in short
- APP 11.1: if it holds personal information, take such steps as are reasonable in the circumstances to protect it from misuse, interference and loss, and from unauthorised access, modification or disclosure. APP 11.2: take such steps as are reasonable in the circumstances to destroy it or ensure it is de-identified once it is no longer needed for any purpose for which it may be used or disclosed under the Schedule, where it is not in a Commonwealth record and the entity is not required by or under an Australian law, or a court/tribunal order, to retain it. APP 11.3: such steps include technical and organisational measures.
- Where a website or app meets it
- Sign-in, password reset and sessions; access between customer accounts; administrator and staff roles; file uploads and downloads; form entry lists and exports; logs and backups; each copy's retention setting.
- What to record or test
- With two invented customers, A and B, request A's record, an uploaded file and an export from B's session and from a browser that is not signed in, and record what comes back. Then, read-only, record for each copy on the row 1 list how long it is kept, who can change that, and whether deleting the original removes the copies.
- Evidence the result can supply
- Request and response pairs showing whether the access check held for the accounts and records tried, negative results for the build tested, each finding's retest status after fixes, and a retention list as read.
- What it cannot show, and who decides
- Whether the steps taken are reasonable in the circumstances, organisational measures such as training and procedures, and anything outside the tested scope: for the business and its adviser. The APP 11 guide goes further.
- Limits and conduct
- Own systems only, using a staging copy where one exists. Two invented customers with test records, no more than ten requests per record, no load, any notice only to an inbox the business controls, and session tokens kept out of the evidence. Any file or export link that works for whoever holds it is used only for the invented records and recorded with its token removed. The retention part reads settings only and deletes nothing. Stop and record if a real customer's record appears.
12. APP 12: access to personal information
- What it asks, in short
- APP 12.1: on request by the individual, give access to the personal information held about them, subject for an organisation to the APP 12.3 exceptions. APP 12.4: an organisation responds within a reasonable period and gives access in the manner requested where reasonable and practicable. APP 12.8: any charge must not be excessive and must not apply to the making of the request. APP 12.9: a written notice when access is refused under APP 12.2 or 12.3, or not given in the manner requested, setting out, among other things, the reasons (except to the extent that would be unreasonable) and the mechanisms available to complain.
- Where a website or app meets it
- Download-my-data features, account and portal document lists, privacy contact forms, and the identity check that comes before any personal information is released.
- What to record or test
- As invented customer A, make one access request through the route the site offers and record the identity check, what was returned and where it was sent. Then, from invented customer B's session, submit a request naming A's email address and record whether any of A's information is released to B.
- Evidence the result can supply
- The route, the identity check observed, the contents of A's response compared with the row 1 list, and whether B's attempt was refused on the build tested.
- What it cannot show, and who decides
- Whether an APP 12.3 exception applies to a request, what period is reasonable, and whether a charge is excessive: for the business and its adviser.
- Limits and conduct
- Own systems only, using a staging copy where one exists. Two invented customers, one request by A and no more than three attempts by B, no load, responses only to an inbox the business controls and deleted afterwards. Any download link in a response is opened only for A's invented record and kept out of the evidence. Stop and record if a real customer's information appears.
13. APP 13: correction of personal information
- What it asks, in short
- APP 13.1: take such steps (if any) as are reasonable in the circumstances to correct personal information held when the entity is satisfied, having regard to a purpose for which it is held, that it is inaccurate, out-of-date, incomplete, irrelevant or misleading, or the individual asks. APP 13.2: if the entity corrects personal information it previously disclosed to another APP entity and the individual asks it to notify that entity of the correction, take such steps (if any) as are reasonable in the circumstances to give that notification, unless impracticable or unlawful. APP 13.5: an organisation responds within a reasonable period and charges nothing for the request, the correction or associating a statement.
- Where a website or app meets it
- Profile and settings screens, correction request forms, and portal records a customer can see but not edit.
- What to record or test
- As invented customer A, submit one correction through the site's own route and record how it is acknowledged. Then, from invented customer B's session, send A's update request again with A's record identifier and record whether the server refuses it. Row 10 shows whether a correction reaches connected copies.
- Evidence the result can supply
- Whether a correction route exists and responds, and whether a write to another customer's record was refused, on the build tested.
- What it cannot show, and who decides
- Whether information is inaccurate, what period is reasonable, and whether a refusal notice under APP 13.3 is adequate: for the business and its adviser.
- Limits and conduct
- Own systems only, using a staging copy where one exists. Invented customers and test records only, no more than five requests, no load, any confirmation only to an inbox the business controls. Stop and record if a real customer's record changes or appears.
What the Australian Privacy Principles are, and where their text sits
The Australian Privacy Principles are rules for handling personal information, and they sit inside the Privacy Act 1988 (Cth) itself.
Section 14(1) of the Act says the Australian Privacy Principles are set out in the clauses of Schedule 1, and section 15 says an APP entity must not do an act, or engage in a practice, that breaches an Australian Privacy Principle. This page quotes Compilation No. 104 on the Federal Register of Legislation, which shows the text of the Act as amended and in force on 4 June 2026, its compilation date.
Its own notes say the effect of uncommenced amendments is not shown in the text of the compiled law.
Schedule 1 opens with an overview that groups the principles into Parts. Part 1 sets out principles that require APP entities to consider the privacy of personal information, including ensuring that APP entities manage personal information in an open and transparent way. Part 2 deals with collection, including unsolicited personal information.
Part 3 is about how APP entities deal with personal information and government related identifiers, including their use and disclosure. Part 4 covers integrity, which takes in the quality and security of personal information. Part 5 deals with requests for access to, and correction of, personal information.
The Office of the Australian Information Commissioner (OAIC) publishes APP guidelines which, in its words, outline the mandatory requirements of the APPs, how it will interpret them, and matters it may take into account when exercising its functions and powers under the Act. The OAIC says both the APPs and the guidelines apply to any organisation or agency the Privacy Act covers.
Its history of the Act records that the Privacy Amendment (Enhancing Privacy Protection) Act 2012, which commenced on 12 March 2014, brought in changes that included the APPs, which replaced the Information Privacy Principles and National Privacy Principles.
This guide stays with the part of that law a website or web application touches, and it is neither legal advice nor an audit. Where it quotes the Act or the OAIC, it gives what the text says and whom it names. Whether the Act covers your business, and whether your practices meet a principle, is for your business to establish with its own adviser.
Who the principles cover: APP entities and the small business exemption
The duty in section 15 falls on APP entities, and in section 6(1) the term APP entity means an agency or organisation.
An organisation, under section 6C(1), is an individual, a body corporate, a partnership, any other unincorporated association or a trust, unless it is a small business operator, a registered political party, an agency, a State or Territory authority or a prescribed instrumentality of a State or Territory.
The small business carve-out turns on turnover and on what the business does. Section 6D(1) says a business is a small business at a time in a financial year if its annual turnover for the previous financial year is $3,000,000 or less, and section 6D(2) looks at the current year's turnover instead for a business that was not carried on at any time in the previous financial year.
The method for working out annual turnover is in section 6DA.
Section 6D(3) defines a small business operator as an individual, body corporate, partnership, unincorporated association or trust that carries on one or more small businesses and does not carry on a business that is not a small business.
Section 6D(4) then lists who is not a small business operator even so: one that carries on a business that has had an annual turnover of more than $3,000,000 for a financial year that has ended after the later of when it started to carry on the business and the commencement of the section; one that provides a health service to another individual and holds any health information except in an employee record; one that discloses personal information about another individual to anyone else for a benefit, service or advantage; one that provides a benefit, service or advantage to collect personal information about another individual from anyone else; a contracted service provider for a Commonwealth contract, whether or not a party to the contract; and a credit reporting body.
Subsections 6D(5) to 6D(8) limit paragraphs (b), (c) and (d) of that list in some cases, among them a disclosure made with the other individual's consent or as required or authorised by or under legislation (section 6D(7)).
Section 6D(9) says a body corporate is not a small business operator if it is related to a body corporate that carries on a business that is not a small business.
Sections 6E and 6EA bring some operators back in. Section 6E applies the Act, with any prescribed modifications, to some small business operators as if they were organisations, in some cases only for particular activities or information.
Under section 6EA, a small business operator may choose, in writing given to the Commissioner, to be treated as an organisation, and the Act applies to it that way while the choice is registered.
The OAIC's small business page says most small businesses are not covered by the Privacy Act 1988, but some are, and that annual turnover for the purposes of the Act includes all income from all sources and does not include assets held, capital gains or proceeds of capital sales.
It offers a Privacy Checklist for Small Business, which it says is not a substitute for legal advice, adding that a business may need advice from its lawyer or other advisers.
Coverage is a fact about the business, not about its website, so settle it with your adviser before reading the rest of this page as describing your obligations.
The thirteen principles, read from Schedule 1
The OAIC's quick reference gives each principle a title and a short statement of its purpose.
The summaries below go back to the Schedule instead, keep the conditions each clause carries, and use the Schedule's own clause numbers. Where a principle treats agencies and organisations differently, the organisation's version is given unless the text says otherwise. Each clause speaks to APP entities, so whether any of it applies to your business, and how, is for your business to settle with its adviser.
APP 1 is headed open and transparent management of personal information. APP 1.2 says an APP entity must take such steps as are reasonable in the circumstances to implement practices, procedures and systems relating to its functions or activities that will ensure it complies with the principles and any registered APP code that binds it, and will enable it to deal with inquiries or complaints from individuals about that compliance.
APP 1.3 requires a clearly expressed and up-to-date APP privacy policy about how the entity manages personal information. Without limiting that, APP 1.4 says the policy must contain the kinds of personal information the entity collects and holds; how it collects and holds it; the purposes for which it collects, holds, uses and discloses it; how an individual may access it and seek its correction; how an individual may complain about a breach of the principles, or of a registered APP code that binds the entity, and how the entity will deal with the complaint; whether the entity is likely to disclose personal information to overseas recipients; and, if so, the countries in which they are likely to be located if it is practicable to specify them in the policy.
APP 1.5 says the entity must take such steps as are reasonable in the circumstances to make the policy available free of charge and in such form as is appropriate, and the note to it says an APP entity will usually make its policy available on its website.
Under APP 1.6, if a person or body asks for a copy in a particular form, the entity must take such steps as are reasonable in the circumstances to give them a copy in that form.
APP 2.1 says individuals must have the option of not identifying themselves, or of using a pseudonym, when dealing with an APP entity in relation to a particular matter. Under APP 2.2, that does not apply if, in relation to that matter, the entity is required or authorised by or under an Australian law, or a court/tribunal order, to deal with individuals who have identified themselves, or if it is impracticable for the entity to deal with individuals who have not identified themselves or who have used a pseudonym.
APP 3.2 says an organisation must not collect personal information, other than sensitive information, unless the information is reasonably necessary for one or more of its functions or activities; APP 3.1 gives the agency version, which adds "or directly related to". Under APP 3.3, an APP entity must not collect sensitive information about an individual unless the individual consents and the same necessity test is met, or APP 3.4 applies, which covers cases such as a collection required or authorised by or under an Australian law or a court/tribunal order, or a permitted general situation.
Section 6(1) defines sensitive information to include, among other things, health information, genetic information that is not otherwise health information, and information or an opinion about an individual's racial or ethnic origin, political opinions, religious beliefs or affiliations, sexual orientation or practices or criminal record that is also personal information.
APP 3.5 says personal information must be collected only by lawful and fair means.
APP 3.6 says it must be collected only from the individual, unless it is unreasonable or impracticable to do so or, for an agency, the individual consents or the agency is required or authorised by or under an Australian law, or a court/tribunal order, to collect it from someone else.
APP 4 covers personal information an entity receives without soliciting it, and section 6(1) says an entity solicits personal information if it requests another entity to provide it, or to provide a kind of information in which it is included. Under APP 4.1 the entity must, within a reasonable period after receiving unsolicited personal information, determine whether it could have collected the information under APP 3 had it solicited it.
If the entity determines that it could not have collected it, and the information is not contained in a Commonwealth record, APP 4.3 says the entity must, as soon as practicable but only if it is lawful and reasonable to do so, destroy the information or ensure that it is de-identified.
Otherwise APP 4.4 applies APPs 5 to 13 as if the entity had collected the information under APP 3.
APP 5.1 says that at or before the time an APP entity collects personal information about an individual or, if that is not practicable, as soon as practicable after, it must take such steps (if any) as are reasonable in the circumstances to notify the individual of such of the APP 5.2 matters as are reasonable in the circumstances, or otherwise ensure the individual is aware of them.
The APP 5.2 matters include the entity's identity and contact details; the purposes of the collection; the main consequences (if any) for the individual if all or some of the information is not collected; the entities, bodies or persons, or the types of them, to which the entity usually discloses personal information of that kind; that its APP privacy policy contains information about access, correction and complaints; whether it is likely to disclose the information to overseas recipients; and, if so, the countries in which they are likely to be located if it is practicable to specify them in the notification or to otherwise make the individual aware of them.
APP 6.1 says that if an APP entity holds personal information about an individual that was collected for a particular purpose, the primary purpose, it must not use or disclose the information for another purpose, a secondary purpose, unless the individual has consented or APP 6.2 or 6.3 applies. APP 6.2 covers, among other cases, a secondary purpose the individual would reasonably expect that is related to the primary purpose, or directly related to it if the information is sensitive information, and a use or disclosure required or authorised by or under an Australian law or a court/tribunal order.
APP 7.1 says an organisation that holds personal information about an individual must not use or disclose it for the purpose of direct marketing, and APPs 7.2 to 7.5 set out the exceptions. For personal information other than sensitive information that the organisation collected from the individual, APP 7.2 allows the organisation to use or disclose it for direct marketing if the individual would reasonably expect that, the organisation provides a simple means by which the individual may easily request not to receive direct marketing communications from it, and the individual has not made that request.
APP 7.3 covers other cases with further conditions, among them a prominent statement in each direct marketing communication that the individual may make such a request, or otherwise drawing the individual's attention to it.
APP 7.4 allows an organisation to use or disclose sensitive information for direct marketing if the individual has consented to that use or disclosure.
Under APP 7.7, the organisation must not charge the individual for making, or giving effect to, a request not to receive direct marketing communications, and must give effect to it within a reasonable period after it is made.
APP 7.8 says the principle does not apply to the extent that the Spam Act 2003, the Do Not Call Register Act 2006 or the other laws it lists apply.
APP 8.1 says that before an APP entity discloses personal information about an individual to an overseas recipient, a person who is not in Australia or an external Territory and is not the entity or the individual, it must take such steps as are reasonable in the circumstances to ensure that the recipient does not breach the principles, other than APP 1, in relation to the information.
APP 8.2 lists cases where APP 8.1 does not apply, and in the circumstances section 16C sets out, an act or practice of the overseas recipient is taken to have been done by the APP entity and to be a breach of the principles by it.
APP 9 applies to organisations and government related identifiers, which section 6(1) defines as an identifier of the individual assigned by an agency, a State or Territory authority, an agent of either acting in its capacity as agent, or a contracted service provider for a Commonwealth contract or a State contract acting in that capacity.
APP 9.1 says an organisation must not adopt such an identifier as its own identifier of the individual unless the adoption is required or authorised by or under an Australian law or a court/tribunal order, or APP 9.3 applies.
APP 9.2 says it must not use or disclose one unless an exception applies, such as where the use or disclosure is reasonably necessary for the organisation to verify the identity of the individual for the purposes of its activities or functions.
APP 10.1 says an APP entity must take such steps (if any) as are reasonable in the circumstances to ensure that the personal information it collects is accurate, up-to-date and complete. APP 10.2 says the same of personal information it uses or discloses, having regard to the purpose of the use or disclosure, and adds relevant to the list.
Under APP 11.1, an APP entity that holds personal information must take such steps as are reasonable in the circumstances to protect the information from misuse, interference and loss, and from unauthorised access, modification or disclosure. Where an entity holds personal information about an individual that it no longer needs for any purpose for which the information may be used or disclosed by the entity under the Schedule, the information is not contained in a Commonwealth record, and the entity is not required by or under an Australian law, or a court/tribunal order, to retain it, APP 11.2 says the entity must take such steps as are reasonable in the circumstances to destroy the information or to ensure that it is de-identified.
APP 11.3 says that, for the purposes of APP 11.1 and 11.2 and without limiting them or any other provision of the Act, such steps include technical and organisational measures.
APP 12.1 says that if an APP entity holds personal information about an individual, it must, on request by the individual, give the individual access to it. For an organisation, APP 12.3 lists the cases in which it is not required to give access, to the extent each applies, among them where giving access would have an unreasonable impact on the privacy of other individuals, or the request is frivolous or vexatious.
Under APP 12.4, an organisation must respond within a reasonable period after the request is made, an agency within 30 days, and must give access in the manner requested if it is reasonable and practicable to do so.
APP 12.8 says an organisation's charge for giving access must not be excessive and must not apply to the making of the request, and APP 12.9 requires a written notice when the entity refuses access because of APP 12.2 or 12.3, or refuses to give it in the manner requested, setting out, among other things, the reasons for the refusal, except to the extent that, having regard to the grounds for the refusal, it would be unreasonable to do so, and the mechanisms available to complain about it.
APP 13.1 says that if an APP entity holds personal information about an individual and either is satisfied that, having regard to a purpose for which it is held, the information is inaccurate, out-of-date, incomplete, irrelevant or misleading, or the individual requests correction, it must take such steps (if any) as are reasonable in the circumstances to correct it to ensure that, having regard to the purpose for which it is held, it is accurate, up-to-date, complete, relevant and not misleading.
APP 13.2 deals with notifying another APP entity, to which the information was previously disclosed, of a correction when the individual asks, unless it is impracticable or unlawful to do so.
APP 13.5 says an organisation must respond to a request within a reasonable period, an agency within 30 days, and must not charge for making the request, for correcting the information or for associating a statement with it.
The OAIC describes the same ground from the individual's side. Its rights and responsibilities page says the Privacy Act allows an individual to know why their personal information is being collected, how it will be used and who it will be disclosed to; to have the option of not identifying themselves, or of using a pseudonym, in certain circumstances; to ask for access to their personal information; to stop receiving unwanted direct marketing; to ask for incorrect personal information to be corrected; and to make a complaint about an organisation or agency the Act covers if they think it has mishandled their personal information.
Each of those can start on a website: a collection notice, an enquiry form, an account page, an unsubscribe link, a profile screen or a contact form.
Forms, analytics, chat, accounts and vendors: the website side of the principles
The principles attach to what an APP entity does with personal information, not to a page, so the map follows the information.
Personal information, in section 6(1), means information or an opinion about an identified individual, or an individual who is reasonably identifiable, whether the information or opinion is true or not, and whether it is recorded in a material form or not. It says an entity collects personal information only if it collects it for inclusion in a record or generally available publication, and that an entity holds personal information if it has possession or control of a record that contains it. The map follows that through five kinds of website feature.
A form brings APP 3, APP 5 and APP 11 together on one screen: what it asks for, what it tells the person at or before the time, and where each submission is kept afterwards. The map asks for a field list taken from the form as built, hidden fields included, and for every place one test submission lands, such as the form's own entries, notification emails and connected services.
Fields that ask about health, beliefs or another category in the section 6(1) definition of sensitive information are marked separately, because APP 3.3 sets a different test for them. Rows 1, 3, 4, 5 and 11 hold those steps.
The OAIC's chapter on key concepts says collection applies broadly and includes gathering, acquiring or obtaining personal information from any source and by any means, including information associated with web browsing, such as personal information collected by cookies. A footnote to that passage says analytical information collected from cookies, such as the number of times a page was visited, will not be personal information under the Privacy Act unless an individual is reasonably identifiable.
The same chapter says that where it is unclear whether an individual is reasonably identifiable, an APP entity should err on the side of caution and treat the information as personal information.
Row 6 records which outside services a page sends requests to, and whether any request carries a value a person typed. Cookie attributes themselves belong to the cookie security guide.
A person can volunteer personal information the business did not ask for, such as text typed into a chat window or a message box. Under the section 6(1) definition, an entity solicits personal information if it requests another entity to provide it, or a kind of information that includes it, and APP 4 sets out what follows when it did not, so row 4 records where volunteered text lands, who can read it, and whether one item can be found and removed.
A chatbot that passes conversations to an outside service also belongs in row 8, which lists the outside services that received data on the build tested.
The AI chatbot security guide covers what a bot can be made to reveal, and from 10 December 2026 a bot that makes decisions about people may raise the APP 1.7 question set out further down.
Customer accounts are where a website touches APP 12 and APP 13 directly, and where this map's APP 11 access tests run. A page that shows or exports a person's records is an access route, a profile screen is a correction route, and the map checks whether each refuses everyone else.
The OAIC's chapter on APP 11 notes that while an APP entity should ensure that an individual is authorised to access information, it should not require an individual to supply more information than is necessary to identify themselves when dealing with the entity.
Rows 11 to 13 test that boundary from a second invented customer's session, for reading records and for changing them, and the broken access control and IDOR guide explains the mechanics.
Every outside service a site uses for forms, email, analytics, chat, hosting or customer records is a place personal information can go. APP 1.4(f) and (g) and APP 5.2(i) and (j) deal with saying whether overseas disclosure is likely and, where practicable, the countries, and APP 8 governs the disclosure itself.
Row 8 gathers the facts for that question: which services received data from the site on the build tested, and where each vendor's own documentation says it stores or processes it.
Reasonable steps, and what a security test can evidence
Several principles turn on steps that are reasonable in the circumstances, APP 11.1 among them, and the text of APP 11 names no particular control or test.
The OAIC's chapter on APP 11, as read on 15 November 2026, says the reasonable steps will depend on circumstances that include the nature of the entity, such as its size, resources, the complexity of its operations and its business model; the amount and sensitivity of the personal information held; the possible adverse consequences for an individual in the case of a breach; the practical implications of a security measure, including time and cost; and whether a security measure is in itself privacy invasive.
It adds that an entity is not excused from taking particular steps by reason only that it would be inconvenient, time-consuming or impose some cost to do so, and that whether those factors make a step unreasonable depends on whether the burden is excessive in all the circumstances.
The chapter gives securing access to premises, encrypting data, anti-virus software and strong passwords as examples of technical measures, and staff training among its examples of organisational measures. It does not mention penetration testing. This page does not present a penetration test as something the Privacy Act requires.
A test is one way to gather evidence about whether the technical measures a business chose behave as intended on the system people use, and whether it is a reasonable step for a particular business is that business's decision, made with its adviser.
What a targeted test can supply is narrow and dated. It can show how a control behaved on the build, accounts and records tested: whether one customer's session could open another customer's record, whether a signed-out browser could fetch an uploaded file, whether a form sent a typed value to an outside service, or whether an opt-out took effect for a test address.
A check that found nothing is a negative result for what was tried, not proof that an area is sound. After fixes, a retest records whether each finding was fixed.
What a test cannot show matters as much. It cannot tell you whether your business is an APP entity, whether a field is reasonably necessary, whether a notice covers the matters that are reasonable in your circumstances, whether a use or disclosure is permitted, or whether an exception to a principle applies.
It sees nothing of organisational measures such as training and procedures, nothing outside its scope, and nothing inside a vendor's platform beyond what that vendor's terms allow. It is not legal sign-off, a compliance opinion or a certification.
The 2024 amendments, and APP 1.7 to 1.9 from 10 December 2026
The Privacy and Other Legislation Amendment Act 2024 received the Royal Assent on 10 December 2024.
The OAIC's history page, which it says it is updating to reflect that Act, says its changes commence on various dates set out in section 2 of the Amendment Act, with the majority of the amendments to the Privacy Act that are within the Information Commissioner's remit having commenced on 11 December 2024.
APP 11.3 came from that Act: the OAIC's chapter on APP 11 says APP 11.3 was introduced by the 2024 Act and applies to personal information held from 11 December 2024, regardless of whether the information was acquired or created before or after that date.
Schedule 1, Part 15 of the 2024 Act commences on 10 December 2026 and adds APP 1.7, 1.8 and 1.9 under the heading "Automated decisions". APP 1.7 says that, without limiting APP 1.3, an APP entity's privacy policy must contain the information in APP 1.8 if the entity has arranged for a computer program to make, or do a thing substantially and directly related to making, 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 to make the decision or do that thing.
APP 1.8 covers the kinds of personal information used in the operation of such programs, the kinds of such decisions made solely by their operation, and the kinds of such decisions for which a thing substantially and directly related to making the decision is done by their operation.
The OAIC's chapter on APP 1 says generative AI tools used to generate text, images, videos, code or synthesis, including chatbots and other types of AI, all fall within the definition of computer program for the purpose of that obligation.
Compilation No. 104 does not show these subclauses, since its notes say uncommenced amendments are not shown in its text.
Compilation No. 104 also carries section 13K. Section 13K(1) says an entity contravenes it if it does an act or engages in a practice that breaches any of a list of principles: APP 1.3 (requirement to have an APP privacy policy), APP 1.4 (contents of the policy), APP 2.1, APP 6.5, APP 7.2(c) or 7.3(c) (a simple means to opt out of direct marketing communications), APP 7.3(d), APP 7.7(a) and (b), APP 13.5, and any other principle prescribed by the regulations.
From 10 December 2026, Part 15 of the 2024 Act also inserts APP 1.7 (contents of APP privacy policy, automated decisions) into that list.
Section 13K(3) says that subsection is a civil penalty provision, and the section's heading describes it as one for which infringement notices or compliance notices can be issued. Separately, section 13(1) says an act or practice of an APP entity is an interference with the privacy of an individual if it breaches an Australian Privacy Principle, or a registered APP code that binds the entity, in relation to personal information about the individual, and sections 13G and 13H are civil penalty provisions for interference with privacy, section 13G where the interference is serious.
Rows 1, 2, 7 and 13 of the map record the website side of several items on the section 13K list. What any of these provisions could mean for a particular business is a question for its adviser.
Working through the touchpoint map
The map has a row for each principle.
Each row names the principle as Schedule 1 does, says in short what it asks, lists where a website meets it, sets out what to record or test, and says what the result can and cannot show. Work through it in this order.
- Settle coverage first. Until your business has established with its adviser whether it is an APP entity, and which of its activities the Act reaches, the map has nothing to be measured against.
- Start with row 1, the system list, which rows 4, 5, 7, 8, 10, 11 and 12 draw on. Read each vendor's terms on security testing, ask the vendor in writing where they are silent or unclear, read your hosting provider's testing policy for your own site, and send nothing to a vendor's platform until the answer is on file.
- Do the read-only rows next. Rows 1, 5, 8 and 9 read pages, documents and settings, submit nothing and send no test requests. Row 8 also uses the host list from row 6, so complete it once row 6 is done.
- Run the rows that send requests, submit forms or sign in, which are rows 2, 3, 4, 6, 7, 10, 11, 12 and 13, only on systems your business owns or is authorised in writing to test, on a staging copy where one exists, with test accounts and invented people, never a real customer, patient, student, tenant or guest.
- Point every confirmation, reset message, export and marketing email a test triggers at an inbox or phone number your business controls.
- Keep each row to the small, fixed number of requests it names. None of them needs load.
- Leave unopened any screen or file that shows a password, key or secret, and keep session tokens out of what you save.
- Stop at the first sign of another person's real information. Write down the request and the response, go no further, and raise it with the person responsible for privacy in the business.
- Delete or list everything the test created: submissions, accounts, subscribers, exports and messages.
- Hand the completed map to whoever makes the decision, starting with your own adviser.
The decision on each principle, and who makes it
Your business does, with its adviser, and the regulator can form its own view.
The OAIC's small business page says an individual has the right to complain if they think a business the Privacy Act covers has not complied with the Act when handling their personal information, and that if the Act covers a small business, the OAIC can investigate, conciliate and, if necessary, make determinations about complaints made about its handling of personal information, and may also commence a Commissioner-initiated investigation.
A customer or insurer who sent you a questionnaire decides what it will accept as evidence for its own purposes, and the security questionnaires guide covers which questions a test can evidence and how to word an honest answer. A completed map, a test report and a retest record are inputs to all of those decisions. None of them is the decision, and none of them is a certificate.
Clever Ops testing beside the map, and its limits
Clever Ops tests the parts of a business that customers reach through a browser or an API.
For a site with no customer logins, the website security check is an external review of what anyone on the internet can see without logging in, such as certificates and transport security, security headers, cookie settings, exposed files and admin paths, and it does not look behind a login.
On WordPress, including WooCommerce stores and member sites, the WordPress security audit works through each role that can log in. For a custom application that customers or staff sign in to, the web application and API penetration test covers, among other areas, authentication and sessions, what each role can see and change, whether one customer can reach another customer's records, the API called directly rather than only through the screens, and file uploads.
That is the ground the access tests in rows 11 to 13 cover.
A chatbot or agent on the site is tested under the AI chatbot and agent security test, which covers, among other things, data the bot can be made to reveal.
The report is evidence for your own decisions and your adviser's, not a compliance opinion or a certificate. Checks that found nothing are recorded as negative results for the build and accounts tested, and one consolidated retest marks each finding fixed, partially fixed, still reproducible or not retested.
Destructive actions are off by default for real people's accounts and records that existed before the test, and reset, lockout and deletion checks run only on test accounts and test records where the rules of engagement allow them.
Evidence has session tokens, passwords, keys and personal details redacted, is stored encrypted in Australia, is processed outside Australia only where your statement of work approves it, and is deleted on the schedule set in the data handling terms.
Some of the work belongs elsewhere. Services that other businesses run, such as a hosted payment page, a booking platform or a newsletter platform, stay out of scope unless their owner agrees. Where a tender or contract requires a CREST-accredited provider, we refer the work to one, because Clever Ops is not CREST accredited.
If Clever Ops built the site or hosts it, the same work is called a security review, not an independent test, and the report says so and names the builder and the host. A report from Clever Ops is not a certification of your site.
Frequently asked questions
They are the clauses of Schedule 1 to the Privacy Act 1988: APP 1 open and transparent management of personal information, APP 2 anonymity and pseudonymity, APP 3 collection of solicited personal information, APP 4 dealing with unsolicited personal information, APP 5 notification of the collection of personal information, APP 6 use or disclosure of personal information, APP 7 direct marketing, APP 8 cross-border disclosure of personal information, APP 9 adoption, use or disclosure of government related identifiers, APP 10 quality of personal information, APP 11 security of personal information, APP 12 access to personal information, and APP 13 correction of personal information. Section 15 of the Act says an APP entity must not do an act, or engage in a practice, that breaches one.
To some small businesses. The OAIC says most small businesses are not covered by the Privacy Act 1988, but some are. Section 6C(1) of the Act leaves small business operators out of its definition of an organisation, section 6D(1) makes a business a small business at a time in a financial year if its annual turnover for the previous financial year is $3,000,000 or less, with a different test in section 6D(2) for a business not carried on at any time in the previous financial year, and section 6D(4) lists entities that are not small business operators even so, among them one that provides a health service to another individual and holds any health information except in an employee record. Sections 6E and 6EA bring some operators back in. The OAIC says its Privacy Checklist for Small Business can help a small business decide if it needs to comply with the Privacy Act, and that it is not a substitute for legal advice, so settle the answer with your adviser.
APP 11.1 requires an APP entity that holds personal information to take such steps as are reasonable in the circumstances to protect it from misuse, interference and loss, and from unauthorised access, modification or disclosure, and APP 11.3 says those steps include technical and organisational measures. The text names no particular test, and the OAIC's chapter on APP 11 does not mention penetration testing. A test is one way to gather evidence that technical measures behave as intended on the system tested. Whether it is a reasonable step for your business is a decision for your business and its adviser.
It depends on whether an individual is identified or reasonably identifiable. The OAIC's chapter on key concepts says analytical information collected from cookies, such as the number of times a page was visited, will not be personal information under the Privacy Act unless an individual is reasonably identifiable, and that where it is unclear, an APP entity should err on the side of caution and treat the information as personal information. Row 6 of the map asks a different question: whether a page sends a value a person typed, such as an email address, to an analytics or advertising service.
APP 1.5 requires an APP entity to take such steps as are reasonable in the circumstances to make its APP privacy policy available free of charge and in such form as is appropriate, and its note says an entity will usually make the policy available on its website. The OAIC's chapter on APP 1 says the policy should be prominently displayed, accessible and easy to download, and gives the example of a prominent link or privacy icon, displayed on each page of the entity's website, that could provide a direct link to it. Row 1 of the map records where the link appears and reads the policy against the APP 1.4 list.
Schedule 1, Part 15 of the Privacy and Other Legislation Amendment Act 2024 commences that day and adds APP 1.7, 1.8 and 1.9. Where an APP entity has arranged for a computer program to make, or do a thing substantially and directly related to making, a decision that could reasonably be expected to significantly affect an individual's rights or interests, and personal information about the individual is used in the operation of the program to make the decision or do that thing, its privacy policy must contain the information APP 1.8 sets out: the kinds of personal information used, the kinds of such decisions made solely by the program, and the kinds for which the program does a thing substantially and directly related to making the decision. Whether that captures a particular chatbot, scoring tool or approval rule is for your adviser.
Scope the right test for your application
Tell us what you have built, who uses it and when it needs to launch. You will get a plain-English recommendation: a website audit, a web application test or a referral to a specialist.