Cookie statement

A cookie is a file that is stored on your computer, tablet, or phone when you visit a website. The website uses these cookies to retrieve your browser preferences and to show relevant content. ’LocalStorage’ is a comparable technique, but for the ease of use, we also share this technique under the name ‘cookies’.

On this page, you can find an overview of all cookies used on our website. The content on this website can change regularly due to changing regulations or an update of the website. We try our best to keep the site as up-to-date as possible. Please visit this website regularly to ensure you are always up to date and you can change your cookies preferences if you require.

We define the following types of cookies:
Functional cookies
Analytical cookies
Marketing cookies
Identification/ Authentication cookies
Social media cookies
Functional cookies
These cookies are necessary for a website to perform in an orderly manner. Functional cookies use your browser preferences, for instance. Therefore you need to set your preferences, for your language or region, only once.

Analytical cookies
These cookies enable us (Xeinadin) to analyse how our visitors (users) interact with the website. This way, we can continuously improve the functionalities and content on the website. Xeinadin uses Google Analytics for this. To be fully GDPR compliant, we do not share any data with Google. Via our partner Contentleaders, we have a Data Processing Agreement with Google.

Identification/ Authentication cookies
The I/A cookies are used to identify all users after they have interacted with the website. Examples of interaction are: filling out of contact form, downloading a brochure, or clicking on a link after receiving an email from Xeinadin. The data that we gather during this interaction is never shared with third parties.

Social media cookies
The ‘Share’/’Like’ buttons (of various social media) below our blogs, articles and news items keep track of how many times an article or post is shared or liked. This tracking is being done by using a script (code) that is fabricated and owned by the social media companies themselves. In some cases, cookies are being placed.

Cookies on our Website
Look in the tabs below to see which cookies we use per category.

Cookies on our Website

Functional cookies

Cookie namePurposeStorage period
cl_cookie_consentLocal Cookie, to determine if cookies can or can’t be stored1 year / 2 months
cl_cookie_timeLocal Cookie, to determine when Cookies are accepted/ rejected.1 year / 2 months
_hjDonePollsHotjar cookie, placed at the moment the feedback poll has been filled out. This cookie ensures that the poll does not appear twice in a row. (read more)1 year
_hjMinimizedPollsHotjar cookie, placed after minimalizing the feedback poll widget. Ensure the poll widget to remain minimalized as long as the cookie exist. (read more)1 year
_hjDoneTestersWidgetsHotjar cookie, placed after the Recruit User Testers widget is filled out. Ensure – after filling out the form – that the form does not appear anymore. (read more)1 year
_hjMinimizedTestersWidgetsHotjar cookie, placed after minimalizing the Recruit User Testers widget. Ensure the poll widget to remain minimalized as long as the cookie exist. (read more)1 year


Analytical cookies

Cookie namePurposeStorage period
_gat*Google Analytics cookie, to limit the quantity of data registered by Google to limit the websites having high visitors number. (read more)1 Minute
__utmaGoogle Analytics cookie, to distinguish visitors. Cookie is reset after each visit. (read more)2 years after reset
__utmtGoogle Analytics cookie, to control the number of requests. (read more)10 minutes
__utmbGoogle Analytics cookie, to determine new sessions/ visits. After each visit this will be reset. (read more)30 minutes after reset
__utmcGoogle Analytics cookie, to determine new sessions and. (read more)After browser session
__utmzGoogle Analytics cookie, to register the user trail to our website. Will be reset after each visit. (read more)0,5 years after reset
__utmvGoogle Analytics cookie, to store amended variables. Only as developer the _setCustomVar is being used. Will be reset after each visit. (read more)2 years
__utmxGoogle Analytics cookie, to determine if a visitor is participating in a research/test (e.g. A-B test). (read more)1,5 years
__utmxxGoogle Analytics cookie, to determine when the experiment the user is participating in, ends. (read more)1,5 years
_gaexpGoogle Analytics cookie, to determine if a visitor participates in a test (e.g. A-B test) and when the experiment ends. (read more)Dependent on the duration of the experiment, average no longer than 90 days.
_galiGoogle Analytics cookie, to determine on which link the visitor has clicked. (read more)30 seconds
__distilleryWistia cookie, to track the video statistics. This way the website knows where the video needs to be resumed after leaving the website.1 year
muxDataWistia Cookie, to keep track of the video statistics.20 years
VISITOR_INFO1_LIVE, PREF_Youtube cookie, to keep track of the number of views of a YouTube video, if this is placed on the website.8 months
_hjIncludedInSampleHotjar cookie, is placed to determine if a user is participating in a experiment and keep track of this user. (read more)

1 year

_clckMicrosoft Clarity cookie. Persists the Clarity User ID and preferences, 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. (read more)

1 year

_clskMicrosoft Clarity cookie, to connect multiple page views by a user into a single Clarity session recording. (read more)

1 day

CLIDMicrosoft Clarity cookie, to identify the first-time Clarity see this user on any site using Clarity. (read more)

1 year


Marketing cookies

Cookie namePurposeStorage period
ANONCHKMicrosoft Clarity cookie, to indicate whether MUID is transferred to ANID, a cookie used for advertising. Clarity doesn’t use ANID and so this is always set to 0. (read more)1 day
MRMicrosoft Clarity cookie, to indicate whether to refresh MUID. (read more)7 days
MUIDMicrosoft Clarity cookie, to identify unique web browsers visiting Microsoft sites. These cookies are used for advertising, site analytics, and other operational purposes.(read more)1 year
SMMicrosoft Clarity cookie, used in synchronizing the MUID across Microsoft domains. (read more)Session

Identification / Authentication Cookies

Cookie namePurposeStorage period
cmpXXXXXXXActiveCampaign Cookie that is used to determine who is who and to analyse behavior.30 days of in-activity
visitorEmailLocal cookie (localStorage) that is used by ActiveCampaign to know who is who after sending a filled out form on the website. 

Delete cookies

You can always revoke the permission granted to Xeinadin for the Cookies. This can be done by changing the settings of your browser.


Control and rejection of cookies
Users have the right to decide whether to accept or reject cookies. Users can apply their cookie preferences by clicking on the appropriate opt-out links provided in the cookie table below.

Users can set or alter the web browser controls to accept or refuse cookies. When rejecting cookies, users may still use our websites, app or platform, though their access to some functionalities and areas may be restricted. How users can refuse cookies through their web browser controls, may vary from browser-to-browser. Please visit your browser’s help menu for more information or check the cookie table below.

Also, most advertising networks offer a way to opt-out of targeted advertising.

Privacy Statement
If the information collected and stored on this website (and database) contains any personal data, the Privacy Statement of Xeinadin also applies.

This Cookie Statement can change. Users will be notified on this website.

For inquiries, please contact us at [email protected]