01About this policy
This policy covers Revelree Access (version 2.0.0, package ca.revelree.accesscontrol), the ticket-scanning application published by Revelree Tickets Inc. (“Revelree”, “we”, “us”). It applies to the app itself — the software installed on a phone or tablet at an event gate.
It is a standalone policy so that it can be read on its own, without needing the rest of our website for context. If you bought a ticket rather than scanned one, the policy that applies to you is our main Privacy Policy.
The app is a barcode reader with a login-by-QR-code. It points a camera at a ticket, asks our server whether that ticket is good, and shows a green or a red screen. It has no ads, no analytics, no tracking, and it never asks where you are.
02Who uses this app
Revelree Access is built for venue and event staff, not for ticket buyers. Attendees never install it; they simply present a ticket to be scanned.
The app collects nothing about the staff member operating it. There is no account, no sign-up, and no password. A device is unlocked for a specific event by scanning an event QR code provided by the organizer. We do not ask for, and the app does not transmit, the operator's name, email address, phone number, or any other personal detail about them.
03Permissions we request
Mobile operating systems require an app to declare every permission it may use. Some of the permissions below are declared by third-party libraries bundled into the app rather than by features we built, and are never actually exercised. We list all of them here, used or not.
Permissions the app actually uses
- Camera — used solely to read QR codes on tickets. No photo or video is ever captured, stored, or transmitted. Decoding happens entirely on the device, and only the decoded QR string is used. The camera feed itself never leaves the phone.
- Vibration — provides haptic feedback on a scan, so staff can feel an accept or a decline without watching the screen.
- Internet / network access — used to make API calls to Revelree so a scanned ticket can be validated and the result recorded.
Permissions declared but not used
- Microphone (Android RECORD_AUDIO, iOS NSMicrophoneUsageDescription) — declared by the camera library the app depends on, but not used. To state it plainly: the app records no audio, ever. It does not listen, it does not capture sound alongside a scan, and no audio of any kind is stored or transmitted.
- Face ID usage description (iOS) — declared by a bundled library, but not used. The app has no biometric feature and does not request Face ID.
Permissions the app does not request at all
- Location — no location permission of any kind is requested, at any precision, in the foreground or the background. The app does not know or record where a device is.
- Notifications — the app sends no push notifications and requests no notification permission.
- Contacts — the app does not request or read the device's contacts.
04Information the app receives
The app is a window onto data that already lives in the organizer's Revelree account. When staff use a feature, our server sends down only what that screen needs:
- Ticket scans: the attendee name, ticket type, and order ID associated with the scanned ticket, along with the accept or decline result.
- Manual ticket lookup: attendee names, ticket status, order IDs, and ticket types, so staff can find a ticket when a code will not scan.
- Will call lists: guest first and last name, phone number, notes, and ticket counts for guests collecting tickets at the door.
- Aggregate event statistics: counts and totals for the event as a whole. These are not personal information.
This information belongs to the event organizer, who is the party that collected it when the ticket was sold. Revelree processes it on the organizer's behalf so that their staff can admit people to their event.
05Data stored on the device
Two things are written to storage on the device itself:
- A session record for the event the device is currently unlocked for. This is cleared when staff switch to a different event.
- A scan history of up to 200 records per event. Each record contains the attendee name, ticket type, order ID, timestamp, and scan result.
The scan history is stored unencrypted in the app's private storage area. It is not cleared when staff switch events, and it remains on the device until the app is uninstalled. Uninstalling the app removes it. Devices used for scanning should be treated as devices that hold attendee information, and should be protected with a device passcode and wiped before being passed on or retired.
Will call lists and manual lookup results are handled differently: they are held in memory only and are gone as soon as the screen is closed. They are never written to storage.
06What the app does not do
Much of what a typical mobile app does, this one deliberately does not. Specifically:
- No advertising, analytics, crash reporting, or tracking SDKs of any kind are included in the app. There are no third-party measurement tools embedded in it.
- No device identifiers are read or transmitted — no advertising ID, no installation ID, and no other device or hardware identifier.
- No data is sold, and none is shared with third parties. We do not sell personal information, and there are no advertising or data-broker relationships attached to this app.
- No push notifications are sent by the app.
- No user profiles are built. Nothing in the app tracks an attendee across events or over time for marketing purposes.
07Transmission and storage
All data moving between the app and our servers is transmitted over HTTPS to www.revelreetickets.com. The connection is encrypted in transit.
Data received by our servers is processed and stored in Canada, under the same protections described in our main Privacy Policy.
08Retention and deletion
On the device, retention works as described in Section 5: the session record clears when staff switch events, will call and lookup data disappears when the screen closes, and the scan history persists until the app is uninstalled. Uninstalling Revelree Access removes all data the app has stored locally.
Requesting deletion of your personal data
If you are an attendee and you want the personal information associated with your tickets deleted, email privacy@revelreetickets.com from the email address on your order, or write to us at the mailing address in Section 11. Tell us which event you attended so we can locate your records.
We will respond within 30 days. Some records must be retained to meet Canadian financial recordkeeping requirements, and some are held by the event organizer as the party that sold you the ticket — where that is the case, we will tell you which records those are and put you in touch with the organizer. Data already copied into a device's local scan history is removed when that device's app is uninstalled.
09Information for attendees
If you are an attendee whose ticket was scanned by this app, this policy describes only the scanning step at the gate. The fuller picture — what we collect when you buy a ticket, how we share it with the event organizer, how long we keep it, and the privacy rights you have under PIPEDA and Quebec's Law 25 — is in our main Privacy Policy. Please read it as well; it is the policy that governs your ticket purchase.
10Changes to this policy
We update this policy when the app changes. When we make material changes, we post the new version here and update the “Last updated” date at the top. The current version always lives at www.revelreetickets.com/privacy/revelree-access.
11How to contact us
Questions about this app, or a privacy request? Reach our Privacy Office:
Revelree Tickets Inc.
Attn: Privacy Office
Email: privacy@revelreetickets.com
Mail: 4154 Petrolia Line, Petrolia, ON, Canada N0N 1R0
If you are not satisfied with our response, you have the right to file a complaint with the Office of the Privacy Commissioner of Canada at priv.gc.ca.
