Cookies policy

Duration: 1 minute

Analytics used throttle request rate (Google Analytics)

Examples of purposes for which a cookie may be used:

This cookie is essential for our site to OR enables us to:

(a) Estimate our audience size and usage pattern.

(b) Store information about your preferences, and so allow us to customise our site and to provide you with offers that are targeted to your individual interests.

(c) Speed up your searches.

(d) Recognise you when you return to our site.

(e) Allow you to use our site in a way that makes your browsing experience more convenient, for example, by allowing you to store items in an electronic shopping basket between visits. If you register with us or complete our online forms, we will use cookies to remember your details during your current visit, and any future visits provided the cookie was not deleted in the interim.

Duration: 24 hours

Analytics used to distinguish users (Google Analytics)

Examples of purposes for which a cookie may be used:

This cookie is essential for our site to OR enables us to:

(a) Estimate our audience size and usage pattern.

(b) Store information about your preferences, and so allow us to customise our site and to provide you with offers that are targeted to your individual interests.

(c) Speed up your searches.

(d) Recognise you when you return to our site.

(e) Allow you to use our site in a way that makes your browsing experience more convenient, for example, by allowing you to store items in an electronic shopping basket between visits. If you register with us or complete our online forms, we will use cookies to remember your details during your current visit, and any future visits provided the cookie was not deleted in the interim.

Duration: 2 years

Analytics used to distinguish users (Google Analytics)

Examples of purposes for which a cookie may be used:

This cookie is essential for our site to OR enables us to:

(a) Estimate our audience size and usage pattern.

(b) Store information about your preferences, and so allow us to customise our site and to provide you with offers that are targeted to your individual interests.

(c) Speed up your searches.

(d) Recognise you when you return to our site.

(e) Allow you to use our site in a way that makes your browsing experience more convenient, for example, by allowing you to store items in an electronic shopping basket between visits. If you register with us or complete our online forms, we will use cookies to remember your details during your current visit, and any future visits provided the cookie was not deleted in the interim.

Duration: session

This cookie will help deliver our advertising to people who have already visited our website when they are on Facebook or a digital platform powered by Facebook Advertising.

Duration: 30 minutes

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.

Duration: session

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.

Duration: N/A

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.

Duration: 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.

Duration: 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.

Duration: 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.

Duration: session

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).

Duration: 365 days

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.

Duration: 365 days

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.

Duration: 365 days

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.

Duration: 365 days

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.

Duration: 365 days

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.

Duration: 365 days

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.

Duration: 365 days

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 Hotjar cookie.