Build log/Events

Event registration forms and UK GDPR: what you can collect and why

An event registration form should collect only what you need to run the event and explain why. Dietary and access needs, marketing consent and sponsor sharing need extra care.

The short answer

  • An event registration form should collect only the personal data needed to run the event, and tell people at the point of collection why and how it will be used.
  • Dietary and access requirements can reveal health or religious belief, which are special category data under UK GDPR and need an extra condition, usually explicit consent.
  • Marketing emails to individuals need consent under PECR unless the soft opt-in applies, and consent to share details with sponsors must name the sponsors.

Under UK GDPR, an event registration form should collect only the personal data you need to run the event, explain why at the point of collection, and rely on a clear lawful basis for each use. UK GDPR is the UK’s version of the General Data Protection Regulation, which works alongside the Data Protection Act 2018 to govern how organisations use personal data. Dietary and access needs, marketing consent and sharing attendee lists with sponsors need the most care.

Collect what you need and say why

Data minimisation, one of the principles of UK GDPR, requires personal data to be adequate, relevant and limited to what is necessary for the purpose. For each field on a registration form, ask what you will actually do with it. If the answer is nothing, remove the field.

FieldTypical purposeLikely lawful basis
Name and emailSend the ticket and event updatesContract, or legitimate interests for free events
Job title and organisationBadges and planning a business eventLegitimate interests
Dietary requirementsCateringContract or legitimate interests, plus an Article 9 condition if it reveals health or religion
Access requirementsMaking the venue and sessions accessibleAs above, because health data needs an Article 9 condition
Marketing preferencesEmails about future eventsConsent, or the soft opt-in where it applies
Sponsor sharingPassing details to named sponsorsConsent

Tell people at the point of collection who you are, what you will use the data for, the lawful basis, who you will share it with, how long you will keep it and what their rights are. A short notice beside the form with a link to the full privacy notice is the usual approach.

Choosing a lawful basis

Every use of personal data needs one of the six lawful bases in Article 6 of UK GDPR. Three come up most often for events.

  • Contract. Processing that is necessary to provide what someone has signed up for, such as issuing a ticket, admitting them and telling them about changes.
  • Legitimate interests. Processing that is necessary for a genuine interest of yours, balanced against the attendee’s interests and reasonable expectations. Badges, attendance records and sensible follow-up after the event often fit here. Record the balancing test.
  • Consent. A freely given, specific, informed and unambiguous indication, given by a clear positive action and as easy to withdraw as to give. Pre-ticked boxes are not consent.

Pick the basis before you collect the data. Consent is a poor fit for things you must do anyway, such as sending joining instructions, because people expect to be able to withdraw it.

Dietary and access needs are often special category data

Special category data is personal data that needs extra protection under Article 9 of UK GDPR, including data about health, religious or philosophical beliefs, racial or ethnic origin and sexual orientation. Event forms collect it more often than organisers realise.

  • An allergy, coeliac disease or a need for step-free access is health data.
  • A request for halal or kosher food may reveal religious belief.
  • A vegetarian meal choice on its own usually reveals neither, though it can in some contexts.

To process special category data you need a lawful basis under Article 6 and a separate condition under Article 9. For events, explicit consent is the condition most organisers rely on. Explicit consent means a clear statement that the person confirms, such as a tick box beside the words “I agree to my dietary and access requirements being shared with the caterer and venue to arrange this event.”

Make these fields optional, ask only for what you will act on, share them only with the catering or venue staff who need them, and delete them soon after the event. A short list of options plus “other, we will contact you” collects less than a free-text box.

Marketing consent under PECR

The Privacy and Electronic Communications Regulations 2003, known as PECR, sit alongside UK GDPR and govern electronic marketing. Sending marketing emails or texts to individuals generally needs their prior consent. The exception is the soft opt-in. It can apply when you obtained the person’s details in the course of a sale or negotiations for a sale, the marketing is about your own similar products or services, and you gave them a simple way to refuse when you collected the details and in every message since.

For paid events, the soft opt-in may cover emails about your future similar events, provided the opt-out was offered on the form. For free events it is less clear-cut, so many organisers ask for consent. Under PECR, emails to people at corporate addresses are treated differently, although sole traders and some partnerships count as individuals and UK GDPR still applies. The Data (Use and Access) Act 2025 amends parts of UK GDPR and PECR, with changes taking effect in stages, so check the ICO’s current guidance before relying on any of these rules.

  • Use an unticked box for marketing consent, separate from the terms and conditions.
  • Keep a record of when and how each person consented and what they were told.
  • Include an unsubscribe link in every message and act on it promptly.

Sharing attendee lists with sponsors

Passing the delegate list to a sponsor discloses personal data to another organisation, which becomes a controller in its own right. Attendees must be told, and where the sponsor will use the data for its own marketing you will normally need their consent.

The ICO’s guidance on consent says that you must name any third-party controllers who will rely on the consent. Wording such as “our carefully selected partners” is not enough. List the sponsors by name on the form, give a separate tick box, and pass on only the details of people who ticked it.

A common alternative is badge scanning at the event, where a sponsor scans the badge of anyone who visits their stand and agrees to be contacted. Tell attendees in advance how this works and what a scan shares.

Photography and filming

Photos and video in which people can be identified are personal data. Organisers usually rely on legitimate interests for general event photography, which means telling people in advance and giving them a practical way to object. Put a photography notice in the registration confirmation and at the venue entrance, explain how images will be used, and offer a simple opt-out such as a different coloured lanyard. Close-up photos of individuals for promotional use, and any photography involving children, need more care, and consent is often the right basis.

Retention, suppliers and security

The storage limitation principle in UK GDPR means personal data must not be kept for longer than the purpose needs. There is no fixed period for event data, so set your own, write it down and apply it.

DataExample retentionReason
Dietary and access requirementsDelete within 30 days of the eventOnly needed to run the event
Registration detailsUntil the next edition of the event, then reviewReasonable follow-up and repeat events
Payment and invoice recordsAs required for tax, generally six years for a companyHMRC record-keeping
Marketing consent recordsFor as long as you rely on the consent, and a period afterProof that consent was given

The periods here are examples. Choose ones that fit your events, and make sure your event platform can actually delete or anonymise data when each period ends.

Your ticketing platform, email service and event app process attendees’ data on your behalf, which makes them processors. You need a written contract with each one that meets Article 28 of UK GDPR, and you need to know where they store the data. Limit access to the attendee list to the people who need it. Check-in devices hold a copy of the list too, as covered in offline event check-in, so encrypt it and wipe it afterwards. For the rest of the event stack, see what an event app needs.

Attendees can ask for a copy of their data, and you must respond to a subject access request within one month. A personal data breach that is likely to pose a risk to people must be reported to the ICO without undue delay and, where feasible, within 72 hours of becoming aware of it.

Building registration into your own platform? We design forms, consent records and retention rules in from the start. See our events sector page.

Questions people ask

Do I need consent to collect dietary requirements?

Dietary requirements that reveal health, such as allergies, or religious belief, such as halal or kosher meals, are special category data under UK GDPR. Processing them needs an Article 9 condition as well as a lawful basis, and for events that is usually explicit consent. Keep the field optional and delete the data soon after the event.

Can I share my attendee list with sponsors?

Sharing an attendee list with sponsors usually needs attendees’ consent, given separately from registration, with each sponsor named. Generic wording such as “selected partners” is not specific enough. Badge scanning at stands, where attendees choose to share their details, is a common alternative.

Can I email attendees about future events?

Under PECR you can email individuals about future events if they consented, or if the soft opt-in applies because they bought a ticket and were offered a way to opt out at the time and in every message. The emails must be about your own similar products or services.

Written by Flavoureak

We build and run Estimark, CurioKids and CalcStack, and we build web and mobile software for other businesses. Start a project.