Cookie policy

Cookies are activated and used during your navigation on this site. These are small text files, usually numbers and letters, that do not create a security risk for your computer, tablet, or smartphone.

Cookies allow us to:

  • Understand the behavior of visitors on the different pages of the website
  • Measure visitors’ activity on the site and their frequency of return to adapt the site to the use of its visitors
  • Measure the number of visits and pages viewed

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:

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 wp-login.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.

When visitors comment on your blog, they too get cookies stored on their computer. This is purely a convenience, so that the visitor won’t need to re-type all their information again when they want to leave another comment. Three cookies are set for commenters:

  • comment_author_{HASH}
  • comment_author_email_{HASH}
  • comment_author_url_{HASH}

AddThis Cookies

__atuvs, __atuvc, …

Since our cookies change frequently, we don’t typically list a description for each cookie or provide exhaustive cookie lists.

The cookies we use can store information such as:

  • Uniquely assigned machine-generated user ID
  • Maintenance cookies that help manage expiration for other cookies
  • User interest modeling
  • How often we see an AddThis user
  • Recording user sharing and social activity
  • Geolocation, used to help publishers know approximately where people sharing information are located. (State level)
  • Record user-specified sharing preferences
  • Optimizing sharing settings for the user.

We use cookies to track users across domains to personalize their services and to collect behavior data for publishers. This data isn’t personally identifiable and users can opt out by visiting

The AddThis tools also, in some circumstances, set cookies on the first-party website domain much like Google Analytics and other packages do. These cookies are used for per-site user preferences and analytics, and are always preceded with an underscore.

Finally, the AddThis tools may expose visitors to various advertising partners, who may in turn set cookies themselves. Any cookies delivered in this way will only be set on the partner’s domain.

For more information on how these practices relate to our privacy features, advertising offerings, and user opt-out, see the What you Should Know page (

Note that there are some additional exceptions to the cookie behavior described here, including when AddThis is in use on cookie-restricted properties such as .gov and .mil domains. For more information, feel free to ask.

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 : collection/analyticsjs/cookie-usage

Other Cookies We Use

  • PHPSESSID: To identify your unique session on the website
  • cookiebar: To store if the user has hidden the cookie bar
  • mp_a36067b00a263cce0299cfd960e26ecf_mixpanel: This cookie is set by Mixpanel for analyzing traffic, and in particular how users reached the plataform. This cookie has a 1 year timeout.
  • CookieConsent: To store if the user consents 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.

Let’s get in touch

Contact Us