pass
The mobile credential proves the requested age threshold.
For technology partners
Integrate the age result—not the identity.
Laurel Secure keeps identity data on-device. The boundary exposes only the decision an age-gated workflow needs: pass, fail, or unable to verify.
01 · Boundary output
A closed, human-readable answer set.
Each outcome tells the surrounding workflow what to do without identifying the patron.
fail
The credential answers that the requested age threshold is not met.
unable_to_verify
The reader cannot complete a trustworthy check, so staff use the normal fallback.
02 · Data shape
The privacy boundary remains intact after the check.
Verification
Identity remains on-device
The identity data involved in the check does not cross into the platform.
Storage
Only aggregates persist
Outcome counts are stored in aggregate, with no patron entity or persistent profile.
Reporting
k=3 before rendering
Day-level buckets below three remain suppressed when reports are rendered.
The practical integration boundary is intentionally small: your product can respond to an age-verification outcome without receiving the identity that produced it.
If that boundary fits your workflow, send us the context. We can start with the verification moment and the outcome your system needs to handle.
Exploring an age-verification workflow?
Tell us where the check happens and how your product uses the result.