1. What we mean by “cookies”
In a narrow technical sense, a cookie is a text string that a site asks your browser to return on later requests to the same host or, in some cases, a partner that uses the same advertising framework. In the broader way regulators use the word, the label also includes local storage, session storage, and pixel tags that store or read a small ID to recognise a browser. For simplicity, we call the whole set “cookies and similar technologies” on this page.
2. Types of storage on this site
We split storage into (a) first party—set when you are clearly visiting our domain, and (b) third party—set when a script loaded from a vendor domain runs in your page context. A font delivery network, for example, may see connection metadata even when it does not set a long-lived cookie, because the browser still opens the network call. The Privacy Policy already explains how we select vendors; this page is about the choices the banner can flip.
First party
Typically includes consent state, a session flag if we use one, and sometimes a test flag for layout experiments when you have opted in.
Third party, optional
May include a vendor’s ID for site analytics, or a marketing network’s light remarketing tag, only if you have chosen that combined category in settings.
3. How the consent banner works
On a first visit, you should see a bar with three high-level actions: Accept All, Reject (necessary only), and Cookie Settings. Accept All turns on the optional analytics and marketing category as well; Reject leaves only what is truly needed to run the public pages; Cookie Settings lets you read the one-line descriptions and use a single toggle for the optional bucket before you save. Save choices record your response in a way that the front end can read on the next page load, so the banner does not flash on every visit.
4. Strictly necessary items
These include the string that encodes the fact you answered the banner, your yes-or-no to optional features, a timestamp, and, when our stack uses it, a short-lived key that allows the secure session to work or prevents cross-site request forgery on any interactive form on our origin. Necessary does not include marketing pixels that could wait for a separate decision, even if a vendor’s marketing product tries to tell you otherwise. You cannot switch necessary items off from our UI without breaking basic navigation, which is why the toggle in the interface is read-only in that row.
5. Optional analytics and marketing
When you allow this group, a vendor we choose may set or read a pseudonymous id to help us know how many people load a long article, whether the mobile and desktop experience both feel stable, and whether a campaign that links to this site brings readers who at least look at a second page. We configure tools to avoid where possible the collection of contact fields you typed into a form, and to disable features that are clearly disproportionate to that goal. You may still see aggregate reporting in a dashboard that we could not re-identify to a single named person even if we wanted to, because the vendor designed it that way.
6. Third parties and their documents
We aim to work with vendors that publish a clear subprocessor or cookie list, maintain HTTPS for their endpoints, and support regional settings where the law says they must. If you need the exact name of a tag we turned on, email us and we will point you to the public documentation we relied on. We do not pick vendors solely because their logo looks familiar; we do check whether their contract and technical posture are compatible with a small business site.
7. How long data may stay on your device
Session cookies are deleted when you close the browser, unless a vendor labels something “session” in name only while actually using a long identifier—when we see that, we reconfigure. Persistent first-party values we control usually use modest lifetimes, often a few months, after which a fresh consent pass may be needed if the law in your place requires renewed clarity. Vendors’ own “maximum lifetime” may be longer; we can delete our relationship with a vendor, but the fastest way to clear a stubborn ID is still your own browser’s storage panel.
8. How to change your mind in the browser
Every major browser can block all cookies, only third-party ones, or let you set exceptions per site. You can also clear storage for chraxelloazlaia.world only, which is gentler than a “clear everything on all sites” day-one reset. After a wipe, the banner is likely to return because the consent memory was removed—this is expected, not a bug. Our Contact form still works, because necessary transport does not need marketing tags.
9. “Do not track” and global privacy signals
Some browsers send a DNT or similar opt-out signal. The industry has not standardised a single response to that header across every jurisdiction. We treat it as a hint: if your browser and local law line up, we will map it, where we reasonably can, to the same off state as Rejecting optional cookies on first load. A conflict between the banner’s saved choice and a later global signal is resolved in favour of the stricter, more privacy-protective setting once we are aware of both.
10. Updates to this text
When a vendor or browser behaviour changes, we will edit this file and leave the as viewed on line in the hero to track the day you loaded the page. The line uses your device clock; if the clock is wrong, the printed date is wrong, so prefer the canonical address to confirm you have the right copy.