Cookie Notice & Consent Guide
A plain-language explanation of how Omelvix uses local browser storage, advertising attribution tokens, and visitor privacy controls across our Portland consulting practice website.
When did this cookie notice take effect?
This document took effect on November 11, 2026. It applies to every visit to omelvix.com and governs how our servers and third-party measurement integrations interact with your web browser. When we alter our storage parameters or implement updated technical protocols, we update this notice immediately and record the exact effective date in this section.
What categories of cookies and local storage does this site use?
We divide all client-side storage keys into three distinct, unambiguous categories. We do not use ambiguous classifications or bundle optional tracking into essential functions:
-
Strictly Necessary Storage: State keys required for fundamental site mechanics, including recording your consent decision, storing your active consultation chat token in
localStorage, and enforcing security tokens during form dispatch. Without these keys, the website cannot remember whether you accepted or declined tracking, and the interactive advisory desk cannot retain your thread. - Analytics & Operational Telemetry: Aggregated measurement tools that count visits, measure scroll depth, and track engagement with our live configurator instrument. These signals do not profile you across unrelated web properties.
- Advertising Attribution: Identifiers that measure whether an advertisement placed on Google Ads, Microsoft Advertising, or Meta Ads resulted in a consultation inquiry. These cookies are placed only when you grant explicit consent.
Which specific cookies and browser tokens are stored on my machine?
The following audit table enumerates every key, script cookie, and local storage item written by omelvix.com or its verified advertising integrations:
| Key Name | Provider | Category | Exact Purpose | Duration |
|---|---|---|---|---|
site_consent_v2 |
Omelvix (1st party) | Strictly Necessary | Stores whether the visitor allowed or declined measurement tags. | 12 months |
chat_token |
Omelvix (1st party) | Strictly Necessary | Session resume token for the live advisory chat widget (buwe786.php). | 12 months |
_ga |
Google Ads / Analytics | Analytics / Ads | Distinguishes unique client browser instances across visits. | 24 months |
_gcl_au |
Google Ads | Advertising | First-party click attribution experiment token for campaign tracking. | 90 days |
_uetsid |
Microsoft Advertising | Advertising | Universal Event Tracking session identifier for Bing ad attribution. | 24 hours |
_uetvid |
Microsoft Advertising | Advertising | Universal Event Tracking permanent visitor token for campaign ROI. | 13 months |
_fbp |
Meta Ads | Advertising | Tracks visits following ad clicks on Meta network platforms. | 90 days |
Which advertising platforms receive click identifiers through this website?
This website is an active landing destination for commercial campaigns. We operate paid campaigns across three major platforms:
-
Google Ads: Paid search and display campaigns route visitors to our practice pages. Clicks arrive with a URL parameter named
gclid(Google Click Identifier). When consent is allowed, this token is written to attribution cookies to measure consultation inquiries. -
Microsoft Advertising: Bing paid search campaigns deliver traffic carrying the
msclkid(Microsoft Click Identifier) parameter to evaluate inquiry conversion rates. -
Meta Ads: Targeted placements on Meta platforms append the
fbclidparameter to inbound links to measure ad performance.
We state plainly that none of these advertising platforms has reviewed, endorsed, or approved Omelvix or our consulting services. We use their standard advertising tools to connect with prospective business clients seeking structured web advisory.
How does Consent Mode v2 regulate advertising and analytics signals?
We implement Google Consent Mode v2 in strict accordance with technical documentation. By default, before you click any button on our banner, all four fundamental consent parameters are initialized in an explicit denied state:
ad_storage: 'denied'— Disallows reading or writing advertising cookies.ad_user_data: 'denied'— Prohibits sending user data to advertising systems.ad_personalization: 'denied'— Blocks personalized remarketing lists.analytics_storage: 'denied'— Restricts analytics tags to cookieless pings.
Under Consent Mode, if you click “Decline” or ignore the banner, these four parameters remain denied. If you click “Allow”, the state dynamically updates to granted. If you later revoke your consent using the footer control, our script immediately dispatches updated commands resetting all four signals back to denied.
How do I choose, alter, or revoke my storage preferences?
When you first open any page on omelvix.com, an unobtrusive banner appears at the bottom edge. You may click “Allow” to enable attribution cookies, or “Decline” to reject all non-essential storage.
Your selection is saved in your browser under the key site_consent_v2 for 12 months. You are never locked into that choice. You can reopen the consent dialog at any time by clicking the link located in the footer of every page on this site.
Furthermore, our website actively detects and respects the Global Privacy Control header (Sec-GPC). If your browser transmits an automated GPC signal, our system treats it as an immediate opt-out for all advertising and measurement keys without prompting you.
What happens if I decline or refuse cookies on this site?
If you decline cookies, the site remains fully operational. You will not face a blocking paywall, degraded styling, or disabled features:
- The live scope configurator on our homepage and pricing page calculates fees and timelines normally.
- The symptom lookup tool filters advisory paths without restriction.
- The inquiry intake form on contact/contact.html and the footer continues to submit data securely to ladu729.php.
- Case documentation across all 12 projects on cases/cases.html remains readable.
The only change is that no advertising tokens (gclid, msclkid, fbclid) will be tied to your visit, and marketing platforms will receive zero conversion attribution records.
Where can I review the privacy policies of third-party platforms?
For complete details on how advertising networks process measurement data independently, please consult their official policy portals:
- Google Ads & Analytics: Review the Google Privacy & Terms framework at policies.google.com.
- Microsoft Advertising: Read the Microsoft Privacy Statement detailing Bing search ad telemetry at privacy.microsoft.com/privacystatement.
- Meta Platforms: Review the Meta Privacy Center covering Instagram and Facebook ad systems at facebook.com/privacy/policy.
Who should I contact with technical questions about site cookies?
If you have questions regarding our implementation of Consent Mode v2, wish to inspect recorded records, or require clarification regarding any storage key, please contact our Portland studio directly:
Omelvix Practice Studio
1201 Northwest Irving Street, Portland, Oregon 97209
Telephone: +1 (324) 555-2313
Direct privacy inquiries: [email protected]
All formal data and cookie inquiries receive an initial response from our lead consultant within 7 business days.