Cookie Policy

The purpose of using cookies is to enhance the user experience on the website. All data we retrieve from our cookies is anonymous and is only used to understand such user experience with the aim to improve it.

What is a Cookie ?

Cookies consist of small files of letters and numbers that are sent from a website and stored in a user’s web browser while a user is visiting a website. When the user visits the same website in the future, the data stored in the cookie can be retrieved by the website to notify the website of the user’s previous activity.

In all case cookies used on the website will not collect any personal identifiable information nor can they carry viruses or install malware on the host computer.

You can consult these different cookies and learn about their usefulness through the listing below. These cookies are enabled by default on your web browser. However, you can configure your browser to alert you each time cookies are created and possibly to prevent their installation. Here is the procedure to follow on the four main browsers:

• Chrome : http://support.google.com/chrome/bin/answer.py?hl=fr&answer=95647
• Firefox : http://support.mozilla.org/fr/kb/activer-desactiver-cookies
• Safari : https://support.apple.com/kb/PH21411?viewlocale=fr_FR&locale=fr_FR
• Internet Explorer : https://support.microsoft.com/fr-fr/help/17442/windows-internet-explorerdelete-manage-cookies Access to our site will not be denied if you disable cookies, but some features may not be available. You will find below the listing and explanations supplied directly by the above mentioned services.

WordPress Cookies

• wordpress_[hash] : On login, wordpress uses the wordpress_[hash] cookie to store your authentication details. Its use is limited to the admin console area.
• wordpress_logged_in_[hash] : After login, wordpress sets the wordpress_logged_in_[hash] cookie, which indicates when you’re logged in, and who you are, for most interface use.
• wp-settings-{time}-[UID] : WordPress also sets a few wp-settings-{time}-[UID] cookies. The number on the end is your individual user ID from the users database table. This is used to customize your view of admin interface, and possibly also the main site interface.
• wordpress_test_cookie : Tests whether or not the browser has cookies enabled. The actual cookies contain hashed data, so you don’t have to worry about someone gleaning your username and password by reading the cookie data. A hash is the result of a specific mathematical formula applied to some input data (in this case your user name and password, respectively). It’s quite hard to reverse a hash (bordering on practical infeasibility with today’s computers). This means it is very difficult to take a hash and “unhash” it to find the original input data. WordPress uses the two cookies to bypass the password entry portion of wplogin.php. If WordPress recognizes that you have valid, non-expired cookies, you go directly to the WordPress Administration interface. If you don’t have the cookies, or they’re expired, or in some other way invalid (like you edited them manually for some reason), WordPress will require you to log in again, in order to obtain new cookies.

Google Analytics

• _gat : This cookie has a 1 minute timeout. Used to throttle request rate.
• _ga : This cookie has a 2 years timeout. Used to distinguish users.
• _gid : This cookie has a 24 hours timeout. Used to distinguish users.
• Google Analytics Cookie Usage on Websites : https://developers.google.com/analytics/ devguides/collection/analyticsjs/cookie-usage

Optimizely

• optimizelyPendingLogEvents : This cookie has a 15 minutes timeout. Used as a cache of a user’s actions between tracking calls. When the tracking call is made the cookie will be wiped. This is to ensure that all events are tracked even if the user is committing actions in rapid succession.
• optimizelySegments : This cookie has a 10 years timeout. It stores information about the user’s characteristics and preferences, such as browser, campaign, device type, configuration and font type.
• optimizelyBuckets : This cookie has a 10 years timeout. It stores information about the page changes applied by each user.
• optimizelyEndUserId : This cookie has a 10 years timeout. It stores the unique ID of the end user.

Other Cookies We Use

• PHPSESSID : To identify your unique session on the website.
• accept-cookies : To store if the user consent the use of cookies. This cookie has a 1 year timeout.
• __cfduid : This cookie is used to identify individual clients behind a shared IP address and apply security settings on a per-client basis. This cookie has a 1 year timeout.

Managing Cookies
Through the use of the website the user gives its implied consent with regard to the cookie policy and usages. If you not agree, then you can visit the website using your browser’s anonymous setting or delete the cookies after having visited this website. Most web browsers allow you to turn off the cookie function. Cancellation of the cookies, as well as blocking or refusing them may have a negative impact on the usability of the website and may limit its functionality.