What this policy covers
Cookies are small text strings. Similar technologies include HTML5 local storage, session storage, shared workers, software development kits inside embedded media, and tracking pixels that execute JavaScript. For readability this document uses the term “cookies” to reference the entire class unless a distinction matters legally. Frizeloneixodeu.world operates the Vireonix domain; questions may be emailed to chat@frizeloneixodeu.world or posted to 151 Camden High St, London NW1 7JE.
We classify cookies so you can align preferences with risk tolerance. Categories mirror the UK ICO’s recommended approach: strictly necessary, functional (if used), analytics, and marketing. Functional cookies are uncommon on this storefront but would cover remembered UI states if deployed.
How consent is captured & refreshed
On your first meaningful interaction, a glassmorphism banner surfaces with Accept all, Reject non-essential, and Cookie settings. Accepting writes a JSON structure to local storage enumerating analytics and marketing approval. Rejecting records negative flags while still allowing necessary operations. Opening settings reveals toggles; strictly necessary cookies remain on because they alone cannot be disabled without breaking essential site mechanics.
You may revisit preferences by clearing site data through browser menus or contacting us for a manual reset walkthrough. Major campaigns might prompt a soft rebanner if the law requires re-consent after a material processing change.
Proof of consent. We log timestamp, banner version identifier, and chosen categories to defend accountability during regulatory inquiries. Logs exclude sensitive card data.
Strictly necessary cookies & storage keys
- Consent vault — local storage key vireonix_cookie_prefs holding Boolean analytics/marketing fields plus ISO timestamps; persists until cleared.
- Session continuity — ephemeral cookies tying your browser to a balanced server node during checkout; expire when the tab closes or after twenty-four hours of inactivity.
- Security tokens — short-lived anti-CSRF values on forms; HttpOnly where implemented server-side.
- Load shedding — infrastructure partners may place resilience cookies to route traffic—retention typically under twenty-four hours.
Analytics cookies (optional)
When permitted, analytics partners help us count visits, measure scroll depth on educational articles, and understand device mix so we optimise for mobile-first experiences. IP addresses may be truncated before storage. Aggregated dashboards cannot reliably re-identify individuals. Retention commonly spans thirteen months from the last event per partner defaults, after which identifiers rotate or expire.
Declining analytics does not remove historical aggregated metrics already baked into trend lines; it stops new event collection from your browser profile going forward.
Marketing & attribution cookies
Marketing cookies or tags activate only when you opt in. They may attribute newsletter clicks, measure creative fatigue, or build custom audiences inside advertising platforms. Partners include large social networks and independent demand-side platforms; each applies independent controller or joint-controller terms described in their privacy notices.
You can withdraw consent granularly. Withdrawing may not retroactively delete data already shared with partners; use partner-provided ad preference centres for complementary controls.
Local storage & invisible pixels
Some experiments store lightweight identifiers in local storage when cookies are blocked, subject to the same consent tier. Invisible one-by-one pixels may fire on order confirmation pages to reconcile server logs with client-side timing—again gated behind marketing consent when used for attribution rather than load balancing.
Browser & device controls
Modern browsers let you block third-party cookies, auto-delete data on exit, or receive prompts before storage. Consult documentation for Chrome, Safari, Firefox, Edge, or Brave. Mobile operating systems provide parallel settings at the OS level for in-app browsers.
If you block strictly necessary storage, checkout, login walls, or consent recall may fail; we surface inline errors when feasible so you understand the trade-off.
Revisions & contact
We amend this Cookie Policy when partners change identifiers, new jurisdictions alter cookie consent rules, or we adopt additional technologies like consent management platforms. Material updates appear with a refreshed dynamic date ribbon correlated to publication day, month, and year.
For questions, email chat@frizeloneixodeu.world. Postal inquiries should reference “Cookie Policy query” so routing teams prioritise appropriately.