What is the GDPR?

GDPR: a European regulation that applies to events, too In effect since May 25, 2018, the General Data Protection Regulation applies to any organization processing the personal data of European residents, regardless of company size. For an event organizer, this practically means that every data collection—including a paper attendance sheet or a badge scan—qualifies as data processing under the GDPR and triggers compliance obligations. CNIL penalties are very real: in 2024, the French data protection authority issued 87 sanctions totaling over €55 million in fines (source: CNIL, 2024 activity report). There's no need to panic, but there is every reason to take action. The two key roles: Data Controller and Data Processor The GDPR is built on a fundamental distinction: the Data Controller and the Data Processor. As an organizer, you are the Data Controller: you decide why and how data is collected. The event platform you use is your Data Processor: it processes data on your behalf, according to your instructions. This distinction has a direct impact: even when delegating to a platform, you remain legally responsible for your processor's practices. We'll delve deeper into this crucial point in the final section. Key takeaway As the organizer, you are the Data Controller. The event management tool you choose is your Data Processor. You are legally accountable for its practices.

Impact of the GDPR on B2B and B2C Event Organizers

B2B events: obligations often underestimated A common misconception: “business data isn’t covered by GDPR”. That’s incorrect. An employee’s contact details, their name, business email, job title, are personal data within the meaning of the regulation. Industry conferences, trade shows, customer seminars: all are affected. The legal basis of “legitimate interest” is often applicable in B2B for sending invitations or sales follow-up, but it must be documented in your records of processing activities. It doesn’t exempt you from informing people. B2C events: an even higher level of requirements In B2C, explicit consent is frequently required, especially as soon as the processing goes beyond the logistical organization of the event. Photos and videos of the event published publicly, collection of health data for a sports event, processing of data on minors: all sensitive cases requiring particular attention. One point is frequently overlooked: post-event communication, sending a replay, satisfaction survey, follow-up newsletter, requires a legal basis distinct from simple registration. Consent obtained for registration doesn’t count as consent for later communications. B2B2C events Some B2B events may also involve guests such as spouses, or even children. For example at “family days” events where the company, factory or plant is open to relatives to show the job of an employed parent. Some companies that are part of industrial heritage may also open their doors during heritage open days. There is then a mix of employee attendees and “general public” attendees or guests.

The obligation to inform individuals

What must a compliant information notice contain? Article 13 of GDPR requires specific content in any information notice: the identity and contact details of the data controller, the purposes and legal basis of each processing activity, the recipients or categories of recipients of the data, the retention period, people’s rights and how to exercise them, the contact details of the DPO if your organization appoints one, and the existence of any transfers outside the European Union. This notice must be written in clear, understandable language; legal jargon is not an alibi, it’s an obstacle. When must the information be provided? The principle is simple but non-negotiable: information must come before collection. In practice, this means making it accessible on the online registration form (before submission), in the registration confirmation email, on the accreditation management app and at the on-site check-in kiosk. Putting a link to the privacy policy in an email footer is not enough. The information must be visible, accessible and presented before the person provides their data.

Transparency in data collection

Identifying the right legal basis for the type of event Each processing activity must rest on one of the legal bases provided for by GDPR. The most common legal bases in events are the following: • Consent: used notably for sending a post-event newsletter, as well as for using photos and videos. It must be freely given, specific, informed and revocable at any time. • Legitimate interest: often used for sending the program, B2B sales follow-ups or certain communications related to the event. Using it requires a documented balancing of interests between the organizer’s needs and the rights of the people concerned. • Performance of a contract: covers, for example, a paid registration or the issue of a badge needed for participation. This legal basis must remain limited to the data strictly necessary for performing the requested service. The classic mistake is to use consent as the default legal basis, when performance of a contract or legitimate interest is often more appropriate, and less burdensome to manage. The key is to define the legal basis upfront and document it. Data minimization: collect only what’s necessary The principle of minimization is one of the foundations of GDPR: you collect only the data strictly necessary for the stated purposes. Applied to events, it leads to concrete questions: is date of birth really needed for an industry conference? Is a phone number essential if all communication is by email? Answering these questions before each event is more effective than an annual audit. Registration form: best practices Compliance is also decided in the details of the form. Checkboxes that aren’t pre-ticked, clear consent wording that is separate for each purpose (one box for registration, another for the newsletter), a link to the privacy policy visible before submission, no unjustified mandatory field: every element counts. A compliant event platform must let you configure these settings without technical workarounds. If your tool doesn’t allow it, that’s a warning sign.

Data retention period

Setting retention periods suited to each purpose There is no universal retention period: it depends on the purpose of each processing activity. A few reasonable benchmarks: billing data must be kept for 10 years under legal accounting obligations; contact data for commercial prospecting, 3 years from the last contact according to CNIL recommendation; event participation data, 12 months maximum for statistical purposes. These periods must be documented in your records of processing activities. Many organizers keep data indefinitely for lack of a procedure: that is a non-compliance in itself. At Appcraft we recommend keeping data for 3 months after the event. In 90% of cases, that is more than enough. Accreditations, badges and attendance data: the special case Data collected during badge scans deserves particular attention. Entry time, sessions visited, interactions with exhibitors: this is behavioral data in its own right. It must be covered by an explicit legal basis, mentioned in the information notice, and deleted after a defined period. This point is frequently ignored at professional events, including in organizations that otherwise consider their GDPR compliance well under control.

Participants' rights

Right of access, rectification and erasure Articles 15, 16 and 17 of GDPR guarantee attendees the right to access their data, have it corrected and request its deletion. You generally have one month to respond to a request (extendable to 3 months for complex requests). Concrete case: an attendee asks for their data to be deleted after the event. You must be able to erase their profile from your platform, the associated emailing lists and any third-party database to which you may have passed on their information. If your platform doesn’t allow this deletion on request, that’s a problem. Right to object and withdrawal of consent The right to object applies to processing based on legitimate interest: the attendee can object at any time, and you must stop this processing unless there are compelling grounds. Withdrawal of consent concerns processing based on consent: it must be as easy as giving it. An unsubscribe link in every email isn’t enough if other consent-based processing is underway. The exercise of these rights must apply to all the processing concerned, not just email sending. How do you organize the handling of these requests in practice? You don’t need a full-time DPO to handle rights requests effectively. Light governance is enough in most cases: appoint an internal GDPR contact (even part-time), create a dedicated email address for requests (such as privacy@yourcompany.com), document each request and its response in a simple register, and make sure your platform allows data export and deletion on request. For mid-sized organizations, an outsourced DPO can provide the necessary legal advice without the constraints of a dedicated hire.

GDPR advice box explaining that an event organizer does not always need a full-time DPO to be compliant.

The Essentials of a Compliant Event Platform

The DPA (Data Processing Agreement): the first document to ask for Article 28 of the GDPR requires a data processing agreement (DPA) between the event organiser and any platform processing personal data on their behalf. This document must set out the subject matter and duration of the processing, its nature and purpose, the types of data processed, the processor’s security and confidentiality obligations, terms for sub-processors, and audit arrangements. Operating without a DPA is non-compliant in itself—exposing you during audits, no matter how robust your technical measures may be. A platform that doesn’t provide a DPA simply cannot be considered compliant. European hosting and technical security: the non-negotiables Beyond the DPA, several technical criteria need vetting. Hosting data on servers located within the European Union is an absolute prerequisite. Transfers outside the EU—especially to US-based sub-processors subject to the Cloud Act—create genuine legal risks that must be governed by Standard Contractual Clauses (SCCs) or other appropriate safeguards. In fact, even if data is hosted on European or French servers, using a US provider such as Amazon AWS or Microsoft Azure still exposes you to the US Cloud Act. Data encryption in transit and at rest, granular access controls, audit logs for full traceability, an incident response plan (including 72-hour breach notifications to supervisory authorities), and recognised certifications like ISO 27001 are reliable hallmarks of security maturity. At AppCraft, these requirements are built directly into our platform architecture: hosting in France on OVH servers (a French company), attendee data strictly isolated from our AI engine, privacy-by-design anonymisation, and an execution-ready DPA for every client. Your checklist for choosing a genuinely GDPR-compliant platform Before signing with a vendor, check off each item point by point: 1. Does the vendor provide an up-to-date, signed GDPR Data Processing Agreement (DPA)? 2. Is data hosted exclusively within the European Union? 3. Is the hosting company subject to foreign legislation incompatible with EU regulations, such as the US Cloud Act? 4. Is data encrypted both in transit (TLS) and at rest? 5. Does the platform provide access logs and complete audit trails? 6. Is there a documented data breach notification procedure (within 72 hours to the regulator)? 9. Are registration forms customisable to enforce data minimisation and consent capture? 8. Can an attendee’s data be erased quickly upon request? 9. Does the platform hold recognised certifications (ISO 27001 or equivalent)? 10. Are all sub-processors clearly listed and covered by contractual safeguards? 11. Can their sales or legal team address your GDPR questions promptly and clearly?

In conclusion

GDPR compliance in events is not a lawyer’s matter: it’s an organizer’s matter. The obligations are concrete, the risks real, and solutions exist, including for organizations with no dedicated DPO. The key is to structure your approach: document your processing, choose a truly compliant platform, inform attendees and give yourself the means to respond to their rights. Beyond strict compliance, data protection is also a trust lever. Attendees who know their data is handled seriously register more easily, share more relevant information and come back for later editions. GDPR rigor, done well, is a competitive advantage as much as a legal obligation. To go further: GDPR compliance naturally raises other related questions, such as cookie management on your event website, the policy on retention of CRM data between two editions of the same event, or the specific challenges of hybrid events where online and in-person attendees aren’t subject to the same processing. These are all topics we’ll keep exploring.

FAQ

Which GDPR legal basis should you choose for processing the data of event participants?

It depends on each specific use, not on the event as a whole. The performance of the contract covers what is strictly necessary for participation, such as a paid registration or the issuance of a badge. Legitimate interest is often appropriate for sending the program or for B2B sales follow-ups, provided that the balancing of interests with individuals’ rights is documented. Consent is required for a post-event newsletter or for the use of photos and videos. A common mistake is to rely on implied consent, even though it is more difficult to manage. Business contact information remains personal data, even in B2B contexts.

How long should participant data be retained after an event?

The retention period depends on the purpose and must be documented in the data processing register. Billing data is retained for 10 years to comply with accounting requirements. Marketing data is retained for 3 years after the last contact, in accordance with the CNIL’s recommendation. Participation data is retained for a maximum of 12 months for statistical purposes. AppCraft recommends retaining the data for 3 months after the event, which is sufficient in the vast majority of cases. Badge scan data (time of entry, sessions attended, interactions with exhibitors) constitutes behavioral data: it must also have a defined retention period.

Is storing data in France enough to ensure its protection?

Not necessarily: it all depends on the host’s nationality. Servers located in Europe—or even in France—but operated by a U.S. provider such as AWS or Azure remain subject to the Cloud Act. It is therefore important to verify who operates the infrastructure. You should also verify that a DPA (data processing agreement) has been signed, that data is encrypted, that audit logs are maintained, that there is a procedure for notifying the CNIL within 72 hours in the event of a breach, and that the provider holds a certification such as ISO 27001. AppCraft hosts its data in France with OVH, a French company, and provides a DPA to each client. However, the organizer remains responsible for its service provider’s practices.