Event Guidelines
1. Introduction
These guidelines apply to events such as conferences, seminars, schools, exhibitions, ceremonies, protocol visits and workshops that are open to speakers and participants outside the CERN community and the processing of personal data takes place at CERN.
It does not apply to training, inductions, and general departmental or team meetings for the internal functioning of the Organisation.
An important aspect for the event organiser to consider is the extent to which personal data must be processed to organise and run the event. This will largely depend on the type and set-up of the event, as well as any related activities offered in connection with it.
As the event organiser will be responsible for the decision about the processing of personal data and the means of the processing, they will be considered the Controlling Service and, as such, in charge of providing a privacy notice to the data subjects concerned.
Depending on the event, the typical data subjects are participants and/or speakers.
These guidelines will provide guidance to the Controlling Service for the compliant processing of personal data required for the management of the participants and speakers of the event. In most of the cases, personal data will be collected and processed before, during and after the event, for various purposes such as:
- Call for abstracts
- Registration of participants and speakers
- Handling of payments
- Promotion of the event
- Communication with participants
- Video conferencing, multimedia and outreach
- Sharing of participants’ and speakers’ data
- Visa formalities
- Accommodation
- Social activities during the event
The following chapters provide data privacy recommendations for various aspects of the management of events are explained. Depending on the specific event, only a part of them may be relevant.
The use of external and internal tools for event management and the retention of the personal data processed in the context of the event will also be addressed.
2. Privacy notice
When organising an event that requires the processing of personal data, the Controlling Service must create a Record of Processing Operations (RoPO) to explain the details of the processing and to provide transparency to the data subjects concerned via a privacy notice.
The RoPO documents only the processing operations performed by the event organiser in his capacity as the Controlling Service.
If the organiser has to apply procedures imposed by other services and must process personal data in this context (for example: for visa formalities, for the issuing of access cards, etc.), the privacy notices of these other services (for example: Host States Relations service, Person and Vehicle Registration Service) should be displayed, in addition to the privacy notice for the event.
For recurrent events, such as yearly conferences or a series of workshops that involve the same data processing, a creation of a single RoPO is sufficient.
Depending on the scope and complexity of the data processing, the Controlling Service should consider documenting the processing operations in separate RoPOs. For example, one RoPO could cover participants’ data, while another could cover speakers’ data where these are processed for different purposes and on a different lawful basis and.
Once the RoPO is published, it will be available in the format of the Privacy Notice (PN). A link to this PN should be provided to data subjects (participants and speakers) on the registration form and on the web site of the event (ideally in the footer section), as well as to any other applicable PNs.
For the organisation of standard events (such as workshops, conferences or seminars), held on the CERN site, online or in a hybrid format, paid or for free, two generic privacy notices were developed:
- PN01661: Organising paid events (onsite, online and/or hybrid)
- PN01681: Organising free events (onsite, online and/or hybrid)
Both are linked to a generic Service Element.
Event organisers may use a generic privacy notice instead of creating their own, provided that it adequately covers the relevant processing activities. For more information about the usage of generic privacy notices, consult the Knowledge Base article Generic Privacy Notices
3. Tools for event management
Event management software provides features and functionalities to support the planning and running of events, such as
- event promotion, for instance by creating a web site to promote the event.
- registration of attendees; their personal details are usually collected directly from the participants through a registration form. It also lets people reserve spots for specific event activities.
- payment of registration fees. A ticketing platform allows ordering tickets online, to process credit cards or other payment forms.
- event planning, by providing tools to organise sessions, speakers, locations, break out rooms, etc.
- check-in of attendees for in person events where tickets and badges must be produced and distributed to the participants.
- event follow-up; for instance, by setting up surveys to capture the experience and feedback of the attendees.
It is recommended to use the CERN tool Indico which provides support in all of the aforementioned domains. It enables organisers to manage an event by avoiding unnecessary transfers, as the personal data is hosted and processed on CERN’s infrastructure.
If the Controlling Service wishes to use a tool that is not yet available at CERN, before using or buying the tool (even if it is freely available), the Cloud Licence Office (CLO) must be contacted at least two to three months before to launch the procurement process.
A note of caution: The use of a freemium tools (i.e. a tool made available by an external provider – commercial or not – with certain features which are free to use) still requires CERN to establish an agreement with the provider. In general, CERN members of the personnel do not have the right to sign Terms of Service or Contracts with providers and start using these tools to process personal data for work related matters. To use an external provider, CERN services must establish an enterprise agreement with adequate data protection measures, which is typically done during the procurement process.
The RoPO of the event should state which event management tool will be used for the purpose of the provision of the online platform to collect and store the data:
- when Indico is used: in the section “Who at CERN has access” an entry covering the data concerned should be added mentioning the Indico service.
- When an external tool is used: in the section “Personal Data we may transfer to others” an entry covering the data concerned should be added, mentioning the external tool provider and its location.
Independently of the tool used for the event management, the registration page should contain a clearly visible link to the Privacy Notice which should be established following the applicable procedure: Records of Processing Operations.
4. Speakers’ personal data
Speakers are key to every event. They intervene as moderators, masters of ceremony, presenters, lecturers, panellists, etc. and as such shape the event. Therefore, the processing of their personal data by the organiser to plan, organise and execute the event is necessary.
The collection and processing of speaker’s data can start before the registrations are open. This is the case, for example, when the event organiser launches a call for abstracts and processes the submissions, the authors’ details and the decision-making process.
In addition to the personal data processed for the management of participants, it is very likely that the event organiser will collect additional data and documents related to the speaker’s contribution, such as title of their talks, abstracts, bios, curriculum vitae, presentation slides, speaker release forms.
All these details must be documented in the RoPO. The purposes of their processing are normally to communicate about the event, to plan, organise and execute the event, for scientific and research purposes.
The lawful basis depends on the existence of a contractual relationship with the speaker. If a speaker agreement has been signed by the parties (see following chapter for more details), the lawful basis would be contract for the data that is processed in the context of the contract preparation and execution. Otherwise, the event organiser could claim a legitimate interest to process the speakers’ data.
Data that is processed in the context to provision of services that are available exclusively to speakers (for instance free accommodation in CERN’s hotel) must also be documented in the RoPO, with the appropriate lawful basis.
4.1 Speakers’ agreements
It is recommended to set-up an agreement with speakers who are not members of the personnel, to clearly define expectations, compensation, how speakers’ intellectual property will be used, etc.
Members of the personnel who speak at events organised by CERN are deemed to do this as part of their professional duties; furthermore, financial compensations are not applicable. Event organisers can claim a legitimate interest in using the members of personnel contributions. A speaker agreement should not be concluded with members of the personnel, but only with external speakers.
When speakers get onstage, they are sharing their intellectual property. For this reason, it is important to clearly describe in the agreement how and where it is planned to share and use their event content and in what form. For example, if their session will be filmed or live streamed and shared via social media channels, if they will be photographed, or if content from their presentation deck will be used for which purposes (e.g. scientific, research, other non-commercial purposes) and in what format, then a clause could be included.
Furthermore, anything related to payment or reimbursement should be outlined in the agreement, as well as services provided to the speaker free of charge (for instance free accommodation in CERN’s hotel).
It is reminded that payment and reimbursement schemes must be defined according to the existing procedures, such as Payment of lecturers in the context of outreach activities and Payment of travel expenses for invited people:
4.2 Presenters of posters at dedicated poster sessions
Due to their activities in the context of the event, the processing of personal data of presenters of posters is very similar to the processing of speakers’ data. The categories of the personal data may slightly differ – instead of titles and content of talks, titles of posters will be processed – but all other considerations regarding speakers’ data detailed in these guidelines apply also to presenters of posters.
5. Promotion of the event
Event organisers may want to promote their event by publishing relevant information, such as event title, dates, venue, speakers, on various media (for example: web sites, flyers, posters, TV spots, radio announcements) in order to bring it to the attention of the target audience. The sharing of personal data of speakers is often part of the public announcement.
If a speaker agreement with clauses regarding the usage of data for promotional purposes exist, the provisions must be respected for the design of any information campaign and the display of personal information of speakers on the promotional material.
The disclosure of speakers’ data in the context of the event promotion constitutes a processing operation that must be documented in the RoPO.
- Depending on the lawful basis that applies to the processing of speakers’ data (see chapter 3), the organiser would rely either on legitimate interest or on contract when disclosing speakers’ data for event promotion purposes.
- The media used for the promotion (web site, posters, TV spots, radio announcements, etc.) should be specified in the RoPO, together with any relevant details (URL of web sites, location of posters, etc.).
- The retention period must be limited to the purpose: the promotion of the event is normally limited in time, starts a few months before the event and finishes together with the event.
- Depending on the event, the target audience of the promotion campaign can range from the general public to a specific community. The scope of the posting of posters, the accessibility of web sites, etc. should be documented in the RoPO under “Who has access”.
6. Registration of participants
The event organiser must consider the kind and set-up of the event to decide whether the registration of the participants in necessary, and, if appropriate, limit the collection and processing of the personal data to the strict minimum.
Events that are open to the general public without limitations (example: webcast for a public announcement) might not require the registration of their participants, whereas in other cases the collection and processing of participant’s data is necessary, for instance if:
- Participation in the event is subject to certain conditions and the organiser has to verify and trace them (e.g. age limitations, restriction to certain professional categories);
- The capacity of the event is limited;
- Fees are to be paid;
- The nature of the event requires the identification of the participants (e.g. networking events).
Essential personal data of participants such as surname, first name, e-mail address and optionally affiliation, institution and/or position are used for organising an event. These data will allow the organisers to manage the event, and to identify and to communicate with the participants and in addition, to produce access cards and to print out the badges (Note: Wearing badges when on the CERN site is mandatory!).
Collection of additional personal data upon registration may be necessary depending, for instance, on the set-up of the event (e.g. subscription to sessions, social activities etc.) or the availability of additional services (e.g. accommodation, visa). Targeted recommendations are provided in the following chapters.
The appropriate lawful basis for the registration of essential personal data of participants would be:
- Either contract in case the registration is necessary to manage the payment of registration fees,
- or legitimate interest if the processing of the data is indispensable, for instance for one of the purposes explained above.
A processing based on consent could also be considered but bears the risk that in case of the withdrawal of the given consent by a data subject, the data must be deleted, which could have serious impacts on the event management. Therefore, this lawful basis should be avoided when possible.
7. Communication with participants
Event organisers will establish a direct communication with participants on many occasions for various purposes, in general by e-mail, occasionally also by phone. The following aspects should be considered in this context:
7.1 Communication with potential participants
The purpose of this communication is the promotion of the event; it takes place usually before the event in form of e-mails announcing the upcoming event (“Save the date”, “Call for papers”, invitations, etc.).
A direct contact can only be established with persons who
- participated in the previous edition of the event, or
- have given their consent to receive information about the topic, for instance by signing up to a newsletter.
When sending the promotional information, the event organiser should give the recipients the possibility to refuse to receive further communication, for instance by replying to the sender or by unsubscribing from a distribution list.
The RoPO must document the distribution of the promotional information; the usage of the e-mail address for this purpose would be based on legitimate interest in case a) or consent in case b).
7.2 Communication with registered participants
At all times the event organiser can contact registered participants to communicate relevant information about the event, for instance reminders of upcoming deadlines, change in the program, announcement of new speakers. The organiser can contact the participants also after the event, for example to invite them to complete a satisfaction survey, share the proceedings after the event etc., as long as the content of the communication relates to the event.
The communication of information other than event-related, for instance marketing, requires the prior consent of each participant.
The RoPO must document the usage of the e-mail address for the communication of event related news; the processing would be based on legitimate interest.
7.3 Future contact with registered participants
Organisers should ask participants if they wish to be contacted in the future regarding similar events and if such is the case, an e-group can be set up with an unsubscribe link should a participant not wish to be contacted with information about future events.
For the collection of consent – ideally to be integrated into the registration form – the following must be observed:
- Consent must be freely given, specific, informed and unambiguous and must result from a statement or a clear affirmative action..
- Pre-ticked boxes or inactivity do not constitute valid consent; the individual must actively indicate agreement (e.g. by ticking a box).
- Granular consent (= separate consent for separate things) for distinct processing operations and purposes is required.
- Clear records must be kept to demonstrate consent. (E.g. Who among the participants gave consent and when? Who withdraw it?)
- There is a specific right to withdraw consent. The persons must be informed of their right to withdraw consent at any time, and withdrawal must be as easy as giving consent.
The RoPO must document the usage of the e-mail address for the distribution of further information based on consent, as well as the record of the consent given, in accordance with the legal obligation set out in § 23 OC 11. It is recommended to keep this record at least for five years, starting from the withdrawal of the consent.
8. Sharing of participants’ and speakers’ data
Data of participants and speakers can only be shared when necessary for the organisation and execution of the event. A case-by-case assessment is necessary to decide which data may be disclosed to whom, taking into account the purpose of the sharing.
As a basic principle, participants’ and speakers’ data can be transferred to specific third parties as long it is necessary for a specific purpose, for instance sharing of name, address and dates of the stay of the speaker with the travel agency to arrange the transport and accommodation.
The RoPO must document which data will be transferred or disclosed CERN internally and externally to whom and for which purpose(s).
8.1 Disclosure of speakers’ data
If an agreement with the speaker has been set up, the relevant provisions must be taken into account by the event organiser when sharing their data.
In case an agreement is not applicable, in general, the event organiser could claim a legitimate interest to widely share speakers’ data required to promote the event, such as their names, titles, biographies, affiliation to an institute, and subject of their talks. In practice, this could be done via the display of these details on web sites or posters that are freely and easily accessible.
Speakers’ contributions, such as their slide presentations, abstracts talks, or recordings of the speech, can be shared amongst the participants or with a larger audience depending on the circumstances. The type of the event, its topic and audience must be considered, as well as intellectual property of the speaker. For events with a focus on scientific exchange and research, the availability of contributions to participants is often expected, as well for paid events. Making contributions available to the general public could be justified as well, for instance for events aimed at the dissemination and popularisation of scientific content.
Due to the complexity of the subject, the event organiser should clarify with the speaker in which way their contributions can be used, ideally before the event in form of an agreement as described in chapter 3.
8.2 Disclosure of participants’ data
In many events, list of participants are available; they contain typically the name and the affiliation of the participants. In order to decide to which extent personal data can be shared with others, the event organiser should consider the kind of event, the expectations of data subjects and the privacy rights of the persons concerned.
8.2.1 Sharing among participants
The recommended approach is to seek the consent of the participant to disclose their data to the other attendees.
However, depending on the character and purpose of the event, the organiser could rely on legitimate interest instead. This is the case in particular for networking events or events for the purpose of scientific exchange, where the identity of each participant is an important information for the attendees. In such kind of events, generally participants expect that an attendees list exists and is shared with them.
That means, the participants would not be asked to agree with the data disclosure. However, the organiser should be prepared to accommodate attendees who don’t want their personal data used in this way, or foresee the possibility to opt-out for attendees who claim that their interest outweighs the interest of the organiser
8.2.2 Public access to participants’ data
The publication of the list of registered participants, for instance on the conference’s web site, requires that each participant has consented to the disclosure of their data.
Such a disclosure without prior consent, e.g. based on the legitimate interest, would be difficult to defend. Relying on legitimate interest of the organiser – for instance to increase the attractiveness of the event and to ensure its success – can be in fact problematic due to
- the difficulty to prove that it is necessary to publish worldwide the attendees‘ list for the successful organisation and execution of the event, as there are other, less privacy invasive ways available to achieve this objective, and
- the rights and interests of the attendees that would have been disregarded by such a mandatory disclosure.
The world-wide publication of personal data can constitute a considerable impairment of the privacy of the individual concerned; in the worst case it can lead even to physical and material damages, for instance if criminals use the participants‘ list to identify possible targets for burglaries.
The collection of consent for a public disclosure of participant’s data could be part of the registration form.
9. Visa formalities
It is the responsibility of the participant to check with the relevant consulate (Swiss or French for events hosted on CERN site, for example), which visa obligations exist in the country of the venue.
This can be mentioned in the Indico page for the event, if applicable.
For events hosted on CERN site, a “Letter of Confirmation” can be sent to the participant if they request it. To do so, the participant has to provide their private address. The letter can be sent by e-mail or post.
It is to be noted that the Controlling Service of the visa formalities at CERN is the Host States Relations service whose privacy notice (that is still to be published!) should be referenced on the registration form. The RoPO of the event organiser should therefore not document the usage of personal data that is collected specifically or otherwise used for the visa formalities.
10. Accommodation
During an event, participants (incl. speakers) can book accommodation either outside or inside CERN. It is recommended to select the option that minimises the amount of personal data to be collected, described in chapters 10.1 and 10.2.a below.
10.1 Accommodation outside CERN
CERN has negotiated special tariffs with hotels located in the local area. The list is available on the CERN Housing website. To book a room, the participant must provide the hotel with standard information such as last name, first name, arrival and departure dates and credit card details to secure the reservation. As this information is submitted directly by the participant to the hotel, there is no need to mention it in the RoPO.
10.2 Accommodation inside CERN
The organiser of the event may have to reserve some rooms in one of the CERN hotels. Booking of a room can be carried out:
a) Either directly by the participant
The participants contacts the CERN Housing Service. To check the availability, the participant must provide the block reservation reference linked to the event, last name and first name, arrival and departure dates and a valid financial guarantee (e.g. credit card).
This information does not need to be documented in the event RoPO, as the Housing Service, as the Controlling Service for this processing activity, has to document it in its own RoPO)
b) Or by the organiser
The organiser collects the accommodation details from the participants. In this case the participant indicates the request to book a room in the registration form, the information collected like name, first name, arrival and departure dates, gender and room type must be documented in the RoPO.
The processing of the corresponding data would be based on consent, and it would be shared internally with the housing service to book the desired accommodation.
11. Access cards and badges
For onsite events, participants are often equipped with conference badges that may serve several purposes: to allow the identification and/or authentication of the individuals, and/or facilitate networking. The appropriate lawful basis for the processing would be legitimate interest.
Sometime badges are equipped with RFID chips offering different functions: to track and trace the badge owner, and for cashless payments, for example. The data capture and analysis through these chips can be privacy invasive, therefore their deployment should be carefully considered by the event organiser. If necessary, a Data Privacy Impact Assessment would have to be carried out following the underlying procedure.
Access cards to the CERN site for external participants should be issued according to the procedure Visitors cards: Access to CERN for visitors and conference participants. The collection of the necessary data for the access cards can be done through Indico or by other means, depending on the choice of the event organiser. The Controlling Service of the data processing for the access card creation is the Security Service, which has to provide the privacy notice to document the data processing.
12. Video conferencing, multimedia and outreach
12.1 Broadcasting
For online and hybrid events, the processing of images and voices of speakers – and if appropriate of participants, too – through video conferencing tools is necessary to conduct the event. For in-person events, the organiser may also consider the use of broadcasting, for instance to reach a broader public.
Therefore, the event organiser can rely on legitimate interest for the processing of the live stream of video and audio data of speakers, if a speakers’ agreement does not govern the subject (in this case the lawful basis would be “contract”).
In how far the transmission of images and/or voices of participants is required depend on the type of the event. It can be essential for interactive events that focus on the exchange among speakers and participants. Consequently, the organiser could claim a legitimate interest. However, in order to respect the right to privacy, participants should be given the choice to interact either via the online chat function usually provided by the video conferencing tool, or orally with or without video.
It is recommended to use the video conferencing systems provided by CERN (currently Zoom), as their contractual conditions assure the respect of privacy of its users and compliance with OC 11.
The RoPO of the event should mention:
- in the data inventory part: that Voice and image of speakers and/or participants are processed, and
- in the “Who has access at CERN” part: that said voice and image are processed by the Video Conferencing service to provide the necessary service.
- in the “Personal Data we may transfer to others” part: that voice and image are disclosed to the participants in the event to allow for the execution of the event.
12.2 Recordings
Whereas, in case of online events the live stream of talks, panel discussions and, to a certain extent, also questions and answers sessions is essential for running the event, this does not necessarily apply to recordings of these contributions and their subsequent processing.
The organiser should consider first whether it is necessary to prepare recordings and for which purpose. As each processing operation is subject to the general principles laid out in OC 11, such as necessity, proportionality and minimisation, recordings should only be made if they are required to achieve the intended purpose.
Recordings that are “nice to have” and are not essential, can only be produced and further processed based on the consent of each individual concerned.
Examples of legitimate purposes to process recordings are:
- allowing interested persons in other time zones to watch the event
- for educational purposes
- for archiving purposes due to the historical and/or scientific interest of the contribution or the whole event
always depending on the topic and type of the event.
Events that are organised by CERN in the context of scientific and research activities are likely to be subject to archiving obligations as set out in Operational Circular no. 3. It should be noted that CERN’s archives are not public, and therefore access to the recordings of events should be limited to the responsible services.
Also, the disclosure of recordings must be adapted to the specific needs. If recordings are kept for educational purposes for instance, access should be limited only to the audience concerned; depending on the subject this could be a group of trainees or even the general public.
The retention period of the recordings should be adapted to the specific purpose. When recordings are used for educational purposes, they should be kept only for as long as training takes place and then they should be deleted; whereas recordings to be archived would be kept for an unlimited amount of time.
If a speaker agreement will be set-up, it should document the purposes for which recordings can be used and for how long, and also the way the recordings are processed and for how long they are kept.
When recordings are established, the RoPO of the event shall mention them in the Retention part, by documenting the purpose(s) and the duration of their conservation.
12.3 Photos
When photographs shall be carried out at events, the recommendations in the Guidelines on the collection, use and storage of photos and videos should be followed.
13. Social activities during the event
During an event it is possible that some social activities are organised either inside or outside CERN. The registration form can contain specific fields to allow the participants to indicate their attendance and any other information that is important in this context. These details are to be documented in the RoPO, as well with whom information is shared.
13.1 Meals
It is possible to collect through the registration form menu preferences and/or if any dietary restrictions exist. This information is to be documented in the RoPO in the field “data used”.
Particular attention is drawn to the sensitive nature of information about dietary restrictions. Information concerning food allergies and dietary preferences linked to religious practices (for example, kosher or halal diets) constitutes sensitive personal data, as it reveals information relating to a person’s state of health or religious beliefs. Its processing is therefore subject to specific requirements.
Information on the number of dietary options required should be provided to the restaurant anonymously.
It is the responsibility of participants to inform the restaurant directly of their specific dietary needs where meals are served at the table. For buffets, the restaurant should clearly label the food corresponding to specific dietary restrictions.
The list of participants and their menu preferences not revealing sensitive information can be shared with the person in charge of organising the meals, to provide assistance during the lunch to participants who have forgotten their choices.
13.2 Outing
In case of organisation of an event outside CERN only the number of participants is given to the bus driver. It is the responsibility of the organisers to check that all inscribed persons are present.
These details are to be documented in RoPO as “external transfer access” since the organiser will send the personal data to the bus driver.
13.3 Visit to experiments in CERN
It is up to the experiment to provide the organisers with their preferred subscription procedure:
- Direct registration with the experiment, which collects the required personal data.
In this case, the event registration form should not collect additional personal data for the visit, other than indicating interest in participating (if applicable). The RoPO should document only this indication of interest..
The experiment as Controlling Service has to provide the privacy notice documenting the processing of the personal data for the visit. - Registration via the event registration form, which collects all information required by the experiment for the visit and for issuing visitor passes.
Typically, these include first name, surname, nationality, date of birth, and place and country of birth. These must be documented in the RoPO..
Any data sharing with the experiment to organise the visit (may it be only the names of the interested persons, or more details) should be indicated in the RoPO of the event organiser.
If the visit takes place underground, the experiment will generate a Safety Impact document using first name, surname and birth date of each visitor. In case of subscription procedure b), these specific purposes are to be documented in the RoPO of the event. Safety rules for a visit to the experimental cavern are documented on the experiment’s web site.
14. Surveys
Surveys during or after the event are often carried out by event organisers in order to evaluate the degree of satisfaction of participants and speakers with content and organisation of the event, thus allowing the event organiser to improve those aspects for future events.
This purpose is likely to constitute a legitimate interest of the organiser to contact participants and speakers and to invite them to complete a survey. However, it is not always necessary to collect personal data through the survey questions. An anonymous completion should be the preferred option; else the collection and usage of the survey answers must be documented in the RoPO.
If the event management tool used is Indico, the integrated survey functionality should be used in order to minimise the processing of personal data.
Furthermore, event organisers should take into account the recommendations in the Survey Guidelines when setting up the questionnaire.
15. Retention of data
The event organiser must follow the Retention Period Guidelines in order to determine the appropriate duration of data retention. As a general principle, personal data may only be kept for as long as they are necessary to fulfill the purpose of the processing.
For the management of events, this means for instance that data collected from participants to register them and to allow them to attend the event, must be deleted or anonymised after the event or the latest after any post-event related activities (e.g. distribution of proceedings to the participants, evaluation of surveys, monitoring and statistics).
Sensitive personal data, e.g. collected in the context of the organisation of meals or social events, shall be deleted (or anonymised) as soon as possible, without delay immediately after the end of the event.
However, event organisers may need to keep certain data for a longer period, for instance to keep trace of individual participation to be able to check eligibility for future events, to allow for the establishment, exercise and/or defense of legal claims in case of allegations of violation of intellectual property, or to comply with archiving obligations.
In such cases, the event organiser should retain only those data that are required for the purpose and delete the rest. For instance, there is no need to keep payment data if data must be kept for future eligibility checks. The retention period should also be adapted to the purpose pursued. For example, if eligibility depends on the participation in the current event, data should not be retained for longer than the next event.
In how far retained participants’ data can be disclosed, depends on the purpose the retention. The explanations in chapter 8.2. concerning the initial disclosure should be taken into account.
The retention of speakers’ data by the event organiser may be required, in particular in case a speaker’s agreement exist to allow for the establishment, exercise or defense of legal claims. Where the processing is based on legitimate interest, the event organiser should preserve essential data of speakers such as identification details and contributions for the case of disputes or litigation.
The Indico application allows a granular definition of retention periods for data collected through the registration form.
Useful Links
Procedure: Processing of personal data for event organisation
Related FAQs
- I am organising a conference for people in and outside CERN. Can I publish on the conference’s web site the list of registered participants with their names and institutes?
- I am organising a conference. Can I share the list of participants with the attendees of the conference?
- Organising an event? Be aware of data protection!