With this cookie policy, we want to explain what cookies and similar technologies are, how we and other service providers use them on this website, what information they collect, how long they are used, and for what purposes.<\/p>
This cookie policy is a supplement to this website's Privacy Policy<\/a>. The cookie policy specifies how a website uses cookies and what data it collects through them, while the privacy policy is a more comprehensive overview of all data processing activities on the website and beyond.<\/p> Cookies are small pieces of information, similar to text files, that can be stored and read on the end device. They serve various purposes, including maintaining basic website functionalities, security and privacy, providing optional website functions, collecting statistical data on visitor traffic, and supporting marketing systems. Practical examples of what can be stored in cookies include login status for user accounts, the contents of shopping carts on e-commerce platforms, or a user ID for website behavior tracking. The setting and reading of cookies in the European Union (EU) and the European Economic Area (EEA) is in accordance with Art. 5 (3) ePrivacy Directive and Recital 66 ePrivacy Directive only permitted if a user has given his consent on the basis of comprehensive information about the purposes of the processing. The website operator may also set cookies if they are strictly necessary to provide you as a user with the expressly requested service, e.g. the basic content of this website or other strictly necessary cookies for basic functionality of the website to be displayed to you without your consent.<\/p> Services and their cookies can be set and read on the legal basis of your consent or a legitimate interest. When you first visited this website, you were asked for your consent and you had the opportunity to object to the use of certain services. We explained which legal basis is used for each service in our consent dialog.Cookies are small text files that websites store on your device (computer, smartphone, tablet) when you visit them. They contain information that can be used to remember your preferences, track your activity on the site, and personalize your experience.\n\nSimilar technologies include:\n\n* **Pixels (or tracking pixels, web beacons, clear GIFs):** These are tiny, transparent images embedded in web pages or emails. When the page or email is loaded, the pixel signals that it has been viewed, allowing websites or advertisers to track user behavior, deliver targeted advertising, and analyze website traffic.\n* **Local Storage and Session Storage:** These are browser features that allow websites to store data directly on your device, similar to cookies but often with larger storage capacities and different lifespans. Local Storage persists even after you close your browser, while Session Storage is deleted when you close the browser.\n* **SDKs (Software Development Kits):** In the context of mobile applications, SDKs are packages of code that allow developers to integrate third-party services, such as analytics or advertising, into their apps. These SDKs can collect and transmit data about app usage, similar to how cookies track web usage.<\/h2>
The information can technically be stored in various ways. The best-known examples of this are HTTP cookies and cookie-like technologies such as local storage, session storage, or IndexedDB. Each type of storage has different properties, which determine the technical handling, accessibility, and controllers authorized to access the information. All these types of storage are usually summarized under the term \"cookies\" and are therefore called as such in this cookie policy.<\/p>The legal basis for setting\/reading cookies primarily stems from data protection and privacy laws. The most influential and widely adopted legal framework is the **General Data Protection Regulation (GDPR)** in the European Union.\n\nHere's a breakdown of the legal basis:\n\n1. **GDPR (General Data Protection Regulation):**\n * **Article 6 - Lawfulness of processing:** This article sets out the lawful bases for processing personal data. For cookies, the relevant bases are:\n * **Consent (Article 6(1)(a)):** This is the most common and often required basis. For non-essential cookies (e.g., analytics, marketing, personalization), you generally need the user's explicit, informed, and freely given consent **before** you set or read them. This consent must be granular (allowing users to consent to different types of cookies) and easy to withdraw.\n * **Legitimate Interests (Article 6(1)(f)):** This basis *can* be used for strictly necessary cookies, but it's a more complex argument and often not applied to cookies that collect user data without clear necessity for the core functionality of the website. It requires a balancing test between the interests of the website operator and the rights and freedoms of the user.\n * **ePrivacy Directive (and its upcoming replacement, the ePrivacy Regulation):** While GDPR covers personal data processing, the ePrivacy Directive (specifically Article 5(3)) has historically been the primary legislation addressing cookies and similar technologies. It requires that users be informed about and consent to the storage of information, or the gaining of access to information already stored, in their terminal equipment. The GDPR's consent requirements are applied to this. The new ePrivacy Regulation aims to consolidate and update these rules.\n\n2. **Other Jurisdictions:**\n * **California Consumer Privacy Act (CCPA) \/ California Privacy Rights Act (CPRA):** In California, cookies that collect personal information are subject to the CCPA\/CPRA. While it doesn't use the same \"consent\" framework as GDPR for all data, it provides consumers with rights to opt-out of the \"sale\" or \"sharing\" of their personal information, which can include cookies used for advertising and analytics purposes. Businesses must provide a clear \"Do Not Sell or Share My Personal Information\" link.\n * **Other National Privacy Laws:** Many countries have their own data protection laws that incorporate principles similar to GDPR and the ePrivacy Directive, requiring consent or other lawful bases for cookie usage. Examples include laws in the UK, Canada (PIPEDA), Australia, Brazil (LGPD), etc.\n\n**Key Principles and Requirements:**\n\n* **Transparency:** Users must be clearly informed about what cookies are being used, why they are being used, and what data they collect. This is typically done through a cookie banner and a detailed cookie policy.\n* **Consent Management:** A robust cookie consent mechanism is essential. This includes:\n * **Cookie Banner:** A prominent notice on the website informing users about cookie usage and soliciting consent.\n * **Granular Choices:** Allowing users to accept or reject different categories of cookies (e.g., essential, analytics, marketing).\n * **Easy Withdrawal:** Users must be able to withdraw their consent as easily as they gave it, often through a link in the website's footer.\n* **Strictly Necessary Cookies:** Cookies that are essential for the basic functioning of the website (e.g., session cookies for login, shopping cart cookies) may not require explicit consent, but they should still be disclosed. However, the interpretation of \"strictly necessary\" can be narrow.\n\nIn essence, the legal basis for setting\/reading cookies hinges on obtaining valid consent from users for non-essential cookies, and disclosing the use of all cookies, while respecting user privacy rights.<\/h2>
What rights does the website visitor have?<\/h2>
You have the right to view your decision history, change your privacy settings, object to the use of services, and revoke your consent at any time. Below, you'll find options for exercising your rights:How to manage cookies in a browser?<\/h2>