Tranche 2 Privacy Act Reforms: What Changes for Candidate and Referee Data

Dilara AlmeidaDilara Almeida18 November 20269 min read
Two people talking in an office corridor with closed laptops under an arm

Privacy Act tranche 2 hiring proposals are still an exposure draft, not commenced law. On 31 August 2026 the Attorney-General released a consultation paper and draft Privacy Amendment (Personal Data Protection) Bill 2026. Submissions closed on 18 September 2026. The page that covers 2026 hiring privacy changes is separate. This note is the draft and the candidate and referee files you already hold.

Map where CVs, referee comments and screening exports sit, who can open them, and which clock would apply if the draft later became law. A 72-hour eligible data breach report to the OAIC is a proposal in that draft, not the clock you run today.

Key Takeaways

  • The Privacy Amendment (Personal Data Protection) Bill 2026 is exposure-draft legislation released on 31 August 2026. It is not in force.
  • The draft would require APP entities to notify the OAIC of an eligible data breach within 72 hours of having reasonable grounds to believe one has occurred. That 72-hour rule is not current law.
  • The draft keeps the 30-day window to assess a suspected eligible data breach.
  • The employee records exemption is unchanged in the draft. Applicant, unsuccessful-candidate and referee records still sit inside the APPs for APP entities.
  • The work now is a vendor file map: where candidate and referee data lives, which subprocessors can reach it, and who owns the breach clock.

Label the draft before you rewrite a policy

The Attorney-General’s 31 August 2026 media release announced a consultation paper and draft legislation. The Department’s hub still frames the Bill as subject to further consideration by government. Gadens and Hall & Wilcox treat the same text as an exposure draft, not commenced reform.

Do not brief hiring managers that “the 72-hour rule has started.” Do not treat a fair-and-reasonable test, a controller-processor split, or a right to erasure as live APP text. Current hiring privacy compliance in Australia still follows the Privacy Act 1988 and the APPs as they stand, including the Notifiable Data Breaches scheme already in force.

  • Status - Privacy Act 1988, including 2024 amendments, in force; Draft Bill and consultation paper only. Not commenced
  • Eligible data breach notice to the OAIC - Assess a suspected eligible breach; take all reasonable steps to finish that assessment within 30 days, then notify; Would notify within 72 hours of reasonable grounds to believe an eligible breach has occurred. The 30-day assessment of a suspected breach is kept in the draft
  • Employee records exemption - Section 7B(3) still applies to private-sector employee records in the current Act; Unchanged in the draft. Gadens and Hall & Wilcox both record that the exemption was not removed

What Privacy Act tranche 2 hiring proposals would change for files you already hold

If the draft later passed in a similar form, handling rules would reach CVs, referee comments, interview notes and screening exports. Gadens records that proposed handling obligations would apply to personal information an entity already holds. There is no grandfathering in that draft.

A fair-and-reasonable test would replace APPs 3, 4 and 6. Collection, use and disclosure would have to be fair and reasonable in the circumstances, including reasonable expectations, transparency, data minimisation, genuine choice, and impact. Consent would not, by itself, save a practice that fails that test. For hiring, that is how much referee commentary you collect, how long you keep unsuccessful-applicant files, and whether you reuse a pool for a role the person never applied for.

Personal information would cover information that “relates to” an identified or reasonably identifiable individual. Collection would include information generated or derived, including through analysis or AI, once it sits in a record. Disclosure would occur when personal information is made accessible to another person or body, even if you keep some control. That last point matters when an ATS, a shared drive, or a reference check vendor can open a referee’s contact details.

The draft would add a controller-processor split. A processor acting on a controller’s documented written instructions would be exempt from most APPs other than APP 1 and APP 11. Gadens notes that processor exemptions would not extend to the Notifiable Data Breaches scheme: both sides would still have independent breach duties. If a vendor acted outside the written instructions, those exemptions would not apply.

Scoring inferences sit in that collection definition. Keep AI recruitment privacy on a separate track. This page is about where the records live and who can reach them.

The 72-hour clock is a draft, not today’s NDB scheme

Hall & Wilcox summarise the draft as requiring organisations to report eligible data breaches to the OAIC within 72 hours of becoming aware of reasonable grounds to believe an eligible data breach has occurred. Gadens adds that an incomplete statement would be allowed where a full statement is not practicable, with reasons for the gaps, then updates as facts arrive. Both firms record that the 30-day assessment of a suspected eligible data breach is preserved in the draft. The 72-hour notice would start only once the entity has reasonable grounds to believe an eligible breach has in fact occurred.

The draft would also add duties to prepare for breaches, contain them, and take reasonable steps to reduce harm, including where the incident never meets the eligible-breach threshold. APP 11 would be tightened so entities can identify the personal information they hold and review security, retention and destruction. None of that is the scheme you operate under today. Current NDB practice still uses the assessment window already in the Act. Do not write “72 hours” into a live policy as if Parliament has already passed it.

Employee records stay exempt. Candidate and referee files do not hide there

Gadens records that the employee records exemption in section 7B(3) survives unchanged in the draft. Hall & Wilcox say the same. Private-sector employee records can still sit outside the APPs in the current Act. Do not plan as if the exemption has already gone.

Candidate data privacy in Australia does not ride on that exemption. An applicant is not an employee. An unsuccessful candidate is not an employee. A referee is a third party. APP entities still handle those records under the APPs. Health information or other sensitive information in a recruitment file still needs the higher handling standard that already applies.

Collect only the referee commentary the role needs, name the purpose, and set a destruction date. That is already APP practice, and the same discipline reference check privacy laws and privacy in online reference checks already ask you to apply.

A vendor due-diligence checklist for candidate and referee data

Righteo’s work is reference checking and assessments, not a privacy-law product. Use the same questions on every vendor that stores a CV, score, or referee comment, including your ATS.

  • Where the file sits. Name the systems that hold applications, interview notes, scores, right-to-work copies, and referee comments, including email and shared drives. If you cannot list the stores, you cannot assess a breach.
  • Who is controller and who is processor. Ask for documented written instructions, not a generic “we comply” clause.
  • Subprocessors. Ask who else can open the record: cloud hosts, transcription tools, offshore support, scoring engines. A disclosure in the draft sense is access, not a formal handover.
  • Breach clocks. Ask how fast the vendor can tell you a hiring file was exposed, against the clock you have today and against the 72-hour OAIC notice the draft would impose if it later became law. Label those two clocks as current versus draft.
  • Retention and destruction. Ask when unsuccessful-applicant and referee records are deleted, including backups. The draft would push APP 11 toward destruction, not only de-identification, when the information is no longer needed.
  • Sensitive information and consents. If you collect health or other sensitive information in recruitment, the draft would keep a specific consent requirement. Bundled or pre-ticked consents would not meet the draft definition.

Write the answers in the vendor file. Waiting for a commencement date is not a map.

Related Resources

Common Questions About Privacy Act Tranche 2 Hiring

1. Is the 72-hour eligible data breach rule current Australian law?

No. A 72-hour notice to the OAIC is a proposal in the 31 August 2026 exposure draft of the Privacy Amendment (Personal Data Protection) Bill 2026. It is not commenced. Current Notifiable Data Breaches practice still uses the assessment window already in the Privacy Act, including 30 days to assess a suspected eligible data breach.

2. Does the employee records exemption cover candidate and referee files?

No. The employee records exemption in section 7B(3) applies to private-sector employee records, and the exposure draft leaves it in place. Applicant files, unsuccessful-candidate files and referee comments are not employee records, so APP entities still handle them under the APPs.

3. Would the draft change who is a processor of hiring data?

Yes, if it later passed in similar form. The draft would treat a vendor that handles personal information only on a controller’s documented written instructions as a processor, exempt from most APPs other than APP 1 and APP 11. Both controller and processor would still have independent Notifiable Data Breaches duties.

4. Do hiring teams need to rewrite vendor contracts this week because the draft exists?

No. An exposure draft is not a reason to pretend the Bill is in force. Map where candidate and referee data sits, name subprocessors, and write processing instructions you could defend if a later Act used that structure.

5. What should a vendor due-diligence checklist cover for recruitment files?

Name every store that holds CVs, scores and referee comments; record controller and processor roles; list subprocessors who can open the file; separate the current breach clock from the draft 72-hour OAIC notice; and set retention and destruction for unsuccessful applicants and referees.

Map Candidate Files Before Any Draft Clock Starts

Privacy Act tranche 2 hiring reform is a draft you can prepare for, not a statute you can already breach. Keep the 72-hour OAIC notice in the proposed column until a later Act says otherwise. Map candidate and referee data, write vendor instructions, and run reference checks only on files you can find and destroy when the purpose ends.

AI Powered

Stop hiring by intuition.

Automate reference checks and skills assessments with Righteo. Get honest, structured insights on every candidate — faster and fairer. Trusted by 1,200+ Australian businesses.