How it works

A scan becomes a decision, then a record.

Every trust decision is made on the server. The phone and the display only supply evidence.

Three steps

  1. Set up a channel

    Pick a template, choose the presence assurance level, and define what happens after an allowed scan.

  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.

  3. Every scan is decided and recorded

    The server decides Allowed, Flagged or Denied, runs your actions, and appends a hash-chained record.

The lifecycle of one scan

  1. 01Entry codeThe display shows a code that is valid for one slot of a few seconds and can be used once.
  2. 02Session openThe phone opens a scan session on the server. Nothing is consumed by just loading the page.
  3. 03IdentityDepending on the channel: a short form, or a passkey bound to the person's account.
  4. 04EvidenceAt PAL2 the phone reads challenge frames; at PAL3 phone and display complete a timed optical loop.
  5. 05CommitThe server evaluates all signals against the display's calibrated thresholds and records Allowed, Flagged or Denied.
  6. 06PipelineFor allowed scans your actions run in order: redirect, presence record, gate decision, webhook, email, script.

Presence assurance levels

LevelWhat it checksWhat it stopsTypical use
PAL0The 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.
PAL1PAL0, 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.
PAL2The 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.
PAL3An 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.

Calibration

Before a channel can run at PAL2 or PAL3, each display collects honest sample scans on site. Thresholds come from the measured latencies (p99 plus a margin), so decisions reflect that screen, that camera and that room.