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.

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.

FAQ

Do I need consent to email event attendees after the event?
It depends on who they are, where they are and what you send. Event logistics emails usually don't need marketing consent. For marketing, UK PECR allows emails to corporate subscribers without consent but requires consent or the soft opt-in for individuals and sole traders, and EU countries vary. GDPR still requires a lawful basis and transparency.
Can I use pre-ticked boxes for event marketing consent?
No. Under GDPR, consent needs a clear affirmative action, and the UK ICO says pre-ticked boxes, opt-out boxes, silence and default settings don't count as valid consent.
Does scanning a badge give an exhibitor consent to market to someone?
Not automatically. A scan shows a conversation happened, and organizer terms may permit sharing data with exhibitors, but whether you can send marketing depends on your lawful basis and local email rules. Ask a consent question during the scan and record the answer.
How do I share attendee data with sponsors under GDPR?
Use a separate, unticked opt-in that names the sponsors who will receive the data and says what they'll use it for. The UK ICO says consent for categories of third parties isn't specific enough, so list the organizations by name, and share only the data of people who opted in.
What consent records should event organizers keep?
Keep who consented, when, how (which form or app), what they were told (the wording and privacy notice version) and whether they've withdrawn. GDPR Article 7 requires you to be able to demonstrate consent for as long as you rely on it.
Is consent the only lawful basis for event data?
No. GDPR Article 6 lists six lawful bases: consent, contract, legal obligation, vital interests, public task and legitimate interests. Running an event someone registered for is often covered by contract, while marketing and data sharing more often rely on consent.

Sources