Privacy
Last updated: October 20, 2026
Who is responsible
Your community, or the company it appoints, runs this QR Check-In deployment and decides how it is used. Questions about your data go to your community administrator.
Residents, guards and administrators
For each account the service stores a name, an email address, a password hash (never the password), a preferred language and your role, units or gates in each community. When you sign in, your session is stored on the server together with the IP address and the browser or device name, so that sessions can be reviewed and ended.
Guests
For each guest pass the service stores the display name the resident entered, a category, the time window and, only if the resident adds them, a vehicle plate and a short note. No ID documents, photos, phone numbers or email addresses of guests are collected. The QR code contains a random token and no personal data.
Gate activity
Each scan records the time, the gate, the guard, the result and the related pass. Administrative changes are recorded in an audit log. These records cannot be edited.
How the data is used
Only to run the service: to decide entry and exit, to show residents their guests, to give guards and administrators the information they need, and to protect the service against misuse. IP addresses are used briefly for rate limiting.
How long it is kept
Each community sets a retention period, 365 days by default. Closed visits, their passes and events older than that are deleted by the operator's retention job.
Where the data is kept
Data stays in the deployment run by your community's operator. QR Check-In includes no third-party analytics, advertising or crash-reporting services. Exports are created only by community administrators and never contain QR tokens.
Your choices
Ask your community administrator to see, correct or remove your data, or to end your sessions. Residents can revoke their own guest passes at any time before they are used.