Cookie policy

Cookies are small text files that are placed on your computer by websites that you visit. They're widely used to make websites work, or work more efficiently, as well as to provide information to the owners of the site.

The tables below explains the cookies we use and why.

First Party Cookies

Cookie

Type

Expiry

Linked Info

Functions

JSESSIONID

Session

Session end

Username

Allows a user, once logged in, to remain logged in as they explore the website.

VOPECRA

Persist

Never

Anonymous

Remembers when a user has elected to accept cookies.

 

Third Party Cookies

Cookie

Name

Type

Expiry

Functions

Google Analytics

_utma

_utmb

_utmc

_utmz

Persistent

 Two years

30 mins

End of session

6 months

These cookies are used to collect information about how visitors use our websites. We use the information to compile reports and to help us improve the site. The cookies collect information in an anonymous form, including the number of visitors to the site, where visitors have come to the site from and the pages they visited.

Click here for an overview of privacy at Google.

Google Translate

googtrans

Session

End of session

Stores your chosen language (if you decide to change it from English). This means that you do not have to select your chosen language every time that you load a new page.

Click here for an overview of privacy at Google.

Hotjar _hjSessionUser{site_id} Persistent 365 days 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 behavior in subsequent visits to the same site will be attributed to the same user ID.
Hotjar _hjSession{site_id} Session 30 mins 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.
Hotjar _hjClosedSurveyInvites Persistent 365 days 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.
Hotjar _hjDonePolls Persistent 365 days 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.
Hotjar _hjMinimizedPolls Persistent 365 days 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.
Hotjar _hjShownFeedbackMessage Persistent 365 days 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.
Hotjar _hjSessionTooLarge Session End of session 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.
Hotjar _hjSessionRejected Session End of session 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.
Hotjar _hjSessionResumed Session End of session A cookie that is set when a session/recording is reconnected to Hotjar servers after a break in connection.
Hotjar _hjid Persistent 365 days 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.
Hotjar _hjRecordingLastActivity Session End of session 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).
Hotjar _hjTLDTest Session End of 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.
Hotjar _hjUserAttributesHash Session End of 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.
Hotjar _hjCachedUserAttributes Session End of session This cookie stores User Attributes which 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.
Hotjar _hjLocalStorageTest Session Under 100ms 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.
Hotjar _hjIncludedInPageviewSample Session 30 mins This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's pageview limit.
Hotjar _hjIncludedInSessionSample Session 30 mins 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.
Hotjar _hjAbsoluteSessionInProgress Session 30 mins This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie.
Hotjar _hjFirstSeen Session 30 mins 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.
Hotjar _hjViewportId Session End of session This stores information about the user viewport such as size and dimensions.
Hotjar _hjRecordingEnabled Session End of session 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.

To find out more about cookies, including how to see what cookies have been set and how to manage and delete them, visit www.allaboutcookies.org.

To opt out of being tracked by Google Analytics across all websites visit http://tools.google.com/dlpage/gaoptout.

To opt out of being tracked by Hotjar visit https://www.hotjar.com/policies/do-not-track/