Cookie Policy

1. What are Cookies?

Cookies, localStorage, sessionStorage, pixels, and similar technologies may store information on a device or access it. Under Basic Consent Mode, no optional technology or measurement request starts before the relevant consent.

2. How We Use Cookies

We use cookies for the following purposes:

• Essential storage records cookie-consent-given and cookie-consent-choices, the consent version/time and language in localStorage, and protects an authenticated session. The cookie-consent-pending and cookie-consent-evidence-outbox keys retain only a minimal pending choice, its revision, and a pseudonymous evidence identifier until the backend confirms it; malformed or expired entries are removed and the maximum validity is 13 months. In the client portal, the current tab may additionally keep only the payment-session id, provider and status in sessionStorage for no more than 30 minutes; checkout URLs, provider tokens and bank-transfer details are not persisted in the browser. This storage is not used for analytics or advertising. After withdrawal, the rejection preference remains stored while optional identifiers for that category are removed.
• We activate Google Analytics 4, _ga and _ga_* cookies, a session identifier in sessionStorage expiring after 30 minutes of inactivity, and pp_analytics_client_id in localStorage for no more than 90 days only after analytics consent. We measure only the page, source and UTM campaign parameters, scroll thresholds, engagement buckets, CTA type/placement, and controlled form friction; we do not record form field values or PII. Raw events and attribution have a 90-day limit.
• We activate Google Ads, advertising cookies, and advertising click identifiers gclid, wbraid, and gbraid only after marketing consent. Google Ads may process the identifiers for advertising measurement; PP Solutions restricted sales attribution retains them for no more than 90 days, and the analytics event store rejects them.
• Optional external services such as reCAPTCHA, Google Maps, YouTube, or Vimeo load only after the relevant category choice or an explicit request for that feature. A language or theme choice cannot activate analytics.
• Google or Vimeo may fetch embedded resources and set their technologies only after consent matching the feature. Windsor.ai does not place its own browser tag on this website; it operates server-side as a read-only reporting integration for selected data.

3. Types of Cookies We Use

4. Managing Cookies

Withdrawal is available as easily as giving consent. After withdrawal, we block future optional tags and remove category storage under our control. You can manage preferences:

• Through Reject all, Accept all, or independent category controls in the banner and Cookie settings.
• Through browser settings that may additionally block or delete cookies and storage.
• By contacting the Controller; contact is not required for ordinary withdrawal on the website.

5. Third-Party Cookies

After the relevant consent, we use Google Ireland Limited services for Google Analytics 4, Google Ads, reCAPTCHA, Google Maps, and YouTube, and Vimeo.com, Inc. for Vimeo media. Windsor Group AG (Windsor.ai) may read selected Google reports and restricted backend views as a reporting processor, but it does not set its own cookies on the user device. Providers may use approved subprocessors and transfers based on an adequacy decision, the EU-U.S. Data Privacy Framework, or Standard Contractual Clauses.

6. Changes to Cookie Policy

Each version has a date. A material change in purpose, provider, or data scope versions the consent and requires fresh consent; the changed category remains disabled until then.