Last updated: 28 May 2026
We process shop, product, order, event, ticket, attendee, check-in, and merchant configuration data needed to provide event ticketing, branded ticket generation and delivery, QR code validation, attendance tracking, billing, support, and app setup.
Attendee and customer data can include name, email, optional phone, order identifiers, ticket number, seat or tier assignment, and attendance status (such as check-in time) when required for the app workflow.
We use privacy preserving operational analytics to understand merchant onboarding and app setup. Analytics events are sent server side only, use a hashed shop identifier, and do not include customer personal data, raw order IDs, addresses, phone numbers, emails, IP addresses, user agents, session tokens, or checkout tokens.
We do not use analytics autocapture, session replay, default page tracking, or customer browser tracking for this purpose.
We may use service providers such as PostHog for privacy preserving product analytics, BetterStack or Logtail for application logs, an email delivery provider for sending branded tickets and notifications, Apple Wallet and Google Wallet for ticket pass delivery, and hosting and database providers required to run the application.
We use data only to operate the app, provide requested ticketing features (including ticket generation, delivery, QR code validation, and check-in), improve onboarding, troubleshoot issues, prevent abuse such as duplicate tickets and automated buying, and comply with legal obligations.
We apply reasonable technical and organizational safeguards, including cryptographic signing of QR codes (HMAC-SHA256) to prevent ticket forgery, encryption for sensitive credentials, and restricted access to production systems.
For privacy questions or requests, contact SIA JB Holdings at [email protected].