Privacy Policy

The AI visibility check stores the URL that was scanned, the score it produced and the full technical result. It stores nothing about the person who asked for it: no account, no IP address, no session, no browser fingerprint. A row says a domain was measured and what was found; there is no field that could say by whom.

That record exists so a site's score can be compared against itself later, which is the only honest way to show that a change worked. It is not readable by anyone but me, and it is not published, sold or shared.

Results are also held in memory for up to an hour so that repeating the same URL does not hit that site's server twice. That cache expires on its own.

Your IP address is used, in memory only, to apply the rate limit that stops the tool being pointed at someone else's server in bulk. It is not written anywhere and it is not associated with anything you scanned.

This is deliberate: you can check a competitor's site without leaving a trail that points at you. What is kept describes the site that was measured, never the person who measured it.

When you send a message, four fields are stored: your name, your email address, your business name if you give one, and your message. Which page you sent it from is stored alongside them, so I know what you were reading when you wrote.

They are used to answer you and to carry on the conversation that follows. They are not added to a mailing list, not sold, and not shared with anyone for marketing.

There is no analytics script on this site. No Google Analytics, no Tag Manager, no Meta pixel, no session recorder. This site sets no cookies of its own. Nothing measures you.

One thing is measured on the server, and it is not people. When a request arrives whose user agent identifies it as an AI crawler — GPTBot, ClaudeBot, PerplexityBot and others of that kind — the visit is recorded: which crawler, which page, when, and the country the request came from. This is how I can show what AI systems actually read, on the site that argues it matters.

A request from an ordinary browser matches none of those names and writes nothing at all. There is no row for you, and no IP address is stored for anyone.

The one exception is the booking calendar embedded on the contact pages. It is a Calendly frame, it sets its own cookies inside that frame, and it is governed by Calendly's privacy policy rather than this one. Everywhere else on the site, the booking button is an ordinary link and nothing loads until you click it.

Booking links carry campaign tags in the URL — which page and which language you clicked from. Those reach Calendly, not this site, and they describe the page rather than you. If you book a call, Calendly records that alongside your booking.

Google Search Console reports which search queries led to this site. It reports totals and countries, never individuals.

Three services process data on this site's behalf, each under its own privacy policy: Netlify serves the pages, Supabase stores contact-form submissions and the blog, and Calendly handles bookings. Fonts are loaded from Google Fonts.

Nothing is shared with anyone beyond that list, and nothing is used to train an AI model.

You can ask me to:

• tell you what I hold about you
• correct anything that is wrong
• delete it

One email is enough and there is no form to fill in. Since the only thing stored is what you typed into the contact form, deletion is immediate and complete.