In June 2018, the Royal Dutch Lawn Tennis Association (KNLTB) handed its members’ personal data to two sponsors and was paid for it. One sponsor sent leaflets, the other ran a telephone campaign. The Dutch data protection authority fined the association 525,000 euros, and on a reference from the Amsterdam District Court the dispute reached the Court of Justice of the European Union (CJEU).
A sponsor’s request can sound routine. Two weeks before a congress, the sponsor’s sales team asks for names, companies and email addresses so it can book meetings. The sponsorship deck promised “access to 600 decision makers”, but that wording leaves open how the organiser will deliver it.
Decide how sponsors and exhibitors will meet attendees before you sell the package. If you intend to share contact details on the basis of consent, give each attendee the choice before registration closes. The options below include pre-booked meetings and explain how the CJEU and the European Data Protection Board (EDPB) approach data sharing. They also cover differences between EU and UK email rules.
Four ways an attendee list leaves your hands
Before you answer that email, name what the sponsor is actually asking for. In everyday event work, “attendee list” covers at least four different transfers, and each has its own legal position under the General Data Protection Regulation (GDPR).
| Form | Who receives what | Usual lawful basis | What you need first |
|---|---|---|---|
| Spreadsheet sent to sponsors or exhibitors | Name, company and contact details of all attendees | Consent (Art. 6(1)(a) GDPR) | A separate opt-in at registration, recipients named |
| Delegate directory for all attendees | Name, company and city, printed or in the app | Consent, or legitimate interest after a careful balancing test | A free choice at registration, fields defined |
| Visible profiles in the matchmaking | Profile with offer and needs, shown to approved groups | Consent | Visibility chosen by the attendee |
| Contact details after a meeting or scan | One person’s details to one exhibitor | Consent | Agreement at registration, documented |
The further the data travels from the event itself, the more everything depends on consent. A directory on the lunch table helps attendees find each other. A spreadsheet in a sponsor’s sales system helps the sponsor sell.
Once you send the file, the sponsor is not your service provider. It decides what happens to the data, which makes it a controller in its own right. You therefore need a lawful basis for the transfer under Article 6 GDPR, and you must name the recipients or categories of recipients when you collect the data (Art. 13(1)(e)). The sponsor then has duties of its own: it must inform attendees at the latest with its first message, and in any case within one month (Art. 14(3)).
The file travels with a to-do list attached.
What the tennis case tells event organisers
The Dutch case is the closest the courts have come to the sponsor’s request. The association had not asked its members for consent and argued that it could rely on legitimate interest instead.
KNLTB: member data passed to sponsors in 2018
In its judgment of 4 October 2024, the CJEU accepted that a commercial interest can be legitimate, provided it is lawful (para 49). But it set a high bar: the transfer must be strictly necessary for that interest, and the members’ rights must not override it (C-621/22, para 57). The court then described a less intrusive route. The association could inform its members beforehand and ask whether they want their data passed to the sponsors, so they keep control over the disclosure (paras 51 to 53).
For an organiser, that describes a registration form. The court did not ban sharing. It pointed to the question you should ask first.
The EDPB agrees. Its Guidelines 1/2024 on legitimate interest (version 2.0, adopted 10 November 2026) say direct marketing “may” be a legitimate interest. But “this does not mean that direct marketing always constitutes a legitimate interest” (para 108). Unsolicited marketing by email or text message can only take place with the prior consent of the recipient, subject to the exception for existing customers (paras 113 and 115). Your sponsor has sold nothing to your attendees, so that exception does not help it.
Email rules differ between the EU and the UK
The rules for emailing business contacts depend on the country.
In the EU, the ePrivacy Directive requires prior consent for email marketing to natural persons (Directive 2002/58/EC, Art. 13(1) and 13(5)). For companies as subscribers, each member state decides how they are protected, and some go further than others. In Germany, for example, the Act against Unfair Competition requires prior express consent for advertising emails to business contacts too (Section 7(2) No. 2 UWG).
The UK draws the line differently. The Information Commissioner’s Office (ICO) states that the electronic mail rule in the Privacy and Electronic Communications Regulations (PECR) “does not apply to corporate subscribers”. But the UK GDPR still applies to the named person behind a business address. Sole traders and some partnerships count as individual subscribers, and the right to object to direct marketing “is absolute” (ICO, business to business marketing guidance, accessed 16 November 2026). The ICO also notes that its guidance is under review after the Data (Use and Access) Act.
A sponsor at an international congress cannot tell from a spreadsheet which regime applies to which row. Neither can you. A list nobody can safely email is worth little.
If you share: five conditions for consent that holds
If you do want to pass contact details to exhibitors or sponsors, consent is the realistic route. Under Article 4(11) GDPR it must be freely given, specific, informed and unambiguous. In your registration form, that means:
- A step of its own: Sharing gets its own unticked box. The EDPB is explicit that pre-ticked opt-in boxes are invalid (Guidelines 05/2020 on consent, para 79), as the CJEU held in Planet49 (C-673/17, 1 October 2019). Bundling several purposes into one agreement also undermines free choice (para 44).
- No condition: Attendance must not depend on it. Article 7(4) asks whether a service is tied to consent that is not needed to provide it. A ticket buyer gets the ticket without the tick.
- Recipients named: Where other controllers will rely on the consent, they should all be identified (EDPB Guidelines 05/2020, para 65). The ICO puts it plainly for marketing lists: “Generic consent covering any third party will not be enough.”
- Fields limited: Decide which fields go out. Name, company and job title are enough to start a conversation.
- Withdrawal and proof: Withdrawing must be as easy as giving consent (Art. 7(3)), and you must be able to demonstrate it (Art. 7(1)). Our guide to the event CRM for organisers shows how to store date, wording and version next to each contact in your customer relationship management (CRM) system.
Naming recipients has a consequence planners often miss. A sponsor who signs in August is not covered by a consent collected in May that did not mention it. Plan the sharing around your sponsor list, not around the registration launch.
Some institutions make this a house rule. The Faculty of Law at the University of Oxford tells its event organisers: “Don’t share attendee lists with sponsors without explicit consent”. The same guidance advises against printing full attendee lists unless necessary (Events and GDPR, accessed 16 November 2026). One sentence, and the question is settled before anyone asks.
Meetings instead of lists: what you can promise sponsors
Even a clean consent answers only half of what the sponsor’s sales team wants. It does not want a spreadsheet, it wants conversations with the right people. The most robust answer separates the two: the data stays with you, and the sponsor gets contacts that attendees have chosen themselves.
From registration form to sponsor meeting, without sending a list
- Registration Attendees choose visibility In a separate step, attendees decide whether exhibitors and sponsors may see their profile.
- Before event Profiles go live Approved groups see only the fields you defined, without email address or phone number.
- Request phase Sponsors request meetings Attendees accept or decline without giving a reason and without a visible status.
- Meeting day Contacts follow meetings Contact details move only from meetings that took place, and only where the attendee agreed.
- Afterwards Report without names Sponsors receive meeting numbers and a breakdown by sector and role, with no personal data.
The sponsor ends up with fewer names but more conversations. Attendees who said no never reach its sales system, and those who said yes expect its message. Associations apply the same logic to industry partners; our guide to industry partner meetings at association congresses shows the rules that keep members in control.
At trade shows, badge scanning at the stand adds a second channel. A scan does not replace consent either, which is why our article on lead retrieval for event organisers argues for a consent layer in registration before you sell scanning licences.
Solution: In Converve, the meeting matrix sets the rules for each pair of participant categories. They can request meetings with each other, only view each other, or not see each other at all. Sponsors and exhibitors then reach attendees through meeting requests on the platform instead of an exported list. You set up registration with ticket types per participant group, and the platform is hosted in Germany with a data processing agreement as standard. How requests and the matrix work together is shown on the B2B matchmaking page.
This changes your sponsorship deck too. Instead of “access to 600 decision makers”, you promise visibility to consenting attendees, a fixed number of meeting requests and a report. How to describe such benefits so sponsors can price them is covered in our guide on how to write a sponsorship prospectus.
Sell meetings, not lists.
What belongs in the sponsor and exhibitor contract
Selling meetings still means some data moves, such as contact details from meetings held. Put the rules in writing before the first file leaves the building:
- Purpose: the data serves follow-up on conversations at the event, not a general marketing database.
- No onward sharing: the recipient does not pass the data to third parties, resellers or other companies in its group.
- Information: the recipient informs attendees under Article 14 GDPR, with its first message and within one month at the latest.
- Marketing: email marketing only where the applicable rules allow it, and any objection to direct marketing is honoured at once (Art. 21(2) and (3) GDPR).
- Deletion: a deadline for unused data and a named contact at the recipient for attendee requests.
Do you decide on registration and data use together with a partner such as an association or chamber? Then you may be joint controllers, and Article 26 GDPR requires an arrangement on who fulfils which duty. Whether your software supports consents, retention periods and processing agreements properly can be tested with our checklist for GDPR-compliant event software.
This article is general information, not legal advice. Agree wording and contracts with your data protection officer or legal counsel.
Four mistakes from the last week before the event
Review the process before the event so the team knows how to handle last-minute requests for a list.
- The list goes to every sponsor, although the form named only one.
- The invitation to the evening reception goes out in an open “To” field, so everyone sees every address.
- The sharing box is pre-ticked or hidden in the terms and conditions.
- Last year’s list goes to this year’s new lead sponsor, whom last year’s consent did not name.
Each can be prevented in the registration form. Afterwards, it is too late. Separate consents need not make the form longer, as our article on registration questions that make matchmaking work shows by splitting questions before and after confirmation.
Frequently Asked Questions
Can I share an attendee list with sponsors under GDPR?
Only with a lawful basis, which in practice almost always means each attendee’s consent naming the sponsor. Legitimate interest rarely carries it: the CJEU requires the transfer to be strictly necessary and pointed to asking members beforehand as the less intrusive route (C-621/22, 4 October 2024).
Can I give a delegate list to all attendees?
Yes, if attendees know beforehand which details it contains and can choose freely. Keep it to name, company and city; email addresses and phone numbers do not belong in a printed directory.
Do I have to name sponsors and exhibitors in my privacy notice?
You must name the recipients or categories of recipients when you collect the data (Art. 13(1)(e) GDPR). If you rely on consent for sharing, the EDPB expects the receiving organisations to be identified (Guidelines 05/2020, para 65). Sponsors who join later are not covered by an earlier consent.
Can an exhibitor email attendees after the trade show?
In the EU, marketing emails to individuals need prior consent under the ePrivacy rules, and Germany extends this to business contacts. In the UK, the PECR email rule does not cover corporate subscribers, but UK GDPR still applies and every objection must be honoured (ICO guidance). Say so in your exhibitor information.
Who is liable if a sponsor misuses the list?
The sponsor is responsible for its own processing. You remain responsible for the transfer: if it lacked a lawful basis, the fault is yours. Settle purpose, onward sharing and deletion in the contract first.
Conclusion: promise meetings, avoid lists
Sharing a list and emailing the people on it raise separate questions. If you rely on consent to share the details, ask for it separately at registration, make it optional and name the recipients.
You can also build a package around meetings. Let consenting attendees make their profiles visible, handle requests on the platform, share contacts from meetings held where appropriate and give sponsors a report without names.
Want to offer sponsors meetings instead of lists? Get in touch with Converve.