UMbRA: 55.5 Million Booking-Verified Identities
Every identification produced by RTIS starts here. UMbRA is the law enforcement identity database behind every scan. 55.5 million booking records sourced from 18,000+ contributing agencies. 50,000+ new records ingested daily. Every record is traceable to a booking-based booking event. Every identification carries a chain of custody from arrest to alert.
Chain of Custody: From Booking to Alert
Every identity in UMbRA is traceable. Not "associated with a social media profile." Not "matched against public records." Traceable to a booking-based booking event conducted by a law enforcement officer at a specific agency on a specific date.
-
Arrest and Booking
An individual is arrested by a law enforcement agency. During the booking process, a booking photograph is taken and identity records are captured. The identity records establish the definitive identity of the individual. The booking photograph is linked to that verified identity.
Technical DetailThe booking event creates a permanent record: verified identity, booking photo, arresting agency, date, and charges. This record is the origin point for everything that follows.
-
Identity Verification
Booking records are cross-referenced against existing law enforcement records. This confirms that the individual is who they claim to be (or identifies them if they provide a false name). The booking verification process is the gold standard for identity verification in law enforcement.
Technical DetailBooking verification establishes a one-to-one link between the physical person and their identity record. No other identification method provides this level of certainty.
-
Record Contribution to UMbRA
The booking record (photograph, identity data, charge information, and the identity verification link) is contributed to UMbRA. 18,000+ law enforcement agencies contribute records through established data-sharing agreements. Each record retains its source attribution: the contributing agency, booking date, and identity verification status.
Technical DetailUMbRA ingests 50,000+ new records daily. The database currently contains 55.5 million verified identities and continues to grow. Source attribution is preserved throughout the record lifecycle.
-
RTIS Comparison
When an RTIS sensor captures an image at a stadium gate, that image is compared against UMbRA records. If a potential match is identified, the system associates the captured image with a booking-verified booking record. The match carries the full provenance chain: the person detected at the gate is linked to a verified identity from a documented law enforcement booking.
Technical DetailComparison runs concurrently with operator X-list checks. UMbRA matches and X-list matches are compartmentalized; each produces independent results routed to different recipients.
-
RAC Verification and Alert Delivery
Every potential match is reviewed by a trained analyst at the Rapid Action Center (RAC) before any alert is sent. The analyst confirms the match, verifies the alert context (warrant status, charge category), and delivers the alert to the designated LE contact. The alert includes the chain of custody reference: the identification is backed by a booking-verified booking record from a named agency.
Technical DetailRAC verification is mandatory. No automated alerts. No unreviewed matches reaching field personnel. The human verification layer is the final link in the chain of custody.
UMbRA vs. Scraped Databases vs. Data Aggregators
Not all identity databases are equivalent. The source of the data, the method of verification, and the chain of custody determine whether an identification holds up under scrutiny. Here is how UMbRA compares to the alternatives.
| Feature | UMbRA | Scraped FR Databases (e.g., Clearview) | Data Aggregators (e.g., CLEAR, LexisNexis) |
|---|---|---|---|
| Data source | Law enforcement booking records from 18,000+ agencies | Social media images scraped without platform consent or user authorization | Public records, commercial databases, credit bureaus, merged from multiple sources |
| Identity verification | Booking-based. Law enforcement-confirmed. Every identity linked to a physical booking event. | None. Name-to-face association inferred from social media profile labels. | Name and address matching. No biometric verification. Alias and identity confusion are common. |
| Chain of custody | Complete. Every record traceable to contributing agency, booking date, and booking event. | None. Images collected at scale with no documentation of origin, accuracy, or currency. | Partial at best. Aggregated from sources with varying quality, timeliness, and accuracy standards. |
| Record count | 56.15M verified identities | 50B+ images (self-reported by Clearview) | Varies. Hundreds of millions of compiled records. |
| Evidentiary value | Meets prosecution standard. Identification backed by identity verification and documented provenance. | Clearview's own contracts disclaim that results are "not admissible evidence." An Ohio judge dismissed a murder case relying on a Clearview identification. | Regularly challenged in litigation. Data staleness, error rates, and lack of biometric verification undermine reliability. |
| Legal standing | Booking records collected under lawful authority by sworn officers. | Scraped without consent. Permanently banned by Meta, Google, and Twitter. Fined by regulators in the UK, France, Italy, and Australia. | Governed by FCRA, DPPA, and state privacy laws. Access restrictions vary by use case. |
| Currency | 50,000+ new records daily. Active law enforcement pipeline. | Unknown update frequency. Scraped images may be years old, deleted, or from deactivated accounts. | Update cycles vary by source. Records may be months or years out of date. |
Database size is meaningless without data provenance. 50 billion unverified images cannot match the evidentiary weight of 55.5 million booking-verified identities.
UMbRA powers the identification. RTIS deploys it at the perimeter. But the venue also maintains its own identity lists through X-LST: banned patrons, VIP recognition, executive protection principals. Those lists are compartmentalized. Venue security sees their X-list alerts. Your team sees UMbRA alerts. Neither sees the other's data.
How X-LST Works for Venue SecurityUMbRA powers identity verification for law enforcement, stadiums, and critical infrastructure. Explore the full scope of the 56.15M+ booking-verified identity database.
See UMbRA Across All IndustriesSee the Data Behind the Alert
We conduct LE briefings under NDA. No sales pitch. A detailed walkthrough of the UMbRA dataset, contributing agency network, chain of custody documentation, and how identifications are produced and delivered to your team.