How TicketTrails handles your information.
This policy covers the main ways Trailtech Group Limited collects, uses, shares, and retains data through TicketTrails. It is written to be read, so if anything here is unclear, contact us and we will explain it.
Operated by Trailtech Group Limited. These are plain-language summaries, not a substitute for the signed agreement.
Who Operates TicketTrails
TicketTrails is a product of Trailtech Group Limited. This policy explains how we collect, use, and protect information when you browse the platform, create an account, buy a ticket, host an event, or contact support.
Where an event runs on a country franchise of the platform, that franchise may act as a separate controller for the information its own event requires. The organizer named on the event page is the first place to take a question about that event's data.
Information We Collect
We collect what the platform needs to take a booking, admit an attendee, and settle a payout. That means account details, order and ticket details, payment references rather than card numbers, support messages, and device and browser data.
- Account and profile details you give us, such as name, email, and phone number.
- Order, ticket, and check-in records created when you transact with an event.
- Payment references and gateway outcomes. Full card numbers never reach our servers.
- Device, browser, and IP data used for security, fraud checks, and rate limiting.
- If you accept analytics cookies, we record your IP address, public page path, and visit times for site and blog readership reports. These reports are available only to administrators.
- Cookie preferences and, when you allow advertising cookies, identifiers used to serve and measure ads on blog pages.
- Event participation records such as scans, seat assignments, and transfers.
How We Use Information
We use data to process purchases, deliver tickets, manage event access, prevent fraud, send operational updates, answer support requests, and improve the product.
We do not use ticket-holder data to build advertising profiles, and we do not sell personal data as a business model. If you allow advertising cookies, Google AdSense may use cookies and similar identifiers to serve and measure ads on blog pages, and may personalize ads according to your consent and Google account or browser settings.
- Taking payment, issuing tickets, and settling payouts to organizers.
- Admitting attendees and preventing duplicate or forged entry.
- Detecting fraud and abuse, including automated pattern checks on orders.
- Measuring consented site visits and blog readership for internal reporting. The admin report uses a rolling 90-day window and removes older IP-based records when it is loaded.
- Sending operational messages about an order or event you are part of.
Security and Retention
We apply technical and organizational safeguards to protect personal information, and keep records only as long as they are needed for service delivery, compliance, dispute resolution, or legitimate operational needs.
Visitor analytics are visible only to ADMIN and SUPERADMIN accounts. The visitor report removes IP-based records older than 90 days when an administrator loads it.
API secrets are stored as a one-way hash. A full API key is shown once at creation and cannot be retrieved afterwards.
Your Choices and Contact
You can contact us for help with account access, a privacy question, or a request to review, correct, or delete information. We will respond within the timeframe applicable law requires, and we will tell you plainly if a request cannot be met and why.
Where your information is held by an event organizer rather than by us, we will point you to them, because they are the controller for that record.
- Ask what information we hold about you.
- Ask us to correct information that is wrong.
- Ask us to delete information we no longer need to keep.
- Object to, or restrict, a use of your information where the law gives you that right.
- Change optional analytics, personalization, and advertising choices using Cookie preferences on the site.
Questions about this document?
Email support@tickettrails.com or open the support center. Quote the section number so we can route it to the right team.