Cookies pay for Velabu's ad traffic, not for anything sold on this page.
Version 1.0
Effective September 7, 2026
Velabu, 31 River Road, Suite 4, Austin, Texas 61698
Google Ads and Microsoft Advertising send paid clicks to velabu.com today, and a Meta Ads campaign may run at the same time. This statement names every cookie category in use, the click identifiers those platforms attach, and how Consent Mode v2 holds storage denied until you say otherwise.
Effective date. This cookie statement took effect on September 7, 2026, and it covers velabu.com in full, including the inquiry form, the support chat widget and any advertising landing page that links here.
Categories in use
Strictly necessary. These keep the site working: they hold the state of the mobile navigation, keep an inquiry form's fields intact if a page reloads, and carry the support-chat token so a conversation survives a page change. They are not switched off by a decline, because the site cannot function as a form and a chat widget without them.
Analytics. Measurement of which pages get read and which links get clicked, so the studio knows whether a services section is doing its job. Set only once you allow storage.
Advertising. The identifiers that Google Ads, Microsoft Advertising and, where a campaign runs there, Meta Ads attach to a click so that a later inquiry can be credited back to the ad that caused it. Set only once you allow storage.
Ad platforms and click identifiers
Three platforms may place a marker in the address bar when you arrive from a paid link. Google Ads attaches gclid. Microsoft Advertising attaches msclkid. Meta Ads attaches fbclid on any campaign that runs there. Each identifier is read by its own platform to credit the click; none of the three is read by the others.
Consent Mode v2
Velabu runs Google's Consent Mode v2 with four signals: ad_storage, ad_user_data, ad_personalization and analytics_storage. All four load denied. They switch to granted only after you press Allow storage on the banner at the foot of every page, and they are set straight back to denied the moment you decline or later withdraw. Consent mode does not stop the ad platforms from receiving a request; it changes what that request is allowed to carry.
Giving or changing consent
The banner offers Allow storage or Decline the first time you load a page. Your answer is written to a browser storage key named site_consent_v2 and held for six months, after which the banner asks again. To change your mind at any point, open Cookie choices in the footer of any page and pick again; the change applies immediately to the four signals above.
A visitor whose browser sends the Sec-GPC signal, Global Privacy Control, is treated as having declined without being asked twice.
If you decline
The inquiry form, the support chat, the navigation and every page of writing on this site work exactly the same. What stops is measurement and ad attribution: no analytics figure is recorded against your visit, and no click identifier is passed on for a later ad conversion. The studio still answers an inquiry sent while declined; it simply cannot tell which ad, if any, brought you here.
The platforms' own documents
Each platform's own handling of the data behind these identifiers is described in its own document, not this one. Microsoft's is the Microsoft privacy statement at privacy.microsoft.com. Google's data practices for Google Ads and Analytics are described across policies.google.com. Neither company has reviewed or approved this website; the links are provided so you can read how each one handles what it receives.
Questions about a specific cookie
Write to office@velabu.com or call +1 (648) 555-1724 and name the cookie or storage key you are asking about. The same four people who write the names also read this inbox. See the privacy policy for how long an inquiry itself is kept, and the terms of service for the rest of the site's rules.