Scope and definitions
Throughout this text, the words we and us mean Xolvarynyzei, the operator of xolvarynyzei.world. A cookie is a small text file stored in your browser; similar storage can include localStorage, sessionStorage, and comparable mechanisms used for the same purposes as a cookie when they store or read a label that identifies a browser or the choices you have made. This page does not list every sub-request your browser may make to third parties; it focuses on the categories of storage you can influence through the consent interface.
Strictly necessary storage
Some storage is used only so the site can load, remember that you have already seen the cookie layer, and store your current consent string in a way that the next page can read. Without this, you would be prompted on every view and some layout preferences could not be applied consistently. In many jurisdictions, this category does not require opt-in in the same way as analytics or marketing, but we still describe it here for transparency. Technically, this can be implemented with a short-lived cookie, with localStorage keyed to our domain, or a combination, depending on the browser and our deployment at the time you read this page.
What it supports
Routing you to the correct host, keeping HTTPS behaviour predictable, and letting the site know whether to show the large consent strip or a compact link to “Cookie settings” after you have decided.
What it is not for
Profiling for unrelated advertising, selling lists of people who visited swim pages, or long-term individual tracking outside what you can switch off in the same consent layer for optional categories.
Optional analytics
If you enable analytics, we aim to work with tools that group activity into pages and sessions rather than building dossiers. Typical outcomes include an approximate count of how many devices opened a page, which links are used most, and how often errors occur, so we can improve wording and catch broken paths. The vendor may set or read a technical identifier. You can turn this category off at any time in Cookie settings; the change is stored so your browser does not re-enable it silently. Where a product cannot fully respect the switch, we will prefer suppliers who document known limitations in their own materials.
Optional marketing
When marketing is on, a label may be stored so that we can measure or personalise our own campaigns: for example remarketing, conversion counting after you click a Google Ad, or similar tools from reputable vendors—always in line with the privacy policy and, where the law requires it, with your prior consent. Those vendors may set or read their own cookies or work with browser signals; their documentation describes retention and your opt-out options beyond this site. If you leave marketing off, we do not use that browser-stored label for on-site ad measurement that depends on the consent layer, though you may still see generic ads elsewhere that are not based on a tag we set here. A separate future email list, if we add one, will have its own sign-up text.
Duration and storage location
Consent records written through the banner are expected to last until you clear data for the site, replace the device, or use a private browsing mode that discards them at the end of a session, whichever happens first. Analytics tools may refresh their identifiers on a schedule defined in their own documentation, often in the order of months. We do not set multi-year “evercookie”-style storage for optional categories. If you want a full reset, use your browser’s “clear data for this site” feature and, if needed, contact us so we can confirm what we can see on the server side for forms you have submitted before.
Third parties and iframes
Embedded video, map tiles, or font delivery can cause your browser to contact other domains. Whether those third parties set additional cookies is governed by their policies. Where we can choose embed modes that do not set unnecessary trackers, we prefer them, but the choice is not always visible to a visitor. If you are reading this as part of a compliance review, feel free to include an inventory request through the Rødovre mailbox with the date you tested.
Your tools beyond this site
- Global Privacy Control and similar “do not track” signals, where a browser or extension sends them, may be read by tools we add in a future version of the stack; the consent layer is still the primary way to set categories for this site today.
- Operating-system-level privacy options can limit cross-app identifiers; we cannot see those from a normal web page, but we respect that they affect what vendors receive.
- Reader mode and script blockers can change which tags run; the site is built so core policy text still reads without optional scripts.
Children, schools, and shared devices
If a device is shared in a home or classroom, a consent choice on your profile may affect everyone using that profile until you clear it. We do not run child-directed services through this static site, but if you are supervising younger visitors, consider using separate browser profiles and reviewing site data together after each session that involves account-style actions.
Updates to this text
When we materially change the categories, we will move the “hero” information forward by updating the page and, where the law expects it, the banner. The date in the band at the top of this file is set automatically in your browser so you can tell which calendar day you are viewing the policy, not a hidden server-only stamp.
Contact and related documents
Postal address: Rødovre Centrum 1, 2610 Rødovre, Denmark. Phone: +45 70 20 85 05. Email: ask@xolvarynyzei.world. The privacy policy deals with the content of contact forms, ordinary correspondence, and records we keep in systems outside the browser. The terms of use set rules for how you may link to, copy from, and rely on this website text.