Third party cookies
We use several third-party services to add interaction and enhance the user experience, the cookies they set are listed below along with information on how to opt-out of them.
You could also use a private browser like Chrome's Incognito Mode or Firefox's Private Browsing feature. Finally, there are several browser add-ons like Ghostery or BetterPrivacy that can help you opt-out of tracking across the web.
We use Google analytics to analyse how our site is being used to improve user experience. All data sent to Google analytics is completely anonymised. You can opt-out directly through Google analytics
The cookies from Twitter are there to support social sharing of this site and its content. Opt-out
Our vacancy listings use LinkedIn to connect to data from their site. Opt-out
Live chat tool which allows users to contact us directly through live web chat.
We use Hotjar cookies to track user interactions with the site, they are responsible for displaying the correct content to your visitors without personally identifying anyone.
Hotjar cookie that is set once a visitor 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.
Hotjar cookie that is set once a visitor 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.
Hotjar cookie that is set once a visitor minimizes an On-site Survey widget. It is used to ensure that the widget stays minimized when the visitor navigates through your site.
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.
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.
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).
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.
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.
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.
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.
This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's pageview limit.
This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's daily session limit.
This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie.