Cookie Policy

Cookies on this site, in plain English.

This page explains what cookies and similar tools 8020ai.co.uk uses, and how you can change your choices at any time.

Last updated: 2 June 2026

Your choices

When you first visit from the UK or Europe, you will see a cookie banner. Nothing beyond the strictly necessary cookies runs until you choose. You can accept everything, reject everything, or open Manage to turn analytics and advertising on or off one at a time.

For all visitors, we may record a first-arrival event with the landing page, referrer, selected campaign parameters, timestamp, and server-side diagnostics. This does not set a visitor ID or session ID before UK or European consent. Reject all stops optional analytics identifiers, session tracking, behavioural events, and advertising tracking for the current visitor.

For visitors whose browser signals suggest they are outside the UK and Europe, where the rules are opt-out rather than opt-in, we may run our analytics and advertising tools by default without showing the banner. These tools include first-party analytics, Google Analytics 4, the Microsoft Advertising (Bing) UET tag, and Microsoft Clarity. Visitors can opt out using the "Cookie preferences" link.

You can change your mind whenever you like. Use the "Cookie preferences" link in the footer of any page to reopen the banner and update your choice.

Strictly necessary

These are always on because the site needs them to load and work. They cover standard technical processing by our hosting and infrastructure providers, such as request logs, security monitoring, and network-level diagnostics. They do not track you for marketing.

Analytics

If you allow analytics, we use 8020AI first-party analytics and Google Analytics 4 (GA4) to see which pages are useful and how the site is performing, so we can improve it. This helps us understand things like which guides people read, where visitors come from, how long sessions last, how far pages are scrolled, and which calls to action are clicked.

Our first-party analytics can store a random visitor ID, session ID, page ID, landing page, referrer, selected query parameters such as UTM fields and Microsoft click IDs, quiz completion events, and checkout initiation events. We do not store raw IP addresses in these analytics events.

If you do not allow analytics and your browser signals suggest you are in the UK or Europe, GA4 runs in a limited, cookieless mode and our first-party analytics does not store analytics identifiers on your device. We may still record the no-storage first-arrival event described above.

Advertising

If you allow advertising, we use the Microsoft Advertising (Bing) UET tag and Microsoft Clarity to measure which ads bring people to the site and to understand how those visits go. This lets us spend our advertising budget sensibly. If you do not allow advertising, these tools receive a "denied" signal and do not store advertising cookies on your device.

How consent works behind the scenes

We use Google Consent Mode and Microsoft UET Consent Mode. For visitors in the UK and Europe, both are set to "denied" by default before any tag loads, and only switch to "granted" once you accept. For visitors outside the UK and Europe, where the rules are opt-out, they may default to "granted" unless you opt out. Your choice is stored in your browser for about six months, after which we will ask again. We do not sell your data.

Other third-party requests

The site requests fonts from Google Fonts and uses Netlify for hosting and form handling. If you book a Close The Gap session, Stripe handles the payment and may set its own essential cookies or similar technical identifiers on its checkout pages so the payment works securely.

Browser controls

On top of the banner, you can manage cookies and site data through your browser settings. You can block third-party requests, clear stored site data, or use privacy-focused browser controls if you prefer.

Future changes

If we add or remove tools later, we will update this page to reflect what changed and explain what has been added. For more on how we handle personal data, see our Privacy Policy.