Need to launch your survey to the European Union (EU)? We have a few things to double check before your launch!

In May 2018, the General Data Protection Regulation (GDPR) entered into effect in the European Union. The new privacy laws have a fundamental impact on how organizations handle data. The GDPR is used to modernize data privacy laws by replacing the previous EU Data Protection Directive. Online Surveys are included in these protection laws. While we do keep our surveys anonymous from personal identifiers such as name, address, email, etc., we do collect demographic information as well as any info that might be inputted from a Panel or List Survey that are protected under these laws. 

The GDPR adheres to seven key principles in hopes to change the ways we treat and perceive personal data. You can read more about these principles in the links down below. 

If you would like to read more about GDPR and the requirements/process behind becoming compliant, please read this blog post. You can also read our EU Privacy Policy here.

To see if you are GDPR complaint, locate the GDPR page. Click on "GDPR" under the "Account" tab at the top of the AYTM page. 

You will then be sent to a new page that will show you your compliance status, allow you to take/retake the survey, or show you your answers once you have completed the survey.

If you have not yet completed the GDPR Compliance test, your screen will look like this:

Your status will be "UNKNOWN" until you complete the test. You can complete the quick GDPR compliance test by clicking "Take Survey Now"

Once the test has been taken, your status will either change to "COMPLIANT"

.....or "NON COMPLIANT"

If you are not compliant, you will not be able to launch to countries in the EU. Please reach out to AYTM through our support email to find out why you might not have been compliant. We will be able to get you in contact with the correct channels to discuss compliance. 

If you have any additional questions, reach out to support@aytm.com and we can put you in touch with our data security officer.

Did this answer your question?