TicketMee Gate is an event access-control application operated by WebMee, used by event staff to check in ticket holders. This policy explains what data the app collects, why, and how it is handled.

1. Your Account (Gate Staff)

Email and password, or Google Sign-In (which shares your name, email address, and Google account ID with us) - used to authenticate you.
Your access session is cached securely on-device (Android Keystore / iOS Keychain) so you stay signed in.
Your role and assigned event are stored server-side against your account.

2. Attendee & Ticket Data

When you scan or search for a ticket, the app fetches and displays that attendee's name, email, ticket type, and check-in status from your organisation's TicketMee account, so you can verify the right person is being admitted. This data belongs to your organisation, not to you or WebMee, and is only shown for tickets you actively look up - the app does not download or store attendee lists in bulk.

For ticket types that require ID verification, the app shows a text answer the attendee already provided at checkout (e.g. a student or staff ID number) for you to visually compare against their physical ID. No photo or scan of any ID document is taken or stored by the app.

3. Scan & Audit Records

Each check-in you perform (ticket ID, timestamp, gate, entry/exit mode, and any gate-question or ID-verification outcome) is sent to and logged against your organisation's account, for entry auditing purposes.

4. Camera Permission

The app requests access to your device camera solely to scan QR codes on event tickets. Camera frames are processed on-device to decode the QR code and are never saved or transmitted.

5. Push Notifications

The app registers your device for push notifications (via Firebase Cloud Messaging) so event admins can send you broadcast messages, such as gate instructions. This registration shares a device token with Google Firebase; no attendee data is included.

6. Offline Storage

When your device is offline, scan queue data is temporarily stored in the app's private local storage, which other apps cannot access. Once connectivity is restored, this data is synced to the server and then cleared from your device.

7. Diagnostics & Crash Reports

If the app crashes or encounters an error, Firebase Crashlytics automatically sends a crash report to Google, including your device model, OS version, app version, and the error details. These reports do not include attendee personal data.

8. Data Sharing

We do not sell your data or share it with third parties for advertising. Data is only shared with Google Firebase (authentication, crash reporting, and push notifications) as needed to operate the app, and with your organisation's TicketMee account.

9. Data Retention

Your account data is retained for as long as your organisation maintains an active TicketMee account. You may request deletion by contacting support.

10. Contact

For any privacy-related questions, please contact: support@webmee.tech