This policy explains how Plyxarongrwhron (the “site” at plyxarongrwhron.world, referred to as “we” or “us”) deploys HTTP cookies, browser storage, and similar technologies, and the controls available to you. The drafting style follows layered disclosure patterns familiar to teams working under the EU ePrivacy framework and the Dutch Autoriteit Persoonsgegevens guidance, while also staying legible in New Zealand and the United Kingdom.
Scope and who this is for
The policy covers visitors, prospective clients, journalists, and partners who browse public pages, complete forms, or adjust consent on this property. It does not replace a signed data processing addendum with your employer; that instrument, when it exists, sits beside this document and the privacy policy. If you access the site on behalf of a public authority, the same rights apply, but you may have additional log retention rules on your own side; we do not know those from here.
What counts as a cookie or a sister technology
In everyday language, a cookie is a small file written by a website into your browser. It can be short-lived and cleared when the browser closes, or it can last longer, depending on the attributes the server sets. Local storage and session storage are larger pockets inside the same browser. We currently prefer local storage to remember the consent you gave to optional categories because it allows us to avoid re-rendering a modal on every subpage while still keeping the data under your own device control first. If a future build switches to a signed server-side cookie, we will update the storage map below.
Our public scripts do not attempt to read unrelated sites’ cookies. When third-party content such as a font CDN loads, that vendor may set its own technical cookies; we list the CDNs in the terms of use materials where relevant.
How consent is requested and recorded
When you first load the site, a banner at the base of the viewport
explains that optional tools exist. You can reject everything
optional in one tap, accept everything in another, or open granular
settings. None of the optional features fire before you make a
choice, except the strictly necessary items described in the next
section. After you pick, we save a small JSON object in
localStorage under a key that includes a version string
so we can prompt you again when categories change. Rejecting
optional categories does not change how contact forms are delivered;
it only affects analytics-like measurement and marketing-style
pixels we might enable later.
Strictly necessary
These mechanisms keep the site usable and aligned with the security model we adopt on the day you visit. They include, but are not limited to, remembering that a consent object exists (to prevent infinite loops of prompts), persisting a CSRF or anti-spam token for forms, and, where a reverse proxy is present, a short correlation identifier that helps the infrastructure reject abusive traffic. You cannot disable these through our on-page switchboard without side effects, because the page would not know whether you are a returning visitor, whether to trust a submission, or how to line up a session across tabs.
Analytics (optional)
When you enable analytics, we or a sub-processor we contract with may place first-party or third-party cookies that help us see, in aggregate, which sections are read, how long pages stay open, and whether navigation paths look broken. We configure such tools, where possible, to shorten IP fields and to turn off ad-related features. You can read more about the underlying agreements in the privacy statement’s processor annex when we publish one.
Marketing (optional)
Marketing technology might measure whether a campaign link led to a visit. We do not mix that signal with a contact form submission in an automated “lead score” for individuals on this site, because that would expand the story beyond what a simple brochure should do. If we ever do partner retargeting, the banner and this text will be revised first.
Retention and your reset rights
Browser-stored objects remain until you remove them, until we change the key name as part of a release, or until the browser vendor evicts the space under its own heuristics. If you are on a shared machine, you should use a fresh profile, incognito mode, or your organisation’s group policy to clear site data after each session. For EU and EEA data subjects, you may also complain to a supervisory authority; for Dutch visitors the Autoriteit Persoonsgegevens is a practical port of call, and for Aotearoa the Office of the Privacy Commissioner can discuss concerns about our handling once you have first tried a direct message.
Want a clean slate? In Chromium-based browsers, open “Clear browsing data,” choose a time range that includes this domain, and tick “Cookies and other site data” and “Site settings.” Safari and Firefox have parallel menus under privacy tabs.
Cross-border placement of scripts
Even when no personal data is clearly typed into a form, the mere connection of your browser to a content delivery node may produce server logs. Those logs, when they sit on a machine in another country, are discussed under international transfers in the privacy policy, including Standard Contractual Clauses or comparable instruments when we work with EEA, UK, or Swiss expectations.
Children and shared devices
The site is not directed to children, and the consent tool assumes an adult user. If a minor uses a guardian’s device, the guardian is responsible for clearing data or rejecting optional categories before hand-off.
Changes to this policy
We adjust this page when the law changes, when we add a processor, or when we retune how storage keys are named. The hero section always displays today’s long-form date in your browser, which helps you see when you are reading, even before we publish a detailed change log. Material changes to optional categories will generally trigger a new prompt.