Basics and vocabulary
When this policy refers to “cookies,” it also includes similar technology such as local storage and session storage entries, unless a distinction matters for a particular feature. Some items are set by us through our own code; others, such as an analytics or advertising script, are set by a partner and read only if you have agreed to that category in the banner or settings box.
Strictly necessary items support core functions. They are not used to build a marketing profile. Optional analytics may help us understand which sections are read most often. Optional marketing may help us show relevant reminders about our own services, not about unrelated industries, and only where we later adopt such a tool in line with this policy.
What we store in practice on this build
On the current public site, the consent system writes a small JSON string to localStorage under a single key, containing flags for necessary (always on), optional analytics, optional marketing, and an update timestamp. That record does not include your name, email, or the content of a contact form.
If you choose “Accept All” or you enable a category in settings and press save, the corresponding flag is set to true. If you choose “Reject,” those optional flags are false. You can re-open the cookie panel at any time from the banner area when it reappears after a change, or by clearing site data in your browser and revisiting, which will show the notice again for a new decision.
The following table is a high-level map. Technology names are indicative and may be replaced by equivalent services over time, in which case we will update the technical documentation here.
| Category | Storage type | Role |
|---|---|---|
| Strictly necessary | localStorage, session, or a minimal session identifier | Remembers that you have answered the banner, loads forms safely, and keeps UI states aligned with server expectations. |
| Analytics (optional) | first-party and, if added later, well-known analytics cookies | Aggregated statistics about page views, scroll depth, and referrers. We prefer anonymised or aggregated data where possible. |
| Marketing (optional) | rare, first-party, if a campaign is active | Helps us avoid repeatedly showing the same studio announcement if you have already read it. |
Why optional categories need your choice
Where the GDPR or UK GDPR applies, we rely on consent for non-essential reading or writing in your browser, except where a narrow exception applies, such as an audience measurement with appropriate safeguards in some member states. Where New Zealand’s Privacy Act 2020 and related guidance are relevant, we still treat transparent choice as a practical baseline even when a strict cookie rule differs.
How you can change or erase choices
Use the “Cookie Settings” action on the banner or equivalent control when present. The toggles in the small dialog are described in the same order here: necessary always on, analytics, marketing. Saving writes the updated object to the same key in localStorage. You can also remove all data for the site from your browser settings, which will feel like a first visit the next time you land here.
Using a private or incognito window usually starts without our prior record, so you can test a clean consent state. If you use multiple browsers, each has its own storage, which is why your choice on a laptop may not be reflected on a tablet until you set it there too.
Retention and scope
Consent data persists until you delete it, replace it, or we ship a new key name as part of a site upgrade, in which case you may be asked to confirm your preferences again. We do not attempt to re-create deleted consent records from backup logs in a way that would undermine your action without a good-faith system reason such as a security investigation.
Contact and related policies
Questions about this page can be sent to: Xolvarynkhim, Shop 3, Coastlands Shopping Town, 150 Rimu Road, Paraparaumu 5032, New Zealand. Email: contact@xolvarynkhim.world. Phone: +64 4 297 2022. A broader view of how we use personal data appears in the privacy policy, which this cookie policy is designed to work alongside, not to replace.