Australian Privacy Act
We don't collect personal information as defined under APP 3 - there's nothing to govern under APPs 6, 8, 11, 12, 13. The architecture removes the question.
Policies can change. Architectures don't. We never built the pipeline that would let us see a face - there's no toggle to flip, no premium tier to unlock. The privacy answer is structural.
The architecture is the promise.
Drag the handle. Surveillance-era CCTV on the left. Occivar™ on the right.
We don't collect personal information as defined under APP 3 - there's nothing to govern under APPs 6, 8, 11, 12, 13. The architecture removes the question.
No personal data under Article 4. No special category data under Article 9. No DPIA triggered by deployment. We can sign a clean DPA on request.
Aligned with ICO's "data protection by design" guidance and the Surveillance Camera Code of Practice - by being neither.
No. Raw video frames never leave the sensor. The inference runs on-device and only anonymous counts and density values are transmitted.
No. There is no face-detection model in the build pipeline. The system cannot identify individuals.
The platform does not collect personal data as defined under GDPR Article 4. No DPIA is triggered by deployment. A clean DPA is available on request.
Occivar does not collect personal information as defined under APP 3, so APPs 6, 8, 11, 12 and 13 do not apply to the system's output. The architecture removes the question.
Yes. Every deployment ships with a customer-side proxy. All telemetry passes through it before reaching Occivar, and customers can mirror it to their own warehouse.
No. Tracking IDs are scoped to a single frame. There is no cross-camera identity continuity.