Transparency layer

Cookie Policy

This document explains how Clearvital uses cookies, browser storage, and similar technologies on clearvital.world. It complements the Privacy Policy and mirrors expectations under the ePrivacy framework as implemented in Germany.

Version anchored to . Storage names may change cosmetically; purpose descriptions remain the source of truth.

Chapter A

What cookies and similar technologies mean here

A cookie is a small text file placed on your device when a server responds to a browser request. Local storage and session storage entries can fulfil comparable functions—remembering UI state or consent decisions without resending full page bundles. Pixel tags or server logs are not “cookies” strictly speaking but may produce analogous identifiers; where those identifiers are personal data, the Privacy Policy applies in parallel.

First-party technologies are set by our domain or scripts we serve directly. Third-party technologies originate from integrated services (for example analytics vendors if you opt in). This distinction matters for liability and consent sequencing.

Chapter B

Legal grounds at a glance

Strictly necessary storage may rely on the exemption for technologies essential to provide an explicitly requested service—for example storing that you dismissed a consent interface so it does not loop infinitely. Optional analytics or marketing tools that read or write identifiers require consent under current European guidance unless a narrow statutory exemption applies, which we do not assume for non-essential measurement.

Consent is collected through the banner and modal on your first visit or after you clear site data. Granular choices survive until you revise them or delete storage manually.

Chapter C

Essential storage we consider necessary

Consent state: Records which version of choices you saved so the website respects them on repeat visits.
Security context: If we deploy bot-mitigation challenges, transient tokens may be required; they are not reused for marketing.
Load distribution: Some hosts set routing cookies to maintain session affinity during deployments; lifetimes are short.

Essential does not mean “everything we find convenient.” We periodically audit whether each key remains justified. If a technology migrates from essential to optional because functionality changes, we recategorise it and request consent where needed.

Chapter D

Optional analytics and marketing

When you enable the analytics and marketing toggle and confirm, we may load scripts that measure aggregated traffic, approximate referral sources, and rudimentary funnel insights for informational pages. Marketing pixels, if introduced later, fall under the same toggle until we separate categories in the interface—with clearer labels if regulators require split consents.

Denied optional storage means those script URLs are not requested; we do not “pretend reject” while pinging endpoints silently. Server access logs still occur at the hosting layer; their retention is covered under the Privacy Policy’s technical data section.

Chapter E

Third-party relationships

Font and icon CDNs may log connection metadata when assets load. We select HTTPS endpoints to reduce tampering. Where feasible, self-hosting replaces remote includes to shorten the third-party chain; updates will be noted in release notes for enterprise clients.

If analytics vendors process data outside the EEA, transfers rely on instruments referenced in the Privacy Policy. Subprocessor notifications happen when contracts require or when a change materially affects you.

Chapter F

Lifetimes and refresh

Consent artefacts generally persist up to twelve months before we ask again, sooner if regulators publish shorter recommended review cycles. Session cookies expire when you close the browser tab or idle time exceeds host defaults. Analytics cookies, if activated, follow vendor-specific max-age values disclosed in internal inventory sheets available on request.

When you revoke consent, we instruct compatible tags to stop further writes; deletion of historical aggregates on vendor dashboards follows their tools’ erase flows.

Chapter G

Browser and device controls

All major browsers let you delete cookies, block third parties, or partition storage per site. Global blocking may break consent recall features or security checkpoints. For precise management, use our in-site modal plus browser tools together.

On mobile WebKit browsers, Intelligent Tracking Prevention may expire storage sooner than our declared maximum; that is expected client behaviour.

Chapter H

Changes and questions

Material changes to categories or vendors will be highlighted with a revised effective date. If we introduce new optional tools, we prompt for fresh consent rather than silently folding them into old bundles.

Email service@clearvital.world for specific technical questions about cookies; operational coaching questions should stay in the general inbox with clear subject lines.