Company
A narrow company, on purpose.
Laurel Secure builds one thing: privacy-preserving age verification for age-gated businesses. We are not on the way to becoming an identity platform.
What we build
Laurel Secure is the company and the cloud control platform. LaurelID is the product: an Android verifier that proves a patron is 21 or older using their mobile ID, and a portal that governs the fleet of verifiers behind it.
That is the whole scope. We do not sell identity data, identity resolution, customer analytics, loyalty matching, or fraud scoring, and we have deliberately built a system that could not be pivoted into any of them without being rebuilt from the schema up.
The constraint everything follows from
One rule shapes every architectural decision: the platform stores operational data only, and structurally cannot store patron identity data.
Treating that as load-bearing rather than aspirational is what produces the rest of the product — the single-element request, the three-outcome vocabulary, the absence of a patron entity, the counter-only tables, the suppression threshold, and the allowlist ingestion contract. None of those are features we added. They are what is left once the rule is real.
How we decide what to claim
A claim on this website needs evidence in our own repositories. A jurisdiction becomes a production candidate only after a real credential has been verified on named hardware through the full production path; public delivery still requires matching live operational authorization.
The same rule produces the parts of this site that read like a competitor wrote them: 14 production-gate jurisdictions, Elo M51 as the recorded physical hardware profile, no certifications, no uptime figure, and a named reporting edge case. We would rather be checkable than impressive.
Where we are
The checked-in evidence records mobile ID validation across 15 jurisdictions in both Apple Wallet and Google Wallet on Elo M51. Canonical production gates currently cover 13 states and Puerto Rico. Arkansas is physically qualified in Apple Wallet and Google Wallet, but official issuing-authority certificate binding remains pending; it is not production enabled. Current operational support is reported only by the live-gated compatibility page, with pilots as the way new operators start. We are early, and the trust center says exactly how early.
What is not on this page
No customer logos, no testimonials, no funding announcements, and no team photos. When there are real ones to show, they will appear here with names attached. Placeholder social proof is the fastest way to lose a security reviewer’s trust, and theirs is the trust that matters most to us.
The most useful next step is a pilot.
Thirty days at one real location tells you more than any amount of company narrative.