What this site and the
yesmcp connector know about you

This website

This is a static site. It sets no cookies, runs no analytics, and embeds no trackers. We collect nothing about your visit.

Nothing on these pages is loaded from a third-party domain, with one named exception below. The typefaces are served from this domain, not from Google Fonts, so your browser makes no request to anyone but us. Every script here is ours and served from this domain: the scroll animation, the chat demo, the scenario map, the booking page, and the one-question checkpoint on the front page. One more small file offers those same things as tools to an AI agent that happens to be browsing this site in a browser which speaks the WebMCP standard. It adds nothing on its own, stores nothing, and in a browser without that standard it does nothing at all. The scenario map keeps the two answers you gave it in your browser's session storage, so that leaving the page and coming back does not make you fill it in again. That stays inside your browser, belongs to that one tab, and is gone when you close it. The checkpoint keeps one word in your browser's local storage once you have answered, so it never asks you twice; that word says nothing about you and never leaves your browser. The front page also asks our own connector for its public status counters.

One page is different, and it is the booking page./book/ asks our connector which windows are open, and that request carries nothing about you. When you fill the form in and press the button, it sends the same three fields any booking needs: your name, your email address and the sentence you wrote. Nothing is stored in your browser, and nothing leaves it until you press that button. What happens to those three fields afterwards is the rest of this page, and it is identical whether you booked from here or from inside an AI chat. An agent browsing this site can prepare a booking through the tools named above, but it cannot send one: the same three fields appear in a card on the page and leave your browser only after you press Confirm yourself.

Booking from inside Telegram

The same booking page has a Telegram version, built to open inside Telegram as a Mini App rather than typed into a browser. It is the one place on this site that loads a file from someone else's domain: Telegram's own telegram-web-app.js, which is what lets a page run as a Telegram Mini App at all.

Inside it, Telegram hands the page your Telegram profile data: your numeric Telegram id, your first and last name, your username if you have one, and your interface language. The name fills the form in for you, the language picks which of the two languages the page speaks, and the id and username travel with the booking so we know which Telegram account it belongs to. That is the whole use. It is not sold, not shared, not used for marketing, and not turned into a profile of you. Your email is still required and still typed by you, because the confirmation email is what actually holds the meeting. Nothing is stored in your browser, and nothing leaves the page until you press the button.

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. We may see aggregate traffic counts in their dashboard. We do not have a profile of any individual visitor, and we are not building one.

If you email us

Mail to yes@yesmcp.com is forwarded to a personal mailbox and read by a person. We 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 we will delete the thread.

What the rest of this covers

Everything below covers the yesmcp MCP connector, the tools yesmcp exposes inside AI assistants such as Claude and ChatGPT (all eight of them: list_availability, book_consult, manage_booking, get_services, advise_scenarios, demo_walkthrough, and the two that draw the cards you see in the chat, booking_widget and services_widget). It does not cover the assistant itself: your conversation with Claude or ChatGPT is governed by that provider's own privacy policy, and yesmcp neither receives nor stores it.

What we collect

We collect data in exactly one place: when you book a consultation. Three fields, all of them given by you, in the conversation, at that moment.

That is the entire list for a booking made on the web or inside an AI chat. A booking made inside Telegram adds two fields and only two, both handed over by Telegram itself: your Telegram id and your username, so the booking is attached to the account that made it. The connector does not ask for, and has no way to receive, a phone number, a company, a payment method, an address, or an account of any other kind.

What we do not collect

• ✓

  No account, no login. Every tool works as a guest. There is no password, no OAuth, no profile.

• ✓

  No conversation content. Every tool that does not manage a booking is read-only. Nothing you say to the assistant reaches us except the three fields you supply when booking. The business type you mention to get scenario advice picks a playbook; it appears in the operational tool-call log described below, with no name or contact attached, and nowhere else.

• ✓

  No payments. No financial transaction happens inside the chat, and no payment details are ever requested there. If a paid engagement follows, it is arranged separately, outside the connector.

• ✓

  No tracking. No cookies, no analytics, no advertising identifiers, no device fingerprinting, no third-party trackers.

• ✓

  No IP address stored with your booking. We rate-limit the booking endpoint to protect it from abuse, and that check lives in memory only. There is one exception, stated plainly: if a request is rejected for exceeding the limit, the originating IP address is written to our abuse log so the abuse can be investigated. A booking that goes through leaves no IP behind.

Why we use it

Solely to arrange and hold the consultation you asked for, and to contact you about it. We do not use your data for marketing, we do not add you to a mailing list, we do not profile you, and there is no automated decision-making.

Where it goes

• →Our own database, on a server yesmcp controls.
• →Our email provider (Resend), which delivers your confirmation email on our behalf.
• →The owner's Telegram, which receives a notification with your name, the time, and your topic, so a person actually sees the booking.
• →Our operational log. Tool calls are logged for reliability and abuse investigation; for a booking, that log line contains the same three fields and nothing more.

We do not sell your data, share it with advertisers, or pass it to anyone beyond the processors named above.

How long we keep it

We keep booking records, including the log entries described above, for 24 months from the date of the booking, and then delete them. Two years is chosen so we can honour a follow-up conversation started a year later, without retaining anything indefinitely.

Test bookings

Bookings made against the reviewer test windows, used by app-directory reviewers, are marked [TEST] and are deleted on the same schedule as everything else. They are real records, because a test booking is a real tool call, and are treated 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.

Children, and changes

The connector is a business-to-business tool and is not directed at children. If this policy changes materially, the effective date at the top changes with it, and the updated text is published at this same URL.

Who is responsible, and contact

This site and the yesmcp connector are operated by Serhii Kravchenko, a private entrepreneur registered in Ukraine. He is the data controller for everything described on this page.

yesmcp · yes@yesmcp.com · privacy requests: privacy@yesmcp.com