App Terms

About the app

The RaveTickets scanner app pairs to an event with a pair code and keeps a device session. It does not create a personal user account on the device. Organizers manage events and staff on the RaveTickets platform at ravetickets.nl.

Permissions and on-device data

• Camera: to scan ticket QR codes. Camera images are processed on the device to read the code and are not stored or uploaded.
• NFC and location (Android): required for in-person card payments. On Android, Stripe Tap to Pay will not start without location access, so the app requests it for that purpose.
• Offline ticket cache: the app stores the event's ticket identifiers and a one-way check value for each QR code (older app versions: the QR signature), from 24 hours before a ticket becomes valid, the name of each personalized ticket holder, a log of accepted scans, a list of recent scans, and any pending scans, on the device so the door keeps working without a connection. Scans that were accepted offline and not yet sent are kept in the app's document directory and stay on the device until they are sent or the user deletes them, also after log out, a replaced pairing or an expired session. Once a pending scan has been sent, its entry keeps only the ticket identifier, time and result, until the door session ends. The cached ticket data, the accept log and the recent list are kept in the app's cache directory, which is not included in iCloud or Android backups (Android backups are switched off for the app). The cached ticket data is limited to the active event and is removed when the app loads a different event, and all of this cached data is removed when the door session ends (at log out, when the pairing is replaced or when the session expires).
• Clipboard: when staff tap Paste, the app reads the clipboard only to fill in the pair code. It is not stored.
• In-person card payments: card-present payments are taken with Stripe Tap to Pay. Card data is handled by Stripe and Apple and never reaches the app or our servers.
• Door-sale placeholder email: an in-person sale is recorded with a placeholder email so the order can be processed without collecting a buyer email at the door.
• Local notifications: the app may show a local notification, for example if a card is declined or times out while the app is in the background. These are on-device only.

Crash reports

When the scanner app crashes, it sends a diagnostic report to our own servers (errors.ravetickets.nl) so we can find and fix the problem. The report contains the error and its technical context: the app version, the operating system, the device model, and the action in progress when it happened. It does not include ticket data, scanned QR codes, payment details, or personal data of buyers or guests. Reports are kept for up to 90 days, and in our encrypted backups for up to about 14 months, and are used only to improve the app.

App updates

The scanner app can receive updates to its app code directly, without an app store release, so an urgent fix reaches the door quickly. Each time the app starts, it asks the update service of Expo (expo.dev) whether an update is available and downloads it in the background. Expo receives the phone's IP address and technical details: the operating system, the version of the app code and the update channel, a random identifier for the app installation and, after an update failed to start, the technical error message of that failure. No ticket, guest, payment or account data is sent. A downloaded update is used the next time the app starts. The app never restarts by itself while it is paired to a door; on the pair screen it may offer to restart when an update is ready.

Acceptable use

Use the app only to check tickets and take payments for events you are authorized to work, and follow our Acceptable Use Policy. Do not share pair codes or attempt to admit guests with copied or duplicated QR codes.

Related terms and data

Platform use is governed by the Terms of Service. How we handle personal data, including the data above and how to request deletion, is described in the Privacy Policy.