#
Cryptographic generation
GateCodes and private share tokens are generated server-side using secure randomness rather than predictable browser randomness.
SECURITY OVERVIEW
Temporary authority should be live, scoped and revocable.
GateCode is designed so the visible code is useful without turning the collector into a permanent account holder. Organisations verify against the live service, while account and organisation boundaries stay enforced on the server.
Live verification modelSERVER CHECK
CredentialFriendly GateCode
ValidationCurrent server state
OrganisationScoped access
LifecycleUpcoming · Active · Revoked · Expired
Offline safety: a previously displayed valid result is not treated as fresh authority. Operational verification requires the live service.
Security is enforced by the backend, not by presentation alone.
⌁
Private share-token hashing
Optional collector-pass secrets are looked up through hashes so the database does not need to retain the raw share secret.
▣
Secure account sessions
Authenticated sessions use server-managed tokens and HttpOnly cookies, with mutation requests protected by same-origin checks.
◎
Organisation scoping
Verification, administration, school data and reports derive their organisation context from authorised server-side membership.
×
Immediate revocation
Revocation changes the live permission state. A collector-pass refresh or organisation verification sees that current state.
≡
Auditable events
Creation, sharing, opening, verification and revocation activity can be recorded as events without treating verification as collection confirmation.
Designed to avoid stale or over-broad authority.
GateCode keeps temporary permissions time-bound and keeps customer operational data separated by organisation and enterprise access.
✓Verification APIs are network-only in the installed PWA.
✓QR scanning resolves through the same server verification logic as typed codes.
✓Role permissions distinguish Owner, Admin, Staff and View-only access.
✓Enterprise site switching is authorised server-side before context changes.
✓Master Diagnostic Mode is separated from customer Enterprise access.
✓Central Operations is restricted to the configured platform owner.
SECURITY WITHOUT COLLECTOR FRICTION
Get started →The person collecting still does not need an account.
GateCode keeps the permanent security controls with the authoriser and receiving organisation.