Commercial, partnership and post-event problems
When a sponsor asks for delegate data beyond what was agreed
A sponsor has asked for the full delegate list with phone numbers, and the registration form only mentioned opt-in sharing.
Opens WhatsApp with a draft you can edit before sending. Nothing is sent automatically.
The short answer
Do not send anything yet. Find the registration wording, the sponsor agreement and the list of what delegates were told, then compare them with exactly what the sponsor is asking for.
Whether sharing is allowed is a privacy question for your data protection contact or legal adviser. Your task is to give them the facts and to offer the sponsor the options that the agreed permissions already allow.
What is known and what is not
Write down what the records show before replying. Anything in the middle column is a question for someone with the authority to answer.
| Known | Not yet known | Who can answer |
|---|---|---|
| The exact data the sponsor is requesting, in its own words | Why the sponsor needs it and what it would do with it | Sponsor contact, asked in writing |
| The wording on the registration form and any privacy notice | Whether that wording covers the sponsor's request | Data protection contact or legal adviser |
| What the sponsor agreement says about delegate data and lead sharing | Whether a separate data agreement was ever signed | Agreement signatory; legal adviser |
| Which delegates ticked an opt-in box, if there was one | Whether the opt-in records are complete and can be exported reliably | Registration platform administrator |
| Where the delegate data is stored and who has access | Whether the registration supplier has its own conditions | Registration supplier, asked in writing |
Who has authority to decide
The organiser decides what it will share, but only after the privacy question is answered by the competent person. In a small association that may be the secretariat head with a data protection contact. In a company it is usually the privacy or legal team.
A project lead can collect the evidence and draft the question pack. The decision on whether sharing is permitted is not for the project lead or the sponsor to make.
- What may be shared: data protection contact or legal adviser.
- Whether a sponsor benefit is changed: committee chair or conference owner.
- What is said to the sponsor: secretariat head, after review.
- What delegates are told, if anything changes: chair and data protection contact.
The realistic options, including stopping or scaling down
The options below range from the narrowest to the widest. Pausing the request is a real option while the question is reviewed.
| Option | What it involves | Consequence to weigh |
|---|---|---|
| Hold the request and ask for the purpose | Reply that the request is under review and ask what data is needed and why. | Sponsor may be unhappy at the delay. Nothing is shared in the meantime. |
| Share only what delegates opted into | Export only the records with a recorded opt-in, with the fields agreed. | The list may be smaller than the sponsor expected. |
| Offer an on-site route | Let delegates choose to give details at the sponsor's stand, for example by badge scan if the platform supports it. | Needs delegate-facing wording and a way to record the choice. |
| Offer aggregated information | Share totals by job level or sector instead of names. | Useful for some sponsors, not others. Needs a check that small groups cannot identify individuals. |
| Decline the request | State what the agreement and registration wording allow and stop there. | May affect the relationship. Confirm the position with your adviser first. |
Who says what to whom
Keep the reply short and factual. Do not state that sharing is lawful or unlawful, and do not promise a date for the answer beyond what you control.
Short template to the sponsor:
- Thank you for your request of [date] for [data requested]. We are reviewing it against the registration wording and the sponsor agreement.
- To help us, please tell us what the data will be used for, who will have access, and for how long.
- We will confirm what can be provided by [date]. In the meantime, the lead-sharing options in the agreement remain available.
Follow-up and preventing a repeat
- Record the request, the review and the final decision in a decision log.
- Use the registration form field minimiser for the next event, so each field has a purpose, an owner and a retention note.
- Add data-sharing terms to the sponsor deliverable tracker, so the permitted route is visible before the sponsor asks.
- Write the permitted sponsor data options into the sponsor reporting checklist and into the registration notice before registration opens.
- Ask your data protection contact to review the form wording before it is reused.
Worked example · Fictional example
Persatuan Fiktif Jurutera Data asks what it may share
Fictional organisation and illustrative figures. No real sponsor, form or agreement is described.
A fictional association hosts a two-day forum for 420 registered delegates. Its gold sponsor writes after the event asking for the full list with mobile numbers. The registration form had an optional box allowing contact by sponsors, ticked by 138 delegates.
The secretariat head holds the request, finds the form wording and the agreement, and sends both to the association's data protection contact with a short question pack. The committee agrees to offer the sponsor the 138 opted-in contacts with name, company and job title, once the contact confirms. Phone numbers are not included because the form did not mention them.
Use this yourself
Question pack for the data protection contact or legal adviser
Send this with the form wording, the sponsor agreement and the sponsor's request attached.
- What exactly has the sponsor asked for, and does the registration wording cover each field?
- Which delegates, if any, gave a recorded opt-in, and what did the opt-in say?
- Does the sponsor agreement or any other document address delegate data?
- Is a separate data-sharing agreement or notice needed before anything is shared?
- Which fields, if any, can be shared, and for what stated purpose?
- Does anything need to be told to delegates, and by whom?
- How long may the sponsor keep the data, and who confirms deletion?
- Should a registration supplier be consulted before any export?
- What must be recorded so we can show what was decided and why?
Handle it in-house, or bring in help?
Your team can usually handle this when
- The registration wording clearly covers sponsor contact and the records are complete.
- The request is small and matches the agreement.
- A data protection contact is already in place.
Outside planning help earns its fee when
- The wording is unclear or opt-in records are incomplete.
- The request touches sensitive fields or many delegates at once.
- Several parties hold the data, such as a registration supplier, a co-host and the sponsor.
Want the request handled in order?
A project lead can gather the form wording, agreement and registration records, draft the question pack for your privacy or legal contact, and manage the reply to the sponsor while your committee decides. A planning diagnostic can review how data is collected and shared across registration, sponsors and suppliers, and list what to change before the next event. Privacy and legal conclusions stay with your own advisers.
Questions organisers ask
Can we send the list if the sponsor promises to be careful?
A promise does not settle the question. Whether sharing is permitted depends on what delegates were told and what the agreement says. Put the facts to your privacy contact or legal adviser first.
What if a delegate asks what we shared?
Keep a record of what was shared, with whom and when, so that you can answer accurately. Your data protection contact can advise on how to respond.
Should we stop the sponsor receiving any leads?
Not necessarily. Leads that delegates agreed to share may still be provided under the agreement. Confirm the position with your adviser before deciding.
Related resources
Content record: Draft. Written from the cited sources and checked by automated rules; not yet independently reviewed.