Cookie policy

What are cookies

A cookie is a file containing an identifier (a string of letters and numbers) that is sent by a web server to a web browser and is stored by the browser. The identifier is then sent back to the server each time the browser requests a page from the server.

Cookies may be either “persistent” cookies or “session” cookies: a persistent cookie will be stored by a web browser and will remain valid until its set expiry date, unless deleted by the user before the expiry date; a session cookie, on the other hand, will expire at the end of the user session, when the web browser is closed.

Cookies may not contain any information that personally identifies a user, but personal data that we store about you may be linked to the information stored in and obtained from cookies.

Different types of cookies

The following types of cookies may be used on our website:

Cookies that we use

1privacy-acceptedpersistentThis local storage key is used to check whether the user has acknowledged the information provided in Cookies & Privacy pop-up.
1_ga2 yearsUsed to distinguish users.
2_gid24 hoursUsed to distinguish users.
3_gat1 minuteUsed to throttle request rate. 

Cookies used by our service providers

Our service providers use cookies and those cookies may be stored on your computer when you visit our website.

1_hjClosedSurveyInvites365 daysHotjar 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.
2_hjDonePolls365 daysHotjar 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.
3_hjMinimizedPolls365 daysHotjar 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 our site.
4_hjShownFeedbackMessage365 daysHotjar 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.
5_hjSessionTooLargeSessionCauses 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.
6_hjid365 daysHotjar 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.
7_hjRecordingLastActivitySessionThis 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).
8_hjTLDTestSessionWhen 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.
9_hjUserAttributesHashSessionUser 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.
10_hjCachedUserAttributesSessionThis 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.
11_hjLocalStorageTestUnder 100msThis 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.
12_hjIncludedInPageviewSample30 minutesThis cookie is set to let Hotjar know whether that user is included in the data sampling defined by our site’s pageview limit.
13_hjIncludedInSessionSample30 minutesThis cookie is set to let Hotjar know whether that user is included in the data sampling defined by our site’s daily session limit.
14_hjAbsoluteSessionInProgress30 minutesThis cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie.
15_hjFirstSeenSessionThis 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.
16_hjViewportIdSessionThis stores information about the user viewport such as size and dimensions.
17_hjRecordingEnabledSessionThis 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.
18_hjSessionRejectedSessionIf 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.
19_hjSessionResumedSessionA cookie that is set when a session/recording is reconnected to Hotjar servers after a break in connection.
1wordpress_test_cookieSessionTests that the browser accepts cookies.

Managing cookies

Most browsers allow you to refuse to accept cookies and to delete cookies. The methods for doing so vary from browser to browser, and from version to version. You can however obtain up-to-date information about blocking and deleting cookies via these links:

Blocking all cookies will have a negative impact upon the usability of many websites.

If you block cookies, you will not be able to use all the features on our website.

Cookie preferences

For further information about our use of cookies, contact us via e-mail at