Cookies nothing follows you without a yes

Two mechanisms run without asking, because they serve what you are actually using: the banner and the form. Neither one is there to track you.

Your cookie choice. When you answer the banner, your answer is kept in your browser's local storage, under the key kaiiza-cookie-consent. Technically that is not a cookie: nothing is sent to a server, the value never leaves your device. It holds your answer, the date, and the version number of this page. Without it, you would be asked again on every click.

The form's memory. On the project request page, the Tally form keeps your answers in progress and a session identifier in your browser, under its own domain name, so that you can pick up later where you left off. Tally adds a random identifier of its own. These are not cookies either, and your answers do not leave your device until you send the form. This data has no expiry date: it stays in your browser until it is cleared. This memory exists nowhere else on the site.

Until you accept, none of the tools that follow is loaded. This is not a setting that makes them discreet: the code is simply never downloaded, no request goes out to them, no cookie exists. If you decline, that stays true.

Google Tag Manager is the carrier: it loads the two tools below once you have agreed. It sets no cookie of its own.

Google Analytics 4 counts visits, their sources, the pages viewed, clicks on the main links and project requests successfully submitted. A marker valid for five minutes in the tab's memory lets the site count a request only once on arrival at the thank-you page; it is deleted after use or withdrawal of consent. It sets two cookies, “_ga” and “_ga_” followed by the site identifier, kept for two years by Google. No advertising feature is switched on: no Google signals, no remarketing, no user ID, no ad personalisation.

Microsoft Clarity records heatmaps and browsing sessions, which shows me where the site gets in your way. It sets “_clck”, kept for a year, and “_clsk”, kept for a day. While your tab stays open, it also keeps a tab identifier, “_cltk”, in your browser's session storage. Masking is set to “Strict” to hide page content in those recordings. The project request pages are excluded entirely: Clarity sees neither what you type in the form nor what you select. Data sharing with Microsoft Advertising is disabled for this site. Microsoft acts here as an independent data controller: the details are in the privacy policy.

What these tools never receive. Page addresses reach Google Analytics cleaned, without anything after the question mark or the hash. Only predefined source or campaign labels may be sent separately. No name, no email address, no phone number, no field content, no request identifier is passed on to them. Technical pages and the styleguide are excluded from consent-based measurement, except for the two thank-you pages used to count submitted requests in Google Analytics.

Declining has to be as quick as accepting, including after the fact. The link below reopens the banner: you answer again, and your new answer replaces the old one.

If you go from yes to no, the site blocks new data from being sent to Google Analytics and Clarity, deletes the measurement cookies it can access on kaiiza.ch and the tab memory used by Clarity, then reloads the page. It cannot delete any cookies stored for Google or Microsoft on their own domains: you can clear those in your browser settings. Cookie-free measurement is not affected: it sets nothing that would need deleting.

You can also clear everything from your browser's privacy settings. Your choice disappears along with the rest, and the banner will ask again on your next visit.