What are cookies?
While surfing to websites, cookies in the form of text files are placed on the hard disk of the visitor's device. This information can be requested again on a subsequent visit to the same website.
What are cookies used?
What types of cookies are there?
There are different types of cookies. A distinction can be made between the functionality, origin and storage period of these cookies. Cookies can be divided into three main categories of cookies, namely the functional, non-functional cookies and the additional cookies.
When you visit our website for the first time, you are asked whether or not to accept the cookies. The approval or refusal can be set per category of cookies, namely the functional, non-functional and additional cookies. No cookies are placed before a visitor's permission has been obtained. Not accepting cookies may result in the website or parts of it not functioning properly. A visitor can adjust his preferences at any time via the link provided for that purpose.
Functional cookies are necessary for the operation of the website. Image or sound playback, security, a cookie that determines whether or not another cookie may be placed are some examples of functions that may require functional cookies, but these are not limited to these. It is strongly recommended to enable these cookies at all times, for the proper functioning of the website and to be able to save your preferences for cookie settings.
|_ab||Used in connection with access to admin.|
|_secure_session_id||Used in connection with navigation through a storefront.|
|Cart||Used in connection with shopping cart.|
|cart_sig||Used in connection with checkout.|
|cart_ts||Used in connection with checkout.|
|checkout_token||Used in connection with checkout.|
|Secret||Used in connection with checkout.|
|Secure_customer_sig||Used in connection with customer login.|
|storefront_digest||Used in connection with customer login.|
|_shopify_u||Used to facilitate updating customer account information.|
|_Brochure_session||Used in connection with broswing through site.|
Non-functional cookies can be placed for statistical, social, targeting and commercial purposes. These cookies are not required for a website to function. For cookies placed by third parties (including Google Analytics), we would like to refer you to the statements that these parties provide on their respective websites. Please note: we have no influence whatsoever on the content of those statements, nor on the content of the cookies of these third parties: Google Analytics, Zopim, Facebook Pixels
|AID||These cookies link your activities on other devices that you have previously signed into your Google account. Based on this, the ads you see on your devices are coordinated and conversion events are measured.|
|TAID||These cookies link your activities on other devices that you have previously signed into your Google account. Based on this, the ads you see on your devices are coordinated and conversion events are measured.|
|id||Used to show personalized advertisements based on previous visits to our website.|
|IDE||Used to show personalized advertisements based on previous visits to our website.|
|__utma||Analytical cookie that measures website visits (anonymous).|
|__utmb||Analytical cookie that measures website visits (anonymous).|
|__utmc||Analytical cookie that measures website visits (anonymous).|
|__utmz||Analytical cookie that measures website visits (anonymous).|
|_ga||Analytical cookie that measures website visits (anonymous). Expires after 2 years.|
|PREF||Used to save users priority, such as language chosen or other adjustments.|
SID' of 'HSID'
||Protects user data from unauthorized access.|
|_gid||Syncs with the Google Analytics _gid cookie, this stores a unique, anonymous number on domain T-Mobile per page to recognize the user journey in Google Analytics. Expires after 1 minute.|
|_gat||This cookie does not keep user information, but limits the number of requests to doubleclick.net.|
|act||This cookie contains a unix time stamp to keep track of when a user has logged in. If you choose to remain logged in, this cookie will expire after 90 days of inactivity. Otherwise, this cookie is a session cookie.|
|c_user||This cookie contains the user ID of the logged in user. If you choose to remain logged in, this cookie will expire after 90 days of inactivity. Otherwise, this cookie is a session cookie.|
|datr||The purpose of the datr cookie is to identify the web browser used to connect to Facebook independently of the logged in user. This cookie plays a key role in the security and integrity functions of Facebook. Expires after 2 years.|
|fr||Cookie intended for interest-based advertising. This cookie expires after 90 days.|
|presence||This cookie is used to contain the chat status of the user. For example, to see which chat tabs are open. This is a session cookie.|
|sb||Creates a user profile to show relevant ads on Facebook. Expires after 2 years.|
|spin||Creates a user profile to show relevant ads on Facebook. Expires after 25 hours.|
|wd||This cookie keeps track of the screen size in order to optimize the facebook integration. Expires after 1 week.|
|xs||This cookie contains: session number, session secret and "secure" flag. If you choose to remain logged in, this cookie will expire after 90 days of inactivity. Otherwise, this cookie is a session cookie.|
|_hjClosedSurveyInvites||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.|
|_hjDonePolls||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.|
|_hjMinimizedPolls||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.|
|_hjDoneTestersWidgets||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.|
|_hjIncludedInSample||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.|
|_hjShownFeedbackMessage||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.|
|_hjid||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.|
|_hjRecordingLastActivity||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
|_hjUserAttributesHash||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.|
|_hjCachedUserAttributes||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.|
|_hjLocalStorageTest||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.|
|_hjptid||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.|
|_hjAbsoluteSessionInProgress||The cookie is set so Hotjar can track the beginning of the user's journey for a total session count. It does not contain any identifiable information.|