We engage the following subprocessors to provide the platform. Each is bound by a data processing agreement. Primary processing and storage take place in the EU. For providers with any processing outside the EEA, we rely on the EU–US Data Privacy Framework (for certified recipients) and/or the EU Standard Contractual Clauses, with the SCCs applying automatically if the adequacy decision ceases to be valid.
| Provider | Purpose | Data involved | Location | Transfer mechanism |
|---|---|---|---|---|
| Amazon Web Services EMEA SARL | Hosting, storage, key management (KMS) | All platform data | EU (Frankfurt, eu-central-1) | EU processing; DPF + SCCs for support edge cases |
| Mailgun (Sinch) | Transactional email delivery | Recipient name, email, email content incl. tickets | EU region | DPF + SCCs (parent) |
| Cloudflare | Website delivery, bot protection (Turnstile) | IP address, request metadata, Turnstile tokens | Global edge, EU-preferred | DPF + SCCs |
| Prelude (Ding SAS) | Verification SMS | Phone number, locale | EU (France) | EU processing |
| MaxMind | IP geolocation and anonymizer checks for fraud prevention | IP address | US | DPF + SCCs |
| OpenAI | Drafting and classifying sponsor outreach emails | Sponsor company data (name, contact person, website text, donation history) — never buyer data | US | DPF + SCCs; no training on our data per DPA |
| Google (Wallet API) | Optional "Save to Google Wallet" passes | Ticket and holder data in a signed pass the buyer chooses to save | Global | Buyer-initiated, client-side redemption |
| Apple (Wallet) | Optional "Add to Apple Wallet" passes | Ticket and holder data in a signed pass (.pkpass) the buyer chooses to save; pass updates via Apple push | Global | Buyer-initiated, device-side storage; DPF + SCCs |
Not subprocessors, but relevant: Fio banka — where the organizer connects their Fio account, we read transaction data and submit refund orders on the organizer's instruction; Fio acts as the organizer's bank, not as our subprocessor. Organizer-connected Mailchimp — where the organizer syncs contacts using their own Mailchimp account — acts as the organizer's own processor under the organizer's contract with Mailchimp, not as our subprocessor. Organizer-configured SMTP/IMAP providers for sponsor campaigns likewise act on the organizer's behalf under the organizer's own contract with them.
Changes to this list
We announce new or replaced subprocessors on this page and by email to organizers at least 30 days before they start processing personal data. Organizers may object on reasonable data-protection grounds per the DPA, section 4.
Last updated 14 September 2026