Venue Axis's facial-recognition integration is built so we never become a biometric handler under the Privacy Act. The system rejects biometric templates at the boundary — the moment a vendor tries to send one, the payload is refused. Match decisions stay with your chosen FRT vendor; the record stays with you.
FRT vendors send Venue Axis a normalised event payload. We accept event metadata. We do not accept — and actively reject — anything that could be a biometric template.
Every FRT vendor that integrates with Venue Axis posts events to a single secure endpoint. Each event is cryptographically signed, validated against a strict schema, and de-duplicated before it's accepted. Anything that looks like a biometric template is refused at the door.
An FRT alert is not a decision — it's a candidate for review. The Floor PWA presents the alert with confidence score and patron reference; the duty manager confirms one of three outcomes: confirmed match, cannot locate, false match. Each outcome triggers the appropriate downstream workflow and feeds the accuracy dashboard.
Per-vendor false-positive rate, confirmed-match rate, cannot-locate rate, by camera and by time of day. The GM portal surfaces these live so you can hold your FRT vendor accountable to the SLA they promised.
When a patron disputes a match, the dispute pack assembles the webhook payload (without biometric data), the floor confirmation, the camera reference, and the FRT vendor's accuracy stats — ready for export to legal or to the patron.
The two-phase resolve, audit-logged outcomes, false-match tracking, and never-store-templates architecture are designed to align with the Code of Practice for Facial Recognition in Hotels and Clubs. Confirm your venue's readiness with the self-assessment below.
We work with FRT vendors whose integration model honours the never-store-templates boundary — match decisions stay on the vendor side, only event metadata crosses to us. Today we lead with the two vendors below.
Australian-headquartered, mid-market focus, clean adapter fit. Adapter is in code; production contract scheduled for Q1 2027.
Self-hosted open-source, used for local development and demo environments. Useful for venues that want to evaluate FRT before committing to a production vendor.
Already running a different FRT vendor — Corsight, Idemia, NEC, or other? Our adapter pattern can integrate any vendor whose events stay within the architectural boundary (event metadata accepted, biometric content rejected). Get in touch and we'll walk through the fit for your existing stack.
Public, free, no login required. 10 questions covering NSW FRT Code (Hotels and Clubs, 2026) alignment — PIA, signage, staff training, accuracy monitoring, vendor due diligence, and patron dispute process. Returns a personalised gap brief with specific clause references and remediation steps.
Open the FRT readiness assessment →