SafePass Privacy Policy
SafePass is a physical access-control tool for organisations that manage their devices with a mobile device management (MDM) system such as Jamf Pro. This policy explains what the apps do with data. In short: the developer collects nothing. There are no accounts, no analytics, no advertising and no tracking.
SafePass Gate (client app)
The app shows a short-lived, encrypted QR code that identifies the device to a gate guard. The identifiers inside it (device serial number, device identifier and MDM record ID) are supplied to the app by the device owner's organisation through its MDM's managed app configuration. The QR code is generated on the device and refreshes every 60 seconds. The app makes no network connections and sends no data anywhere. The data reaches anyone only when a guard scans the code on screen.
SafePass Admin (gate app)
The admin app uses the camera only to scan SafePass QR codes. Camera images are processed on the device and are never stored or transmitted. After a scan, the app decrypts the code and sends the device identifiers to your organisation's own device management service (Jamf Pro or Jamf Manager for Android), using the server address and credentials your organisation configures. The organisation can optionally configure a scan-log endpoint that it runs itself. Neither the developer nor any third party receives this data.
Data the developer receives
None. The developer runs no servers for these apps and has no access to the identifiers, scan events or credentials they handle. Apple may provide anonymised crash and usage statistics to developers when a user has opted in to share them with app developers. These contain no personal data.
Your organisation
Your organisation decides what is configured on its devices and how its MDM and any scan log store and use data. For questions about that, contact your IT administrator. Your organisation's own privacy policy governs that data.
Children
SafePass is a workplace tool and is not directed at children.
Changes
If this policy changes, the updated version will be posted on this page with a new date.
Contact
Kavankumar Joshi · joshikavan92@gmail.com