Deze pagina is juridisch bindend en wordt daarom alleen in het Engels gepubliceerd. De Engelse versie is leidend. Al het andere op tickts is beschikbaar in jouw taal.
Sub-processors
Last updated: 29 October 2026
TICKTS LTD (Company No. 17029682) engages the third-party providers below to help deliver the ticketing service. This page is the current, canonical list of our sub-processors and mirrors the table in our Privacy Policy. For the contractual terms under which we engage them, see our Data Processing Agreement.
| Provider | Purpose | Data Shared | Location |
|---|---|---|---|
| Stripe | Payment processing (Stripe Connect) | Payment details, name, email, transaction data | US (EU SCCs) |
| PayPal (Europe) S.à r.l. et Cie, S.C.A. | Payment processing where an Organiser takes payment through PayPal (PayPal Commerce Platform); the Organiser is the merchant of record | Name, email, transaction data, IP address | EU (Luxembourg) |
| TicketPlan | Optional refund-protection product offered at checkout (policy administration and claim handling) | Name, email, ticket details, event name and date | UK |
| Google Analytics (GA4) & Measurement Protocol | Website analytics and performance monitoring; where an Organiser has enabled it, server-side purchase measurement (Measurement Protocol) | IP address (anonymised), usage data, device info; for a completed purchase where enabled, a SHA-256 hashed email address | US (EU SCCs) |
| Brevo (Sendinblue) | Transactional and marketing email delivery, including open and click tracking via embedded pixels and link rewriting | Name, email address, email engagement events (opens, clicks, bounces) | EU |
| Sentry | Error monitoring and crash reporting | Error data, IP address, browser info | US (EU SCCs) |
| Cloudflare | CDN, DDoS protection, DNS | IP address, request metadata | Global (EU SCCs) |
| Apple Wallet | Digital wallet ticket passes | Ticket data (event name, date, venue), attendee name where provided, barcode token, PassKit metadata for lock-screen previews | US (EU SCCs) |
| Google Wallet | Digital wallet ticket passes | Ticket data (event name, date, venue), attendee name where provided, barcode token, Google Wallet metadata for lock-screen previews | US (EU SCCs) |
| Google Places API | Venue address lookup and validation | Search queries, location data | US (EU SCCs) |
| Google OAuth | Social sign-in (“Continue with Google”) | Name, email address | US (EU SCCs) |
| Apple Sign-In | Social sign-in (“Continue with Apple”) | Name, email address (user may choose to hide email) | US (EU SCCs) |
| Google reCAPTCHA v3 | Bot detection and fraud prevention during registration | IP address, browser behaviour, device data | US (EU SCCs) |
| Meta (Facebook) Pixel & Conversions API | Conversion tracking and advertising attribution, in-browser (Pixel) and server-side (Conversions API); consent required | Page views and device info (Pixel); for a completed purchase, a SHA-256 hashed email address and IP address (Conversions API) | US (EU SCCs) |
| TikTok Pixel & Events API | Conversion tracking and advertising attribution, in-browser (Pixel) and server-side (Events API); consent required | Page views and device info (Pixel); for a completed purchase, a SHA-256 hashed email address and IP address (Events API) | US / Singapore (SCCs) |
| Companies House | Business identity verification for Organiser accounts | Company registration number, business name | UK |
| Cloudways (DigitalOcean) | Application hosting and managed cloud infrastructure | All data stored on the Platform (encrypted at rest) | UK / EU (London region) |
| Anthropic (Claude) | AI writing assistance for Organisers (improving event descriptions) and Organiser AI tooling | Event details and draft text the Organiser submits; not used to train Anthropic’s models | US (UK IDTA / SCCs) |
| Klarna / Clearpay | Optional buy-now-pay-later payment methods offered through Stripe at checkout | Payment and eligibility data you provide to the provider if you choose that payment method | EU / US (via Stripe) |
| Stay22 | Accommodation map embedded on some event pages | IP address and page context if you interact with the map | Canada (UK adequacy) |
| Mailchimp (Intuit) | Optional Organiser integration: where an Organiser connects their own Mailchimp account, their buyers’ details sync to that Organiser’s audience (Organiser-directed; the Organiser is the controller) | Name, email, order context | US (UK IDTA / SCCs) |
Organiser-directed marketing and conversion tools. Where an Organiser chooses to connect their own marketing or conversion-tracking accounts, those providers, currently Meta (Conversions API), Google Ads, TikTok (Pixel and Events API) and Mailchimp, are engaged at that Organiser’s direction and only for that Organiser’s events. In those cases the Organiser is the controller for that processing and is responsible for their own relationship with the provider, as set out in our Data Processing Agreement. Where these server-side conversion tools are enabled, and only where the buyer has accepted advertising cookies, a completed purchase is sent from our server to the provider as a SHA-256 hashed email address and (for Meta and TikTok) the buyer’s IP address, de-duplicated with the in-browser pixels.
Changes to this list. This page is kept current. We will update it whenever we add or replace a sub-processor. Organisers acting as data controllers may object to a new sub-processor on reasonable data-protection grounds by emailing [email protected].
