When it comes to GDPR,
we've got your back at events.


The EU General Data Protection Regulation (GDPR) is designed to protect the data privacy of EU citizens and to reshape the way organizations that interact with EU citizens approach data privacy. The main purpose of GDPR, which takes effect on May 25, 2018, is to give EU citizens greater control over their personal information.

How will this affect you and your events?

It goes without saying that events involve the transfer of attendees’ personal information, from event registration to onsite lead capture to follow-up. Receiving and documenting EU attendees’ consent to use their personal information is at the center of GDPR.

In legal terms, your customers and contacts—including the people you interact with at events—are "data subjects." Your company controls their data, and are appropriately named "controllers." As a third-party data "processor," atEvent processes the data you capture, on behalf of your company. GDPR provides a set of rights that may be applicable to your customers, and imposes a set of regulations that may be applicable to both your company (controller) and your processors.

atEvent Product Enhancements

Scroll below to find a detailed list of the enhancements we have built to help you be compliant. 


What it means for you

You’re at an industry event, and you meet a new French prospect who is interested in your company's solution. You’re now required to get his explicit, written consent prior to following up with him post event.

How We Help You Comply

To enable you to stay compliant, we have added a GDPR consent capture feature. You will have the option when setting up or managing an event to enable a GDPR consent feature in the atEvent mobile app. This feature will allow you to capture consent in the app at the time of lead capture during the event, either through a check box or a signature.

After consent is captured, you can then continue scanning and recording the interaction details. A GDPR Compliance “yes” indicator will show on the Leads page in atEvent Central for each consenting lead and can be mapped to your MA/CRM.

Right To Be Forgotten

What it means for you

Let’s say your British contact John Clark calls you to ask you to stop contacting him, and to remove him from your records. You must comply with his request by removing all of his PII (personally identifiable information) from your database and systems.

How We Help You Comply

To assist you with the Right to be Forgotten request for event interaction data, we have added new capabilities.  You will have the ability to delete lead and interaction records in atEvent Central, in order to comply with the Right to be Forgotten clause of GDPR. When one of your contacts requests that his information be removed from atEvent, you can delete the information from the Leads page in atEvent Central, and confirm the deletion when prompted. 

atEvent Central will delete the record and show a transaction ID for the deleted record.

Note that the information will only be deleted in atEvent Central—not your Marketing Automation or CRM system.

Disclaimer: This website is neither a magnum opus on EU data privacy nor legal advice for your company to use in complying with EU data privacy laws like the GDPR. Instead, it provides background information to help you better understand how atEvent has addressed some important legal points. This legal information is not the same as legal advice, where an attorney applies the law to your specific circumstances, so we insist that you consult an attorney if you’d like advice on your interpretation of this information or its accuracy. In a nutshell, you may not rely on this information as legal advice, nor as a recommendation of any particular legal understanding.