Cookies & ads policy
Nine numbered facts about every cookie, storage key and ad identifier this site uses.
QUEUE STUDIO runs paid traffic to this site from Google Ads and Microsoft Advertising today, with Meta Ads a live possibility. Everything that reads your browser or writes to it is numbered below, in order, with nothing folded into a general "we may use cookies" paragraph.
Last updated: September 14, 2026
When this notice took effect
This notice took effect on September 14, 2026 and describes the cookies, storage keys and advertising identifiers in use on siruhewu.com from that date. It's the only page on this site that names every ad platform, every click identifier and the full state of Consent Mode v2 in one place — the privacy policy and terms of service refer back to it rather than repeating it.
The three categories in use here
Strictly necessary storage keeps the site working: it remembers your cookie choice and, if you open it, your support chat token. It doesn't require your permission because the site can't function without it, and it's never used to build an advertising profile.
Analytics storage would let us measure how visitors move through the site in aggregate. Advertising storage lets Google Ads, Microsoft Advertising and, where a campaign runs there, Meta Ads recognise that a visit followed one of their ads and tie it back to that ad for billing and measurement. Both of these are optional, both are off by default, and both stay off until you say otherwise.
Every cookie and storage key, named
This is the complete list. Nothing else on this site reads or writes browser storage.
| Name | Set by | Purpose | Duration |
|---|---|---|---|
site_consent_v2 | siruhewu.com | Stores your allow or decline choice for optional storage so the banner doesn't ask again | 12 months |
| Chat token | siruhewu.com, in local storage | Reconnects you to an open support chat conversation after a reload | Until the conversation closes or 12 months, whichever comes first |
_gcl family | Google Ads | Carries the gclid click identifier so a conversion can be matched to the ad that produced it | Up to 90 days, only if you allow advertising storage |
MUID / _uetsid | Microsoft Advertising | Carries the msclkid click identifier for the same matching purpose | Up to 30 days, only if you allow advertising storage |
_fbp | Meta Ads, where a campaign runs there | Carries the fbclid click identifier for the same matching purpose | Up to 90 days, only if you allow advertising storage |
The platforms sending paid clicks here
Google Ads and Microsoft Advertising run traffic to this site right now. Meta Ads may. In their own lowercase technical documentation these appear as google ads, microsoft advertising and meta ads, and each one appends its own identifier to the end of the link a visitor clicks: gclid from Google Ads, msclkid from Microsoft Advertising, and fbclid from Meta Ads. If your link has one of those three strings in it, that's the platform reading which ad, keyword or placement sent you.
What Consent Mode v2 actually does
We run Google's consent mode, version two, on every page load, before any tag fires. Four signals sit inside it: ad_storage, ad_user_data, ad_personalization and analytics_storage. All four load denied. They only switch to granted the moment you press "Allow storage" on the banner below, and if you press "Decline," or later change your mind, all four go straight back to denied — not at the end of the visit, immediately.
| Signal | Before a choice | After "Allow" | After "Decline" |
|---|---|---|---|
ad_storage | Denied | Granted | Denied |
ad_user_data | Denied | Granted | Denied |
ad_personalization | Denied | Granted | Denied |
analytics_storage | Denied | Granted | Denied |
How you give or change that choice
The banner fixed to the bottom of the frame on your first visit gives you two buttons: "Allow storage" and "Decline." Whichever you press writes site_consent_v2 and sets the four consent mode signals to match. To change your mind later, open "Cookie settings" in the footer legal row at the bottom of any page — it reopens the same choice, and your new answer overwrites the old one immediately.
Change your storage choice now
Checking your current choice…
What happens if you decline
The site itself doesn't change. Every page loads, the tabs on the homepage switch, the Drop & Loadout Lab runs, and the inquiry form and support chat still work — none of that depends on advertising or analytics storage. What stops is the connection between your visit and any ad click that brought you here: Google Ads, Microsoft Advertising and Meta Ads keep the four consent mode signals denied, so they can't tie a conversion back to a specific ad, keyword or audience, and no advertising or analytics cookie gets written to your browser.
The platforms' own documents
Each advertising platform publishes its own account of how it handles data once a signal reaches it, separate from what we control on this page. Google's practices for Google Ads are described at policies.google.com/privacy. Microsoft Advertising's handling is described in the Microsoft privacy statement at privacy.microsoft.com/privacystatement. Meta's is described in its own data policy, published on Meta's own site. None of these platforms has reviewed or approved siruhewu.com; these links describe their handling of the data our site sends them, nothing more.
Ask about a specific cookie
If a browser extension flags a specific name from the table above, or you want to know why a particular request fired on a particular page, write to office@siruhewu.com with the name and the page, or call +1 (776) 555-5853. We can trace it against the list above faster than a generic privacy inbox can.