The GDPR is a regulation that is enforced from 25 May 2018. It affects all websites located in the European Union, and websites that have EU citizens as users.
Next in line is the ePrivacy Regulation, which is currently in process in the EU, and which is expected to become a regulation in 2019.
The ePrivacy Regulation will have much of the same scope as the GDPR, and will stipulate requirements aimed specifically to protect the privacy of electronic communications.
Why do I need cookie consent on my website?
Cookies of both first and third party provenance on websites track users in different ways.
For example the IP address, or merely the actions and behavior of users on the site and from site to site.
Many modern websites have hundreds of active cookies and online tracking in use on their site.
To find out what cookies are in use on your website, you can try our free website audit.
This service scans up to five pages of your website and sends you a report on the cookies and online tracking in use on these pages, giving you an insight into the tracking of your users that is going on on your site.
Example of a GDPR compliant cookie consent… and one that is not
In the wake of the ePrivacy Directive, implemented in 2002 and notoriously known by its nickname, “The Cookie Law”, cookie consent pop-ups and banners started showing up on all but every website.
Since the enforcement of the GDPR on 25 May 2018, however, simple “accept cookies” banners no longer do.
Here is an example of a compliant cookie consent message:
...and here is one that is not compliant:
In other words, the user is not presented with any real choice, and there is no true insight or information about what cookies are set on the browser, where they come from and what purposes they serve.
Whereas in the compliant cookie message (the white one), the user is informed of the purposes of the cookies up front. The cookies (which, as mentioned, can be numerous) are arranged in four comprehensible categories, and one may then tick or untick the types of cookies, that one wishes to accept and reject.
One may also choose to see a detailed overview of the cookies in use.
The overview simply folds out of the consent banner, mapping all active cookies and presenting them in an accessible manner.
At a glance, the user can now scroll through all of the cookies, see where they come from, read a description of their function and check their duration.
The user can then easily accept or reject the different types of cookies.
Detailed overview in an GDPR compliant cookie consent message.
Checklist of requirements for GDPR compliant cookie consents
Your GDPR and ePrivacy compliant cookie consent system should ensure that the consent is…
- Transparent: Given on the basis of clear and specific information about data types and purpose
- Prior: Given before any processing other than the strictly necessary takes place, also known as ‘prior consent’
- Unambiguous: Given as an affirmative, positive action
- Documented: Recorded and securely stored as evidence that consent has been given
- Reversible: The users must be able to withdraw their consent whenever they want
- Renewed: Regularly renewed. (The ePrivacy Directive proposes once a year).
The easiest way to comply is to find a reliable cookie consent software that is based upon a thorough study of the new regulations and therefore can ensure compliance with it.
Check out Cookiebot, one of the few fully GDPR and ePrivacy Directive compliant cookie services on the market.
What is the GDPR all about?
The main purpose of the General Data Protection Regulation is to bring the EU legislation up to date with the digital age, protecting personal privacy and restoring the control over their own data to the users.
The latest law on protection of personal data dates from back in 1995.
1995. That’s almost ten years prior to Facebook!
… and long before cookies were used for anything and everything from customizing websites to fencing in customers in a sophisticated web of targeted marketing.
The GDPR sets out strict requirements on data handling procedures, transparency, documentation and user consent.
For a quick overview of the main themes of the GDPR, check out the EU Commission’s infographic on the subject, Data Protection: Better rules for small businesses.
What does the GDPR mean for my website in general?
For website owners, the two primary aspects to be aware of are:
1. How you manage and store personal data in general:
What personal data are you handling? Do you really need this data, or can you get by without it? Are you able to detect and properly delete personal data, if a user so requests? Is the data securely stored? Do you have proper procedures in place in case of a data breach?
2. The cookies and tracking in use on your website:
This goes for both first-party and third-party cookies in use on your website. All cookies that directly identifies a person or can potentially be combined to identify a person may only be used once you have your user’s proper consent to it.
Nowadays, there often are hundreds of cookies and tracking technologies in use on most modern websites, and more often than not, website owners don’t even themselves have the full picture of the tracking in use on their own website.
To meet the requirements, make sure to have a thorough and compliant setup for getting and securely storing the consents to the cookies on your website. Start by finding out what cookies are in action on your website, and whether the use is compliant.
All cookies that process personal data are subject to the new regulations.
In practice, this means most cookies, such as cookies for analytics, cookies for advertising and for functional services, for example survey and chat tools.
What do the requirements mean for my website?
If you operate a website in the EU or have users from EU countries, you must comply with the General Data Protection Regulation.
In short, complying means taking great care to handle personal data in a lawful manner.
What is personal data in the GDPR?
The GDPR covers both data that is directly personal, such as a name, a photo, an email address, bank details, IP address etc., and data that can be combined in a way that can single out and identify individual users.
If your website or organization processes such data, then it must be revised to meet the new requirements.
Six lawful reasons to process data
It is worth knowing that consent is one of six lawful reasons to process personal data.
Therefore, before applying a setup for user consents, consider whether the processed personal data falls under one of the other categories for lawfulness.
My website doesn’t process personal data, but I use Google Analytics, Mailchimp, social media buttons, Salesforce etc. Do I need a cookie consent?
All of the services and features mentioned above are examples of third-parties on your website.
They deposit cookies on your user’s browsers as they visit your website.
You are responsible for protecting your website users and for giving them clear information and choice about how their data is being used, both by you and by third parties in use on your website.
How do I implement a cookie consent on my website?
The easiest way to become compliant is by finding a solution that takes care of your cookie consent for you.
-For example Cookiebot, which is one of the few fully compliant solutions on the market.
Cookiebot offers a smooth user experience - both for you as a website owner and for the users of your website.
Once you have found the cookie consent solution of your choice, there are two main ways of implementing it on your website:
If you have a Wordpress site, you can simply use a Wordpress plugin.
Otherwise, you can add a cookie consent script directly to your website.
Wordpress plugin for GDPR-compliant cookie consent
If you have a Wordpress website, the easiest way to implement cookie consent on your website is by making use of a Wordpress plugin.
You can find and install cookie consent plugins in the plugin menu point in the admin area of your Wordpress site.
Be sure to look for the Cookiebot plugin which is fully compliant with both GDPR and the EU ePrivacy Directive.
Script for GDPR compliant cookie consent
See the cookiebot script here.