Tracker registry & ePrivacy alignment

Cookie Policy

This policy unpacks how Movira domains deploy cookies, pixels, and comparable storage. It pairs with the privacy notice and the interactive preference center surfaced through the floating consent module. Document version below refreshes whenever categories or vendors change in a meaningful way.

As published on

1. What counts as a cookie here

We use the term to cover HTTP cookies, HTML local storage, session storage, service-worker caches that store identifiers, and pixel tags that write browser storage indirectly. Scripts execute only after you opt in through the relevant category except for strictly necessary items.

Controller: Xexvalonuequidza.world, Lijnbaan 140, 3012 ER Rotterdam, Netherlands · chat@xexvalonuequidza.world

2. Strictly necessary storage

These technologies keep the site stable: load-balancer affinity, bot mitigation tokens, CSRF protection, authenticated staff sessions, fraud heuristics, consent string persistence, and accessibility preferences such as reduced motion where stored locally.

They do not track you across unrelated brands and cannot be switched off without breaking checkout flows.

3. Analytics cohort (opt-in)

With consent, we may activate first-party measurement scripts or privacy-oriented analytics partners to understand scroll depth, navigation funnels, and error rates. IP addresses may be truncated before storage.

What we learn

Aggregated counts, dwell bands, and device class breakdowns without persistent individual profiling.

What we avoid

Sharing raw clickstreams with behavioural ad networks unless marketing consent also applies.

4. Marketing cohort (opt-in)

Upon approval, ad partners can sync pseudonymous identifiers to attribute campaigns, build suppression lists, sequence creative rotation, or measure incremental reach. Frequency caps reduce redundant impressions.

You may withdraw consent granularly; partners must honour revocations within their documented service-level objectives.

5. Browser storage beyond cookies

Local storage holds compressed consent snapshots for sixty days to prevent redundant banners. Service workers may prefetch static assets; they do not store personal data unless analytics toggles explicitly require it.

6. Typical lifetimes

Session cookies: deleted when the browser closes unless labeled persistent below.
Analytics identifiers: thirteen months or vendor default if shorter.
Remarketing tags: up to twenty-four months with automated pruning.

Vendors publish dynamic tables; request the latest export through privacy contact if you need exact names per domain.

7. Managing preferences

Use the Cookie settings button on the banner or reopen the modal through browser developer shortcuts we document in FAQs. Browser-level blockers remain compatible though they may hide non-essential modules altogether.

Accept all: enables analytics and marketing where available.

Reject: leaves only essential storage active.

Save choices: mirrors granular switches inside the modal.

8. Third-party interplay

Some embeds (maps, video hosts) attempt to set their own cookies. We lazy-load those components behind consent gates or replace them with static fallbacks on denied states.

9. Review cadence

Security reviews this text quarterly or after any major vendor swap. The dated banner at the top reflects the last holistic editorial pass.

10. Questions

Email chat@xexvalonuequidza.world with “Cookie Policy” in the subject for traceability.