EU legislation requires all website operators to inform website visitors about their usage of cookies
and similar technologies, e.g. pixels, (hereinafter “cookies”) and to collect the user’s
consent to such cookie usage.
What are cookies?
Cookies are small text files which are sent to your device (computer, laptop, smartphone, tablet) by the website you visit. Cookies are stored on your device in your browser’s file directory. Your browser sends these cookies back to the website each time you revisit it so it can recognize your device and improve your user experience on each subsequent visit. Cookies allow us e.g. to tailor a website to better match your interests or to store your password so that you do not need to re-enter it every time. Please note that certain functions of our website may no longer work or work not correctly without cookies. If you want to learn more about cookies and how they work in general, please visit www.allaboutcookies.org or www.youronlinechoices.eu.
Categories of cookies
Depending on their function and their intended purpose, cookies can be assigned to the following categories: strictly necessary cookies, performance cookies, functional cookies and targeting cookies.
Strictly necessary cookies
Strictly necessary cookies are required to navigate our websites and operate basic website functions. Examples for strictly necessary cookies are login cookies, shopping cart cookies or cookies to remember your cookie settings. Without these cookies certain basic functionalities cannot be offered. Strictly necessary cookies are always active and will be placed without your consent. To the extent that information processed in connection with strictly necessary cookies should qualify as personal data, the legal ground for that processing is Linde’s legitimate interest to operate the website (Art. 6 (1) lit. (f) GDPR).
Performance cookies – aka analytics cookies – collect information on your usage of our websites. They identify e.g. your internet browser, operating system, visited websites, duration and number of website visits, previously visited website, most commonly visited websites and errors you experienced. The information collected is aggregated and anonymous. It does not allow a personal identification. It only serves the purpose of evaluating and enhancing the user experience of our websites. To the extent that information processed in connection with performance cookies should qualify as personal data, the legal ground for that processing is your consent (Art. 6 (1) lit. (a) GDPR).
Functional cookies enable a website to store information and options you have already previously entered (e.g. username, language settings, layout settings, contact preferences or your location) in order to offer you improved personalized functions. They are also used to enable requested functions, like playing videos. To the extent that information processed in connection with functional cookies should qualify as personal data, the legal ground for that processing is your consent (Art. 6 (1) lit. (a) GDPR).
Targeting cookies – aka cookies for marketing purposes – are used to offer more relevant and interest-specific content to you, to limit the display frequency of ads and to measure the efficiency of an advertising campaign. They register if you have visited a promoted website or not, and which content you used. Such information may be shared with third parties, e.g. advertisers. Legal basis for the processing of personal data in connection with targeting cookies (if any) is your consent (Art. 6 (1) lit. (a) GDPR).
Cookies we use on our website
This website uses the following cookies:
|visitor_id||The visitor cookie, set by the tracking code on website visitors. This is shown as “visitor_id” followed by the unique identifier for that visitor, eg. “visitor_i6780”. No personally identifiable information is stored in the cookie, and the visitor remains anonymous until they convert (when website visitors convert, a prospect record is created in Pardot, and the visitor_id and prospect record are fused together).||Pardot.com|
|_ga||Used to distinguish users.||2 years||google.com|
|_gid||Used to distinguish users.||24 hours||google.com|
|_gat||Used to throttle request rate. If Google Analytics is deployed via Google Tag Manager, this cookie will be named _dc_gtm_<property-id>.||1 minute||google.com|
|AMP_TOKEN||Contains a token that can be used to retrieve a Client ID from AMP Client ID service. Other possible values indicate opt-out, inflight request or an error retrieving a Client ID from AMP Client ID service.||30 seconds to 1 year||google.com|
|_gac_<property-id>||Contains campaign related information for the user. If you have linked your Google Analytics and Google Ads accounts, Google Ads website conversion tags will read this cookie unless you opt-out. Learn more.||90 days||google.com|
|_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||hotjar.com|
|_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||hotjar.com|
|_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||hotjar.com|
|_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||hotjar.com|
|_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||hotjar.com|
|_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||hotjar.com|
|_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||hotjar.com|
|_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||hotjar.com|
|_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||hotjar.com|
|_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||hotjar.com|
|_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||hotjar.com|
|_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||hotjar.com|
|_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||hotjar.com|
|_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||hotjar.com|
|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|
How can I disable cookies or revoke my cookie consent?
You can revoke your consent at any time. To do this, you must deactivate / delete your cookies. One way to deactivate cookies set by our website is to click on the respective link in the cookie cookie confirmation. Another way to deactivate cookies is to change the cookie settings in your internet browser. You will typically find the browser settings for cookies in the options, tools or settings of your internet browser. You can also consult the “Help” menu of your browser. Different browsers may use different mechanisms to disable cookies.
Pullach, February 2021