Privacy and AI crawler policy

What this site collects

Nothing. There is no contact form, no analytics script and no cookie banner, because there are no cookies to consent to. The only thing on the site that takes an input is the booking panel on /contact, and that is an embedded Calendly widget.

When you book, the name, email address and any notes you type go to Calendly, not to us, and Calendly is the data processor for them under its own privacy policy. We see them in the resulting calendar invite and we use them to hold the call and reply to you. We do not sell, rent or trade them.

Our crawler policy, in full

We sell advice about crawler access, so ours is published rather than described. The live file is at /robots.txt and it is commented.

Answering crawlers: allowed

OAI-SearchBot, Claude-SearchBot, PerplexityBot, Bingbot and Googlebot are allowed everywhere. These are the crawlers that fetch a page so it can be cited in a live answer. Blocking one removes you from that surface entirely, which is the most common self-inflicted problem we find.

User-initiated fetchers: allowed

ChatGPT-User, Claude-User and Perplexity-User fire when a person asks about us by name. Two of them document that they ignore robots.txt, so our rules for them are a statement of intent rather than a control, and we say so in the file.

Training crawlers: allowed, deliberately

GPTBot, ClaudeBot, Google-Extended, Applebot-Extended, Amazonbot, Meta-ExternalAgent and CCBot are allowed. This is a content-licensing decision, not a technical one, and it is a legitimate decision to make the other way. We allow it because inclusion in training is how a small brand becomes known to a model without a live retrieval step.

Google-Extended is worth naming separately because it is the most misunderstood token in the list: it governs Gemini training and grounding in some Google products, and it does not affect AI Overviews or AI Mode eligibility. Blocking it does not protect you from what most people think it protects them from.

What we do not do

No crawler is blocked, no rate limit is applied, and there is no bot-management rule at our CDN. If you fetch this site with any user agent you get the same HTML a browser gets. You are welcome to check.