Cookie Policy

What cookies and similar technologies mean here

Cookies are small text strings a server places on your device through the browser. Pixels, local storage, session storage, and indexed databases can behave similarly for preference persistence. Throughout this Policy the word “cookie” includes those parallels unless we specify otherwise.

Inventory of purposes by category

Strictly necessary. Security tokens, bot-mitigation challenges, cart integrity cues (if a shop flow is active), CSRF protection, and user interface state such as collapsed accordions purely for layout. These run regardless of optional consent where exempt under ePrivacy implementation guidance.

Analytics. Activated only if you choose “Accept all” or enable the analytics toggle in Cookie settings. We prefer aggregated metrics—page views, scroll depth buckets, anonymous funnel steps—and configure vendors to shorten IP addresses or discard them when technically feasible.

Marketing and attribution. Also opt-in. May include conversion pixels that help evaluate whether an advertisement drove a visit. Partner terms govern additional retention; we review vendor lists quarterly and remove dormant tags.

Functional extras. Optional conven such as remembering a selected language variant beyond the browser default. If we add these, they will appear in the settings modal with plain-language labels.

How you grant or refuse consent

First-time visitors see a bottom banner with Accept all, Reject, and Cookie settings. Rejecting keeps only strictly necessary processing. Accept all enables analytics and marketing where implemented. Cookie settings opens a glass-style panel with category toggles; Save choices writes preferences to local storage so the banner does not nag on every navigation until you clear site data or we bump a major policy version that requires renewal.

You may withdraw consent at any time by clearing storage and revisiting, or by contacting us for manual guidance if a future dashboard link is added to the footer design.

Local storage versus HTTP cookies

Our consent log may use localStorage keys such as revion_cookie_prefs holding a JSON object with boolean flags for analytics and marketing. This file is not transmitted automatically on every HTTP request like a classic cookie, but it is still personal data if combined with other identifiers.

Typical lifetimes

Session cookies expire when you close the browser. Persistent first-party analytics cookies commonly last twelve to twenty-four months depending on vendor defaults; we negotiate shorter periods when contracts allow. Marketing pixels may reset timers whenever you interact with a partner site. Consent records persist until overwritten.

Third-party involvement

When a third party sets a cookie, their controller responsibilities apply in addition to ours. We list representative partners in onboarding documentation supplied to enterprise clients and update this Policy when the public site adds a new category-class partner. Payment processors may set fraud-prevention cookies independent of our banner; consult their policies for those domains.

Browser and device controls

Major browsers let you block third-party cookies globally, delete existing cookies on exit, or request “Do Not Track” (not uniformly honoured). Mobile operating systems offer reset advertising identifiers. These tools supplement rather than replace our consent UI.

Rights and questions

Under the GDPR and similar statutes you may object to certain processing stemming from non-essential cookies. Because some rights overlap with general personal data processing, see the Privacy Policy for access and erasure pathways. Direct cookie questions may be emailed to ask@tluzarinkhimreon.world.

Updates

We will revise this Cookie Policy when regulators issue guidance, browsers phase out third-party cookies, or we restructure consent management vendors. Material changes may trigger a refreshed banner prompt. The dynamic date badge reflects the day you load the page; archival PDF exports for enterprise customers may carry a separate version string.