Our cookies explained
Some of our cookies are required for the core functionality of the website. These cookies ensure that our website works correctly, and therefore they cannot be disabled.
Holds user confirmation of all terms & conditions, set when visiting the site for the first time.
_m_lat & _m_lon
When the user accepts Meesa's use of geolocation, latitude and longitude data will be saved in these cookies to offer a personalized experience.
Number of times our website has shown the PWA installation banner to the user. It will be shown a maximum of 3 times.
Seconds since last time the PWA installation banner was shown. It will be shown again after 15 minutes of website use.
A list of profiles or companies recently viewed by the user. Our website will make suggestions based on characteristics of these profiles.
Stores permission (or refusal) for analytical cookie usage.
These cookies are used to improve our services for customers and visitors. They will only be set with the user's consent.
Cookie used to distinguish individual users on our domain for Google Analytics, expires after 2 years.
Cookie used to distinguish individual users on our domain for Google Analytics, expires after 24 hours.
Used to persist Google Analytics session state, expires after 2 years.
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. Expires after 365 days days.
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. Expires after 365 days days.
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. Expires after 365 days days.
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. Expires after 365 days 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. Expires after 365 days days.
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. Expires after 100ms.
This cookie is set to let Hotjar know whether that visitor is included in the data sampling defined by your site's pageview limit. Expires after 30 minutes.
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. Expires after 30 minutes.
This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie. Expires after 30 minutes.
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.
This stores information about the user viewport such as size and dimensions.
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.