Liability Protection and Regulatory Alignment
Safience was built from the ground up to pass legal review. Zero biometric retention, booking-verified data sourcing, human verification on every match, and an architecture designed to meet the technical and operational criteria for SAFETY Act eligibility. This is security technology your legal team will approve.
Zero Biometric Retention
Non-match images are discarded immediately after comparison. No biometric template is created. No biometric database exists at your venue. There is nothing to breach, subpoena, or litigate over.
Booking-Verified Sourcing
Every identity in UMbRA (55.5M records) is traceable to a booking-based law enforcement booking record. Complete chain of custody from source to match. Court-ready evidence standard.
Human Verification (RAC)
Every potential match is reviewed by a trained analyst at the Rapid Action Center before any alert is sent to your team. No automated actions on matches. No false-positive alerts reach your security operations.
Compliance Across Jurisdictions
| Regulation | Status | How Safience Addresses It |
|---|---|---|
| BIPA (Illinois Biometric Information Privacy Act) | Compliant by architecture | Zero biometric data retained. No biometric template created. No consent collection required because no biometric data is stored. |
| CUBI (California Consumer Privacy Act biometric provisions) | Compliant by architecture | Same zero-retention architecture. No biometric data processing subject to CUBI requirements. |
| GDPR (General Data Protection Regulation) | Aligned | No personal biometric data stored. Non-match comparisons produce no data artifact. Match alerts contain identity information sourced from law enforcement records, not venue-generated biometric data. |
| State biometric statutes (TX, WA, NY, others) | Compliant by architecture | The zero-retention model eliminates the triggering condition for biometric privacy obligations across all current state statutes. |
| ADA / Civil rights | No disparate impact | Human verification (RAC) on every match prevents automated decision-making. No patron is denied entry by an algorithm. |
RTIS deployment aligns with NIST OSAC Technical Guidance Document 0008 for facial recognition use in public safety contexts. This alignment provides a recognized framework reference for legal review and regulatory discussions.
Request a Legal and Compliance Review
Our team will walk your General Counsel and CISO through the zero-retention architecture, compliance positioning, and regulatory alignment.