Security
Built to be checked, not trusted.
QRChannels records what happened in a way that can be verified later, and keeps as little personal data as the check requires.
Audit by design
Hash-chained records
Every scan and every admin change is appended to a per-organization chain. One button recomputes it and shows the first broken link, if any.
Immutable script versions
Script versions are numbered, hashed with SHA-256 and frozen. Live channels only run versions approved by a second person.
Exports with manifest
CSV and JSON exports ship with a manifest of row counts, file hashes and the head hash of each chain at export time.
Evidence photos, break-glass only
Photos are encrypted on the display. Viewing needs an admin, a written reason and an audit entry. They are deleted automatically after the retention period.
Practices
- Server-side decisions
- Phones and displays never decide. Client clocks are never used for hard time bounds.
- Display keys
- Each display holds a non-extractable key in the browser. Keys can be rotated; the previous key stays valid for 60 seconds.
- Secrets stay server-side
- Display keys, session keys, webhook secrets and signing secrets are encrypted at rest and never shown again after creation.
- Signed outputs
- Redirects and webhooks carry HMAC signatures your systems can verify.
- No raw IP addresses
- IPs are stored only as salted hashes with a daily salt.
- Tenant isolation
- Every record belongs to one organization; access is checked by role on every read and write.
- Retention
- Raw fields such as user agents and signal details are purged after the organization's retention period. Aggregates remain.
- No face recognition
- Evidence photos are never analysed automatically. There are no thumbnails.
- Browser hardening
- Content Security Policy, no referrer on scan pages, and rate limits on every public endpoint.
Limits
No web technology can prove physical distance on its own; higher levels make cheating require an on-site accomplice and leave evidence.