Skip to main content
A common question at the gate is whether a visitor could screenshot their QR code and share it with someone else, or reuse an old code to get back in. Rekkeh has layered protections that make this difficult in practice, even though the system does not directly detect screenshots.

​
No screenshot detection

Rekkeh does not have screenshot detection. If a guest takes a photo of their QR code, the image is functionally identical to the original for the life of the pass. The system scans the code, not the screen it appears on.

​
What stops a reused QR

Three checks prevent most reuse scenarios:
  1. Validity window: Guest passes expire after the chosen duration (2 hours to 7 days, depending on how they were created). A screenshot from yesterday will not work today.
  2. Authorization check: Revoked passes are rejected immediately. If the host or admin cancels the invite, the QR becomes invalid regardless of when it was captured.
  3. Workflow check: For single-entry passes, the system records whether the bearer has already checked in. If someone tries to enter again with the same pass, the scanner shows that entry was already granted.

​
Rotating resident pass protection

Resident passes use a rotating QR code that changes every 15 minutes. Even if someone photographs a resident’s screen, the captured code becomes invalid after the current rotation window expires. The Resident app generates a fresh code automatically.

​
Repeated entry is stopped by workflow

If a guest with a multi-entry pass leaves and returns, that is allowed by design. But if someone else tries to use a copied QR after the original bearer has already checked in, the workflow check will flag it. The gate operator sees the prior entry record and can deny admission.

​
Practical rule for operators

When in doubt, scan the code. The Gate Ops app will tell you whether the pass is valid, expired, revoked, or already used. Do not admit someone based on a screenshot alone if the scan result shows any warning or denial.
For the full verification sequence Rekkeh runs at the gate, see How Rekkeh verifies access.