What are cookies?
We may place small text files called ‘cookies’ on your device when you visit our website. These files do not contain personal data, but they do contain a personal identifier allowing us to associate your personal data with a certain device. Cookies are NOT viruses, any kind of malware, programs or applications. Cookies can't see the files on your device.
Why do we use cookies?
Cookies serve several useful purposes for you, including:
We use three types of cookies on our website?
Changing Cookie Settings?
You can alter your cookie settings on our website at any time using our cookie settings section.
Deleting cookies
Your internet browser generally accepts cookies automatically, but you can often change this setting to stop accepting them. You can also delete cookies manually. Deleting or no longer accepting cookies may prevent you from accessing certain aspects of our website where cookies are necessary or because the website forgot your preferences. Most web browsers allow some control of most cookies through the browser settings. To find out more about cookies, including how to see what cookies have been set, visit www.aboutcookies.org or www.allaboutcookies.org
Essential cookies
Cookie
laravel_session
Purpose
This cookie is used internally by the website’s owners, when uploading or renewing website content.
Duration
1 Day
Cookie
XSRF-TOKEN
Purpose
Ensures visitor browsing-security by preventing cross-site request forgery. This cookie is essential for the security of the website and visitor.
Duration
1 Day
Performance cookies
Cookie | Purpose | Duration |
---|---|---|
_hjClosedSurveyInvites | 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. | 365 days |
_hjDonePolls | 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. | 365 days |
_hjMinimizedPolls | 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. | 365 days |
_hjShownFeedbackMessage | 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. | 365 days |
_hjid | 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. | 365 days |
_hjRecordingLastActivity | 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). | Session |
_hjTLDTest | 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. | Session |
_hjUserAttributesHash | 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. | Session |
_hjCachedUserAttributes | 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. | Session |
_hjLocalStorageTest | 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. | Under 100ms |
_hjIncludedInPageviewSample | This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's pageview limit. | 30 minutes |
_hjIncludedInSessionSample | 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. | 30 minutes |
_hjAbsoluteSessionInProgress | This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie. | 30 Minutes |
_hjFirstSeen | 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. | Session |
hjViewportId | This stores information about the user viewport such as size and dimensions. | Session |
_hjRecordingEnabled | 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. | Session |
Performance cookies
_gat_UA-92443388-37, _gid, _ga, _gclxxxx, _gat_UA-145808401-2, _gat_xxxxxxxxxxxxxxxxxxxxxxxxxx | These cookies are set by Google Analytics. Google Analytics is a web analytics service offered by Google that tracks and reports website traffic. These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. All information these cookies collect is aggregated and therefore anonymous. If you do not allow these cookies then we will not know that you have visited our site, and will not be able to monitor its performance. |