Cookie Usage and Consent Policy
Last Updated: 2025-10-29 (Note: Content dynamically combines multiple policies.)
Cookie Usage Policy\n\nSECTION 1. INTRODUCTION AND CONSENT FRAMEWORK\n\n1.1. **Purpose.** This Cookie Usage Policy (the 'Policy') provides comprehensive information regarding the use of cookies, tracking technologies, and similar methods by DesirePlex ('The Company') on its Platform.\n\n1.2. **What Are Cookies?** Cookies are small text files that are downloaded to your computer or mobile device when you visit a website. They allow the website to recognize the User's device on subsequent visits, typically to improve the functionality of the site, remember preferences, and collect analytical data.\n\n1.3. **Consent and Legal Basis.** In compliance with global regulations, including the GDPR and ePrivacy Directive, the Company utilizes a robust Cookie Consent Management Platform (CMP). Non-Essential Cookies (e.g., performance, advertising, affiliate) are only placed on the User's device after the User has provided their **explicit, affirmative consent**.\n\nSECTION 2. CATEGORIES OF COOKIES USED\n\nThe Company uses cookies that fall into the following four primary categories:\n\n2.1. **Strictly Necessary (Essential) Cookies.**\n\n(a) **Purpose:** These cookies are essential for the User to browse the Platform and use core features, such as accessing secure areas, maintaining session state (allowing Users to stay logged in), and ensuring age gate verification.\n(b) **Legal Basis:** Legitimate Interest / Performance of Contract. These cookies do not require specific consent as the Platform cannot function correctly without them.\n(c) **Examples:** Session cookies, age verification status cookie, Cryptomus payment session cookie.\n\n2.2. **Performance (Analytics) Cookies.**\n\n(a) **Purpose:** These cookies collect information about how Users utilize the Platform, such as which pages are visited most often and if they receive error messages. This data is aggregated and anonymous and is used purely to improve how the Platform functions and performs.\n(b) **Legal Basis:** Consent.\n(c) **Examples:** Anonymous usage metrics, traffic source identification.\n\n2.3. **Functionality Cookies.**\n\n(a) **Purpose:** These cookies allow the Platform to remember choices the User makes (such as username, language, or region) and provide enhanced, more personalized features. They may also be used to remember changes the User has made to text size, fonts, and other customizable elements.\n(b) **Legal Basis:** Consent.\n(c) **Examples:** Remembering User preferences for content display, volume settings for audio content.\n\n2.4. **Targeting / Advertising (Affiliate) Cookies.**\n\n(a) **Purpose:** These cookies are used to deliver advertisements and track affiliate referrals that are more relevant to the User and their interests. They are also used to limit the number of times a User sees an advertisement and help measure the effectiveness of advertising campaigns, specifically including tracking clicks on **affiliate links** and attributing commissions.\n(b) **Legal Basis:** Explicit Consent.\n(c) **Third-Party Interaction:** These cookies are often placed by third-party advertising or affiliate networks (e.g., those managing the DesirePlex affiliate program) with the Company’s permission.\n\nSECTION 3. THIRD-PARTY COOKIES AND TRACKING\n\n3.1. **Third-Party Responsibility.** The Platform incorporates content and features from third-party providers (e.g., Cryptomus for payment, affiliate tracking partners, social media integrations, and analytics services). These third parties may set their own cookies and tracking technologies.\n\n3.2. **Cryptomus Tracking.** When a User interacts with the payment gateway, Cryptomus may place cookies essential for payment processing, security, and fraud prevention. The Company is not responsible for the privacy practices of Cryptomus; Users are encouraged to review the Cryptomus privacy policy.\n\n3.3. **Affiliate Cookies.** Affiliate tracking cookies are crucial for the operation of the DesirePlex affiliate program. These cookies drop an anonymous tag to identify the referring affiliate partner upon a User's first visit. **Users must explicitly consent to Targeting/Affiliate cookies for this tracking to occur.**\n\nSECTION 4. MANAGING YOUR COOKIE CONSENT AND OPT-OUT\n\n4.1. **Consent Management Platform (CMP).** Upon first accessing the Platform, Users will be presented with the CMP, providing granular control over which categories of Non-Essential Cookies they consent to (Performance, Functionality, Advertising/Affiliate).\n\n4.2. **Modifying Consent.** Users may adjust their cookie preferences at any time by accessing the dedicated 'Cookie Settings' link available in the footer of the Platform.\n\n4.3. **Browser Controls (Opting Out).** Users can manage or delete cookies through their browser settings. Most browsers allow Users to refuse all cookies or to refuse only third-party cookies. However, blocking all cookies (especially Essential Cookies) may negatively impact the functionality and accessibility of the Platform.\n\n4.4. **Withdrawal of Consent.** The withdrawal of consent for non-essential cookies will result in the Company and its partners ceasing the collection of data via those cookies moving forward. Withdrawal does not affect the lawfulness of processing based on consent before its withdrawal.\n\n--- [ Policy Section Break ] ---\n\n## Cookie Consent Management Policy\n\nSECTION 1. CONSENT FRAMEWORK AND PURPOSE\n\n1.1. **Scope and Application.** This Consent Management Policy establishes the procedures for obtaining, documenting, and managing User consent for the processing of personal data via cookies and similar tracking technologies on the DesirePlex Platform, in accordance with global privacy legislation, specifically including GDPR's consent requirements.\n\n1.2. **Definition of Valid Consent.** The Company considers consent to be valid only if it is:\n\n(a) **Freely Given:** The User must have a genuine choice and must not be coerced.\n(b) **Specific:** Consent must relate to specific purposes (e.g., Analytics, Advertising).\n(c) **Informed:** The User must be fully informed about what they are consenting to (as provided in the Cookie Policy).\n(d) **Unambiguous:** Consent must be given by a clear, affirmative action (e.g., ticking a box or clicking an 'Accept' button).\n\n1.3. **Consent Management Platform (CMP).** The Platform employs a dedicated CMP to facilitate a transparent and user-friendly consent process, which serves as the primary mechanism for collecting and recording consent.\n\nSECTION 2. CONSENT MECHANISMS AND USER OPTIONS\n\n2.1. **Initial Banner and Granular Choice.** Upon the User's first visit to the Platform, a conspicuous banner or pop-up will appear, offering the following clear and distinct options:\n\n(a) **'Accept All'**: Grants consent for all cookie categories (Performance, Functionality, Advertising/Affiliate).\n(b) **'Reject All'**: Denies consent for all non-Essential cookies.\n(c) **'Manage Preferences'**: Directs the User to a granular control center where they can individually select or deselect specific non-Essential cookie categories.\n\n2.2. **Equality of Choice.** The options to 'Accept All' and 'Reject All' (or an equivalent option that closes the banner without consent) are presented with equal prominence to ensure the consent is freely given.\n\n2.3. **No Pre-Ticked Boxes.** All preference options within the 'Manage Preferences' section for non-Essential cookie categories are presented as un-ticked by default. The User must actively opt-in to each category.\n\n2.4. **No Cookie Wall.** Access to the core functionality of the Platform is not conditional on consenting to non-Essential cookies.\n\nSECTION 3. DOCUMENTATION AND AUDIT TRAIL\n\n3.1. **Documentation Obligation.** The Company maintains a detailed and auditable record of all User consents, rejections, and withdrawals to demonstrate compliance with legal requirements. This record includes:\n\n(a) **Identity:** The unique User ID (or pseudonymized identifier like an IP address or device ID).\n(b) **Timestamp:** The date and time the consent was given or withdrawn.\n(c) **Status:** Whether consent was given or refused for each category of cookies.\n(d) **Version:** The version of the Cookie Policy/Consent Policy in effect at the time of consent.\n\n3.2. **Retention of Records.** Consent records are retained securely for a period that allows the Company to demonstrate compliance in the event of a regulatory audit, typically for the duration the consent is valid plus a reasonable audit period (e.g., six months).\n\nSECTION 4. WITHDRAWAL OF CONSENT AND RENEWAL\n\n4.1. **Right to Withdraw.** Users have the unconditional right to withdraw their consent for one or more cookie categories at any time. Withdrawal is as easy as granting consent.\n\n4.2. **Withdrawal Procedure.** Consent can be withdrawn via the 'Cookie Settings' link prominently displayed on the Platform footer or within the User's account dashboard.\n\n4.3. **Impact of Withdrawal.** Upon withdrawal, the Company immediately stops placing cookies related to the withdrawn category, and ceases any further processing of data collected via those cookies. Withdrawal does not affect the lawfulness of processing that occurred based on valid consent prior to its withdrawal.\n\n4.4. **Consent Renewal.** The Company will re-request consent from the User under the following circumstances:\n\n(a) If the User clears their browser cookies and accesses the Platform again.\n(b) If there is a material change to the types of cookies used or the purposes for which they are processed.\n(c) If the Company's recorded consent period for the User expires (typically 6 or 12 months).