Proof you were there.
Dynamic QR codes that turn a scan into a verified, auditable event.
The problem
A QR code alone proves nothing.
Printed QR codes are copied
A photo of a static code works from anywhere, for as long as the code exists.
Screenshots travel
One person on site can share the code with everyone who is not.
Sign-in sheets lie
A name on paper says nothing about who wrote it, or when.
How it works
Three steps from screen to record.
Step 1
Set up a channel
Pick a template, choose the presence assurance level, and define what happens after an allowed scan.
Step 2
Put a display where it matters
Any screen becomes a display. It shows a code that changes every few seconds and never leaves the room.
Step 3
Every scan is decided and recorded
The server decides Allowed, Flagged or Denied, runs your actions, and appends a hash-chained record.
Presence assurance levels
Choose how much proof a scan needs.
| Level | What it checks | What it stops | Typical use |
|---|---|---|---|
| PAL0 | The entry code is fresh: it changes every few seconds and works once. | Printed copies and old photos of the code. | Event check-in, feedback, low-stakes attendance. |
| PAL1 | PAL0, plus identity bound to a passkey on the phone and soft signals. | Sending the code to someone else to check in for you. | Staff presence, course attendance. |
| PAL2 | The phone reads consecutive challenge frames from the display within a hard time bound. | Screenshots and live relays that arrive too late. | Shift start, controlled areas. |
| PAL3 | An optical loop between phone and display, timed on the display clock, with optional evidence photo. | Remote relays; cheating needs an accomplice on site and leaves evidence. | Guard tours, audits, regulated checks. |
No web technology can prove physical distance on its own; higher levels make cheating require an on-site accomplice and leave evidence.
Templates
Start from a template.
Presence check-in
Record who was present, where and when, with the level of proof you choose.
Gate check
Allow or deny entry against an access list and office hours, decided on the server.
One-time verified link
Open a signed link only for someone standing in front of the display.
Guard tour
Checkpoints in a fixed order with maximum gaps; broken and abandoned runs are flagged.
Custom script
Your own decision logic in a sandbox, versioned, hashed and approved before it runs.
Audit by design
Records you can verify, not just read.
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.
Set up your first channel.
One organization, one display, one phone. The first verified scan takes a few minutes.