Australia version. Opens on the Australia filter: the Privacy Act 1988 with the 13 APPs, the Notifiable Data Breaches scheme, current penalties and the new automated decision duty, plus WCAG. US version

Software Compliance Checklist (Australia)

Build a software compliance checklist for Australia: the Privacy Act, 13 APPs, Notifiable Data Breaches and new penalties, plus WCAG and global standards.

The interactive tool loads here when JavaScript runs.

About this tool

What is the Software Compliance Checklist?

This version opens on the Australia filter, which lists the Privacy Act 1988 with its 13 Australian Privacy Principles, and WCAG. The Act covers Australian Government agencies and organisations with annual turnover above A$3 million, plus some smaller ones such as health service providers and businesses that trade in personal information, so many start-ups are inside it from their first health or data product.

The Notifiable Data Breaches scheme sits inside the Act: an entity must assess a suspected breach within 30 days and notify the OAIC and the people affected when it is likely to result in serious harm. Penalties for serious interferences with privacy by a body corporate reach the greater of A$50 million, three times the benefit obtained, or 30% of adjusted turnover in the relevant period.

The Privacy and Other Legislation Amendment Act 2024 added more: a statutory tort for serious invasions of privacy from 10 June 2025, lower penalty tiers and infringement notices, and from 10 December 2026 a duty to explain in privacy policies decisions made with automated processing that significantly affect people. Switch to Global for ISO 27001, SOC 2 and PCI DSS, which Australian buyers also ask about.

  • 31 laws, standards and frameworks with requirements and penalties
  • Search plus domain and geography filters
  • Custom checklist downloaded as Markdown task list
  • CSV export of the filtered list
  • Runs in your browser with no account
Read the guide: Which Compliance Rules Apply to Your Software? A Map for Engineers

Updated

How to use the Software Compliance Checklist

  1. On the Browse Compliances tab, type in Search compliances (for example "cookies" or "health") and narrow with the Domain and Geography filters.
  2. Click a card to open its details: requirements, applicability, penalties, related items and official resources.
  3. Click the + on a card to add it to your checklist.
  4. Open the My Checklist tab, rename the checklist, and click Download MD to save a Markdown file with a checkbox for every requirement.
  5. Use Export Report on the Browse tab to download the currently filtered list as CSV.

Worked examples

Health booking app under A$3 million turnover

Input

Geography: Australia

Output

2 results: WCAG and the Privacy Act 1988 with the APPs

The small business exemption does not help here: health service providers are covered whatever their turnover, so the APP and NDB requirements go straight into the checklist.

Credit decision engine

Input

Geography: Australia, open the Privacy Act (APPs) card

Output

Seven requirements, the last being to explain significant automated decisions in the privacy policy from 10 December 2026

Plan the privacy policy update with the model documentation: what personal information feeds the decision and which decisions are made or substantially assisted by the system.

Background and insight

Most software teams meet compliance through a product decision rather than a legal memo: a signup form that collects a birth date, a checkout that stores card numbers, an analytics script that sets cookies for EU visitors. Each of those pulls in a different regime. Card data brings PCI DSS, health records held for a US covered entity bring HIPAA, children under 13 bring COPPA, and EU residents' personal data brings GDPR wherever the company is based.

The documents differ in kind. GDPR, CCPA and HIPAA are laws with regulators and fines; GDPR's upper tier is EUR 20 million or 4 percent of worldwide annual turnover, whichever is higher, and it requires breach notification to the authority within 72 hours. PCI DSS is a contractual standard set by the card brands (version 4.0 became the only active version in 2024). SOC 2 is an attestation report by an independent CPA firm against AICPA criteria, not a certification. WCAG 2.2, published by the W3C in October 2023, is the technical yardstick most accessibility laws point to.

Engineering work tends to repeat across regimes: an inventory of personal data, access control and audit logs, encryption in transit and at rest, retention and deletion, breach response, vendor contracts, and accessible UI. Building those once and mapping them to each framework is cheaper than treating every framework as a separate project.

Common use cases

  • Scoping a new product

    List the regimes a feature might trigger before design starts, while changes are cheap.

  • Answering a security questionnaire

    Get a quick summary of SOC 2, ISO 27001 or HIPAA terms an enterprise buyer asks about.

  • Planning an engineering roadmap

    Download a Markdown checklist and turn requirement lines into tickets.

  • Onboarding new engineers

    Give a team a shared vocabulary for the frameworks their product is subject to.

Tips and limitations

  • Write the NDB assessment steps into your incident runbook so the 30-day clock is tracked from the first suspicion.
  • List overseas recipients of personal information (cloud hosts, support tools) for APP 8 before you sign the contracts.
  • Destroy or de-identify personal information you no longer need; APP 11 covers retention as well as security.
  • Commercial email also falls under the Spam Act 2003, which this list does not cover; check consent separately.

Sources and further reading

Frequently asked questions

Does the Privacy Act apply to my small business?

Usually not if annual turnover is A$3 million or less, but several kinds of small business are covered anyway, including health service providers, businesses that trade in personal information and contractors to the Australian Government.

What is the maximum penalty under the Privacy Act?

For a serious interference with privacy by a body corporate, the greater of A$50 million, three times the benefit obtained, or 30% of adjusted turnover in the relevant period. Lower tiers and infringement notices now cover less serious contraventions.

When must a data breach be reported in Australia?

When it is likely to result in serious harm to someone whose information is involved. Assess a suspected breach within 30 days, then notify the OAIC and the affected people as soon as practicable, with recommended steps they should take.

What changes on 10 December 2026?

Privacy policies must explain the kinds of personal information used, and the kinds of decisions made, where a computer program makes or substantially assists decisions that could significantly affect people's rights or interests.

Can people sue for invasion of privacy in Australia?

Since 10 June 2025, a statutory tort lets individuals sue for serious invasions of privacy that were intentional or reckless, subject to exemptions and defences in the Act.

Is there an in-depth guide to the Software Compliance Checklist?

Yes. “Which Compliance Rules Apply to Your Software? A Map for Engineers” covers the background, how it works, common pitfalls and worked examples. Read the full guide.