Sealed ticketing
Dynamic tickets designed to limit duplication, support offline admission checks and govern resale.
| Version | 2.0 — 15 September 2026 |
|---|---|
| Intended audience | Technical, security, integration and partner teams |
| Status | Technical description based on public information; implementation parameters to be confirmed |
Purpose and scope
Reduce the value of a static ticket capture and allow the producer and venue jointly to apply resale rules, without requiring Seal to retain the buyer’s name.
Operating principle
- A ticket is issued with a dynamic identifier or code bound to its admission rights.
- The code changes so that an old photo or capture loses operational validity.
- At entry, the checking device validates the ticket using data and keys provisioned for online or offline mode.
- The first valid use and concurrent attempts are handled under the admission policy.
- Resale above face value remains disabled unless the producer and venue jointly agree.
Targeted threats
- Duplication by screenshot
- Multiple sale of the same ticket
- Ticket counterfeiting
- Resale above the authorised price
Components and responsibilities
| Component | Role |
|---|---|
| Verified organisation or publisher | Establishes identity, channels or domains and manages authorised people. |
| User or approver | Presents live evidence or participates in authorisation under policy. |
| Seal service | Evaluates necessary verification elements and returns a result limited to the use case. |
| Integrating system | Binds the Seal result to the exact action, applies business rules and retains required audit data. |
| Verifier | Checks the result in context and does not interpret it as a guarantee of truth. |
Data and privacy
The stated public principle is data minimisation: no GPS, biometrics or cameras for identity and presence modules; local browser computation when a media or document module processes a file; and retention of irreversible fingerprints and limited metadata rather than source content. The exact fields, retention periods, logs, subprocessors and transfers must be confirmed in a data-processing appendix.
Expected security properties
- Temporal freshness of live evidence
- Separation of roles and factors
- Binding of the result to the context or action
- Minimisation and non-disclosure of source content
- Proportionate traceability without turning Seal into a central identity database
Limitations and assumptions
- Offline mode requires rigorous provisioning, key management and later synchronisation.
- Real-time relay attacks and simultaneous admission attempts must be addressed explicitly.
- Resale rules depend on integration with ticketing systems and the applicable legal framework.
Items to confirm before integration
- API, request and response schemas, authentication and quotas
- Applicable algorithms, key lengths, entropy sources and rotation
- Time tolerances, clock synchronisation and expiration handling
- Error handling, revocation, recovery and service continuity
- Logging, retention, location, deletion and regulatory obligations
- Penetration testing, independent cryptographic review and vulnerability disclosure process
Public references
- https://seal.lifaio.com/go
- https://lifaio.com/seal-lifaio/
Notice: this document describes the publicly communicated conceptual operation. It does not replace an API specification, cryptographic analysis or independent security audit.
UK patent applications pending: GB2619490.2 · GB2619948.9 · GB2620153.3 · GB2620211.9 · GB2620220.0 · GB2620253.1 · GB2620315.8 · GB2620629.2 · GB2621074.0 · GB2621382.7 · GB2622122.6 · GB2622135.8
