Cookies are small files which are stored on your computer. A cookie often includes an anonymous unique identifier. Cookies do not damage your computer. You do not have to accept cookies. You can decide if you want to accept cookies by changing the settings on your browser. Switching off cookies will still allow you to view the majority of content on our site, although it may reduce its functionality.
On this website we use as few cookies as possible, store the smallest amount of information that we need for as short a time as possible, and try only to use cookies that are essential to providing you with the service or improving your user experience.
We use the following cookies on this website
Cookies that measure website use
We use Google Analytics to help us analyse how you got to the website, the pages you visit, the time you spend on the website and the things you click on.
We use Hotjar to understand how much time you spend on particular pages, which links are clicked and what you do and don't like. Understanding this feedback enables us to maintain and improve the service.
Hotjar uses cookies and other technologies to collect data relating to our users’ behaviour and their devices. This includes:
- screen size
- device type (unique device identifiers)
- browser information.
Hotjar stores this information on our behalf in a pseudonymised user profile.
Hotjar is contractually forbidden to sell any of the data collected on our behalf.
_hjSessionUser{site_id}
A Hotjar cookie that is set when a user 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 behaviour in subsequent visits to the same site will be attributed to the same user ID.
Expires: 365 days
JSON
_hjSession{site_id}
A cookie that holds the current session data. This ensues that subsequent requests within the session window will be attributed to the same Hotjar session.
Expires: 30 minutes
JSON
_hjShownFeedbackMessage
A Hotjar cookie that is set when a user minimises or completes incoming feedback so that it will load as minimised immediately if the user navigates to another page on which it is set to show.
Expires: 365 days
Boolean true/false
_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 exceeds the limit.
Expires: session
Boolean true/false
_hjSessionRejected
If present, this cookie will be set to ‘1’ for the duration of a user’s session, if Hotjar rejected the session from connecting to our WebSocket due to server overload. This cookie is only applied in extremely rare situations to prevent severe performance issues.
Expires: session
Boolean true/false
_hjSessionResumed
A cookie that is set when a session/recording is reconnected to Hotjar servers after a break in connection.
Expires: session
Boolean true/false
_hjid
A 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 behaviour in subsequent visits to the same site will be attributed to the same user ID.
Expires: 365 days
UUID
_hjRecordingLastActivity
This should be found in session storage (as opposed to cookies). It gets updated when a user recording starts and when data is sent through the WebSocket (the user performs an action that Hotjar records).
Expires: session
Numerical Value (Timestamp)
_hjTLDTest
When the Hotjar script executes, we try to determine the most generic cookie path we should use, instead of the page hostname. This way 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.
Expires: session
Boolean true/false
_hjUserAttributesHash
User attributes sent through the Hotjar Identify API are cached for the duration of the session in order to show when an attribute has changed and needs to be updated.
Expires: session
Hash
_hjCachedUserAttributes
This cookie stores user attributes that are sent through the Hotjar Identify API whenever the user is not in the sample. .
Collected attributes will only be saved to Hotjar servers if the user interacts with a Hotjar feedback tool, but the cookie will be used regardless of whether a feedback tool is present.
Expires: session
JSON
_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.
Expires: under 100ms
Boolean true/false
_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.
Expires: 30 minutes
Boolean true/false
_hjAbsoluteSessionInProgress
This cookie is used to detect the first page view session of a user. This is a true/false flag set by the cookie.
Expires: 30 Minutes
Boolean true/false
_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.
Expires: session
Boolean true/false
_hjViewportId
This stores information about the user viewport such as size and dimensions.
Expires: session
UUID
_hjRecordingEnabled
This is added when a recording starts and is read when the recording module is initialised to see if the user is already in a recording in a particular session.
Expires: session
Boolean true/false
Cookies that help with our marketing and communications
We also use cookies set by third parties such as Facebook and Linkedin.
Essential cookies
There are some cookies that essential to your use of this website. For example, remembering your progress through a form.
