About
We think people at events deserve one identity, not twenty logins
Events run on dozens of independent systems: registration, exhibitor manuals, stand builders, caterers, lead capture, event apps. Each one rebuilds the same picture of who is who. EventID gives the industry one shared, trustworthy answer.
What we believe
Identity is infrastructure
It should be boring, standard and dependable. That's why EventID speaks plain OpenID Connect rather than a proprietary SDK.
The person stays in control
Every app is approved by the person using it. They can see what each one receives and take it back.
Context matters as much as identity
Knowing someone's email isn't enough. Suppliers need to know which company they represent and which event they're at.
Security and privacy
How we handle data
- Where
- All personal information is stored in AWS Sydney (ap-southeast-2). Backups stay in Australia.
- Who decides
- EventID is the data controller for the identities it holds, and works to the Australian Privacy Principles.
- What apps see
- Only what the person consents to and the organiser grants. Each app gets its own pairwise identifier.
- How we sign people in
- Passkeys, email one-time codes, optional passwords checked against known breaches, and authenticator-app MFA. Admins must use a passkey or authenticator.
- What we record
- Sign-ins, membership changes, grants and data access, in an append-only, hash-chained audit log.
- This website
- Has no cookies, analytics or trackers. If you email us, we use your message only to reply.
Want to help shape it?
We're looking for organisers and suppliers to pilot EventID with. We'd love to hear about your events.