Legal
Cookie Policy
What sets a cookie or a storage key on this site, why, and what happens if you say no.
Effective September 24, 2026
Vexnaros · vexnaros.comRead alongside the privacy policy
Effective date. This cookie notice took effect on September 24, 2026, and covers every cookie or storage key vexnaros.com is capable of setting from that date forward. Check back here if the list of ad platforms running on the site ever changes — that is where an update would show first.
Three categories. This site sets or reads cookies and browser storage in three groups: strictly necessary, analytics, and advertising. Strictly necessary storage keeps the site and the chat widget working — it holds your consent choice and, if you open the chat widget, the conversation token, and it does not require your permission because the site cannot function without it. Analytics storage measures which pages get read and where a visitor came from, in aggregate, and it does not run until you allow it. Advertising storage is what lets Google Ads, Microsoft Advertising and, where a campaign runs there, Meta Ads recognize that a visit followed one of their ads, and it also waits for your permission.
The table. Below is every cookie or storage key this site is capable of setting, what sets it, what it does, and how long it lasts. A key marked advertising or analytics is never written until you press Allow in the banner.
| Name | Set by | Purpose | Duration |
|---|---|---|---|
site_consent_v2 | Vexnaros (necessary) | Stores your allow or decline choice for analytics and advertising storage | 6 months |
chat_token | Vexnaros (necessary) | Reconnects your browser to an open support chat conversation | Until the conversation is closed or 18 months, whichever comes first |
_ga, _ga_* | Google Analytics | Distinguishes visitors for aggregate traffic measurement | Up to 13 months |
_gcl_au | Google Ads | Links a gclid click to a later inquiry for ad measurement | Up to 90 days |
MUID | Microsoft Advertising | Links an msclkid click to a later inquiry for ad measurement | Up to 13 months |
_fbp | Meta Ads | Links an fbclid click to a later inquiry, where a Meta campaign runs | Up to 90 days |
The click identifiers. When a visitor arrives from a paid ad, the platform that served the ad usually attaches an identifier to the link: gclid for a Google Ads click, msclkid for a Microsoft Advertising click, and fbclid for a Meta Ads click. Each identifier lets the sending platform match that specific click to the ad that produced it, so it can report whether the click led anywhere and, once storage is allowed, refine who else sees the ad.
Consent mode. This site runs Google's Consent Mode v2. Four signals — ad_storage, ad_user_data, ad_personalization and analytics_storage — start denied for every visitor and stay denied until the visitor presses Allow in the cookie banner. Once allowed, the advertising and analytics cookies in the table above are permitted to write. If a visitor later declines or withdraws that choice, all four signals return to denied immediately.
Giving or changing consent. The banner appears on first visit with two buttons: Allow and Decline. Pressing Allow sets all four Consent Mode v2 signals to granted and lets the analytics and advertising cookies above write. Pressing Decline keeps them denied and only the necessary cookies run. You can change that choice at any time using the "Cookie settings" link in the footer of every page, which reopens the same banner.
If you decline. The site works fully without analytics or advertising storage — you can browse the catalogue, use the lookup tool, open the chat widget and submit an inquiry with nothing beyond the necessary cookies in place. What stops is measurement: we can't tell which page or which ad led to your visit, and Google, Microsoft and Meta receive no advertising identifier tied to that visit.
Reading the platforms' own terms. Google's cookie and advertising practices are documented at policies.google.com. Microsoft Advertising's handling of the msclkid identifier and related data is documented in the Microsoft privacy statement at privacy.microsoft.com. Meta's cookie use, where a campaign runs there, is documented in Meta's own cookie policy, linked from its advertising help center.
Questions about a specific cookie. Write to [email protected] naming the cookie or the page you were on, and we'll answer directly rather than pointing you back to this page. The full data categories, retention periods and legal bases behind this cookie policy are set out in the privacy policy.
Your current choice is stored under site_consent_v2 in this browser for six months. Change it any time — it takes effect immediately, on this device.
What Consent Mode v2 is holding right now
Reflects your last saved choice on this device
- ad_storage
- Denied until you press Allow; controls whether an advertising cookie can be written.
- ad_user_data
- Denied until you press Allow; controls whether click data is sent to an ad platform.
- ad_personalization
- Denied until you press Allow; controls whether an ad platform can use your visit to personalize ads shown elsewhere.
- analytics_storage
- Denied until you press Allow; controls whether an analytics cookie can measure this visit.