Privacy Policy for the NiceCheckIn Scanner App¶
Last Updated: November 4, 2026
Introduction¶
The NiceCheckIn Scanner app checks tickets at venue entrances. Venue staff pair a phone, tablet or NQuire terminal with their venue's NiceCheckIn account, then scan ticket barcodes, QR codes or NFC wristbands. The app asks the NiceCheckIn service whether each ticket is valid and shows the result.
This policy explains what data the app processes, why, and who is responsible for it.
Who Is Responsible¶
- The venue that uses NiceCheckIn decides which tickets are checked, which devices check them and why. It is the controller under the GDPR for all data in this policy, the device data of staff phones included.
- Aifinity GmbH runs NiceCheckIn and processes this data on the venue's behalf, under a data processing agreement with the venue.
The venue decides the legal basis. For ticket checks this is usually the ticket contract, for device data the venue's legitimate interest in running its entry control.
Ticket holders and venue staff who want to use their privacy rights should contact the venue. We forward requests that reach us to the venue.
Data the App Sends¶
The app sends ticket and device data only to the NiceCheckIn service in the region the venue
uses: the EU (api.nicecheckin.com) or the US (api.us.nicecheckin.com). It also loads the
venue's media, switches venue devices and uses Google ML Kit, as described below.
Ticket scans¶
- The content of each scanned barcode or QR code.
- For NFC wristbands, the ticket ID stored on the band. If the venue checks wristbands by chip number, the band's UID instead.
We use this to check the ticket, record the entry and, where the venue set it up, open a gate.
Device identity and pairing¶
- The Android ID of the device, a random identifier Android creates for this app on this device. It identifies the paired scanner in its requests to the service.
- Pairing requests. A device is paired when venue staff approve a code shown in the app, or scan a pairing QR code from the venue account.
Device status report¶
While paired, the app reports its health every 10 minutes and when the Wi-Fi signal changes: app version, device model and manufacturer, Android version, uptime, free and total memory and storage, whether NFC and the screen are on, network interface names and IP addresses, Wi-Fi signal strength and frequency, and the response time of the service.
The report contains no Wi-Fi network name, no access point address, no MAC address and no location.
Data Stored on the Device¶
- The address of the NiceCheckIn service and the device's access key, in the app's private storage. Android backup and device to device transfer exclude this file.
- Images and videos the venue shows on the scan screen, in the app's cache.
- Scan events with the scanned codes, in the Android system log on the device. The app does not upload this log. On NQuire terminals, the Newland device management can upload it for support.
Permissions¶
| Permission | Why |
|---|---|
| Camera | Scans barcodes and QR codes on phones. The app analyzes images on the device and never sends them. |
| NFC | Reads ticket wristbands. |
| Internet, network state | Talks to the NiceCheckIn service and reports network status. |
| Foreground service (connected device) | Keeps a USB scanner or gate light connected while the app runs. |
| Notifications | Shows that the USB scanner or gate light service runs. |
| Wake lock | Keeps venue videos playing on the scan screen. |
The app does not use location, contacts, the microphone, accounts or the advertising ID. It does not ask for Bluetooth access.
Venue Media and Devices¶
The scan screen shows images and videos the venue chose. The app loads them from the addresses the venue set, which can be outside NiceCheckIn. Those servers see the device's IP address.
After a scan, the NiceCheckIn service can tell the app to switch a gate relay or light in the venue's network. These requests carry only the commands the venue configured, no data from the device. They can use plain HTTP inside the venue's network.
Third Party Services¶
The app uses Google ML Kit to read barcodes from the camera. Barcode detection runs on the device and images are not sent to Google. ML Kit sends usage and diagnostic data about the barcode feature to Google, as described in Google's ML Kit data disclosure.
The app contains no advertising, analytics or crash reporting services.
Data Retention¶
- Validation logs: 90 days.
- Device status: we keep only the latest report, for as long as the venue has a contract with us or the device is registered on our platform.
- Data on the device stays until the app is uninstalled or its data is cleared.
Data Security¶
- All traffic to the NiceCheckIn service uses HTTPS.
- The device access key stays in the app's private storage and is never included in backups or device transfers.
- Each paired device has its own access key.
International Data Transfers¶
The app sends data to the region the venue uses. For venues on the US region, NiceCheckIn processes the data in the United States.
ML Kit sends its usage data to Google, which can process it in the United States. Google is certified under the EU-US Data Privacy Framework.
Children's Privacy¶
The app is a tool for venue staff and is not directed at children. A scanned ticket can belong to a child. The app treats it like any other ticket and learns nothing else about the holder.
Your Rights¶
Under the GDPR you have the right to access, correct, delete and restrict the processing of your data, to data portability and to object. Contact the venue, which is the controller. You can also complain to a data protection authority.
California residents: we do not sell or share personal information.
Delete Your Data¶
- Ticket holders: ask the venue to delete your ticket and entry data. We delete it on the venue's instruction.
- Venue staff and devices: a venue admin removes the device under Devices in NiceCheckIn. This deletes its pairing and its device status report. Uninstalling the app or clearing its data removes everything stored on the device.
- Or email us: write to support@aifinity.io with the venue name. We forward the request to the venue and act on its instruction.
Validation logs are not deleted on request. The venue needs them as a record of how each ticket was used, for example to settle disputes. They are deleted automatically after 90 days.
Changes to This Policy¶
We update this policy when the app or the law changes. The date at the top shows the latest version.
Contact¶
Aifinity GmbH, see the imprint for our address.
Email: support@aifinity.io