Zervuqo sets ad-tracking cookies to run Google, Microsoft and Meta traffic to this site

Effective date.

This cookies notice took effect on 24 September 2026. It is reviewed whenever the studio changes which platforms it advertises through or which storage keys those platforms attach; the date above moves only when the substance changes, not on a routine reread.

Categories in use.

Three categories run on this site. Strictly necessary storage keeps the page working: it remembers your cookie choice under site_consent_v2 and, if you open the chat widget, holds the chat token so a conversation survives a reload. It is not optional and carries no ad identifier.

Analytics storage measures which pages get read and for how long, so the studio can tell whether a page written for a search phrase like "operations audit consulting" is actually being read past the first screen. It is denied until you allow it.

Advertising storage is what lets Google Ads, Microsoft Advertising and, where a campaign runs there, Meta Ads recognize that a visit followed a paid click, and measure whether that click led anywhere. It is also denied until you allow it, and it is the category that carries gclid, msclkid and fbclid.

Advertising platforms and identifiers.

Google Ads and Microsoft Advertising send paid clicks to this site today, and Meta Ads may. Each platform appends its own click identifier to the landing URL so it can tell a click apart from ordinary traffic: gclid for a Google Ads click, msclkid for a Microsoft Advertising click, and fbclid for a Meta Ads click. Those parameters are read by the platform's own script, not typed by you, and they are the mechanism this whole notice is about.

Consent Mode v2.

The site runs Consent Mode v2 through Google's tagging setup. Four signals are involved: ad_storage, ad_user_data, ad_personalization and analytics_storage. All four load denied by default on every first visit, before you have made a choice. Choosing "Allow storage" in the banner sets the advertising and analytics signals to granted for that browser. Choosing "Decline," or later withdrawing consent, sets all four straight back to denied — consent mode does not leave a partial state hanging.

Giving or changing consent.

The banner that appears on your first visit asks you to allow or decline optional storage; nothing optional loads before you answer. A Global Privacy Control signal (the browser's Sec-GPC header) is read as a decline automatically, without a second prompt. To change your mind later, open Cookie settings in the footer of any page — it reopens the same choice and rewrites site_consent_v2 immediately.

If you decline.

Declining does not break the site. The pages, the configurator, the inquiry form and the chat widget all work the same either way, because none of them depend on advertising storage to function. What stops is measurement: Google Ads and Microsoft Advertising can no longer tie a later visit back to the click that brought you here, and the studio loses the ability to see which keyword or ad actually produced an inquiry. That is a cost to the studio's reporting, not to your use of the site.

The platforms' own policies.

Once a click identifier reaches Google, Microsoft or Meta, what those companies do with it is governed by their own documents, not this one. Google's practices are described at policies.google.com. Microsoft Advertising's are described in the Microsoft privacy statement at privacy.microsoft.com. Meta's are described in its own data policy where a campaign runs there. None of these companies has reviewed or endorsed this website; they simply receive the signal a click sends them.

Questions about a specific cookie.

Write to [email protected] naming the cookie or the page, or call +1 (365) 555-8425 during studio hours. The same address handles a request if what you actually want is a copy or a deletion of what the studio holds on you, through the data request route in the privacy policy.