Cookie policy
Nine numbered sections cover every cookie this catalogue sets and why.
This page lists what velaxmora.com stores in your browser, what each entry is for, and exactly where to change your mind about advertising storage.
Jump to a section
This notice took effect on 24 September 2026.
The date below decides which version of our cookie practices applies to your visit.
This is the cookie notice currently in force at velaxmora.com, effective 24 September 2026. It works alongside our privacy policy, which covers what we do with data more broadly; this page is specifically about what gets stored in your browser and why.
Three categories of storage exist here: necessary, analytics and advertising.
Only one of these three ever needs your permission first.
Strictly necessary. This covers the single consent record we keep in your browser so we know your choice and don't ask twice. It runs regardless of what you choose, because it exists to record the choice itself.
Analytics. This would let us see, in aggregate, how many people view a page and roughly how they found it. Analytics storage is held denied until you allow it, under Consent Mode v2, explained below.
Advertising. This covers the click identifiers attached by Google Ads, Microsoft Advertising and Meta Ads, and any storage those platforms use to measure or personalise ads. Advertising storage is also held denied until you allow it.
Here is the actual list: name, who sets it, what it's for, how long it stays.
This table is the complete inventory of cookies and storage keys this site can write.
| Name | Set by | Purpose | Duration |
|---|---|---|---|
| site_consent_v2 | Velaxmora | Remembers your storage choice so the banner does not reappear | 12 months |
| chat_token | Velaxmora (jeze703.php) | Lets you return to an open support conversation | Until the conversation ends or 18 months, whichever comes first |
| _gcl / gclid parameter | Google Ads | Matches a click on a Google ad to a later visit, only if you allow storage | Up to 90 days |
| _uetsid / msclkid parameter | Microsoft Advertising | Matches a click on a Microsoft ad to a later visit, only if you allow storage | Up to 30 days |
| _fbp / fbclid parameter | Meta Ads | Matches a click on a Meta ad to a later visit, only if you allow storage | Up to 90 days |
The advertising rows only get written to your browser once you allow storage. Before that, and if you decline, no value in those three rows is set.
gclid, msclkid and fbclid are the three identifiers behind our paid traffic.
This is what each platform's identifier is for and when it gets used.
Google Ads attaches gclid to a link when someone clicks a Google ad that leads here. Microsoft Advertising attaches msclkid the same way for a Microsoft ad. Meta Ads attaches fbclid for a Meta ad. Each identifier exists only to tell the platform that sent the click that a visit happened, so that platform can measure its own advertising.
Consent Mode v2 governs four signals, and all four start denied.
This is the mechanism behind every "allow" or "decline" choice on this site.
Velaxmora runs Google's Consent Mode v2. The four signals it manages — ad_storage, ad_user_data, ad_personalization and analytics_storage — are held denied by default, before you make a choice. Choosing "Allow storage" in the banner sets all four to granted. Choosing "Decline," or later turning your choice off, sets all four back to denied immediately. Consent mode applies the same way regardless of which of the three ad platforms sent you here.
You choose once in the banner, and can change it from the footer at any time.
This is exactly where the choice is made and where to undo it later.
The first time you visit, a banner at the bottom of the page offers "Allow storage" or "Decline." Whichever you pick is written to site_consent_v2 and applied through Consent Mode v2 as described above. To change your mind later, use the "Cookie settings" link in the footer of any page, which reopens the same choice.
Your current choice is stored in this browser only and is not visible to us until you interact with the banner or the cookie settings control.
ad_storage— advertising cookies and identifiersad_user_data— sending user data to ad platforms for measurementad_personalization— using data to personalise adsanalytics_storage— aggregate analytics measurement
Declining costs you nothing on this site; it only turns off ad measurement.
Here is precisely what still works, and what stops, if you decline.
If you decline, the catalogue, the inquiry form, the supply calculator and the support chat all keep working exactly as before — none of them depend on advertising or analytics storage. What stops is any advertising measurement: no gclid, msclkid or fbclid value is retained, no analytics event is stored, and Google, Microsoft and Meta receive nothing that could tie your visit to an ad click. If you arrived here through a paid ad and decline, that specific ad's platform simply will not be able to report your visit back to us.
Each ad platform publishes its own privacy documentation, linked here directly.
These are the platforms' own pages, not ours, for how they handle the identifiers described above.
Microsoft's handling of msclkid and related advertising data is described at privacy.microsoft.com. Google's handling of gclid and its advertising products is described at policies.google.com. Meta's advertising data practices are described in its own data policy, linked from Meta's own sites. None of these three pages is operated by Velaxmora, and we cannot change what they say.
Questions about a specific cookie go to [email protected].
This is the direct line for anything this page did not answer.
Velaxmora, 61 Market Street, Office 12, Austin, Texas 91496, United States
For the fuller picture of what we collect and why, read our privacy policy, and see our terms of service for how an inquiry works.