Do I need a strict cookie consent required on my website to comply with GDRP

First of all: The GDPR doesn't talk about cookies. 

The older EU Cookie Law from 2011 does. And it says that site owners must inform visitors that cookiers are used, what they are used for, and give the visitor ability to control cookies. 

The newer ePrivacy Directive (which isn't yet approved) says this about cookies:

EUROPA websites must follow the Commission's guidelines on  privacy and data protection and inform users that cookies are not being used to gather information unnecessarily.

The  ePrivacy directive – more specifically Article 5(3) – requires prior informed consent for storage or for access to information stored on a user's terminal equipment. In other words, you must ask users if they agree to most cookies and similar technologies (e.g. web beacons, Flash cookies, etc.) before the site starts to use them.

For consent to be valid, it must be informed, specific, freely given and must constitute a real indication of the individual's wishes.

But then it also goes on and says this:

However, some cookies are exempt from this requirement. Consent is not required if the cookie is:

  • used for the sole purpose of carrying out the transmission of a communication, and
  • strictly necessary in order for the provider of an information society service explicitly required by the user to provide that service.

Cookies clearly exempt from consent according to the  EU advisory body on data protection- WP2

  • user‑input cookies (session-id) such as first‑party cookies to keep track of the user's input when filling online forms, shopping carts, etc., for the duration of a session or persistent cookies limited to a few hours in some cases
  • authentication cookies, to identify the user once he has logged in, for the duration of a session
  • user‑centric security cookies, used to detect authentication abuses, for a limited persistent duration
  • multimedia content player cookies, used to store technical data to play back video or audio content, for the duration of a session
  • load‑balancing cookies, for the duration of session
  • user‑interface customisation cookies such as language or font preferences, for the duration of a session (or slightly longer)
  • third‑party social plug‑in content‑sharing cookies, for logged‑in members of a social network.

Triggerbee only sets first party cookies and can be categorized as user-input .

Still need help? Contact Us Contact Us