Cookies & storage
Each note beside this text names the exact cookie, who sets it and how long it lives.
Read straight down the main column for the policy itself, or check the margin next to any paragraph for the definition, date or cross-reference that goes with it.
This notice, dated
This cookie notice took effect on 14 September 2026, alongside the privacy policy it sits beside. Where the two disagree on a detail, this page is the authority for cookies and storage specifically, and the privacy policy is the authority for everything else.
Three categories, nothing hidden between them
Strictly necessary storage keeps the site itself working: it remembers your consent choice and, if you open the chat widget, the token that lets a conversation continue. This category runs regardless of your cookie choice, because without it the site can't function.
Analytics storage would measure how many visitors reach a page and where they came from. Advertising storage is what lets Google Ads, Microsoft Advertising and Meta Ads recognise that a click on one of their ads led to a visit here. Both of these stay off until you say otherwise.
What "off" actually means
Before you choose, no analytics or advertising cookie is written and no advertising identifier is stored locally. The click identifier may still arrive in the page URL because the ad platform put it there, but nothing on this site writes it to storage or forwards it anywhere until you allow storage.
The cookies and storage keys, by name
This is the complete list running on ziruqen.com. If a name isn't here, it isn't ours.
| Name | Set by | Purpose | Duration |
|---|---|---|---|
site_consent_v2 | Ziruqen (first party) | Stores your Allow / Decline choice for ad and analytics storage | 12 months |
| Chat token | Ziruqen (first party, in localStorage) | Lets you return to an open chat conversation | 18 months, matching the chat retention period |
_gcl_au / Google Ads storage | Google Ads | Links a click carrying gclid to a later visit, once allowed | Up to 90 days, set by Google |
| Microsoft Advertising click storage | Microsoft Advertising | Links a click carrying msclkid to a later visit, once allowed | Up to 30 days, set by Microsoft |
| Meta Ads pixel storage | Meta Ads, where a campaign runs | Links a click carrying fbclid to a later visit, once allowed | Up to 90 days, set by Meta |
What arrives in the link before any cookie is even set
When an ad on google ads sends someone here, the link usually carries gclid. A Microsoft Advertising link carries msclkid. A Meta Ads link carries fbclid. These identifiers arrive in the URL itself, independent of whether you've made a cookie choice yet — the choice you make governs whether this site is allowed to store or forward them, not whether the platform put them in the link.
These three identifiers are the only advertising click identifiers this site handles. There is no cross-network identifier beyond what each platform itself attaches.
Consent Mode v2, signal by signal
This site runs Google's consent mode with four signals — ad_storage, ad_user_data, ad_personalization and analytics_storage — and every one of them defaults to denied on first load, before you've touched the banner. Choosing "Allow" moves all four to granted. Choosing "Decline," or simply not choosing, leaves them denied.
If you allow storage and later change your mind, all four signals return to denied immediately — there's no lag where a withdrawn choice keeps running until a cookie happens to expire.
Where the choice lives, and how to change it
The banner at the bottom of every page offers "Allow" and "Decline" before any optional storage runs. Your answer is written to site_consent_v2 in your browser and applied immediately to the four Consent Mode signals above.
To change your mind later, open "Cookie choices" in the footer of any page. That reopens the same banner with your current choice shown, and a new choice takes effect the moment you make it — you don't need to clear your browser or find a separate settings page.
Declining costs you nothing the site itself needs
If you decline, the workshop still works exactly the same: you can browse every service page, run the job configurator, submit the inquiry form and use the chat widget. None of those depend on advertising or analytics storage. What stops is only the measurement that would otherwise tell us whether a specific Google Ads, Microsoft Advertising or Meta Ads click turned into an enquiry.
The cookie banner itself does not block the page while you decide — you can read, scroll and use the site with the choice left open, though optional storage stays denied until you actually choose "Allow."
Each platform's own document, not our summary of it
For how Google itself uses data once storage is allowed, see Google's own policy at policies.google.com. For Microsoft Advertising, see the Microsoft privacy statement at privacy.microsoft.com. Meta publishes its own cookie and data policy for Meta Ads directly on its own site. This page describes only what happens on ziruqen.com; each platform's document governs what happens once your data reaches them.
Questions about a specific cookie
If you want to know why a particular name showed up in your browser's storage inspector, email office@ziruqen.com or call +1 (429) 555-0256 and describe what you found. For everything else about your data, the full privacy policy covers collection, retention and your rights in detail; the warranty and refusal terms referenced elsewhere on this site are in the terms of service.