Cookie Policy

To manage the cookies and similar technologies used (tracking pixels, web beacons, etc.) and related consents, we use the consent tool “Real Cookie Banner”. Details on how “Real Cookie Banner” works can be found at https://devowl.io/rcb/data-processing/

The legal basis for the processing of personal data in this context are Art. 6 (1) (c) GDPR and Art. 6 (1) (f) GDPR. Our legitimate interest is the management of the cookies and similar technologies used and the related consents.

The provision of personal data is neither contractually required nor necessary for the conclusion of a contract. You are not obliged to provide the personal data. If you do not provide the personal data, we will not be able to manage your consents.

Third Party Cookies – Functional

YouTube

YouTube enables the embedding of content published on youtube.com into websites to enhance the website with videos. This requires processing the user’s IP-address and metadata. Cookies or cookie-like technologies can be stored and read. These can contain personal data and technical data like user IDs, consent, settings of the video player, connected devices, interactions with the service, push notifications and used account. This data can be used to collect visited websites, detailed statistics about user behaviour, and it can be used to improve the services of Google. It can also be used for profiling, e.g. to provide you with personalized services, such as ads based on your interests or recommendations. This data may be linked by Google to the data of users logged in on the websites of Google (e.g. youtube.com and google.com). Google provides personal information to their affiliates and other trusted businesses or persons to process it for them, based on Google’s instructions and in compliance with Google’s privacy policy.

Vimeo

Vimeo enables the embedding of content published on vimeo.com into websites to enhance the website with videos. This requires processing the user’s IP-address and metadata. Cookies or cookie-like technologies can be stored and read. These can contain personal data and technical data like user IDs, consent, security tokens, language, settings of the video player, interactions with the service and the used account. The data can be used to collect visited websites, detailed statistics about user behaviour, and it can be used to improve the services of Vimeo. This data may be linked by Vimeo to the data of users logged in on the websites of Vimeo (e.g. vimeo.com). It can also be used for profiling, e.g. to provide you with personalised services, such as ads based on your interests or recommendations. Vimeo provides personal information to authorized vendors, advertising companies, analytics providers, affiliates and advisors while taking reasonable efforts to review vendors for their privacy and data security practices.

Google Maps

Google Maps enables the embedding of maps directly into websites to enhance the website. This requires processing the user’s IP-address and metadata. Cookies or cookie-like technologies can be stored and read. These can contain personal data and technical data like user ID, consent, settings of the map viewer and security tokens. This data can be used to collect visited websites, detailed statistics about user behaviour, and it can be used to improve the services of Google. This data may be linked by Google to the data of users logged in on the websites of Google (e.g. google.com and youtube.com). Google provides personal information to their affiliates and other trusted businesses or persons to process it for them, based on Google’s instructions and in compliance with Google’s privacy policy.

Google Tag Manager

Google Tag Manager makes it possible to configure and manage tags (e.g. integration of third-party services, tracking of events, forwarding of collected data between different services and similar actions). This requires processing the user’s IP-address and metadata. Google Tag Manager can also collect information about e.g. the status of the browser used, including error messages, subpages accessed including their history (only on this website), clicks on elements, scroll depth on the website and visibility of certain elements, form entries, interactions with YouTube videos, and contextual events on the website (e.g., adding a product to the shopping cart), and use this data to personalise the website for you, as well as pass on collected data to third-party services, insofar as there are legal bases for data processing by these services. The data is processed to provide the functionalities of the Google Tag Manager and to improve Google’s services. Google provides personal information to their affiliates and other trusted businesses or persons to process it for them, based on Google’s instructions and in compliance with Google’s privacy policy.

Third Party Cookies – Statistics

Google Analytics

Google Analytics creates detailed statistics of user behaviour on the website to obtain analysis information. This requires processing a user’s IP-address and metadata which can be used to determine a user’s country, city and language. Cookies or cookie-like technologies can be stored and read. These can contain personal data and technical data like user ID which can provide the following additional information:

– time information about when and how long a user was or is on the different pages of the website

– device category (desktop, mobile and tablet), platform (web, iOS app or Android app), browser and screen resolution a user used

– where a user came from (e.g. origin website, search engine including the searched term, social media platform, newsletter, organic video, paid search or campaign)

– whether a user belongs to a target group/audience or not

– what a user has done on the website and which events were triggered by actions of the user (e.g. page views, user engagement, scroll behaviour, clicks, added payment info and custom events like e-commerce tracking)

– conversions (e. g. if a user bought something and what was bought)

– gender, age and interest if an allocation is possible 

This data can also be used by Google to collect visited websites, and it can be used to improve the services of Google. It can be linked across multiple domains, which are operated by this website operator, with other Google products (e.g. Google AdSense, Google Ads, BigQuery, Google Play) which the website operator uses. It can also be linked by Google to the data of users logged in on the websites of Google (e.g. google.com). Google provides personal information to their affiliates and other trusted businesses or persons to process it for them, based on Google’s instructions and in compliance with Google’s privacy policy. It can also be used for profiling by the website operator and Google, e.g. to provide a user with personalised services, such as ads based on a user’s interests or recommendations.

Third Party Cookies – Marketing

Google Ads

Google Ads Conversation Tracking tracks the conversion rate and success of Google Ads campaigns. Cookies are used to differentiate users and track their behavior on the site in detail, and to associate this data with advertising data from the Google Ads advertising network. In addition, the data is used for so-called “remarketing” to display targeted advertising again to users who have already clicked on one of our advertisements within the Google Ads network. This data may be linked to data about users who have signed in to their Google accounts on google.com or a localized version of Google.

HubSpot

HubSpot enables customer relationship management (CRM) functions, including contact forms, newsletter sign-ups, live chat, and the management of marketing and sales interactions. This requires processing the user’s IP address and metadata. Cookies or cookie-like technologies can be stored and read. These can contain personal data and technical data such as user IDs, timestamps, browser information, consent status, and interaction history.

The data can be used to recognise returning visitors, pre-fill forms, store preferences, and provide personalised website experiences. HubSpot cookies may also track website usage patterns such as visited pages, length of stay, and conversions (e.g. submitting a form or signing up for a newsletter). These cookies allow HubSpot and the website operator to create detailed statistics about user behaviour, attribute marketing success to campaigns, and optimise the website and communication with users.

This data may be linked by HubSpot to the data of users logged in on HubSpot’s own services or processed in connection with the website operator’s CRM system. HubSpot provides personal information to its affiliates and other trusted partners to process it on HubSpot’s behalf, based on HubSpot’s instructions and in compliance with HubSpot’s privacy policy. Data may also be transferred to HubSpot, Inc. in the United States, with appropriate safeguards in place under applicable data protection law.

First Party Cookies – Essential

Real Cookie Banner
Real Cookie Banner asks website visitors for consent to set cookies and process personal data. For this purpose, a UUID (pseudonymous identification of the user) is assigned to each website visitor, which is valid until the cookie expires to store the consent. Cookies are used to test whether cookies can be set, to store reference to documented consent, to store which services from which service groups the visitor has consented to, and, if consent is obtained under the Transparency & Consent Framework (TCF), to store consent in TCF partners, purposes, special purposes, features and special features. As part of the obligation to disclose according to GDPR, the collected consent is fully documented. This includes, in addition to the services and service groups to which the visitor has consented, and if consent is obtained according to the TCF standard, to which TCF partners, purposes and features the visitor has consented, all cookie banner settings at the time of consent as well as the technical circumstances (e.g. size of the displayed area at the time of consent) and the user interactions (e.g. clicking on buttons) that led to consent. Consent is collected once per language.