How to Capture GDPR-Compliant Consent at Events
The short answer: To capture GDPR-compliant consent at events, ask with an unticked, separate opt-in for each purpose (event emails, marketing, sharing with sponsors), name every organization that will use the data, say people can withdraw at any time, and record who consented, when, how and to which wording. Consent isn't the only lawful basis (GDPR Article 6 lists six), and in the UK the PECR rules let you email corporate subscribers without consent but require it for sole traders and individuals unless the soft opt-in applies.
Checked 2026-10-19. By EventMarketingSoftware.com.
Do you need consent to collect attendee data at events?
Not always: you need a lawful basis under GDPR Article 6, and consent is one of six. Running the event someone registered for is usually covered by contract, while marketing emails and sharing data with sponsors often rely on consent.
Article 6(1) lists consent, contract, legal obligation, vital interests, public task and legitimate interests. Map each use of event data to one basis before you write the form: registration and event logistics (contract), post-event marketing (consent or legitimate interests depending on channel and local rules), sharing with sponsors and exhibitors (often consent), photography and recording (consent or legitimate interests with clear notice).
Electronic marketing has its own rules on top of GDPR (PECR in the UK, national ePrivacy laws in the EU), so check those for email and SMS follow-up.
What makes event consent valid under GDPR?
Valid consent is freely given, specific, informed and unambiguous, given by a clear affirmative action, and as easy to withdraw as to give. GDPR Article 7 and the UK ICO's guidance spell out what that means in practice.
Article 7 requires that you can demonstrate consent, that a consent request mixed with other terms is clearly distinguishable, that people can withdraw at any time and are told so, and that a service isn't made conditional on consent the service doesn't need.
The ICO adds: keep the request separate from terms and conditions; use granular opt-ins for each purpose; don't use pre-ticked boxes, silence or default settings; name your organization and any third-party controllers relying on the consent (categories of third parties aren't specific enough); and explain purposes and the right to withdraw.
How should you word consent on a registration form?
Use short, separate, unticked checkboxes for each optional purpose, each naming who will use the data and for what, with a link to the privacy notice. Keep required event processing out of the checkboxes.
Example structure (adapt with your legal team): 1) No checkbox for event logistics; state in the notice that you'll use details to run the event. 2) Unticked box: 'Email me about future [Company] events and products. I can unsubscribe at any time.' 3) Unticked box: 'Share my name, company, title and email with [Sponsor A] and [Sponsor B] so they can contact me about their products.' 4) Notice on photography and recording, with a way to opt out such as a different lanyard color.
Don't make attendance conditional on marketing consent, which Article 7(4) flags as a sign consent isn't freely given.
How do you handle consent for badge scans and lead retrieval?
Treat a badge scan as a conversation record, not blanket marketing consent, unless the organizer's terms and your own process make the marketing purpose clear and specific.
Organizer terms vary. The 2026 NAMM Show's lead retrieval order form, for example, says registered guests agreed to share their personal information with exhibiting companies via lead retrieval, and advises exhibitors to seek their own expert advice on privacy compliance. That covers data sharing with you; it doesn't decide which marketing you can send.
Practical steps: add a consent question to your lead retrieval qualifiers ('May we email you about [topic]? Yes or no'); record the answer, date and staffer; send a one-time follow-up with an easy opt-out to people who said no only if your lawful basis and local rules allow; and keep scanned leads out of marketing lists until you've checked. See /guides/how-to-choose-a-lead-retrieval-app.
What records of consent should you keep?
Keep records showing who consented, when, how, what they were told, and whether they've withdrawn, for as long as you rely on that consent. The ICO lists these as the records you need to demonstrate consent.
In practice: store the consent flag, timestamp, source (registration form, booth app, kiosk), the exact wording or a version ID of the form, and the privacy notice version. Map these to CRM fields when you sync (see /guides/how-to-sync-event-leads-to-salesforce-and-hubspot) so consent travels with the record.
Review and refresh consent if purposes change; the ICO suggests considering refreshing consent every two years where in doubt.
How do B2B email rules differ for event follow-up?
In the UK, PECR lets you send marketing emails to corporate subscribers (companies, LLPs, Scottish partnerships, government bodies) without consent, but individual subscribers (sole traders and some partnerships) need consent unless the soft opt-in applies. GDPR still applies to the personal data in work emails.
The ICO says it's good practice to keep a do not email list of businesses that opt out and screen against it. The soft opt-in covers existing customers who bought or discussed buying a similar product and were given a clear chance to opt out when you collected details and in every message; it doesn't cover prospects or bought-in lists.
EU countries implement ePrivacy rules differently, and some require consent for B2B email too. Check the rules where your attendees are, and use /glossary/gdpr for background.
What should you check in your event software?
Check that your registration, app and lead retrieval tools support unticked custom consent fields, store timestamps and wording versions, sync consent to your CRM, and are covered by a GDPR Article 28 data processing agreement.
Also check where data is hosted, the subprocessor list, retention and deletion settings, and how attendee data is shared with sponsors (ideally only for attendees who opted in). In our October 2026 data, 246 of about 700 event tech vendors published or offered a GDPR DPA; compare vendors at /security-check and read /guides/how-to-run-a-security-review-for-event-software.