Cookie policy
On our transgroom.com website we use cookies and similar techniques. Functional and analytical cookies help to keep our website optimized and improved over time. Tracking cookies allow us and our partners (including social networks) to track your internet behavior and provide you with personalized offers within and outside our own website. By continuing on our website you agree with the above.
Third party partner cookies:
Mention Me: refer-a-friend promotions (essential cookies)
Functional cookies
| Name | Origin | lifespan | Description |
|---|---|---|---|
| transgroom_session | Transgroom | Session | This cookie remembers your session. |
| cookie_consent_functional | Transgroom | Session | This cookie remembers your functional cookie preference. |
| cookie_consent_analytics | Transgroom | Session | This cookie remembers your analytical cookie preference. |
| cookie_consent_marketing | Transgroom | Session | This cookie remembers your marketing cookie preference. |
| XSRF-TOKEN | Transgroom | 2 hour(s) | This cookie is used to protect our website against CSRF (Cross-Site Request Forgery) attacks. |
| mm_allocation | Mention Me | 6 months | This cookie is used to track which promotions a user participates in to provide a more consistent experience. |
| mm_id | Mention Me | 6 months | This cookie is used to distinguish unique users and browsers. |
Analytical cookies
| Name | Origin | lifespan | Description |
|---|---|---|---|
| _gat | Transgroom | Session | This cookie provides Transgroom.com with information about the number of (unique) visitors, the visitor sessions, how visitors use the site and via which channel (social media, search engines, etc.) Transgroom.com was reached. Used to decrease the request speed. |
| _gid | Transgroom | 1 day(s) | This cookie provides Transgroom.com with information about the number of (unique) visitors, the visitor sessions, how visitors use the site and via which channel (social media, search engines, etc.) Transgroom.com was reached. Google Analytics then provides insight into this data on the basis of an analysis report |
| _ga | Transgroom | 730 day(s) | This cookie provides Transgroom.com with information about the number of (unique) visitors, the visitor sessions, how visitors use the site and via which channel (social media, search engines, etc.) Transgroom.com was reached. Used to distinguish users. |
Marketing cookies
| Name | Origin | lifespan | Description |
|---|---|---|---|
| hjClosedSurveyInvites | hotjar.com | 365 day(s) | Hotjar cookie that is set once a visitor interacts with a Survey invitation modal pop-up. It is used to ensure that the same invite does not reappear if it has already been shown. |
| _hjDonePolls | hotjar.com | 365 day(s) | Hotjar cookie that is set once a visitor completes a poll using the Feedback Poll widget. It is used to ensure that the same poll does not reappear if it has already been filled in. |
| _hjMinimizedPolls | hotjar.com | 365 day(s) | Hotjar cookie that is set once a visitor minimizes a Feedback Poll widget. It is used to ensure that the widget stays minimized when the visitor navigates through your site. |
| _hjShownFeedbackMessage | hotjar.com | 365 day(s) | Hotjar cookie that is set when a visitor minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if the visitor navigates to another page where it is set to show. |
| _hjid | hotjar.com | 365 day(s) | Hotjar cookie that 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 | hotjar.com | Session | This should be found in Session storage (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). |
| _hjTLDTest | hotjar.com | Session | 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. |
| _hjUserAttributesHash | hotjar.com | Session | 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 | hotjar.com | Session | 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 | hotjar.com | < 100ms | 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 almost immediately after it is created. |
| _hjIncludedInSample | hotjar.com | Session | This cookie is set to let Hotjar know whether that visitor is included in the sample which is used to generate Funnels. This is a session cookie which is destroyed when the user leaves the site. |
| _hjAbsoluteSessionInProgress | hotjar.com | 30 minutes | This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie. |