One key is stored for everyone. Ad cookies wait until you press Allow.

Three kinds. Only the first is set before you choose.

Strictly necessary. The key that remembers your choice on the banner, and the chat token if you open the support chat. Without them the banner would ask on every page and the chat would forget you mid-conversation. They carry no ad data.

Analytics. Counts of visits and pages, used to see whether someone who looked at the services page went on to the contact page. Only after Allow.

Advertising. Cookies from Google Ads, Microsoft Advertising and Meta Ads that store the click identifier so the platform can match a click to an enquiry. Only after Allow. We use them to measure campaigns, not to follow you around other sites.

This is the full list. Platform cookie names are the ones each platform documents for its tag; they appear only after you allow them.

Our fonts come from Google Fonts. That request sets no cookie, but Google sees your IP address when it serves the file.

Because you came from a paid ad. Google Ads, Microsoft Advertising and Meta Ads send visitors here, and each adds its own identifier to the link.

• gclidGoogle Ads
• msclkidMicrosoft Advertising
• fbclidMeta Ads

It is a random string. It does not contain your name or email. On its own, sitting in the address bar, it does nothing. It only becomes a measurement when a platform tag, allowed by you, stores it in a cookie and later reports that the click ended in an enquiry. Decline, and the string stays in the address bar unread.

Everything ad-related is held at no. The very first line of script on each page sets Google Consent Mode v2 before any tag loads.

Four signals start as denied: ad_storage, ad_user_data, ad_personalization and analytics_storage. While they are denied, Google's tags write no ad or analytics cookies and send no user data for ads. Microsoft's UET tag follows the same consent state. Press Allow and all four switch to granted. Press Decline, or withdraw later, and all four are set back to denied on the spot.

If your browser sends Global Privacy Control, we read it as a Decline and do not show you the question.

The banner at the bottom of the screen has two buttons of the same size: Decline and Allow. It never covers the page, so you can read first and answer later.

To change your answer, use the Cookie settings button in the legal row at the bottom of every page, including this one. It brings the banner back. Choose again and the new answer replaces the old one in site_consent_v2 straight away. Clearing your browser's site data does the same thing more bluntly: the key goes, and the banner asks again on your next visit.

Your answer is kept for 12 months. After that we ask once more.

Nothing you would notice. Every page loads. The enquiry form sends. The chat works. The price bases on the services page are the same for everyone.

What stops is on our side: no ad or analytics cookie is set, Google, Microsoft and Meta get no report that your click turned into an enquiry, and we do not know which campaign brought you. We would rather lose that number than pester you for it.

Once you allow them, the three ad platforms receive what their own tags collect. Each one publishes how it handles that data:

• Google: policies.google.com/privacy, and how Google uses data from sites that run its tags at policies.google.com/technologies/partner-sites.
• Microsoft: the Microsoft privacy statement at privacy.microsoft.com/privacystatement.
• Meta: facebook.com/privacy/policy.

What we ourselves keep from an enquiry, and for how long, is in the privacy policy.

Us. Name the cookie, or paste what your browser shows, and we tell you what set it and why.

Email [email protected], call +1 (220) 555-1197, or write to Velorenta, 3 Station Road, Office 12, Austin, Texas 21868, United States. To have the data behind a cookie deleted, use the data request route; it is answered within 14 days.