Cookie Policy
Cookies and parallel storage technologies are how modern browsers remember consent, protect sessions, and—when you say yes—let Nexvia understand aggregated traffic. This document mirrors what our banner explains, but stretches into implementation detail so curious engineers, procurement teams, and supervisory auditors can follow the trail.
Reference refresh:
What this Policy covers
We describe HTTP cookies, HTML5 local storage entries, session storage mirrors, and pixels that behave like cookies. Together they are storage technologies. Some activate without consent because they are essential; others wait for your tap on Accept or a granular save inside the settings modal.
Controller contact mirrors the Privacy Policy: Westersingel 108, 3015 LB Rotterdam, Netherlands, email talk@hipwrist.world.
Strictly necessary storage
These bits keep the cookie banner honest, store CSRF tokens on forms when we enable them, persist session identifiers during checkout pilots, and honor load balancer affinity. They cannot be declined without breaking navigation. Dutch implementation acts view them as exempt from prior consent when strictly limited to service delivery.
- nexvia_cookie_prefs_saved (localStorage): remembers whether you finalized a decision.
- nexvia_cookie_analytics|marketing (localStorage): mirrors your last toggle states for modal reopening.
Analytics layer
If you opt in, lightweight scripts may record pseudonymous identifiers, truncated IP addresses, device class, coarse geography, and engagement metrics. We configure retention on vendor dashboards to the minimum interval that still yields trend visibility—typically between two and fourteen months depending on the partner.
Analytics cookies never aim to score individuals for credit or employment; if a vendor introduces such features, we disable them contractually.
Marketing and attribution
Marketing cookies remember which creative version you saw, whether you arrived from a partner newsletter, and help frequency-cap repetitive ads. They activate only after explicit opt-in and can be revoked instantly through the banner’s reject path.
Local storage nuances
Some browsers partition storage per top-level site. If you clear site data manually, consent resets and the banner reappears—this is expected behavior under privacy-forward browser engineering, not a malfunction.
Vendor due diligence
Before enabling third-party tags, we review privacy policies, subprocessors, SCC attachments, and incident history. Major analytics or ad partners must provide EU data residency options or documented transfer safeguards. Summaries of active vendors live in our internal registry, and we email redacted excerpts when enterprise buyers request them under NDA.
| Layer | Typical purpose | Opt-in? |
|---|---|---|
| Necessary | Security, consent string | No |
| Analytics | Funnel diagnostics | Yes |
| Marketing | Attribution | Yes |
Managing preferences after the first visit
Open the cookie modal by clearing localStorage keys beginning with nexvia_ and
refreshing, or email us to trigger a manual reset during support hours. Browser-level controls
remain available: Safari Intelligent Tracking Prevention, Firefox strict mode, and Chromium
third-party cookie deprecation experiments may change how long tags survive even after consent.
Blocking all cookies indiscriminately may hide contact forms or disable fraud checks, so consider site-specific exceptions if you need wholesale ordering.