Privacy across Tickgetr and the scan app

This page covers the Tickgetr website, organiser dashboard and mobile Tickgetr scanner for Android and iOS. Tickgetr is the trade name of Daan Deltour, sole proprietorship, company number 1016.507.441, Lombaardstraat 14, 8900 Ieper, Belgium. Privacy contact: info@tickgetr.be.

The organiser determines the purposes and required attendee data for their event and acts as its controller. Tickgetr processes ticket and scanning data on their behalf as processor. Tickgetr is controller for its own account management, invoicing, security and optional website analytics.

The app signs in through Firebase Authentication with an anonymous app user identifier. The scanner API verifies that identity and derives a separate, opaque device binding for the scanner roster. Firebase may also process technical authentication, integrity and security information such as IP address, user agent and app identifier.

The event code is used only to request access. Only after organiser approval does the device receive a short-lived scanner session and a device- and event-bound offline package.

• For all tickets in the linked event: name, buyer email, ticket type, ticket number, number of tickets in the order, validity state and any first scan time.
• An opaque order reference shows which tickets belong to the same order. The app does not receive the original order or payment identifier for this purpose.
• Event, enrollment, session, epoch and manifest identifiers and their expiry boundaries to restrict access to the correct event and device.
• For a scan attempt: an opaque ticket reference, keyed QR hash, unique attempt ID, scan time and outcome.
• A Firebase App Check integrity token and technical connectivity and synchronisation state needed to admit only genuine app builds, fail closed and safely process pending offline scans.
• The scanner receives no phone number, ticket price, bank details or raw ticket QR. Buyer email and the opaque order reference are used only in attendee details.

• Authenticate a scanner and restrict it to its enrolled event.
• Show enough ticket information to verify the attendee at the entrance.
• Validate a ticket, record admission and warn about invalid or duplicate scans.
• Keep scanning available during a temporary connection loss and synchronise pending changes afterwards.
• Investigate support, reliability and security incidents.

An approved scanner stores an AES-GCM-encrypted offline package containing the full event ticket list. Its encryption key is held separately in the device's secure storage. The routing index contains only ticket references and QR hashes; ticket records contain the limited attendee details listed above.

A raw QR is used only briefly in memory to calculate a keyed hash locally. The app does not store or transmit the complete QR. Before showing a green offline result, it stores an encrypted pending attempt containing an opaque ticket reference and QR hash.

The manifest remains usable for at most twelve hours and never beyond the active scanner roster; temporary attendee data has a separate short TTL. After expiry, the app refuses offline green and removes expired manifest and attendee data. Pending scan attempts remain until server acknowledgement so an admission action is not silently lost.

Choosing End Session removes the session, enrollment binding and encrypted event cache from that device. Organisers should use managed, locked devices and end the session after entry closes.

Firebase Authentication and Google infrastructure support accounts and event data; Railway supports the website and API. Amazon Web Services SES supports transactional email. Firebase App Check uses Google Play Integrity on Android and Apple App Attest, with DeviceCheck as fallback, on iOS. These services may process technical authentication, app, device and integrity information.

Digiteal is our payment partner. We provide the required organisation, contact, banking and verification details for onboarding and payments. Digiteal may also process these under its own legal obligations; payment verification is not marketing consent.

Google Maps supports address suggestions when you use that feature. Google Analytics measures public website pages after your separate cookie choice. Google's tracking code is not loaded on account, administration, ticket checkout or scanning pages. We measure pages, limited clicks and scrolling, and whether the contact form is started, sent or encounters an error. We do not include names, email addresses, form content, banking details, ticket codes or order references. We do not use session recordings. Change your choice through Cookie preferences at the bottom of the website.

Event data is available to the organiser and their approved scanning devices. Each device receives the full ticket list for offline operation, so buyer email addresses are visible to authorised entrance staff. Do not share pairing codes, scanner sessions or attendee lists outside that team.

Providers may process data outside the European Economic Area. Such transfers require the applicable GDPR safeguards, such as a valid adequacy decision or standard contractual clauses. Contact info@tickgetr.be for information about the providers and safeguards applicable to your data.

Invoices, accounting evidence and necessary payment records are retained for applicable tax obligations. The usual legal retention period for Belgian VAT documents is ten years, starting on 1 January following their issue or the closing of the books. This does not mean all attendee or scanning data is needed for ten years.

Other account, event, ticket and support information is retained while needed for the service, refunds, disputes or a documented obligation. There is currently no universal automatically enforced retention period for all server records. Deletion requests are reviewed; financial evidence is not blindly erased together with an account.

Email info@tickgetr.be with the subject Privacy request for access, correction or deletion. Include only the email address, event name and order reference needed to find the record. Do not send passwords, active scanner codes or complete QR codes. We may request proportionate identity verification.

Operational change and administrator audit logs are limited to necessary metadata and intended for a maximum retention of 365 days. Automated cleanup requires an active server task; this does not shorten retention of the original financial evidence.

Account and order services use the data required to perform the contract. Invoicing and mandatory payment checks serve legal obligations. Security, incident investigation and necessary support may rely on legitimate interests, taking your rights and data minimisation into account.

Website analytics requires your separate consent. Organisers may receive a review request two days after their event and a reminder for the next edition ten months later. We use valid specific consent or the existing-customer exception for our own similar ticketing service: when you directly provide your organisation contact address, we explain this use and offer an easy, free opt-out. Without that recorded collection notice and an actually used ticketing service, there is no automatic basis for sending these emails. Existing withdrawals remain in force; old profiles and events are not enrolled retrospectively. Opt out alongside the contact address, through the link in each message or via info@tickgetr.be. We retain minimal withdrawal evidence to honour your request. Transactional ticket, payment and account messages remain separate.

After analytics consent, Google Analytics processes pages, campaigns, limited interactions and technical visit information using a random visitor ID. These records are not fully anonymous. Visitors may decline or block tracking, so the counts are not a complete visitor register. We do not enable advertising personalisation or Google Signals. Withdrawal stops measurement; website-accessible cookies are cleared on your device.

You can request access, correction, erasure, restriction or portability where the GDPR grants that right in your circumstances. You can object to processing based on legitimate interests; objections to direct marketing are respected. You can withdraw consent at any time without affecting earlier lawful processing.

We normally respond within one month. The GDPR permits an extension for complex requests; we inform you within that first month. You may also complain to the Belgian Data Protection Authority through dataprotectionauthority.be. The organiser may be the appropriate contact for data relating to a specific event.

This page is updated when the website, scanner app or its data flows materially change. Questions about this notice or an event data request can be sent to info@tickgetr.be.