Am I Misusing a Driver's Licence or Medicare Number?
Select the ways your business handles TFNs, Medicare numbers, driver's licences and passports. Get an instant APP 9 check across 18 common Australian scenarios.
Under APP 9 of the Privacy Act 1988 (Cth), a business must never adopt a government-issued identifier — a Tax File Number, Medicare number, driver's licence number, passport number or similar — as its own identifier for an individual. Using or disclosing one is also restricted to identity verification, obligations to an agency, or a legal requirement. Select the practices below to see where your gaps sit.
Last updated: 2 July 2026
How each practice is scored
| Result | Meaning |
|---|---|
| Compliant | Required or authorised by law, or genuinely necessary to verify identity for your business's activities |
| Gap | Banned outright as an adoption or unrelated use of the identifier, or you can't confirm a genuine verification necessity |
Why "just sighting ID" isn't the same as adopting it
APP 9 draws a sharp line most businesses don't realise exists. Sighting or recording a driver's licence to verify someone's age or identity is usually fine — it's reasonably necessary for the transaction. But turning that same number into your customer ID, patient record ID, or database primary key crosses into "adoption", which APP 9.1 prohibits outright, with no consent-based workaround.
The exceptions that do apply are narrow and specific: AML/CTF identification, a TFN declaration for tax reporting, or a genuine court order. A debt collector isn't automatically an "enforcement body" under the Act, and sharing an identifier across business units for unrelated purposes isn't covered either — both are common gaps this check flags.
Government ID check
Select every way your business currently handles government related identifiers. For each one that isn't automatically exempt or banned outright, tell us whether it's genuinely necessary to verify identity. You'll get an instant APP 9 report at a permanent URL you can revisit or share.
When you need a government ID check
- — Your account, membership or patient records have never been reviewed against APP 9
- — You're newly covered by the Privacy Act following the 1 July 2026 threshold removal
- — You sight or record driver's licences, passports, Medicare numbers or Centrelink CRNs as part of onboarding
- — You disclose customer identifiers to payroll providers, verification services, or debt collectors
- — You're preparing for an OAIC inquiry or a compliance audit
Frequently asked questions
What does APP 9 of the Privacy Act require?
APP 9 prohibits adopting a government related identifier as your own identifier for an individual, and restricts using or disclosing one to identity verification, obligations to an agency, a legal requirement, or enforcement activity by an enforcement body.
Can a business use a driver's licence number as a customer ID?
No. APP 9.1 bans adopting a government related identifier — including a driver's licence, Medicare or passport number — as your own identifier for the individual, regardless of consent. Use an internally generated customer number instead.
When can a business record a government related identifier?
Generally where it's reasonably necessary to verify identity for your business's activities, or required or authorised by law — such as AML/CTF customer identification or a TFN declaration.
What does the free government ID check check?
It checks the practices you select against a catalogue of 18 common Australian scenarios, flagging which are banned outright, which need a genuine verification necessity you haven't confirmed, and which are exempt.
Select your practices above to get an instant APP 9 government ID report.
Get my government ID report →