Photos and IDs are police-only
Guest photos and ID scans can only be opened from the police dashboard, by a signed-in officer. The partner app and the SafeAI assistant cannot see, fetch or show them.
Security & privacy
Guest data, only where it belongs.
Safe CheckIn handles identity documents, so it is built to keep them from anyone who doesn't need them. The front desk captures them; the police can view them; everyone else is kept out.
Safeguards
Built into the platform.
Every view is logged
Each time an officer opens a guest photo or ID scan, the view is recorded in the audit log.
ID numbers are masked for the desk
The partner app shows ID numbers masked, like XXXX-XXXX-1234. Only police see the full number.
Nothing left on the device
Captured photos are cleared from the front-desk device as soon as the check-in is saved.
Two-step police sign-in
A correct password is not enough. Officers must also enter a one-time passcode, valid for five minutes and limited to five attempts.
Limits on sign-in attempts
Sign-in and passcode checks are rate limited separately, which slows down password guessing.
Evidence with a fingerprint
Every evidence file gets a SHA-256 fingerprint when it is uploaded. Each download re-checks it and logs whether the file is unchanged.
No open file storage
Uploaded files are never served publicly. They are only reachable through signed-in, permission-checked requests.
Strong signing keys required
The server refuses to start without a strong secret for signing sign-in tokens. There is no default to fall back on.
Who sees what
| Data | Front desk | Police | SafeAI |
|---|---|---|---|
| Guest name and stay details | Yes | Yes | Yes |
| ID number | Masked | Full | Masked |
| Guest photo and ID scans | No | Yes, logged | No |
Questions about security?
We're happy to walk your team through how Safe CheckIn handles guest data.