Start hereCheck coverage and classify information
~84 days leftOpen step
Guide library
Regulation Asia–Pacific

Australian Privacy Act

Privacy Act 1988 · APPs and Notifiable Data Breaches scheme

Implement Australian Privacy Principles and prepare to assess eligible data breaches.

Who it applies to

APP entities, including many Australian Government agencies and private sector organizations, subject to specific coverage and exemptions.

What you’ll produce

Documented APP controls and an incident assessment and notification workflow.

Check recent Privacy Act amendments, sector rules and exceptions before applying the general APP or NDB workflow.

TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

What applies to each entity, product and activity?
Have Legal or Regulatory confirm scope and applicable deadlines for each entity, activity and jurisdiction. Assign owners for incident reporting, filings and lifecycle changes where required.
Who will do the work and who can sign?
Appoint a sponsor, a day-to-day lead and a named owner for every workstream. Set aside their time and decide who can approve the outcome, accept remaining risk or authorize a filing.
Which deadlines can we promise?
Separate fixed external dates from internal targets. Confirm dependencies such as a vendor, test lab or assessor, and approve a backup plan if their dates slip.

How to spend the first week

  1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
  2. Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts.
  3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.

What to review each week

Monitor obligations without a named owner, filings or notifications approaching deadline, and changes that should reopen the scope decision.

Kickoff brief to share with your team

Fill this in with your sponsor and send it to the people who own the work.

Australian Privacy Act kickoff brief
Business reason and required outcome  [Contract, obligation or approval]
Scope and exclusions  [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones  [Date, source and owner]
Executive sponsor and authorized signer  [Names]
Project lead and backup  [Names]
First workstream  Check coverage and classify information · Privacy officer + legal [Name and due date]
People, effort and external costs  [Estimate, owner and contingency]
Evidence folder and reviewer access  [Location, access owner and review date]
Decisions and blockers  [Item, options, owner and decision date]

First week
1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
2. Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts.
3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
How to hand off evidence
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
  3. Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
DATES AND TRIGGERS

Official milestones

See the deadline calendar
  • 30 calendar days

    Outer assessment window

    Take all reasonable steps to finish the assessment within 30 days after awareness of grounds to suspect an eligible breach.

    Official reference (opens in a new tab)
The whole journeyabout 84 days across 4 steps
  1. 01Check coverage and classify informationPrivacy officer + legal · ~14 days
  2. 02Implement APP processesPrivacy + product · ~28 days
  3. 03Secure data and control disclosuresSecurity + suppliers lead · ~28 days
  4. 04Assess suspected eligible breachesIncident lead + privacy officer · ~14 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 11 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Check coverage and classify informationPrivacy officer + legalAt initiationSet a start dateScope assessment; Data mapOpen
Implement APP processesPrivacy + productBefore collection and on requestsSet a start datePolicy and notices; Rights workflow; Retention scheduleOpen
Secure data and control disclosuresSecurity + suppliers leadBefore sharing data and ongoingSet a start dateSecurity controls; Recipient assessments; Disposal recordsOpen
Assess suspected eligible breachesIncident lead + privacy officerAs soon as reasonably practicableSet a start dateAssessment record; OAIC statement; Notice logOpen
0 of 4 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.

  1. 01

    Check coverage and classify information

    Who Privacy officer + legal When At initiation

    Determine whether the entity and processing are covered. Map sensitive information, overseas disclosures, retention and relevant exemptions.

    What to produce

    Scope assessmentMemo

    Gather first

    • Service inventory and architecture
    • Customer commitments and contracts
    • Applicable criteria or legal text

    How to prepare it

    1. Write the exact decision this memo supports. Name the legal entity, service, environments and dates. Attach a boundary diagram and state which people, vendors and processes can affect the scope.
    2. List the exclusions next to the inclusion list. Give a reason for each one and describe any shared service that crosses the boundary.
    3. Review the draft with service owners and the person making the decision. Freeze the approved version and add a review date or trigger for changes.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Decision
    Cover the hosted billing service for the April to June review.
    In scope
    Production billing API, hosting, releases and production access.
    Excluded and why
    Internal HR tool. It has no access to billing systems or data.
    Dependencies
    Cloud hosting and corporate identity provider.
    Approval
    Service owner approves after checking the architecture and contract.

    Check before handing it over

    A reviewer can use the memo to classify a named system and see how shared dependencies are handled.

    Give the approved scope and any open questions to whoever will map requirements, select samples or review the engagement.

    Data mapDiagram worksheet

    Gather first

    • System and vendor inventory
    • Examples of live transactions or data events
    • Approved boundaries and information categories

    How to prepare it

    1. Sketch an entry point, storage location, processing system and recipient for each flow. Label arrows with what moves and in which direction.
    2. Show trust boundaries, geographic locations, contracts or interconnections that matter. Include administrative access, backups and deletion paths where relevant.
    3. Walk through a real end-to-end transaction with engineering and operations. Save an accessible diagram and keep the reviewed flow register beside it.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Source
    Web checkout
    Destination
    Billing API in EU region
    Data and purpose
    Order reference and billing email to send the receipt
    Protocol and boundary
    HTTPS, crosses from public network into hosted production
    Owner and validation
    Billing owner, validated against request logs on 2026-11-12

    Check before handing it over

    An engineer can trace collection to deletion, and a reviewer can see every crossing or third-party handoff.

    Use the worksheet to design the diagram. Share the diagram with the people confirming scope, transfers or controls.

  2. 02

    Implement APP processes

    Who Privacy + product When Before collection and on requests

    Maintain an APP privacy policy and collection notices, evaluate consent where appropriate, and test access and correction channels.

    What to produce

    Policy and noticesMemo

    Gather first

    • Approved data map and purposes
    • Applicable disclosures and languages
    • Actual rights, consent and contact channels

    How to prepare it

    1. Write the information a person needs at the point of collection or disclosure. Use the applicable legal checklist to cover who, why, what, recipients, retention and choices.
    2. Match every promise to the real product and supplier configuration. Draft any short collection notice alongside the longer policy and use language appropriate to the audience.
    3. Have privacy and product owners check the draft against the live journey. Publish the approved version, record where it appears and test all contact and choice links.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Audience and moment
    Customer account contact, on the invoice email form
    Plain wording
    We use your billing email to send receipts and help with billing questions.
    Choices and contact
    Link to the applicable privacy request channel.
    Supporting record
    Processing activity P-014 and retention schedule FS-04
    Publish and verify
    Legal approval, web form URL, version and date

    Check before handing it over

    A reader can understand the intended use and reach the correct rights channel. The notice matches what the service actually does.

    Send approved text to the publishing owner and give support teams the version and effective date.

    Rights workflowMemo

    Gather first

    • Covered rights and scope exceptions
    • Intake channels and identity verification rules
    • Systems, vendors and escalation contacts

    How to prepare it

    1. Start from each intake channel. Write who logs the request, verifies the requester and calculates the due date under the applicable rule.
    2. Map tasks to system owners. Include gathering records, searching vendors, deciding exemptions, securing replies and obtaining approval for extensions or denials.
    3. Run a test request end to end. Track timestamps, handoffs and output. Fix gaps and repeat the test before putting the procedure into use.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Trigger
    A verified customer requests access through the support form.
    Triage
    Open a case and record receipt time, jurisdiction and deadline.
    Handoffs
    Billing and customer operations return records using restricted links.
    Quality check
    Reviewer checks redactions, exemptions and controller instructions where applicable.
    Close
    Send the response securely and save delivery evidence and date.

    Check before handing it over

    A new case worker can follow the procedure and deliver a test response without inventing missing steps or timings.

    Train intake, operational and backup staff. Make the intake instructions and current contact list easy to find.

    Retention scheduleSpreadsheet

    Gather first

    • Record categories and storage map
    • Legal and business retention needs
    • Deletion, archival and legal-hold process

    How to prepare it

    1. List each record type, storage system, owner and event that starts the retention period. Document the rationale and any applicable hold or exception.
    2. Select and test the deletion, return or archive procedure. Account for backups, vendors and logs, and keep evidence of what was disposed of and when.
    3. Have owners and legal sign off. Schedule reviews and flag cases where a system cannot yet apply the approved schedule.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Record class
    Support conversation metadata
    Retention trigger
    Case closes
    Rule and basis
    Internal schedule RS-12, check contractual and legal retention requirements.
    Disposal method
    Scheduled purge with restricted job evidence. Legal hold overrides deletion.
    Owner and check
    Support operations, monthly export and purge reconciliation

    Check before handing it over

    A system operator can apply the rule and show evidence of deletion, exception or hold.

    Send authorized rules to system and vendor owners and file the verified disposition evidence.

  3. 03

    Secure data and control disclosures

    Who Security + suppliers lead When Before sharing data and ongoing

    Apply reasonable safeguards, assess overseas recipients, document contracts and test destruction or de-identification.

    What to produce

    Security controlsSpreadsheet

    Gather first

    • Applicable criteria, requirements or risk decisions
    • Current procedures and configurations
    • Names of people operating or reviewing each control

    How to prepare it

    1. Give each requirement and implemented control an ID. Write a short control statement naming who does what, when and in which system.
    2. Record the evidence the control produces and how it could be tested. For a shared or inherited control, state who owns each part.
    3. Walk through one control with its operator. Check a real recent run, record gaps and obtain approval for exclusions or alternate controls.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Requirement
    Production access is reviewed periodically.
    Control ID
    AC-04
    Control activity
    IAM team exports administrator roles every quarter. System owners approve or revoke each assignment.
    Owner and frequency
    IAM lead, quarterly
    Evidence
    Export with filters, annotated review and removal tickets
    Test and status
    Reconcile export to current roles. Inspect approvals. Operating.

    Check before handing it over

    A different person can operate the control or test it using the matrix and its evidence links.

    Give the baseline to control owners and the assessor before walkthroughs or sampling.

    Recipient assessmentsSpreadsheet

    Gather first

    • Verified transfer map and remote access paths
    • Recipient contracts and safeguards
    • Current transfer rules, mechanisms and local restrictions

    How to prepare it

    1. Record exporters, importers, roles, countries, data and purposes. Include onward transfers or remote access if relevant to the governing law.
    2. Identify the permitted basis, mechanism or exemption and why it fits. Document safeguards, any required risk assessment and supporting clauses or approvals.
    3. Secure legal review and set triggers for reassessment, such as a new country, recipient or subcontractor. Tie the decision to procurement or product release.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Transfer ID
    XFER-018
    Parties and data
    EU controller to external support provider, ticket metadata
    Country and access
    Remote access from recipient country, limited support staff
    Mechanism and review
    Use applicable transfer mechanism. Legal assessment L-019 pending.
    Controls and approval
    Role restrictions and access logs. No production access until approved.

    Check before handing it over

    The register shows actual access paths, the basis for each transfer and a clear release decision.

    Share the decision with supplier and access owners so they can implement the conditions before data is available.

    Disposal recordsSpreadsheet

    Gather first

    • Record categories and storage map
    • Legal and business retention needs
    • Deletion, archival and legal-hold process

    How to prepare it

    1. List each record type, storage system, owner and event that starts the retention period. Document the rationale and any applicable hold or exception.
    2. Select and test the deletion, return or archive procedure. Account for backups, vendors and logs, and keep evidence of what was disposed of and when.
    3. Have owners and legal sign off. Schedule reviews and flag cases where a system cannot yet apply the approved schedule.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Record class
    Support conversation metadata
    Retention trigger
    Case closes
    Rule and basis
    Internal schedule RS-12, check contractual and legal retention requirements.
    Disposal method
    Scheduled purge with restricted job evidence. Legal hold overrides deletion.
    Owner and check
    Support operations, monthly export and purge reconciliation

    Check before handing it over

    A system operator can apply the rule and show evidence of deletion, exception or hold.

    Send authorized rules to system and vendor owners and file the verified disposition evidence.

  4. 04

    Assess suspected eligible breaches

    Who Incident lead + privacy officer When As soon as reasonably practicable

    Complete and record assessment. If serious harm is likely and remediation does not prevent it, notify OAIC and affected individuals as required.

    What to produce

    Assessment recordMemo

    Gather first

    • Approved test scope and criteria
    • Population and sample records
    • Test approach, results and reviewer requirements

    How to prepare it

    1. State objective, dates, scope and the method before describing results. Record the tester, any independence requirements, and how samples were selected.
    2. For each item, compare what should have happened with what the evidence shows. Describe impact and link the evidence or recorded exception.
    3. Add limitations, obtain review and give each finding an owner and a date. Retain the underlying samples and calculations with the signed version.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Test objective
    Check that production role removals happen within the internal deadline.
    Method and population
    All September departures. Test each privileged account.
    Expected result
    Remove access within one business day.
    Observed result
    11 on time. One late by two days, ticket IAM-114.
    Finding and follow-up
    F-008. Retest the next departure and verify alerting.

    Check before handing it over

    Someone who did not run the test can reproduce the result and tell a finding from a scope limitation.

    Give management the findings and evidence links. Share observations with an external reviewer where the engagement calls for it.

    OAIC statementMemo

    Gather first

    • Incident case facts and awareness timestamps
    • Current authority forms and applicable notification criteria
    • Approved recipients and counsel or incident lead

    How to prepare it

    1. Identify the recipient and required fields. Prepare a concise account of what happened, data and people affected, likely consequences, protective steps and an official contact.
    2. Mark unknown facts and state how they will be updated. Confirm recipients and secure delivery or required portal before sending.
    3. Obtain the prescribed approval. Keep the sent version, delivery receipt and any follow-up or supplement with the case.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Recipient and reference
    Approved authority or affected person, incident INC-041
    What happened
    An account viewed a link beyond its permissions. Investigation continues.
    Likely effect and protection
    Access was revoked. Review your recent account activity and contact support for help.
    Contact and update
    Approved incident contact, updated facts after log review
    Approval and record
    Privacy lead approved, receipt recorded in case file

    Check before handing it over

    Use the applicable authority’s language and official portal where required. Every material factual statement can be traced to the case.

    Have the authorized notifier submit through the official channel and add the receipt and follow-up date to the incident log.

    Notice logSpreadsheet

    Gather first

    • Case, change or communication records
    • Required fields and timing
    • Named case owner and authorized recipients

    How to prepare it

    1. Give each event a record ID. Record the action or request, receipt or send time, owner and the deadline or next date.
    2. Write the decision and link the response or supporting record. Track delivery, escalation or verification separately so a sent message is distinguishable from an accepted one.
    3. Review open rows on a regular cadence. Restrict personal details to the case system and keep the register to IDs and necessary dates.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Record ID
    REQ-022
    Event and date
    Verified access request received 2026-11-07 UTC
    Owner and target
    Privacy operations, internal review by 2026-11-23
    Decision and status
    Approved response, sent securely
    Completion evidence
    Case delivery record, 2026-11-24
    Follow-up
    None, approved by the reviewer

    Check before handing it over

    Every open item has a next action and closed items have a verifiable record of closure or delivery.

    Use the log at case reviews and provide a restricted copy only where the engagement requires it.

PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes