A cookie is a type of digital tag that stores your online visit. Almost every website uses cookie technology. The cookie is downloaded by your Internet browser during your first visit to a website. When you next visit the site from the same device, the cookie and the information it contains are sent back to the original website (original cookies) or to another site to which it belongs (third-party cookies). The website can therefore detect that it has already been opened using this browser.
The cookies used on our site are categorized as follows:
A distinction should be made between persistent and session cookies:
Persistent cookies: these cookies remain on a User's device for the period of time specified in the cookie. They are activated each time that the User visits the website that created that particular cookie.
Session cookies: these cookies allow website operators to link the actions of a User during a browser session. A browser session starts when a User opens the browser window and finishes when they close the browser window. Session cookies are created temporarily. Once you close the browser, all session cookies are deleted.
Strictly Necessary or obligatory cookies let you move around the Website and use essential features like secure areas. They are only stored on your computer while you browse the Website.
If your browser blocks such cookies, we cannot guarantee how the Website will perform during your visit. The use of obligatory cookies is not subject to your consent. Necessary cookies cannot be disabled via the features of this Website. You can, however, disable cookies in your web browser at any time.
Analytic cookies collect information about how you use our Website - e.g. which pages you visit and if you experience any errors. These cookies do not collect any information that could identify you and are only used to help us improve how our Website works, understand what interests our Users and measure how effective our content is.
Our analytic cookies are mainly managed for us by Google Analytics. However, we don't allow the third party to use the cookies for any purpose other than those listed above.
At any time, you can change your cookie settings by going to the Cookie Preference Center by clicking on the Cookie button in the footer of each page of this Website
TBC once you will have a new Website and agreed on a cookie preference center.
Used to distinguish users.
Used to distinguish users.
Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_<property-id>.
Contains a token that can be used to retrieve a Client ID from AMP Client ID service. Other possible values indicate opt-out, inflight request or an error retrieving a Client ID from AMP Client ID service.
30 seconds to 1 year
Contains campaign related information for the user. If you have linked your Google Analytics and Google Ads accounts, Google Ads website conversion tags will read this cookie unless you opt-out. Learn more
Hotjar cookie. This cookie is set once a visitor interacts with a Survey invitation modal popup. It is used to ensure that the same invite does not re-appear if it has already been shown.
Hotjar cookie. This cookie is set once a visitor completes a poll using the Feedback Poll widget. It is used to ensure that the same poll does not re-appear if it has already been filled in.
Hotjar cookie. This cookie is set once a visitor minimizes a Feedback Poll widget. It is used to ensure that the widget stays minimizes when the visitor navigates through your site.
Hotjar cookie. This cookie is set once a visitor submits their information in the Recruit User Testers widget. It is used to ensure that the same form does not re-appear if it has already been filled in.
Hotjar cookie. This session cookie is set to let Hotjar know whether that visitor is included in the sample which is used to generate funnels.
This cookie is set when a visitor minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if they navigate to another page where it is set to show.
Hotjar cookie. This cookie is set when the customer first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.
This should be found in sessionStorage (as opposed to cookies). This gets updated when a visitor recording starts and when data is sent through the WebSocket (the visitor performs an action that Hotjar records).
When the Hotjar script executes we try to determine the most generic cookie path we should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed.
User Attributes sent through the Hotjar Identify API are cached for the duration of the session in order to know when an attribute has changed and needs to be updated.
This cookie stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. These attributes will only be saved if the user interacts with a Hotjar Feedback tool.
This cookie is used to check if the Hotjar Tracking Script can use local storage. If it can, a value of 1 is set in this cookie. The data stored in_hjLocalStorageTest has no expiration time, but it is deleted immediately after creating it so the expected storage time is under 100ms.
This cookie is set for logged in users of Hotjar, who have Admin Team Member permissions. It is used during pricing experiments to show the Admin consistent pricing across the site.
For more information, please read about Hotjar Cookie.
Enjoy your browse!