Cookie policy and storage consent framework
This document outlines how Zavalorin employs browser storage, telemetry variables, and advertising parameters under Google Consent Mode v2 for our Denver reference practice.
When does this cookie policy take effect?
This Cookie Policy took effect on October 16, 2026. It provides a detailed explanation of how cookies, local web storage keys, session tokens, and network telemetry parameters operate across zavalorin.com.
We operate as an independent medical reference desk in Denver, Colorado. Our digital property delivers drug monographs, patient educational articles, and pharmaceutical reference specifications. We employ tracking technologies strictly to sustain web security, preserve user communication sessions, and measure the effectiveness of our paid search ad placements.
What tracking and storage categories do we employ?
We categorize storage mechanisms into three distinct classifications based on functional necessity:
Strictly Necessary Storage
Essential for delivering basic web services, security enforcement, and state persistence. This category includes our consent persistence key (site_consent_v2), anti-CSRF protection tokens, render verification timestamps (tm), and live chat session keys (chat_token). These keys cannot be turned off as the website cannot operate safely without them.
Analytics & Measurement Telemetry
Used to understand how visitors engage with our pharmaceutical guides, which reference monographs are consulted, and whether navigation links function properly. Under Consent Mode v2, analytics storage remains completely locked until the visitor grants explicit affirmative consent.
Advertising & Attribution Trackers
Appended to URLs when visitors arrive from promotional campaigns across Google Ads, Microsoft Advertising, and Meta Ads. These cookies and URL query strings correlate specific search queries and campaign placements with quote submissions, verifying that our ad budget is directed to legitimate healthcare editorial queries.
What specific cookies and storage keys are stored?
The following table enumerates all first-party and third-party storage tokens, local cache identifiers, and tracking variables utilized across our Denver editorial platform:
| Identifier / Key | Origin / Provider | Category | Technical Purpose | Retention Duration |
|---|---|---|---|---|
site_consent_v2 |
First-party (Zavalorin) | Necessary | Stores the visitor's Consent Mode v2 choice (granted/denied) and timestamp | 12 months |
chat_token |
First-party LocalStorage | Necessary | Maintains conversation state and thread continuity with the Denver desk | 6 months |
tm |
First-party (Hidden Form Token) | Necessary | Unix timestamp verifying render time against bot speed heuristics | Single transmission |
_ga, _ga_* |
Google LLC / Google Ads | Analytics | Distinguishes unique sessions and aggregates monograph page views | Up to 24 months (only if granted) |
_gcl_au, gclid |
Google LLC / Google Ads | Advertising | Stores campaign click attribution parameter for Google Ads network | 90 days (only if granted) |
_uetmsclkid, msclkid |
Microsoft Advertising | Advertising | Records Microsoft Advertising click identifier for conversion analysis | 90 days (only if granted) |
_fbp, fbclid |
Meta Platforms, Inc. | Advertising | Stores Meta Ads attribution parameter for editorial traffic campaigns | 90 days (only if granted) |
Note: No payment gateway tokens, cardholder caches, or customer profile authentication cookies exist on this site.
Which advertising platforms append click identifiers?
Zavalorin actively runs paid search and display campaigns on commercial ad networks to connect healthcare platforms and specialty clinics with our reference monograph service. When an ad link is clicked, the following parameters are appended to our URLs:
-
google ads: Appends the
gclid(Google Click Identifier) parameter to inbound requests. This string conveys campaign and keyword attribution directly to Google's conversion tracking servers. -
Microsoft Advertising: Appends the
msclkid(Microsoft Click Identifier) parameter to evaluate search query intent and track quotation form completions. -
Meta Ads: Appends the
fbclidparameter when traffic originates from Meta ad placements.
These identifiers are parsed solely to evaluate acquisition efficiency and refine landing page content. Neither Google, Microsoft, nor Meta has reviewed, approved, or certified our medical reference publications or pricing.
How does Google Consent Mode v2 manage tracking variables?
Our website implements Google Consent Mode v2 (consent mode) as its primary data governance protocol. When any page on zavalorin.com loads, four statutory consent variables are immediately initialized to a default denied state before third-party libraries can execute:
Core Consent Signals
ad_storage: Denied by default; controls local advertising cookie writes.ad_user_data: Denied by default; controls sending personal data to advertising services.ad_personalization: Denied by default; prevents personalized retargeting profiles.analytics_storage: Denied by default; blocks analytics storage tokens and visit modeling.
State Modification Engine
When a user selects "Allow Storage", our client script issues an update command transitioning all four signals to granted. Conversely, if "Decline Non-Essential" is selected, or if consent is revoked later, ad_storage, ad_user_data, ad_personalization, and analytics_storage are instantly locked back to denied.
How do you grant, modify, or revoke your consent?
You hold total control over your storage choices on this website:
Upon your initial visit, a docked consent banner appears at the bottom of the viewport presenting two explicit options: "Allow Storage" and "Decline Non-Essential". Making a choice immediately registers your decision under the site_consent_v2 key for 12 months.
You can change your mind at any moment. Every page of this website carries a persistent "Cookie Settings" button in the footer legal bar. Clicking this button reopens the consent banner instantly, allowing you to switch between granted and denied configurations with immediate effect. Additionally, if your browser transmits the Global Privacy Control header, our site automatically enforces an opt-out state.
What happens if you refuse or decline storage?
If you click "Decline Non-Essential" or enable browser-level cookie blocking:
- What continues to function flawlessly: You retain full access to all pharmaceutical reference guides, patient instruction articles, pricing rate cards, the interactive Per-Unit Price Estimator, the editorial standards dossier, and our direct scope inquiry form. You can read every monograph without penalty.
- What is disabled or constrained: Third-party advertising attribution cookies are prevented from writing to your device; Google Ads, Microsoft Advertising, and Meta conversion tracking scripts operate in cookieless ping mode without personal user identifiers; and multi-session live chat history may not persist if browser local storage is cleared.
Where can you review third-party advertising privacy terms?
The advertising platforms that direct visitors to our Denver practice maintain their own published privacy frameworks. We encourage you to review their policies directly:
- Microsoft Advertising: Microsoft's collection, use, and disclosure of telemetry data is governed by the Microsoft Privacy Statement available at privacy.microsoft.com.
- Google Ads: Details on how Google processes ad measurement data, Consent Mode signals, and click parameters are detailed at policies.google.com.
- Meta Ads: Meta's policies regarding ad impression measurement and marketing attribution are documented at facebook.com/privacy/policy/.
How can you contact our technical desk regarding cookies?
If you have technical questions regarding a specific tracking cookie, wish to audit the active telemetry parameters on zavalorin.com, or need assistance modifying your storage preferences, contact our Denver editorial and technical desk: