Regulation (EU) 2016/679 (GDPR) directly affects any organiser who collects data from attendees. Emails, names, phone numbers, purchasing preferences — all of this is personal data that must be processed in line with the regulation. In Spain, this is complemented by Organic Law 3/2018 on the Protection of Personal Data and the Guarantee of Digital Rights (LOPDGDD). Article 83.5 of the GDPR sets the upper tier of fines at €20 million or 4% of total worldwide annual turnover, whichever is higher; Article 83.4 sets a lower tier of €10 million or 2%. This guide covers the essentials.
The risk isn't theoretical. The Spanish Data Protection Agency (AEPD) reported on 23 January 2026 that it had received 2,765 notifications of personal data breaches in 2025, 80% of them from the private sector. That's 7.6 notifications a day (our own calculation based on the AEPD's figure). An organiser with a database of buyers falls squarely within that universe.
What data do you collect as an event organiser?
As an event organiser, you collect more data than you probably realise. It's important to identify all of it so you can manage it properly.
- Purchase data: name, email, phone number, billing address
- Access data: entry time, zone, validation attempts
- Behavioural data: pages visited, abandoned carts
- Device data: IP address, browser, operating system
- Optional data: preferences, date of birth, gender
The useful exercise isn't listing them, but cross-referencing each piece of data with its legal basis and retention period. This table is the skeleton of the record of processing activities required under Article 30 of the GDPR:
| Data | What you use it for | Legal basis (Art. 6.1 GDPR) | Retention period |
|---|---|---|---|
| Buyer's name and email | Issuing and sending the ticket | Performance of a contract, point (b) | For the duration of the contract and any applicable limitation periods |
| Billing data | Meeting tax obligations | Legal obligation, point (c) | For the period set by tax law |
| Email for the newsletter | Selling the next event | Consent, point (a) | Until withdrawn |
| Validation time and gate | Capacity and access control | Legitimate interest, point (f) | For as long as needed to run the event |
| CCTV footage | Venue security | Legitimate interest, point (f) | One month (Art. 22 LOPDGDD) |
| Health or accessibility data | Allocating an adapted space | Explicit consent, Art. 9.2(a) | For as long as needed to provide the service |
Sources: Articles 6.1, 9.2 and 30 of the GDPR and Article 22 of the LOPDGDD. Tax retention periods are covered in detail in our guide to tax obligations for ticket sales. The specifics of what you can and can't ask for in the purchase form are covered in our guide on what data you can request from a ticket buyer.
What legal bases exist for processing data?
Article 6.1 of the GDPR requires every processing activity to rely on one of the six legal bases it sets out. For event organisers, the most relevant are:
- Performance of a contract: you need the data to sell and deliver the ticket
- Consent: for sending newsletters or marketing communications
- Legitimate interest: for preventing fraud or improving the service
- Legal obligation: tax data you must retain by law. See our guide to tax obligations for ticket sales for more detail
Two caveats on legitimate interest. The first is that point (f) of Article 6.1 makes it conditional on it not being overridden by "los intereses o los derechos y libertades fundamentales del interesado" ("the interests or fundamental rights and freedoms of the data subject"), so it requires a written balancing test, not just a label. The second is that Article 21.2 of the GDPR gives attendees the right to object at any time to processing for direct marketing purposes, in which case "los datos personales dejarán de ser tratados para dichos fines" ("the personal data shall no longer be processed for such purposes"). No balancing test survives an objection.
How do you obtain consent correctly?
Article 4.11 of the GDPR defines consent as a "libre, específica, informada e inequívoca" ("freely given, specific, informed and unambiguous") indication, and Article 7 sets out the conditions for demonstrating and withdrawing it. This means you can't use pre-ticked boxes, make the purchase conditional on accepting marketing, or bury consent inside generic terms and conditions. If you also send marketing communications by email or SMS, Article 21 of Law 34/2002 (LSSI-CE) also applies.
- Separate tick boxes for each purpose (one for marketing, another for third parties)
- Clear, plain language, with no legal jargon
- Withdrawing consent must be as easy as giving it
- A record of when and how each consent was obtained
Paragraph 1 of that Article 21 is unequivocal: "Queda prohibido el envío de comunicaciones publicitarias o promocionales por correo electrónico u otro medio de comunicación electrónica equivalente que previamente no hubieran sido solicitadas o expresamente autorizadas por los destinatarios de las mismas" ("The sending of advertising or promotional communications by email or any other equivalent electronic means that have not previously been requested or expressly authorised by their recipients is prohibited"). Paragraph 2 opens the only useful door for a promoter: if a prior contractual relationship exists, the data was obtained lawfully, and the communication relates to products or services similar to those already contracted, you can write to someone who has already bought from you. In exchange, you must offer the right to object through "un procedimiento sencillo y gratuito" ("a simple and free procedure"), both when the data is collected and in every message. In practice: someone who bought a ticket to your festival can receive the announcement for next year's edition; someone who bought a theatre ticket isn't a natural audience for a third party's campaign. How to put that sequence together is covered in our guide to email marketing for events.
What rights do attendees have over their data?
Articles 15 to 22 of the GDPR grant attendees a series of rights over their data that you must be able to honour. Article 12.3 gives you one month from receipt of the request to respond, extendable by a further two months where the complexity or number of requests justifies it, provided you inform the data subject within the first month and explain the reason for the delay.
- Access: finding out what data you hold on them
- Rectification: correcting inaccurate data
- Erasure: deleting their data (subject to legal exceptions)
- Portability: receiving their data in a structured format
- Objection: refusing certain types of processing
Two operational nuances. Portability under Article 20 only covers data the data subject themselves provided to you, and only processing based on consent or contract, and it must be handed over "en un formato estructurado, de uso común y lectura mecánica" ("in a structured, commonly used and machine-readable format"): a CSV works, a screenshot doesn't. And erasure under Article 17 isn't absolute: point 3(b) excepts it where processing is necessary "para el cumplimiento de una obligación legal" ("for compliance with a legal obligation"), which is exactly what applies to the tax records of a sale. Deleting the marketing profile while keeping the invoice isn't a contradiction — it's what the regulation requires.
When do you need an impact assessment for your event?
When the processing involves high risk. Article 35.1 of the GDPR requires a data protection impact assessment (DPIA) to be carried out before processing begins, and the AEPD publishes the list of types of processing requiring an impact assessment envisaged under Article 35.4. That list sets out a practical criterion: a DPIA will be necessary "en la mayoría de los casos en los que dicho tratamiento cumpla con dos o más criterios" ("in most cases where the processing meets two or more criteria") of the eleven it lists.
Several of these criteria intersect at a large festival: processing involving "perfilado o valoración de sujetos" ("profiling or evaluation of individuals", criterion 1), "el uso de datos biométricos con el propósito de identificar de manera única a una persona física" ("the use of biometric data for the purpose of uniquely identifying a natural person", criterion 5), "el uso de datos a gran escala" ("large-scale use of data", criterion 7), "asociación, combinación o enlace de registros de bases de datos de dos o más tratamientos con finalidades diferentes o por responsables distintos" ("matching, combining or linking records from databases of two or more processing operations carried out for different purposes or by different controllers", criterion 8), and "la utilización de nuevas tecnologías o un uso innovador de tecnologías consolidadas" ("the use of new technologies or an innovative use of established technologies", criterion 10).
Let's run the numbers on a concrete case — our own reading of the list, not an AEPD ruling: a festival that validates access by fingerprint, cross-references its buyer database with its cashless system, and segments campaigns by purchasing behaviour meets criteria 5, 7, 8 and 10. That's four out of eleven: the DPIA stops being optional.
Can you use facial recognition or fingerprints for access control?
Only with a very solid legal basis, and almost never with consent alone. On 23 November 2023, the AEPD published its guide *Tratamientos de control de presencia mediante sistemas biométricos* ("Processing for presence control using biometric systems"), and in its press release it states that it regards "el tratamiento de datos biométricos, tanto para identificación como para autenticación, como un tratamiento de alto riesgo que incluye categorías especiales de datos" ("the processing of biometric data, whether for identification or authentication, as high-risk processing that includes special categories of data").
There are three consequences. You need a circumstance that lifts the prohibition in Article 9.1 of the GDPR, plus a condition under Article 6 that legitimises the processing. You need a DPIA "de forma previa al inicio del tratamiento" ("prior to the start of processing"). And you must demonstrate "la superación del triple análisis de idoneidad, necesidad y proporcionalidad" ("that the triple test of suitability, necessity and proportionality has been passed"): if a named QR code or an NFC wristband solves the access control problem, a fingerprint fails the necessity test. That's why most venues stick with QR and NFC-based access control, which processes far less data and doesn't fall under Article 9.
What about suppliers and processors?
When you use a ticketing platform, an email marketing service, or any other supplier that accesses your attendees' data, Article 28 of the GDPR requires a written data processing agreement. That article sets out the minimum content the contract must include: subject matter, duration, nature and purpose of the processing, type of data, categories of data subjects, and the processor's obligations — including acting only on your instructions and deleting or returning the data once the service ends.
- Check that your suppliers comply with GDPR
- Sign data processing agreements
- Check where they store the data (international transfers)
- Keep a record of every supplier with access to data
Three points standard-form contracts tend to miss. Article 28.2 prohibits the processor from subcontracting without your prior authorisation, in writing, whether specific or general: if your platform switches transactional email providers, you have the right to be told and to object. Article 28.3(h) gives you the right to audit them or to receive their audit results. And if a supplier processes data outside the European Economic Area without an adequacy decision in place, the usual instrument is the standard contractual clauses from the Commission's Implementing Decision (EU) 2021/914, which must be signed and completed with an assessment of the destination country. The starting point for that conversation is simple: ask in writing for the list of sub-processors and the country where the data is hosted before you sign — not after the first incident.
What should you do about a security breach?
Article 33.1 of the GDPR requires notification of a security breach to the supervisory authority — in Spain, the Spanish Data Protection Agency — "sin dilación indebida y, de ser posible, a más tardar 72 horas después de que haya tenido constancia de ella" ("without undue delay and, where feasible, no later than 72 hours after having become aware of it"). Two nuances are often overlooked: you don't need to notify if the breach is unlikely to pose a risk to people's rights and freedoms, and if you go over 72 hours you must explain the delay. If the risk is high, Article 34 also requires you to inform those affected. The AEPD publishes a guide to breach notification; having the protocol ready before it happens is what makes the difference.
The AEPD's 2025 figures help put this in perspective. Of the 2,765 notifications received, eleven were escalated for further investigation on grounds of high severity: 0.4% (our own calculation). Notifying isn't an admission of an infringement; failing to notify, by contrast, is itself a breach of Article 33. The highest-impact breaches, according to the Agency itself, stemmed from ransomware and intrusions into information systems, but among the most frequent are the mundane ones: sending personal data to the wrong recipients and accidentally disclosing personal data. An email to all your guests with their addresses visible in the "cc" field is exactly that.
Two useful tools. The AEPD offers Comunica-Brecha RGPD to help decide whether those affected need to be informed under Article 34. And Article 33.5 requires you to internally document all breaches, including those you don't notify, along with their effects and the remedial measures taken: that record is the first thing an inspection will ask for.
What mistakes do organisers make most often?
Six, and none of them require a hacker.
- Guests emailed with visible addresses. A message with a hundred addresses on display is a confidentiality breach — exactly the kind the AEPD describes as the most frequent.
- The pre-ticked marketing box. Incompatible with Article 4.11 of the GDPR, which requires an unambiguous indication.
- Handing the buyer database over to a sponsor. That's a different purpose and needs its own legal basis and prior information. It doesn't fit within the ticket sale contract.
- Exporting the database to a new tool without a processing agreement. Article 28 applies just as much to a trial CRM as to your main platform.
- Asking for an ID document "just in case". The data minimisation principle in Article 5.1(c) requires you to collect only what is adequate and limited to what's necessary.
- Keeping CCTV footage for more than a month. Article 22 of the LOPDGDD requires you to delete it within that period unless it documents unlawful acts.
Why is GDPR an opportunity and not just an obligation?
GDPR isn't just a legal obligation — it's an opportunity to build trust with your attendees. Handling data transparently and responsibly improves your reputation and reduces risk. Invest the time to get the basics right, and update them whenever your processes change.
And what part of this does Futura Tickets cover?
No platform makes you a compliant controller automatically: you are the controller, and the platform is the processor. What does change depending on the provider is who ends up holding the data. Futura Tickets is a Spanish SaaS ticketing platform for professional organisers. With Futura Tickets, the attendee database belongs 100% to the organiser: emails and phone numbers are handed over in full, in line with GDPR. That matters on the day an attendee exercises their right of access or erasure: if you can't export or delete the data, you can't honour the request within the one month set out in Article 12.3. Details are available on our pricing page.
What to check before opening sales
Six checks, all of them before the first ticket is sold.
Write the record of processing activities before building the form. Article 30 of the GDPR requires it, and it also forces you to decide the legal basis for each piece of data. If you don't know which basis covers a field, that field shouldn't be there.
Separate the tick boxes and keep the evidence. One for the purchase, one for marketing, one for data sharing. Plus a record of the date, time and exact wording shown: Article 7.1 makes you responsible for proving that consent existed.
Sign the processing agreement with your platform and ask for its list of sub-processors. Get the hosting country in writing. If data goes outside the EEA, use the standard contractual clauses from Decision 2021/914.
Decide today who handles a right-of-access request. You have one month from the date of the request. An unowned inbox is the most common way to miss that deadline.
Prepare the breach protocol before the event. Who detects it, who assesses the risk, who notifies, and with what information. The 72 hours in Article 33 keep running over a festival weekend too.
Review what access technology you're going to use. If someone proposes fingerprint or facial recognition, the short answer is that you need to lift the Article 9 prohibition and carry out a prior DPIA. If a named QR code will do the job, use the QR code.
Sources
All links were accessed on 11 October 2026. This guide is for informational purposes only and doesn't replace legal advice for a specific case.
- Regulation (EU) 2016/679 (GDPR) — Art. 4.11 and 7 (consent), Art. 5.1(c) (minimisation), Art. 6.1 (legal bases), Art. 9 (special categories), Art. 12.3 (response deadline), Arts. 15–22 (rights), Art. 28 (processor), Art. 30 (record of processing activities), Arts. 33 and 34 (breaches), Art. 35 (impact assessment), Arts. 83.4 and 83.5 (fines)
- Organic Law 3/2018 on the Protection of Personal Data and the Guarantee of Digital Rights — Art. 7 (minors under fourteen) and Art. 22 (CCTV)
- Law 34/2002 on information society services (LSSI-CE), Art. 21
- Spanish Data Protection Agency (AEPD)
- AEPD: guide to managing and notifying security breaches (PDF)
- AEPD: the Agency received 2,765 notifications of personal data breaches in 2025 (press release, 23 January 2026)
- AEPD: lists of types of processing requiring an impact assessment, Article 35.4 (PDF)
- AEPD: guide on processing for presence control using biometric systems, November 2023 (PDF)
- AEPD: press release on the use of biometric data for presence and access control
- AEPD: Comunica-Brecha RGPD tool
- Commission Implementing Decision (EU) 2021/914, standard contractual clauses for the transfer of data to third countries
