Privacy — driver identity verification
Face templates are sensitive information under the Privacy Act 1988. This page records how the POC handles them and what an operator still has to do.
What OptaCOR stores
- The outcome of each check, its time, and why it was triggered.
- A reference number for the provider's session.
- The device identifier and, where the browser gives it, the location.
- Who overrode a held job, and the reason they gave.
What OptaCOR never stores
- Photographs of a driver's face.
- Images of identity documents.
- Face templates or any other biometric representation.
There is no column in the schema that could hold one, which is a stronger guarantee than a policy: see src/db/schema.sql.
The alternative pathway
A supervised depot check-in is always available, and choosing it costs a driver nothing. This is not a courtesy — a consent with no genuine alternative is not voluntary, and there is adverse Australian precedent on mandated workplace biometrics.
Still the operator's job
The operator, not OptaCOR, is the APP entity collecting this data. Outstanding before any production rollout:
- A Privacy Impact Assessment, completed and documented, recording why less intrusive alternatives were judged insufficient.
- An updated privacy policy naming biometric collection and the provider.
- Confirmed AU or NZ data residency, and a contracted retention and deletion SLA.
- Consultation with drivers, and with the TWU where applicable.
The notice shown at capture
What happens to your photos
- Veriff takes and keeps them. OptaCOR never stores your photos.
- Your employer gets the result and a reference number — nothing else.
- It is kept so Your employer can show who was driving, for Chain of Responsibility and insurance.
- This is sensitive information under the Privacy Act. You can ask Your employer to see it, correct it, or complain.