Effective 14 September 2026
Biometric / Facial Verification Notice
14 — Biometric / Facial Verification Notice
Effective Date: 14 September 2026 Controller: OZ Ride Pty Ltd (ABN 52 694 735 487). Audience: Drivers, at the point you take the identity-verification selfie in the Driver App (onboarding, and any later periodic re-verification). Governing law: Western Australia, Australia. Defined terms: Capitalised terms not defined in this document have the meaning given in 00 — Definitions.
Change note (v1.1, 14 September 2026): section 2 no longer says RapidID checks vehicle registration against the national vehicle register (NEVDIS). RapidID verifies identity documents only; your vehicle's registration is recorded from your declaration and checked by our team against the WA Department of Transport's public register. No other change.
This notice exists because the step it describes — matching your live selfie against your licence photo — involves Sensitive Information (biometric information) about you under section 6 of the Privacy Act 1988 (Cth). The Privacy Policy covers this processing too, but this standalone notice gives you the detail the Privacy Act expects you to be given at the point that kind of information is actually collected, separately from the general onboarding paperwork. Read this before you take the verification selfie.
1. What happens, in plain terms
When you complete identity verification (at onboarding, and again at any periodic re-verification we require):
- You take a live selfie in the Driver App. The camera captures a short burst of frames rather than a single still image, so the system can check the image is a live person in front of the camera rather than a photo of a photo.
- That selfie is compared — one-to-one — against the photograph on the licence document you separately uploaded for that same onboarding or re-verification step. This is a match, not an identification: the system is only ever answering "does this live selfie match this one specific document photo you told us is yours?" It is never searched against a database or gallery of other people's photos, and it is never used to work out who you are from a crowd or from an unknown photo.
- A separate, independent check looks at the selfie itself for signs it is a genuine live capture — eyes open, no sunglasses, a sharp/clear image, a reasonable pose — and estimates an age range from the same image, as a secondary integrity check.
- Based on how closely the selfie matches the licence photo, your verification either passes automatically, is flagged for a human reviewer to check, or is treated as a failed attempt (clause 5).
2. Who performs the match, and where
The one-to-one facial comparison and the liveness check are performed by AWS Rekognition, a facial-analysis service operated by Amazon Web Services, run in AWS's Sydney (ap-southeast-2) region. Your selfie images are sent to Rekognition as image data for the comparison; Rekognition is not used to search you against any external database, watch-list, or gallery.
Correction from the previous Privacy Policy (v2.0): an earlier version of the Privacy Policy said your "biometric template" was generated by RapidID. That was incorrect. RapidID performs document verification only — checking your licence or ID document against the Australian Government's Document Verification Service. Your vehicle's registration is not sent to RapidID; it is recorded from your declaration and checked by our team against the WA Department of Transport's public register. RapidID does not see, score, or process your face. The biometric match described in this notice is performed exclusively by AWS Rekognition. This notice supersedes that earlier description.
3. Three different things, not one — profile photo, verification photo, and biometric template
These terms get used loosely elsewhere in the app and in everyday conversation. In this notice they mean specific, different things:
- Verification photo/selfie — the live selfie burst you capture during the identity-verification step described in clause 1. Used only for the one-off comparison against your licence photo.
- Biometric match result — the outcome of that comparison: a confidence score, a pass/flag/fail outcome, and the liveness-check and age-range results described in step 3 of clause 1. This is a result, not an image — see clause 4 for exactly what form it takes and how long it is kept.
- Profile photo — where your verification selfie passes, a copy of the passing frame is also saved as your driver profile photo (the photo that may be shown to Riders and used operationally to identify you, for example to Vehicle staff or support). This is a normal account photo, stored like any other identity document you provide — it is not itself a "biometric template."
We do not create or store a mathematical "facial template" or "faceprint" of you for future re-matching outside the specific verification attempt it was created for. Each verification attempt is compared independently against your on-file licence photo; we do not build or retain a searchable biometric index of Drivers.
4. What is stored, and for how long
| What | Where | Retention |
|---|---|---|
| The passing verification selfie frame, saved as your profile photo | OZ Ride's encrypted document storage | Ordinary driver-account document retention (duration of your account + 7 years after termination), the same as your other identity documents |
| A record of every verification attempt — including AWS Rekognition's full response (match confidence, face-geometry data, liveness-check results, estimated age range) | OZ Ride's database, in an audit table | No defined retention window is currently enforced for this record — it is kept without an automated deletion job (not yet enforced automatically). A retention window and a purge job are on our engineering list; until they are live, treat this record as retained indefinitely |
| Your licence document image itself (used for the comparison, separately from the selfie) | OZ Ride's encrypted document vault | Target: deleted 7 days after your document is successfully verified (not yet enforced automatically — the deletion job exists but has not been switched on) — see the Privacy Policy, clause 8 |
5. What happens if the match fails, or is inconclusive
- Strong match: your verification passes automatically and you can proceed.
- Borderline match: your attempt is flagged for a human reviewer, who checks the images and the automated result before deciding.
- Weak or no match: the attempt is treated as a failed verification. Depending on how many failed attempts you have had, this may affect your Compliance Status and your ability to go online — see the Driver Service Agreement.
A failed or flagged verification does not, by itself, mean you have done anything wrong — image quality, lighting, and camera issues are common causes. If your verification is repeatedly flagged, contact support so a human reviewer can look at it directly.
6. Consent
Because this processing involves Sensitive (biometric) Information, we ask for your specific consent to it at the point you take the verification selfie, separately from your general acceptance of the Driver Service Agreement and Privacy Policy. That consent is taken on its own screen in the Driver App, immediately before you take the selfie: the screen explains the comparison, has a tick-box for you to consent, and has a "Not now" option that lets you stop without taking the selfie.
You may withdraw this consent at any time by contacting support, but doing so means you cannot complete or maintain identity verification, which will place your Compliance Status into a non-compliant state and suspend your ability to go online — this is the same consequence described for DVS consent withdrawal in the Privacy Policy, clause 9.4, and in the Driver Service Agreement.
7. Your rights
The rights described in the Privacy Policy, clause 9 (access, correction, deletion, withdrawal of consent, complaints) apply to the information described in this notice in the same way they apply to your other Personal Information. Because the biometric-match record described in clause 4 does not yet have a defined retention window, a deletion request for that specific record will be actioned on a best-efforts basis until the automated retention/purge job referenced in clause 4 is built.
8. Why no gallery search or facial recognition is performed
We deliberately use AWS Rekognition only in one-to-one "compare faces" mode against a single document photo you provided for that specific attempt, not in a "search faces" or gallery mode that would compare you against a database of other people. This is a narrower, lower-risk use of facial-analysis technology than general facial recognition, and it is the reason we describe this system as "facial verification," not "facial recognition," throughout the legal framework.
9. Contact
Questions about this notice or the identity-verification process:
- OZ Ride privacy:
privacy@oz-ride.com, or by post to OZ Ride Pty Ltd, Privacy Officer, 224 Balcatta Road, Balcatta WA 6021, Australia. - OAIC:
oaic.gov.au, 1300 363 992.
10. Related documents
- Privacy Policy — the platform-wide privacy policy (clauses 2.2, 2.6, 3, 5A, 6, 8, and 9 all cross-reference this notice).
- Driver Service Agreement — the consequences of a non-compliant Compliance Status.
- Computer Vision Privacy Disclosure — the separate, unrelated audience-measurement camera system in Player Tablets (not covered by this notice).
End of Biometric / Facial Verification Notice.