Wildfire's privacy statement
Last updated: 24 October 2026
Draft: a lawyer is still checking this text, and it may change.
How Wildfire handles the personal details it decides about itself: those of the organisers who use it and their teams, of visitors to wildfire.tickets and its dashboard, of people who join the waitlist or ask for a demo, and of organisers Wildfire would like to work with. And where to read about the details of an event's buyers, registrants and contacts, which the event's organiser decides about.
1. Who we are
Wildfire (wildfire.tickets), run by Socialista, Casembrootstraat 60RD, 1972CC IJmuiden, the Netherlands (KvK 61396478). For the details in this statement, Socialista is the controller: it decides what they are used for and is responsible for them.
Questions about your details, and requests to use your rights: [email protected].
2. Buyers, registrants and contacts of an event
When you buy a ticket in a Wildfire shop, sign up for an event, or are in an organiser's list of contacts, the event's organiser decides what your details are used for and is the controller. Wildfire handles those details only on the organiser's behalf, as their processor, under a processing agreement (wildfire.tickets/terms/processing), and uses them for nothing of its own.
What happens with them is in "Your details when you buy a ticket" (wildfire.tickets/privacy/tickets) and "Your details when you sign up for an event" (wildfire.tickets/privacy/signups). Questions and requests about them go to the organiser; when they reach us, we pass them on and help the organiser answer.
3. Organisers and their teams
Your name, email address and password (kept by the sign-in server only as a one-way hash), your company's name, and the second factors you add (an authenticator app, a passkey). For people invited into an account: their name, email address, role and the events they may work on. If you sell tickets: your business's name, address, KvK and VAT numbers, and the Stripe account it uses. If you use the Wildfire app: your phone's push address.
Billing: what you use (messages, emails) and pay, and your invoices. Your payment method stays with Stripe.
Security: when you sign in, with the internet address and browser you sign in from; what Wildfire's staff do when they look into an account to help; and who exported data or moved money, and when.
Support: the emails and messages you send us, and our answers.
The assistant: a question you type into the dashboard's assistant, with the page you asked it on and what you pointed at, goes to Anthropic for an answer and is not kept by Wildfire. Never type a fan's or buyer's details into it.
Why, and why that is allowed: to give you the account and the service and to bill for them, because that is our contract with you; to keep accounts and the service safe and to find abuse, our legitimate interest in a safe service; to keep the books, the law. Wildfire emails you about your account and the service, such as a failed payment or a change to its terms.
4. Visitors of wildfire.tickets and the dashboard
The pages about Wildfire on wildfire.tickets set no cookies and use no analytics. The dashboard sets only the cookies it needs to work: the one that keeps you signed in, short-lived ones while you link Stripe or Weeztix, and, for Wildfire's staff, while they look into an account. Those need no consent.
Wildfire's server, and Cloudflare in front of it, see your internet address and what your browser asks for. Wildfire's own access logs keep that for 7 days, to keep the service running and safe: our legitimate interest.
Event pages and ticket shops on wildfire.tickets are the organisers'. Each organiser asks for itself about measuring visits and about advertising, two separate choices that the Cookies link at the foot of their pages changes; what follows from them is in the texts for buyers and for people who sign up.
5. The waitlist and demo requests
When you join the waitlist: your name, email address and, if you give it, your company. When you ask for a demo: your name, email address and phone number.
Used only to invite you, or to contact you about the demo you asked for: steps you asked for before a possible contract. Kept for 24 months, then deleted.
6. Organisers we would like to work with
Wildfire keeps a list of event organisers it would like to work with, in a workspace only Wildfire's staff can open. About a person there: their name, the organisation they work for, their business email address and phone number, the organisation's website, Instagram account and city, how we came to know them, and notes of our calls, emails and meetings.
Where it comes from: from you, from your organisation's own website and social media, from someone who referred you to us, or from an event where we met.
Why: to offer Wildfire to organisers, which is our legitimate interest in finding customers. You can object at any time; we then stop and delete your details. Otherwise they are deleted 24 months after our last contact.
7. Who else handles them
Wildfire uses these companies to run the service, each under an agreement that protects the details. The same list applies to the details Wildfire handles for organisers. The players an organiser can put on an event page are the exception: they are not Wildfire's, and they get nothing until a visitor presses play.
Contabo (Contabo GmbH, Germany): The server Wildfire runs on, which Wildfire manages itself and which holds the database and the files. Everything Wildfire keeps. Germany.
Dropbox (Dropbox, Inc., United States): The nightly backups, encrypted on Wildfire's server before they leave it, so Dropbox cannot read them. Each is kept for 7 days. An encrypted copy of the database. The United States. Details that reach the United States do so under the EU-US Data Privacy Framework where the company is certified under it, and otherwise under the European Commission's standard contractual clauses.
Cloudflare (Cloudflare, Inc., United States): Domain names, the network in front of Wildfire's server, and the check that a visitor is a person (Turnstile) at busy sales. Internet addresses and the requests that pass through it; for the check, signals from the browser. Worldwide, nearest to the visitor. Details that reach the United States do so under the EU-US Data Privacy Framework where the company is certified under it, and otherwise under the European Commission's standard contractual clauses.
Stripe (Stripe Payments Europe, Limited, Ireland): Ticket payments, made on the organiser's own Stripe account, and Wildfire's own billing of organisers. A buyer's name, email address and payment details; an organiser's billing details. The EEA and the United States. Details that reach the United States do so under the EU-US Data Privacy Framework where the company is certified under it, and otherwise under the European Commission's standard contractual clauses.
Resend (Plus Five Five, Inc., United States): Sending every email: the organisers' campaigns from their own domains, the mails about tickets, and Wildfire's own mail about accounts. Email addresses, names and the emails themselves. Sent from Ireland (eu-west-1), by a company in the United States. Details that reach the United States do so under the EU-US Data Privacy Framework where the company is certified under it, and otherwise under the European Commission's standard contractual clauses.
Meta (Meta Platforms Ireland Limited, Ireland): WhatsApp messages, for organisers who use WhatsApp (the WhatsApp Business Platform), sign-ups through an organiser's ads on Facebook and Instagram, the posts an organiser publishes on their own Facebook Pages and Instagram accounts and the comments and messages people send them there, and, only after a visitor's yes to advertising given to that organiser, the organiser's Meta pixel and the sign-ups and purchases on their pages told to it. And, for an organiser who connects their own ad account, their customer lists: the email addresses and phone numbers of the organiser's buyers and sign-ups, made unreadable (hashed), so the organiser's ads reach them or leave them out, except anyone who objected. Phone numbers, names and messages; for the pixel, contact details made unreadable (hashed) and what was done. The EEA and the United States. Details that reach the United States do so under the EU-US Data Privacy Framework where the company is certified under it, and otherwise under the European Commission's standard contractual clauses.
TikTok (TikTok Technology Limited, Ireland): The videos an organiser publishes on their own TikTok account. And only for an organiser who adds a TikTok pixel, and only after a visitor's yes to advertising given to that organiser: the pixel, and the purchases told to it. And, for an organiser who connects their own ad account, their customer lists: the email addresses and phone numbers of the organiser's buyers and sign-ups, made unreadable (hashed), so the organiser's ads reach them or leave them out, except anyone who objected. Contact details made unreadable (hashed), and what was done. The EEA, the United States, and staff elsewhere, China included, who may reach the details. Under the European Commission's standard contractual clauses.
Google (Google Ireland Limited, Ireland): Google Tag Manager, only for an organiser who adds one and only after a visitor's yes to advertising given to that organiser; Google Ads, for an organiser who connects their own account: their hashed customer lists (Customer Match), and, only after a visitor's yes to advertising, the sign-ups and purchases told to their conversion action; notifications to the Wildfire app on the Android phones of an organiser's team (Firebase Cloud Messaging); and the mailbox that receives the email people send to Wildfire. What the organiser's tags collect; for Google Ads, contact details made unreadable (hashed), the Google ad click and what was done; a phone's push address and the notification; the emails sent to Wildfire. The EEA and the United States. Details that reach the United States do so under the EU-US Data Privacy Framework where the company is certified under it, and otherwise under the European Commission's standard contractual clauses.
Snap (Snap B.V., the Netherlands): Only for an organiser who connects their own Snapchat ad account or adds a Snapchat pixel: their customer lists (the email addresses and phone numbers of the organiser's buyers and sign-ups, made unreadable (hashed), so the organiser's ads reach them or leave them out, except anyone who objected), and, only after a visitor's yes to advertising given to that organiser, the sign-ups and purchases told to the pixel. Contact details made unreadable (hashed), the Snapchat ad click, and what was done. The EEA and the United States. Details that reach the United States do so under the EU-US Data Privacy Framework where the company is certified under it, and otherwise under the European Commission's standard contractual clauses.
Reddit (Reddit, Inc., United States): Only for an organiser who connects their own Reddit Ads account: their customer lists (the email addresses of the organiser's buyers and sign-ups, made unreadable (hashed), so the organiser's ads reach them or leave them out, except anyone who objected). And for an organiser who adds its conversions, only after a visitor's yes to advertising given to that organiser: the sign-ups, shop steps and purchases told to it. Email addresses made unreadable (hashed). For conversions: contact details made unreadable (hashed), the Reddit ad click, the address and browser of the visit, and what was done. The United States. Details that reach the United States do so under the EU-US Data Privacy Framework where the company is certified under it, and otherwise under the European Commission's standard contractual clauses.
Spotify (Spotify AB, Sweden): Only for an organiser who connects their own Spotify ad account: their customer lists (the email addresses and phone numbers of the organiser's buyers and sign-ups, made unreadable (hashed), so the organiser's ads reach them or leave them out, except anyone who objected). And for an organiser who adds its conversions, only after a visitor's yes to advertising given to that organiser: the sign-ups, shop steps and purchases told to it. Contact details made unreadable (hashed). For conversions: contact details made unreadable (hashed), the address of the visit, and what was done. The EEA and the United States. Details that reach the United States do so under the EU-US Data Privacy Framework where the company is certified under it, and otherwise under the European Commission's standard contractual clauses.
Apple (Apple Inc., United States): Notifications to the Wildfire app on the iPhones of an organiser's team. A phone's push address and the notification, which says how sales go and never names a buyer. The United States. Details that reach the United States do so under the EU-US Data Privacy Framework where the company is certified under it, and otherwise under the European Commission's standard contractual clauses.
Weeztix (Weeztix, the Netherlands): For organisers who sell their tickets through Weeztix, their own choice: their orders read into Wildfire, and orders placed in their Weeztix shop through WhatsApp. Buyers' names, email addresses, phone numbers, orders and answers. The Netherlands.
ntfy (ntfy.sh): Alerts to Wildfire's own staff when something needs a person to look at it. No personal details: an alert is scrubbed of names, addresses, numbers, links and codes before it is sent. The service's own servers.
Anthropic (Anthropic, PBC, United States): The assistant in the dashboard, which answers an organiser's questions about Wildfire and about selling tickets, and the AI writer that drafts an automation's email for them. Only what the organiser types into the assistant or the writer, the address of the page they asked it on, the part of the screen they pointed at and the email they ask to improve. Never what is on the screen, so no fan's or buyer's details. Anthropic does not use it to train its models. The United States. Details that reach the United States do so under the EU-US Data Privacy Framework where the company is certified under it, and otherwise under the European Commission's standard contractual clauses.
YouTube, Vimeo, Spotify and SoundCloud (Google Ireland Limited (YouTube), Vimeo.com, Inc. (United States), Spotify AB (Sweden), SoundCloud Global Limited & Co. KG (Germany)): A video or playlist an organiser puts on their event page. Nothing loads from them until the visitor presses play. Once play is pressed, the visitor's browser connects to them directly, and each handles what it gets under its own privacy statement. Each provider's own.
Wildfire does not sell personal details and uses them for no advertising of its own.
8. Outside the European Economic Area
Wildfire's server is in Germany, and most details stay in the European Economic Area. These companies are in the United States, or may reach details from outside the EEA: Dropbox, Cloudflare, Stripe, Resend, Meta, TikTok, Google, Snap, Reddit, Spotify, Apple and Anthropic. Section 7 says on what basis for each: the EU-US Data Privacy Framework for a company certified under it, and otherwise the European Commission's standard contractual clauses. The backups at Dropbox are encrypted before they leave, so Dropbox cannot read them.
You can ask us for a copy of the safeguards that apply.
9. How long
An account's details: as long as the account exists. Once it is deleted, only what the law makes us keep stays: invoices and sales records, for seven years.
Waitlist entries and demo requests: 24 months. Organisers we would like to work with: 24 months after our last contact.
What Wildfire's staff did, and other admin and security logs: 24 months. Sign-in logs: 90 days. Server access logs: 7 days. Backups: 7 days.
The details Wildfire handles for organisers follow the organiser's own choices and the periods in the texts for buyers and for people who sign up; a waiting room's entries, for example, are deleted 30 days after the sale.
10. Keeping them safe
Email addresses and phone numbers are stored encrypted, the database itself keeps each account's details apart, the links people get are kept only as a one-way hash, and moving money or exporting data asks for a second factor. More is on wildfire.tickets/trust.
11. Your rights
You may ask to see your details, to have them corrected or deleted, to receive them to take elsewhere, to have their use limited, and to object to their use; an objection to being contacted about Wildfire is always followed. Where we rely on your consent, you may take it back at any time.
An organiser can export their account's details and delete their account in the dashboard's Settings. For anything else, write to [email protected]; we answer within a month.
You can also complain to the Autoriteit Persoonsgegevens, the Dutch data protection authority (autoriteitpersoonsgegevens.nl).
12. Changes
When this statement changes, the date at the top changes with it.