Every identity in UMbRA traces to a law enforcement booking source
County, state, and federal law enforcement agencies submitting records
Continuous ingestion from active law enforcement partnerships
Database Size Is Meaningless Without Data Provenance
Three approaches to identity intelligence. One is sourced from booking-verified law enforcement records. The other two are not. That distinction determines whether your match holds up in court, survives an audit, or creates a liability.
Three Approaches to Identity Data
Not all identity databases are equal. The source of the data, the method of verification, and the chain of custody determine whether a match is actionable or a liability.
| Category | |||
|---|---|---|---|
Why Data Provenance Matters
A facial recognition match is only as reliable as the data behind it. UMbRA is the only identity database where every record is traceable to a booking-verified law enforcement booking.
Booking-Verified Identity
Every record in UMbRA originates from a law enforcement booking where the individual was booked and identity-verified. The identity is verified at the point of collection, not inferred from a social media profile or assembled from public record fragments.
Complete Chain of Custody
Each record can be traced from the contributing agency through ingestion and storage to the moment of match. This audit trail is what separates court-ready evidence from an unverified algorithm output.
50,000+ New Records Daily
UMbRA is not a static archive. More than 18,000 law enforcement agencies contribute records. The database grows by over 50,000 verified identities every day, sourced from active booking systems across county, state, and federal jurisdictions.
NIST tested Clearview's algorithm. They did not test Clearview's database. Algorithm performance and database quality are two entirely different questions.
What Happens When the Data Is Wrong
When an identity match is based on a scraped image with no verification, the downstream consequences are serious:
Wrongful Detention
A false match in a law enforcement context can lead to wrongful detention.
Civil Liability
A false match in a private security context creates civil liability.
Inadmissible Evidence
A match that cannot be traced to its source is inadmissible as evidence.
Stale Data
A match based on stale aggregated data may reference an identity that no longer exists at that address, phone number, or employment.
Every match Safience delivers through RTIS is backed by UMbRA's verified data and confirmed by a human analyst at the RAC before any alert reaches your team. The system does not act on unverified data. It does not act without human review.
See the Difference in Practice
Request a technical architecture review. We will walk you through UMbRA's chain of custody, the RAC verification workflow, and what a match looks like from sensor to alert.