GDPR and ticketing: what European organisers need to know

All articles

Most ticketing platforms collect your participants' data and use it for their own marketing. A GDPR compliant ticketing platform keeps the data relationship between you and your audience.

You sell a ticket. The participant enters their name, email, and payment details. On most ticketing platforms, that data now belongs to the platform. They add the participant to their own mailing lists, retarget them with ads for competing events, and share aggregated data with partners. Your participant signed up for your concert, not for a lifetime of marketing from a company they have never heard of.

For European organisers, this is not just a trust problem. It is a legal one.

"Who is the data controller when I use a ticketing platform?"

Under the GDPR, the data controller is the entity that determines why and how personal data is processed. When you sell tickets through a marketplace platform, the platform typically acts as a joint controller or even the sole controller of participant data. That means they decide what happens with your audience's information.

With Praticable, you are the data controller. Praticable processes participant data on your behalf as a data processor. The distinction matters: you decide what data is collected, how it is used, and who has access. Praticable does not use participant data for its own marketing, does not sell it, and does not share it with third parties.

"Where is the data stored?"

Praticable's infrastructure runs on European servers. Participant data, transaction records, and event information are stored in the EU. This simplifies compliance for organisers who need to demonstrate that personal data does not leave the European Economic Area without adequate safeguards.

Payment data is handled by Stripe, which is PCI DSS compliant and offers European data residency options. Because you connect your own Stripe account, the payment relationship is between your organisation and Stripe, not mediated by Praticable.

"My participants did not consent to being marketed by the platform"

This is one of the most common GDPR violations in the ticketing industry. A participant purchases a ticket to your event and starts receiving promotional emails from the platform about unrelated events. The participant did not consent to this; they consented to buying a ticket from you.

Praticable does not send marketing to your participants. The only communications participants receive are transactional: their ticket confirmation, their wallet pass, and any notifications you choose to send through the dashboard. You control the messaging. There is no parallel channel where the platform is building its own relationship with your audience.

"What about the right to deletion?"

Under the GDPR, individuals can request that their personal data be deleted. On a marketplace platform, this request is complicated: the participant's data is entangled with the platform's own systems, marketing databases, and analytics pipelines.

With Praticable, deletion is straightforward. Participant data associated with your events can be removed from the system. Because Praticable does not replicate participant data across marketing systems or third-party integrations, there are fewer places where data lingers after deletion.

"How does this affect independent theaters and small venues?"

Independent theaters and small cultural venues often lack a dedicated legal team to navigate GDPR compliance. They need a ticketing platform that is compliant by design, not one that requires them to audit a complex data-sharing arrangement.

A GDPR compliant ticketing platform for independent theaters means:

  • No surprise data sharing. Your participants' information stays within the systems you control.
  • Clear data processor agreements. Praticable provides a DPA (Data Processing Agreement) that defines exactly what data is processed and how.
  • Minimal data collection. Praticable collects only what is needed to process the ticket purchase and deliver the ticket. No behavioural tracking, no profiling, no cookies for ad targeting.
  • Auditability. Your data is in your Stripe account and your Praticable dashboard. Two systems, both under your control, both auditable.

"What should I look for in a GDPR compliant ticketing platform?"

Five questions to ask any ticketing provider:

  1. Who is the data controller? If the platform is the controller, they decide what happens with your participants' data.
  2. Does the platform market to my participants? If yes, your participants are being contacted without your knowledge or their meaningful consent.
  3. Where is the data stored? Data stored outside the EU requires additional legal safeguards.
  4. Can I get a Data Processing Agreement? A reputable processor will provide one without hesitation.
  5. What happens when a participant requests deletion? The answer should be simple and complete, not "we will look into it."

Praticable answers all five clearly: you are the controller, there is no platform marketing, data is stored in the EU, a DPA is available, and deletion is straightforward.


GDPR compliance is not a feature you add later. It is an architecture decision. Praticable is built so that the data relationship stays between you and your audience, where it belongs. Learn more about how it works or request a demo.