Twitter Instagram

Cookie Policy

How do we use Cookies on our website?
Our website uses cookies to distinguish you from other users of our website. This helps us to provide you with a good experience when you browse our website and also allows us to improve our website.

A cookie is a small file of letters and numbers that we store on your browser or the hard drive of your computer if you agree. Cookies contain information that is transferred to your computer’s hard drive.

We use the following cookies:

Strictly necessary cookies
These are cookies that are required for the operation of our website.

Analytical/performance cookies
They allow us to recognise and count the number of visitors and to see how visitors move around our website when they are using it. This helps us to improve the way our website works, for example, by ensuring that users are finding what they are looking for easily.

Functionality cookies
These are used to recognise you when you return to our website.

Targeting cookies
These cookies record your visit to our website, the pages you have visited and the links you have followed.

Without cookies enabled, we can’t guarantee that the website and your experience of it are as we intended it to be. Please find a list of the individual cookies we use in the table below:

Please note third parties (including, for example, advertising networks and providers of external services like web traffic analysis services) may also use cookies, over which we have no control. These cookies are likely to be analytical/performance cookies or targeting cookies.

You may block cookies by activating the setting on your browser which allows you to refuse the placing of all or some cookies. However, if you use your browser settings to block all cookies (including essential cookies) you may not be able to access all or parts of our website.

Except for essential cookies, all cookies will remain unless the cookie cache is cleared, unless otherwise indicated above.

Cookie NamePurpose
ajs_anonymous_id, ajs_group_id, ajs_user_idUsed for Analytics and to track visitor usage and events
phpsessidUsed by bidwidget which runs on our site
phpsessidSet by WordPress, which runs our site
gat, ga, gidUsed by Google Analytics
utma, utmb, utmc, utmt, utmv, utmzUsed by Google Analytics
wp-settings-3, wp-settings-time-3, wp-settings-5, wp-settings-time-5, wordpress_test_cookieSet by WordPress, which runs our site
wp-settings-time-3Set by WordPress, which runs our site
viewed_cookie_policySet by the cookie policy plugin used to gain consent on our site
personalization_idFor Twitter integration and sharing capabilities for the social media.
VariousIf you are logged in as a backend manager then WordPress may set a number of cookies

Hotjar Cookies

From 1st April to 30th June 2022, the following Hotjar Tracking Code cookies will be set when using this website.

Relating to the user

_hjSessionUser{site_id}
• Set when a user first lands on a page.
• Persists the Hotjar User ID which is unique to that site.
• Ensures data from subsequent visits to the same site are attributed to the same user ID.
• 365 days duration.
• JSON data type.

_hjid
• Set when a user first lands on a page.
• Persists the Hotjar User ID which is unique to that site.
• Ensures data from subsequent visits to the same site are attributed to the same user ID.
• 365 days duration.
• UUID data type.

_hjFirstSeen
• Identifies a new user’s first session.
• Used by Recording filters to identify new user sessions.
• Session duration.
• Boolean true/false data type.

_hjUserAttributesHash
• User Attributes sent through the Hotjar Identify API are cached for the duration of the session.
• Enables us to know when an attribute has changed and needs to be updated.
• Session duration.
• Hash data type.

_hjCachedUserAttributes
• Stores User Attributes 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.
• Cookie used regardless of whether a Feedback tool is present.
• Session duration.
• JSON data type.

_hjViewportId
• Stores user viewport details such as size and dimensions.
• Session duration.
• UUID data type.

Relating to the session

_hjSession{site_id}
• Holds current session data.
• Ensures subsequent requests in the session window are attributed to the same session.
• 30 minutes duration.
• JSON data type.

_hjSessionTooLarge
• Causes Hotjar to stop collecting data if a session becomes too large.
• Determined automatically by a signal from the WebSocket server if the session size exceeds the limit.
• Session duration.
• Boolean true/false data type.

_hjSessionRejected
• If present, set to ‘1’ for the duration of a user’s session, when Hotjar has rejected the session from connecting to our WebSocket due to server overload.
• Applied in extremely rare situations to prevent severe performance issues.
• Session duration.
• Boolean true/false data type.

_hjSessionResumed
• Set when a session/recording is reconnected to Hotjar servers after a break in connection.
• Session duration.
• Boolean true/false data type.

_hjLocalStorageTest
• Checks if the Hotjar Tracking Code can use local storage.
If it can, a value of 1 is set.
• Data stored in_hjLocalStorageTest has no expiration time, but it is deleted almost immediately after it is created.
• Under 100ms duration.
• Boolean true/false data type.

_hjIncludedInPageviewSample
• Set to determine if a user is included in the data sampling defined by your site’s pageview limit.
• 30 minutes duration.
• Boolean true/false data type.

_hjIncludedInSessionSample
• Set to determine if a user is included in the data sampling defined by your site’s daily session limit.
• 30 minutes duration.
• Boolean true/false data type.

_hjAbsoluteSessionInProgress
• Used to detect the first pageview session of a user.
• 30 minutes duration.
• Boolean true/false data type.

_hjTLDTest
• We try to store the _hjTLDTest cookie for different URL substring alternatives until it fails.
• Enables us to try to determine the most generic cookie path to use, instead of page hostname.
• It means that cookies can be shared across subdomains (where applicable).
• After this check, the cookie is removed.
• Session duration.
• Boolean true/false data type.

Relating to Recordings

_hjRecordingEnabled
• Set when a Recording starts.
• Read when the Recording module is initialized to see if the user is already in a recording in a particular session.
• Session duration.
• Boolean true/false data type.

_hjRecordingLastActivity
• Set in Session storage as opposed to cookies.
• Updated when a user recording starts and when data is sent through the WebSocket (the user performs an action that Hotjar records).
• Session duration.
• Numerical Value (Timestamp) data type.

Relating to Feedback and Survey tools

_hjClosedSurveyInvites
• Set when a user interacts with an external link Survey invitation modal.
• Ensures the same invite does not reappear if it has already been shown.
• 365 days duration.
• Boolean true/false data type.

_hjDonePolls
• Set when a user completes an on-site Survey.
• Ensures the same Survey does not reappear if it has already been filled in.
• 365 days duration.
• Boolean true/false data type.

_hjMinimizedPolls
• Set when a user minimizes an on-site Survey.
• Ensures that the Survey stays minimized when the user navigates through your site.
• 365 days duration.
• Boolean true/false data type.

_hjShownFeedbackMessage
• Set when a user minimizes or completes a Feedback widget.
• Ensures the Feedback widget will load as minimized if the user navigates to another page where it is set to show.
• 365 days duration.
• Boolean true/false data type.