Hospitality
Bars & nightclubs
Use an on-device age result at entry without creating a profile of the patron.
Who it’s for
Where age must be checked—and identity should not be kept.
Laurel Secure is for age-gated entry, sale, and handoff workflows that need a clear result without creating a patron identity record.
01 · Age-gated settings
One privacy boundary across different checkpoints.
The setting changes. The mechanism does not: verify on-device, then pass only one of three outcomes across the boundary.
Events
Age-restricted venues
Apply the same three-outcome check wherever entry has an age threshold.
Retail
Liquor & tobacco
Receive an age decision at the point of sale without receiving identity fields.
Regulated retail
Cannabis dispensaries
Keep the age-verification result separate from a patron identity or visit profile.
Retail
Adult retail
Answer the age question while identity remains on the patron’s device.
Commerce
Pickup & handoff
Use the same closed outcome set at an age-gated collection or delivery point.
02 · Shared operating truth
Different settings. The same data discipline.
Local
Verification stays on-device
The identity data involved in the check remains on the device.
Minimal
Only the outcome crosses
Pass, fail, or unable to verify is the complete decision vocabulary.
Aggregate
Reports count, not people
Storage is aggregate-only, and day-level buckets stay suppressed below k=3.
03 · Fit check
A digital identity is required for the on-device path.
Laurel Secure’s electronic verification path depends on a supported digital identity on the patron’s device. When that path is unavailable or the result is unable to verify, staff use the business’s established fallback.
The fallback stays outside Laurel Secure. The platform does not create a patron entity or a persistent profile for either path.
Have a different age-gated setting?
Tell us where the check happens and what your team needs from the result.