Privacy
This is a static site. It sets no cookies, runs no analytics, embeds no trackers and loads nothing from a third-party domain. The fonts are served from here, and there is no JavaScript on any page. I collect nothing about your visit.
What the host sees
The site is served by Cloudflare Pages. Like any web host, Cloudflare handles the technical request data needed to deliver a page: IP address, user agent, the URL you asked for. I may see aggregate traffic counts in their dashboard. I do not have a profile of any individual visitor, and I am not building one.
If you email me
Mail to [email protected] is forwarded to a personal mailbox and read by me. I keep the correspondence for as long as the conversation is useful, use it only to answer you, and never add anyone to a list or pass an address to a third party. Ask and I will delete the thread.
The Yes MCP connector
Yes MCP also runs its own MCP connector — the tools you can reach from inside an AI assistant
such as Claude or ChatGPT (list_availability, book_consult,
get_services, advise_scenarios, demo_walkthrough).
This section covers exactly what that connector collects. It does not cover the assistant
itself: your conversation with Claude or ChatGPT is governed by that provider's own policy,
and I neither receive nor store it.
The connector collects data in exactly one place: when you book a consultation. Three fields, all given by you, in the conversation, at that moment: your name (so I know who I am meeting), your email address (to send the confirmation and be reachable about the meeting), and a one-line topic (so the call is not spent on discovery). That is the entire list. There is no account, no login, no payment inside the chat, and no way for the connector to receive anything else. The business type you mention to the scenario advisor is used to pick an answer in the moment and is not stored.
A booking goes to: a database on a server Yes MCP controls; the email provider (Resend, resend.com), to deliver your confirmation; my Telegram, so a person actually sees the booking; and an operational log carrying the same three fields. Nothing is sold, shared with advertisers, or passed to anyone beyond those processors. One deliberate exception, stated plainly: if a request is rejected by the abuse rate-limit, the originating IP address is written to the abuse log so abuse can be investigated. A booking that goes through leaves no IP behind.
Booking records — including those log entries — are kept for 24 months from
the date of the booking, then deleted. To have yours deleted sooner, email
[email protected] from the address you booked with;
I handle these by hand and confirm within 30 days, in practice much sooner. You can ask for a
copy or a correction the same way. Cancelling or rescheduling is done by replying to the
confirmation email. Test bookings made by directory reviewers are marked
[TEST] and are treated — and deleted — identically.
If we work together
An engagement is a different matter, and it gets its own written agreement before anything starts. That covers who controls the data your system holds, where it goes, and what happens to access credentials when the work ends. Nothing on this site creates that agreement.
Changes
If this page changes materially, the date at the top changes with it. Questions or a request to remove something: [email protected].