Skip to main content

Our cookie policy

In Milian Group ( Webent ), we use cookies to enhance the user experience, tracking and analysis of our traffic, to provide the best user experience. Cookies are small, text based files stored in your computer, during the visit of our website. You can remove cookies anytime using the built-in functionality of your web browser, but keep in mind it can break certain functionality of our website and therefor lower the quality of your user experience.

We use 2 different categories of cookies that differ in purpose.

I. Cookies needed

This category is designed to provide you with all the features you need to make our site work properly.

cookieconsent_status - this cookie is used to determine whether you have already accepted the cookie consent dialog. It automatically expires in 1 year.

The main purpose of this cookie is: Functionality

fe_typo_user - This cookie name is associated with the Typo3 web content management system. It is generally used as a user session identifier to enable user preferences to be stored. It is set to be destroyed at the end of a browser session. It contains a random identifier rather than any specific user data.

The main purpose of this cookie is: Functionality

2. Analytics cookies

This set of cookies is used to track and analyze traffic to our website. We use Google Analytics & Hotjar for this purpose.

Google Analytics

_ga - This cookie is used to distinguish users for tracking with Google Analytics. Cookie lasts 2 years.

_gid - This cookie is also used to distinguish a user with Google Analytics, but will expire in 24 hours. / Li>

_gat - Used to speed throttle requests. If Google Analytics is deployed through Google Tag Manager, this cookie will be named_dc_gtm_. This cookie will expire in 1 minute.


We use Hotjar to better understand our users' needs and optimize this service and your experience (eg, How much time they spend on which sites they choose to click, what users do and dislike, etc.) Allows us to build and maintain our user feedback services.

Hotjar uses cookies and other technologies to collect data about the behavior of our users and their devices (especially device IP address (captured and stored only in anonymous form), device screen size, device type (unique device identifiers), browser information, geographic location (country only), preferred language used to display our site).

Hotjar stores this information in a pseudonymized user profile. Nor does Hotjar use this information to identify an individual user or to compare it with other individual user data. For more details, see the Hotjar privacy policy by clicking this link.

You can use this link to opt out of Hotjar cookies.

You can read more about Hotjar cookies here.

Hotjar cookies
_hjClosedSurveyInvitesHotjar cookie. This cookie is set once a visitor interacts with a Survey invitation modal popup. It is used to ensure that the same invite does not re-appear if it has already been shown.365 days
_hjDonePollsHotjar cookie. This cookie is set once a visitor completes a poll using the Feedback Poll widget. It is used to ensure that the same poll does not re-appear if it has already been filled in.365 days
_hjMinimizedPollsHotjar cookie. This cookie is set once a visitor minimizes a Feedback Poll widget. It is used to ensure that the widget stays minimizes when the visitor navigates through your site.365 days
_hjDoneTestersWidgetsHotjar cookie. This cookie is set once a visitor submits their information in the Recruit User Testers widget. It is used to ensure that the same form does not re-appear if it has already been filled in.365 days
_hjIncludedInSampleHotjar cookie. This session cookie is set to let Hotjar know whether that visitor is included in the sample which is used to generate funnels.365 days
_hjShownFeedbackMessageThis cookie is set when a visitor minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if they navigate to another page where it is set to show.365 days
_hjidHotjar cookie. This cookie 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
_hjRecordingLastActivityThis should be found in sessionStorage (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
hjTLDTestWhen 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
_hjUserAttributesHashUser 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
_hjCachedUserAttributesThis 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.


_hjLocalStorageTestThis 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 immediately after creating it so the expected storage time is under 100ms.


_hjptid This cookie is set for logged in users of Hotjar, who have Admin Team Member permissions. It is used during pricing experiments to show the Admin consistent pricing across the site.