Plixernoaequezl

What we mean by “cookie” on this page

We use the term for first-party and third-party HTTP cookies, HTML5 local storage keys, and similar technologies (such as session storage) that can persist on your device after a visit. The policy covers how we use them together with the in-page cookie consent module. Some browsers already phase out third-party cookies; where that is true, we will note when a function moves to a first-party or server-side alternative.

The three permission buckets in the banner

Strictly necessary items let the site store that you have answered the notice and what version of the choices you saw. They also remember your rejection of optional categories, so the banner is not a recurring interruption every fresh tab. This bucket cannot be turned off here because disabling it at the product level would mean the consent system itself has nothing to read against.

Analytics, if you allow it, may include session length, page addresses, and coarse geography derived from the IP, depending on the vendor. We do not set out to use these tools to single out a named person, but a vendor may be capable of more granular reporting if you log into their other products—please review their file if you are logged in elsewhere on the same device.

Marketing, if you allow it, may load pixels or tags that help us or an agency measure an ad you clicked, attribute a form completion, or cap how often a creative is shown. You can browse without it; some partner pages you reach after leaving the site will have their own notices.

Why we prefer local storage for the banner state

Our static deployment stores your consent JSON under a versioned key in local storage so a server round trip is not required. When we publish a material change to the categories or a new vendor, we can bump a version flag so you see the banner again even if a raw date check would miss it. The key name does not include your name; it is a site-wide flag.

How long they live

Strictly necessary storage lasts until you clear it or we ship a new version string that overwrites the object. Optional files created by a vendor can range from a short session to many months, depending on that vendor’s configuration; we will request lean defaults when we can. When an analytics or marketing file expires, it may reappear on the next page load if you still have consent active—at that point it is a fresh file with a new clock.

Who else might read a token

We may in the future work with a processor to host a script that sets its own file under the processor’s domain, subject to a data processing addendum. The Privacy policy lists the categories of recipients we work with, even when the exact product name is not on this static site today. The consent choice you set here is what our JavaScript is written to respect before a third tag is even inserted.

Practical things you can do

Use Reject to keep the minimum footprint, or Cookie settings to uncheck just one optional column. In parallel, you can use your browser’s “clear site data” for this domain, block third parties globally, or install an extension that enforces a list you trust. In some mobile environments, a system-level limit on cross-app tracking also reduces what partners see.

“Do not track” and industry signals

Old “Do not track” headers are not a uniform legal standard, and this site does not change behavior on that header alone. In regions that define an opt-out of sale or sharing, we will align that signal with the tools available from regulators when and if we operate covered advertising, as also described in the privacy file.

When we refresh this list

We will edit this text when a new class of technology appears (for example, first-party data clean rooms) or when the banner gains another toggle. A meaningful change will also be reflected in a short in-product notice the next time you are prompted or when you return after a storage reset, so you are not bound by terms you have not been given a clean chance to read.