Section 01 — Effective date

This cookie notice took effect on 14 September 2026 and covers every cookie and browser storage key set by murevix.com from that date on.

Section 02 — The three categories in use

Strictly necessary storage keeps the site working — it holds your consent choice and nothing else, and it runs whether or not you allow anything. Analytics storage, used only after you allow it, helps us see which pages get read. Advertising storage, also only after you allow it, carries the click identifiers described below so a paid campaign can be measured against the inquiries it produces.

Section 03 — The cookies and storage keys themselves

This is the complete list. Nothing on this site sets a cookie that isn't in this table.

Cookies and local storage keys set by murevix.com
Name	Set by	Purpose	Duration
site_consent_v2	Murevix, first-party	Stores your allow/decline choice for analytics and advertising storage	12 months
chat_token	Murevix, first-party, localStorage	Keeps the support chat conversation attached to your browser so it can be reopened	Until you clear browser storage
_gcl_aw / gclid parameter	Google Ads	Attaches a Google Ads click to later activity on the site, once allowed	Up to 90 days
MUID / msclkid parameter	Microsoft Advertising	Attaches a Microsoft Advertising click to later activity on the site, once allowed	Up to 13 months
_fbp / fbclid parameter	Meta Ads	Attaches a Meta Ads click to later activity on the site, where a campaign is running, once allowed	Up to 90 days

Section 04 — Advertising platforms and their click identifiers

Google Ads sends traffic to this site and attaches gclid to the landing URL of a click. Microsoft Advertising attaches msclkid the same way. Meta Ads, where a campaign is active, attaches fbclid. Each identifier only gets written to storage once you allow it — before that, the parameter may pass through the URL but nothing on this site persists it.

gclidmsclkidfbclid

Section 05 — Consent Mode v2

Consent mode governs four signals: ad_storage, ad_user_data, ad_personalization and analytics_storage. All four load denied by default, before you've made any choice. Clicking allow in the banner below sets all four to granted. Clicking decline, or changing your mind later, sets all four straight back to denied.

Section 06 — How consent is given, and how to change it

A banner offers Allow and Decline the first time you visit. Whichever you choose is written to site_consent_v2 and Consent Mode v2 is updated to match. To change your mind afterward, use the "Cookie settings" control in the footer of every page — it reopens the same choice and rewrites the same signals, whether that means granting storage you'd previously declined or withdrawing storage you'd previously allowed.

Section 07 — What happens if you decline

The site itself works exactly the same either way — every page renders, the inquiry form still posts to submit.php, and the support chat still connects. What stops is measurement: no analytics storage is written, and no gclid, msclkid or fbclid is retained, so a campaign that brought you here has no way to see that an inquiry followed. Declining costs you nothing on this site; it only limits what the ad platforms can see.

Section 08 — Where the platforms document their own handling

Each advertising platform publishes its own account of what it does with an identifier once it receives one. Google's practices are documented at policies.google.com. Microsoft Advertising's are documented at privacy.microsoft.com. Read either alongside this page if you want the platform's side of the exchange rather than ours.

Section 09 — Asking about a specific cookie

If you want to ask about anything in the table above, or dispute what's stored under your visit, email office@murevix.com or call +1 (561) 555-9478. For the fuller picture of retention periods and legal bases, see the privacy policy.

Nine things this site stores in your browser, numbered plainly.