Zero identity logging
Only age-outcome aggregates reach the platform — never a name, never a document. That keeps patron identity outside your operational data footprint.
Laurel Secure
Laurel Secure verifies age at the threshold and forwards only an age-check outcome: pass, fail, or unable to verify. Names, birthdates, and document numbers never leave the reader — your venue gets operational truth without entering identity-logging scope.
IDENTITY_RETAINED = FALSE, enforced by architecture
01 — WHY OPERATORS SWITCH
Only age-outcome aggregates reach the platform — never a name, never a document. That keeps patron identity outside your operational data footprint.
Connectivity, battery, and trust-material state for every reader — visible from a phone behind the bar before a device dies mid-shift.
Owners, admins, operators, installers, support — each sees exactly the screens their shift requires, nothing else.
0
Patron identity fields stored, ever
k=3
Minimum day-bucket size before aggregate reports render
3
Allowed outcomes: pass, fail, or unable to verify
1
Age-check outcome crosses the device boundary
02 — THE BOUNDARY IS THE PRODUCT
Most vendors promise not to keep identity data. Laurel Secure is built so it structurally cannot — the data model has no columns for it, the API contracts have no fields for it, and day-bucketed reports suppress groups below k=3.
Verification results are stored as counters — there is no per-person row to exist.
Any reporting bucket below threshold is suppressed before it can render, anywhere.
The platform sees trust-material state, never credential material itself.
Tell us about your venues and we'll scope a pilot around your locations and timeline.