Cookies policy
This Cookies Policy forms part of our general Privacy Notice. Take a look at our full privacy notice.
Cookies and similar technology
In common with most websites, we use cookies and other standard internet technologies to help us improve our website.
What are cookies?
Cookies are small text files that are placed on your computer by websites that you visit. These text files can be read by these websites and help to identify you when you return to a website. Cookies can be “persistent” or “session” cookies. Persistent cookies remain on your computer when you have gone offline, while session cookies are deleted as soon as you close your web browser.
If you choose to use our website without blocking or disabling cookies or opting out of other technologies, you will indicate your consent to our use of these cookies and other technologies and to our use (in accordance with this policy) of any personal information that we collect using these technologies. If you do not consent to the use of these technologies, please be sure to block or disable them using your browser settings, the opt-out links identified in this policy, or the settings within our mobile apps.
Use of cookies by Imosphere Ltd
The table below explains the cookies we use and why.
| Cookie | Name | Purpose | Expires |
|---|---|---|---|
| Cookie Pop-up | CookieAcknowledgement | Used to obtain consent to set cookies on your computer or devices. | On deleting cookies |
| Google Analytics | _ga | Used to distinguish users. | 2 years |
| _gid | Used to distinguish users. | 24 hours | |
| _gat | Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named dc_gtm. | 1 minute | |
| AMP_TOKEN | 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 | |
| _ gac _ | Contains campaign related information for the user. | 90 days | |
| __utma | Used to distinguish users and sessions. The cookie is created when the javascript library executes and no existing __utma cookies exists. The cookie is updated every time data is sent to Google Analytics. | 2 years from set/update | |
| __utmt | Used to throttle request rate. | 10 minutes | |
| __utmb | Used to determine new sessions/visits. The cookie is created when the javascript library executes and no existing __utmb cookies exists. The cookie is updated every time data is sent to Google Analytics. | 30 mins from set/update | |
| __utmc | Not used in ga.js. Set for interoperability with urchin.js. Historically, this cookie operated in conjunction with the __utmb cookie to determine whether the user was in a new session/visit. | End of browser session | |
| __utmz | Stores the traffic source or campaign that explains how the user reached your site. The cookie is created when the javascript library executes and is updated every time data is sent to Google Analytics. | 6 months from set-update | |
| __utmv | Used to store visitor-level custom variable data. This cookie is created when a developer uses the _setCustomVar method with a visitor level custom variable. This cookie was also used for the deprecated _setVar method. The cookie is updated every time data is sent to Google Analytics. | 2 years from set/update | |
| Hotjar | _hjClosedSurveyInvites | Hotjar cookie that is set once a user interacts with an External Link Survey invitation modal. It is used to ensure that the same invite does not reappear if it has already been shown. | 365 days |
| _hjDonePolls | Hotjar cookie that is set once a user completes a survey using the On-site Survey widget. It is used to ensure that the same survey does not reappear if it has already been filled in. | 365 days | |
| _hjMinimizedPolls | Hotjar cookie that is set once a user minimizes an On-site Survey widget. It is used to ensure that the widget stays minimized when the user navigates through your site. | 365 days | |
| _hjShownFeedbackMessage | Hotjar cookie that is set when a user minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if the user navigates to another page where it is set to show. | 365 days | |
| _hjSessionTooLarge | Causes Hotjar to stop collecting data if a session becomes too large. This is determined automatically by a signal from the WebSocket server if the session size | Session | |
| _hjid | 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. | 365 days | |
| _hjRecordingLastActivity | This should be found in Session storage (as opposed to cookies). This gets updated when a user recording starts and when data is sent through the WebSocket (the user performs an action that Hotjar records). | Session | |
| _hjTLDTest | 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. | Session | |
| _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. | Session | |
| _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. | Session | |
| _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 almost immediately after it is created. | Under 100ms | |
| _hjIncludedInPageviewSample | This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site’s pageview limit. | 30 minutes | |
| _hjIncludedInSessionSample | This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site’s daily session limit. | 30 minutes | |
| _hjAbsoluteSessionInProgress | This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie. | 30 Minutes | |
| _hjFirstSeen | This is set to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions. | Session | |
| _hjViewportId | This stores information about the user viewport such as size and dimensions. | Session | |
| _hjRecordingEnabled | This is added when a Recording starts and is read when the recording module is initialized to see if the user is already in a recording in a particular session. | Session |
Note: For Google Analytics your IP address is anonymised.
To opt out of being tracked by Google Analytics across all websites, visit http://tools.google.com/dlpage/gaoptoutOpens a new window.
Managing cookies
You can use the settings within your browser to control the cookies that are set on your computer or mobile device.
To find out how to see what cookies have been set and how to reject and delete cookies, please visit Opens a new window.
To find out how to manage cookies on popular browsers: