1. Contents
  2. Cookie policy

Filed with the privacy policy

The short version: one key is always set, because it remembers your answer. Everything that measures advertising waits for you to press Allow, and the footer has a button to take that back.

Printed pages squared in a cream card file on linen
Version 1.0, kept on file beside the privacy policy.

Xavriqon · xavriqon.com · Cookie policy

One cookie key is set without asking, and it only remembers your answer.

Version
1.0
Effective
October 6, 2026
Updated
October 6, 2026
Covers
xavriqon.com
§ 1

Three categories, and only one runs by default

A cookie policy for a site this size should be short. This one is. The xavriqon.com cookies and browser storage fall into three groups.

  • Strictly necessary. The key that stores your consent answer, and the chat token if you open the chat. Without the first, the banner would ask on every page. These run whatever you choose.
  • Analytics. Counting visits and which pages they reach. Held off by the analytics_storage signal until you allow it.
  • Advertising. Cookies set by Google Ads, Microsoft Advertising and Meta Ads to tell whether a paid click led to a letter. Held off by ad_storage until you allow it.

We set no cookie for profiling, retargeting lists, A/B tests or social sharing buttons. There are no social buttons.

§ 2

The storage table

Every name the site can write to your browser. Third-party durations are the platforms' published defaults; they can change them without telling us, and their own documents in § 7 are the final word.

Every row marked Advertising or Analytics stays unwritten until you press Allow.

§ 3

The ads that bring people here

This site runs paid advertising now. Google Ads, Microsoft Advertising and Meta Ads send clicks to it. Each platform adds a parameter to the address when you click: gclid from Google Ads, msclkid from Microsoft Advertising, fbclid from Meta Ads.

That parameter arrives in the address bar whether or not you accept cookies, because it is part of the link. What changes with your choice is whether it gets stored. Declined: we copy it only into the hidden source field of a form you choose to send, and nothing is written to your browser. Allowed: the platform's cookie in § 2 keeps it so a letter sent next week still counts.

§ 4

Consent Mode v2 and its four signals

The site uses Google consent mode, version 2. Before any tag loads, four signals are set to denied:

ad_storagedenied by default
ad_user_datadenied by default
ad_personalizationdenied by default
analytics_storagedenied by default

Press Allow and all four become granted. Press Decline, or later withdraw, and all four return to denied immediately, on the same page, without a reload. While denied, Google tags may send a cookieless ping that a page was viewed; they store nothing and cannot use the visit for personalised ads. A browser sending Global Privacy Control is treated as a decline and is never shown the question.

§ 5

Giving a choice, and changing it later

The banner appears at the foot of your first page. It does not cover the content and you can keep reading without answering. No answer counts as no. Your answer is kept for 6 months under site_consent_v2; then the banner asks once more.

To change your mind, use the Cookie settings button in the footer of every page, or the one below. It reopens the same two choices. Clearing this site's storage in your browser does the same job the long way.

§ 6

If you decline

Everything you came for keeps working: every page, the fit checker, the inquiry form, the chat. Your letter reaches us the same way and gets the same reply.

What stops: no advertising or analytics cookie is written, the four signals stay denied, and we lose the ability to tell which ad sent you unless you send a form. That is our problem, not yours. We will never hide content behind the banner or ask twice on the same visit.

§ 7

The platforms' own documents

Once a platform's cookie is set, that platform's own rules govern what it does with it.

How we handle what reaches our own inbox is in the privacy policy. The ground rules for using the site are in the terms of use.

§ 8

Asking about one cookie

If a name shows up in your browser that is not in § 2, tell us. It means a platform changed something and the table is out of date. Write to [email protected] with the cookie name, call +1 (378) 555-8712, or post a letter to 152 Oak Lane, Suite 4, Austin, Texas 33038, United States.

Xavriqon · Austin, Texas Cookie policy v1.0 · effective October 6, 2026