Last updated: November 12, 2026

Privacy policy

This site runs analytics and advertising measurement for every visitor by default. This page explains what runs, what it collects, and how to turn it off.

What runs on every page

Tracking starts on the first page view. There is no cookie banner and no opt-in step, and turning off JavaScript does not stop the pixel fallback from loading.

  • Google Analytics 4 (measurement ID G-CD3C6C6SBB) records page views, events, device and browser details, approximate location, and how you interact with the site.
  • Meta pixel (dataset 1008542822282717) records page views and a Lead event when you submit a lead form. The lead form sends Meta an event ID with the Lead event. If a server Lead event is also sent through the Conversions API, it uses the same event ID so Meta can match and deduplicate the events.
  • Google Ads conversion tracking: there is no Google Ads tag on this site. The Google Analytics property is linked to our Google Ads manager account, so Google Ads can use its data and audiences. If a Google Ads tag is added, it will load the same way, by default, with no consent prompt.

We do not read or act on browser Do Not Track or Global Privacy Control signals. Those signals do not change what loads or what is recorded.

Google Analytics advertising features

This site turns on Google signals and the advertising features of Google Analytics: demographics and interests reports, cross-device measurement and remarketing. Google uses its own cookies and device identifiers, together with data from people who are signed in to a Google account and allow ads personalisation, to give us reports on visitors' age range, gender and interests and to measure visits across devices. Those reports reach us only as totals, not tied to a named person. Google and its partners also use advertising cookies to show ads, including ours when we advertise, based on your visits to this site and other sites (remarketing). You can turn off personalised ads from Google in Google Ads Settings; that changes which ads Google shows you, but it does not stop this site's tags from loading. To stop Google Analytics from measuring your visits on this and other sites, install the Google Analytics opt-out browser add-on; it is designed to stop Google Analytics, and with it the Google Ads measurement that runs through our Google Analytics link, but not the Meta pixel. This site runs the Google tag in a background worker (Partytown), and we have not confirmed that the add-on reaches it there, so a content or tracker blocker is the reliable way to stop Google Analytics on this site.

What is collected and shared

  • Pages you visit, the referring page, campaign parameters (utm_source, utm_medium, utm_campaign, utm_term, utm_content), and ad click IDs (gclid, gbraid, wbraid, fbclid, msclkid, li_fat_id).
  • Device, browser, operating system, screen and language details, and an approximate location derived from your IP address.
  • What you send through a lead form: name, company, email, message, and any attachments you choose to upload.
  • First-party cookies set by these tools, including _ga, _fbp and _fbc.

The analytics and advertising data described above is shared with Google and Meta for measurement, attribution, audience building and ad optimisation. Form submissions go to the service providers below; Meta may receive the server-side advertising data described next. Those companies process the data under their own terms and privacy policies.

When you submit a lead form, our server may send Meta contact details you provide, such as your email address, after normalizing and hashing them with SHA-256. Through the Conversions API, it may also send your browser details, page URL, Meta event ID, a hashed country code fixed to US in our configuration, and your IP address and _fbp / _fbc identifiers when available, for advertising measurement and attribution. When both a browser Lead event and a server Lead event are sent, they use the same event ID so Meta can match and deduplicate them. We do not send your name, email address, message or attachments to Google Analytics.

Service providers

The lead forms, attachments and chat assistant run through service providers that process the data for me:

  • Boost Business runs the n8n intake workflow at n8n.boostbusiness.ai. Lead form submissions (your name, company, email address, message, attachment links, page and campaign values, the Meta event ID, and the _fbp and _fbc cookies when the pixel has set them) go there, and it sends the email or message notification about your request.
  • Cloudflare hosts this site and its API, runs the Turnstile bot check on the lead and chat forms, and stores the attachments you upload in its object storage. A short-lived upload session cookie authorizes the upload, and the notification links to the stored files.
  • OpenAI powers the chat assistant. Messages you type in the chat are sent from your browser to this site's /api/chat endpoint and on to the OpenAI API to generate the reply.

These providers process data to deliver and answer your request, run the site and its bot protection, produce the chat reply and, for Boost Business and Cloudflare, support the server-side advertising measurement described above. Their own terms and privacy policies apply.

How to opt out

There is no site-wide opt-out control, because tracking is on for everyone by default. You can still limit what is done with your data:

Blocking Google or Meta requests in your browser does not stop a server-side event sent after you submit a form.

  • Email i@anton.qa or use the contact page and ask us to stop using your information for advertising, or ask what we hold about you or to delete it. We will honour the request: we stop using the information we hold about you for advertising and exclude you from our Google and Meta ad audiences, and we answer access and deletion requests for the data we hold. This does not switch off the tags in your browser; the ad or tracker blocker below does that.
  • Block requests to Google and Meta with an ad or tracker blocker; this stops the tags on your next visit. Clearing cookies removes the identifiers the tags have stored, and blocking cookies stops new ones being set; neither stops the tags. A blocker stops these browser tags, but click IDs, campaign values and the Meta identifiers already stored in your browser are still sent with a form you submit, so we can tell which ad brought you.
  • Turning off JavaScript stops Google Analytics and the Meta pixel script, but the Meta pixel's no-JavaScript page-view image still loads, so it does not stop all tracking.
  • Use the ad-personalisation controls Google and Meta provide for their own networks; those settings apply across all sites that use them, not only this one.

Contact

Questions about this policy or your data go to i@anton.qa. The contact page also reaches me directly.