Cookie Policy
Cookies and similar storage technologies stitch together the modern web. This document inventories what Pavira deploys on vornyxoldlix.world, why each category exists, how long identifiers linger, and how you can flip switches even after a first visit. Pair it with our Privacy Policy for the full picture of personal data processing conducted by Vornyxoldlix.world from Rotterdam.
Identity: Vornyxoldlix.world — Binnenweg 201, 3014 GJ Rotterdam, Netherlands — chat@vornyxoldlix.world
Definitions in plain language
A cookie is a small text file your browser stores when a server sends a Set-Cookie header. Local storage and session storage APIs can hold larger preference objects. Pixel tags, SDKs inside packaged apps, and server-side sessions may synchronize with those client files. For readability we refer to the bundle as “cookies” unless a distinction matters legally.
First-party
Set by hostnames we operate directly—typically load balancers, consent logs, and session continuity after login if we add accounts later.
Third-party
Originate from embedded analytics suites, advertising verification partners, or fraud networks only after you opt in where law demands prior consent.
Strictly necessary storage
These items power security features, distribute traffic, remember your cookie choices, prevent cross-site request forgery in any authenticated areas, and maintain shopping cart integrity during checkout. They do not require consent under the ePrivacy exemption for communications strictly needed to provide an explicitly requested service, though you may still disable them in aggressive browser modes at the cost of broken flows.
- Load balancer stickiness: keeps your TCP session on healthy nodes during deployments.
- Consent string: stores JSON describing accepted or rejected optional categories so we do not bombard you with banners each page view.
- Session continuity: ephemeral identifiers for multi-step forms until submit or timeout.
Analytics storage after consent
When you activate analytics toggles, we may record pseudonymous identifiers to compute unique visitor estimates, scroll depth histograms, conversion funnels, and creative fatigue metrics. Retention aligns to vendor defaults, often twenty-four to twenty-six months, but we configure shorter windows where products allow. IP truncation or replacement with aggregator-only reports may apply regionally.
Marketing and advertising storage after consent
Advertising partners may drop identifiers to cap frequency, attribute impressions to eventual orders, or build remarketing segments when permissible. You can withdraw consent through our banner or partner-specific portals such as the EDAR framework. Children-oriented profiling is not part of our roadmap.
Your control plane
Browsers offer global cookie blocking, per-site exceptions, and “delete on exit” schedules. Our banner’s “Reject” issues the narrowest viable optional footprint while keeping necessity cookies. Re-opening “Cookie settings” surfaces category toggles mirroring GDPR granularity expectations.
Signal in
You land on Pavira; necessary cookies attach immediately to honor security baselines.
Choice recorded
Optional tags wait until Accept, granular Save, or implied continuation per jurisdiction.
Ongoing audit
Quarterly we diff vendor libraries against this listing and archive change logs with timestamps including for the running quarter.
Updates and versioning
Technology partners rotate domains occasionally. When that happens we publish a short addendum referencing the effective engineering change. Major policy shifts trigger proactive email only if you maintain an account with marketing flags; otherwise the banner may reappear to refresh consent.
Live reference stamp: