If you are a professional who manages a client’s guest list, the GDPR applies to you, even though a couple organizing their own celebration is in principle exempt. You therefore need to know your role, give each vendor only what they need, protect allergy and religious meal information, and delete the data once the event is over.
In short
- The « purely personal or household activity » exemption covers private individuals, not the wedding planner, caterer, DJ or venue.
- Your obligations depend on your role, controller or processor. That role is judged on the facts, not on what the contract says.
- An allergy is health information. A halal or kosher meal can reveal a religious belief. Both are sensitive data.
- The caterer does not need phone numbers, and the DJ does not need allergies: send each person their share, nothing more.
- After the event, delete the data or hand it back. Do not keep it « just in case ».
The couple and the professional: two different situations
Under Article 2, the GDPR does not apply to processing carried out « by a natural person in the course of a purely personal or household activity ». A couple who keep their guest list in a spreadsheet are, in principle, in that situation.
You, on the other hand, work in a professional capacity. The exemption is aimed at an individual in their private life, not at the business that receives the list in order to deliver a service. And a guest list is indeed a list of personal data, meaning information « relating to an identified or identifiable natural person »: names, email addresses, phone numbers, meal choices, table assignments.
A company organizing a seminar or an evening event is even more straightforward. It is not a private individual: the GDPR applies to it and to its vendors alike.
A note on scope: the GDPR is a European Union regulation, and the links in this article point to the French authority, the CNIL, which publishes the text and its guidance in French. If you work outside the EU and the EEA, or if your event involves guests in several countries, check which data protection rules and which national authority apply to you.
Controller or processor: who plays which role?
The GDPR distinguishes two roles. The controller determines the purposes and means of the processing. The processor processes data « on behalf of the controller ». The CNIL reminds us of this in its guide on identifying your role: the qualification does not depend on a contractual choice but on the facts. The question to ask yourself is therefore simple: who decides what, and who carries out what?
| Situation | Likely role | Why |
|---|---|---|
| A company entrusts its seminar to an agency | The company is the controller, the agency is often the processor | The company decides who is invited and why. The agency follows its instructions. |
| A wedding planner who manages the couple’s list | The planner is generally the controller | The couple is in principle exempt. The planner chooses their tools, their vendors and what is collected. |
| A caterer who receives the meal choices and tables | Processor if they follow instructions, controller if they use the data for their own purposes | It all depends on how the data is actually used. |
| Online software that hosts the list | Processor | It processes the data on behalf of its customer. |
This table is no substitute for a case-by-case analysis. The GDPR also provides for joint controllers (Article 26), who set purposes and means together and divide their obligations in an agreement. Be careful: under Article 28(10), a processor that determines the purposes and means itself is considered a controller for that processing. That is the case of a caterer who reuses a list they received for their own marketing.
The CNIL advises documenting the reasoning that led to your qualification. A few lines in your standard client file are enough to start with.
Allergies, halal, kosher, reduced mobility: sensitive data
For the CNIL, sensitive data includes in particular health data and religious or philosophical beliefs. In a wedding guest list, you find them in three places:
- Allergies and intolerances reveal information about a person’s physical health. That is the definition of health data given in Article 4.
- Halal or kosher meals can reveal a religious belief.
- A « wheelchair » or « reduced mobility » note can also reveal information about a person’s health.
As a rule, Article 9 prohibits processing this data. It provides exceptions, including the explicit consent of the person concerned. The CNIL describes this consent as an active, explicit step, preferably in writing, which must be freely given, specific and informed.
What this changes in practice
- Ask the guest directly, for example in the RSVP form, and say clearly what the information will be used for: adapting their meal.
- Ask for the meal they would like, never their religion. « No pork », « halal » or « vegetarian » is enough for the caterer.
- Keep only the information needed for the service: the tree nut allergy, not the medical history.
For the logistics, that is, collecting allergies and getting them all the way to the plate, read our guide to allergies and dietary requirements at weddings.
Minimisation: each vendor gets their share of the list
Article 5 requires data that is « adequate, relevant and limited to what is necessary in relation to the purposes ». In practice, the complete list should not circulate. Here is a working basis to adapt:
| Vendor | What they need | What they do not need |
|---|---|---|
| Caterer | Number of covers, adults and children, dietary requirements and allergies with the name and table of the people concerned | Phone numbers, addresses, replies from guests who declined |
| Venue | Headcount, floor plan, accessibility needs relevant to the welcome | Meal details, guests’ contact details |
| DJ or MC | First names of people mentioned on the microphone, key moments | Allergies, dietary requirements, contact details |
| Photographer or videographer | Key people and the group photos requested | Full list, dietary requirements, contact details |
This sorting is also a matter of security. The less the list circulates, the less likely it is to leak.
Sharing without leaks
Article 5 also requires « appropriate security ». Article 32 asks for measures suited to the risk, notably against unauthorized disclosure. Three common habits run against this principle:
- The spreadsheet attached to an email. Every send creates one more copy, which can be neither withdrawn nor updated.
- The messaging group where the list or a screenshot is pasted. Every member keeps it on their phone.
- The single PDF file sent to everyone, with phone numbers and allergies.
Prefer individual access, limited to what each vendor needs to see, and which you can withdraw. If a PDF is still necessary, make one per vendor: our article on the wedding PDF file explains how to adapt it, and the one on vendor coordination shows how to work from a single source of information.
In the event of an incident, such as an email sent to the wrong address or a lost phone, Article 33 applies. The controller must notify the supervisory authority of the breach « without undue delay and, where feasible, not later than 72 hours », unless it is unlikely to result in a risk to individuals. The processor must inform the controller without undue delay.
The contract with your vendors and tools: Article 28
When you have data processed by a processor (a software provider, a host, sometimes a vendor), Article 28 requires a contract. It sets out the subject matter, duration, nature and purpose of the processing, the types of data and the categories of people. Check that it requires the processor to:
- process the data only on your documented instructions;
- bind its staff to confidentiality;
- take the security measures of Article 32;
- engage another processor only with your prior written authorization;
- help you respond to requests from individuals;
- delete or return the data at the end of the service, at your choice, and destroy existing copies;
- provide you with the information needed to demonstrate compliance and allow audits.
In its guide on managing subcontracting, the CNIL also recommends asking the provider for its security policy and setting out the conditions for returning and destroying data at the end of the contract.
Finally, think about the record of processing activities (Article 30). Organizations with fewer than 250 employees are in principle exempt, but not if the processing is not occasional or involves sensitive data, which is often the case for a professional who handles allergies at every event.
After the event: retention, deletion and guest requests
The GDPR does not set a retention period for a guest list. It lays down a principle (Article 5): do not keep data longer than necessary for its purpose. Once the party is over, the seating and the meal choices serve no further purpose. Set your rule in writing, state it in your terms, then apply it:
- delete the list and the dietary requirements, or return them to the client, within the stated period;
- ask your own vendors to do the same;
- do not forget the copies: attachments, downloads, printouts, screenshots in messaging apps.
If a guest asks for access to their data or for its erasure, Chapter III of the GDPR applies. The controller replies within one month, extendable by two further months if the request is complex, provided the person is informed. The right to erasure (Article 17) applies in particular when the data is no longer necessary or when the person withdraws their consent. If you are a processor, pass the request on to the controller and help them respond.
Article 14 also requires, with some exceptions, that people whose data was not collected from them be informed. A short notice in the guest reply form is often the simplest solution.
Common mistakes
- Reusing guests’ contact details for marketing. You become the controller of this new processing, with all the obligations that come with it.
- Believing the contract decides the role. The facts are what count.
- Asking for religion instead of the preferred meal.
- Forgetting printouts. A paper file with guests’ contact details, left on a table at the end of the evening, is a leak like any other.
Building a data-respectful guest list with Eventelio
Eventelio replaces neither your legal analysis nor your procedures. Several of its features do, however, support minimisation:
- Access per vendor. Each invited vendor receives their own access, with rights you set one by one: schedule, venues and times, key people, meals and dietary requirements, requested photos, floor plan, guests and seating, music, contact details. They never see prices, deposits, payments or internal notes.
- Dietary requirements and allergies where they are needed. Each guest has a « diet or allergy » field, and the caterer can view the named list, with the number of people concerned and their table, within the rights you grant. This information is declarative: it must be confirmed by the caterer’s food safety procedures.
- One PDF file per participant, limited to what they are entitled to see.
- A clarified role. When you organize the event for your clients, you are the controller for their data; Eventelio acts as a processor for hosting and running the platform. The details are set out in the privacy policy and the terms and conditions.
- A free online seating chart that processes the list only in your browser: nothing is sent to Eventelio. You can turn off saving on the device or erase everything in one click.
If your client connects their own assistant to their event, read our advice on access keys and the change log. To go further, see the pages for caterers and for event agencies.
Frequently asked questions
Do the couple need to have their guests sign anything?
A couple organizing their own celebration is in principle covered by the household exemption. However, if you collect allergies or religious meal choices yourself, provide for explicit consent and clear information, for example in the reply form.
Can the caterer keep the list after the wedding?
If they are a processor, they must delete or return the data at the end of the service, unless a legal retention obligation applies. In every case, they must not keep it longer than necessary.
Can you ask a guest about their religion?
It is not necessary: ask for the preferred meal. Even so, a halal or kosher meal can reveal a religious belief. Treat it as sensitive data.
What should you do if a guest asks to be removed from the list?
If you are the controller, reply within a month, erase their data if the conditions of Article 17 are met, then inform your vendors. If you are a processor, pass the request on to the controller without delay.