Cookies

Websites mainly use cookies to:

• identify users
• remember users’ custom preferences
• help users complete tasks without having to re‑enter information when browsing from one page to another or when visiting the site later.

Cookies can also be used for online behavioural target advertising and to show adverts relevant to something that the user searched for in the past.

How are they used?

The web server supplying the webpage can store a cookie on the user’s computer or mobile device. An external web server that manages files included or referenced in the webpage is also able to store cookies. All these cookies are called http header cookies. Another way of storing cookies is through JavaScript code contained or referenced in that page.

Each time the user requests a new page, the web server can receive the values of the cookies it previously set and return the page with content relating to these values. Similarly, JavaScript code is able to read a cookie belonging to its domain and perform an action accordingly.

What are the different types of cookies?

A cookie can be classified by its lifespan and the domain to which it belongs. By lifespan, a cookie is either a:

• session cookie which is erased when the user closes the browser or
• persistent cookie which remains on the user’s computer/device for a pre-defined period of time.

As for the domain to which it belongs, there are either:

• first-party cookies which are set by the web server of the visited page and share the same domain
• third-party cookies stored by a different domain to the visited page’s domain. This can happen when the webpage references a file, such as JavaScript, located outside its domain.

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.

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- WP29 include:

• 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.

The cookie consent solution is a JavaScript‑based kit that, after some site‑specific configuration, will automatically add a header banner to the page. This header banner will disappear once the user has accepted or refused the cookies used on the site.

This solution provides the following functionalities:

• JavaScript to automatically display the header banner in 24 languages
• a wizard to declare your cookies and the link to your cookies notice page
• a JavaScript API with methods and functions that help to prevent prior storage of cookies
• a corporate‑consent cookie to remember the choice of the user across websites
• a template for the cookie notice page.

This is a central service: you have to include the JavaScript file on your website and add a one‑site‑specific configuration file listing the cookies you are using. You will also have to add a short HTML parameter to every element in your site that sets a cookie.