On device
Identity stays local
The identity data used for verification remains on-device during the check.
Company
Privacy, engineered into the boundary.
Laurel Secure exists to answer an age question without turning the answer into an identity record. Verification stays on-device. The business receives only a result.
01 · Why we exist
Proof of age should not require a copy of identity.
Many age checks collect far more than the decision needs. Laurel Secure takes a narrower path: the identity interaction and age verification happen on the device, then only pass, fail, or unable to verify crosses the boundary.
The platform stores aggregate counts rather than a patron record. There is no patron entity and no persistent patron profile behind the reporting interface.
02 · How we work
The minimum is the design.
Each layer carries only what the next layer needs—and nothing about who was checked.
At the boundary
Three outcomes only
The platform receives pass, fail, or unable to verify—not identity fields.
In reports
Small buckets stay hidden
Day-level report buckets do not render until they reach the k=3 threshold.
Bring us the hard questions.
Explore the verification boundary, or contact us about a specific use case.