# What Claude sees through your connector: seven questions owners ask me > «If my customers talk to my business through Claude, does my data end up in the AI?» That is the first question I hear from anyone who runs a clinic, a studio or a firm, and the honest answer is short: Claude sees exactly what your connector chooses to show it, and nothing more. I run a connector that books real consultations inside Claude, so below are the seven questions owners ask me, answered from that connector. Plain words, one example each, no theory. First, one word you will meet in every answer. A connector offers Claude a short list of **tools**. A tool is one thing Claude may ask your business to do: show free times, book a slot, list your services. Everything below follows from this: Claude can only do what your tools do, and can only see what your tools return. ## 1. Does Claude see my customer database? No. Claude never touches your database, your calendar or your files. It sends a request to one tool and reads that tool's answer. If no tool returns your customer list, your customer list does not exist for Claude. On my connector, the tool for free times returns free times. The booking tool returns one confirmation. There is no tool that lists customers, so nobody can ask for the list, however the question is phrased. ## 2. What does my customer's chat actually send to my server? Only the fields the tool asks for. Not the conversation, not the customer's Claude account, not their email unless they type it for a booking. My booking tool asks for four things: the chosen slot, a name, an email and a one-line topic. The customer types them in the chat a minute before. The tool that cancels or moves a booking asks for two: the booking reference from the confirmation email and the email it was made with. The tool that shows services asks for nothing. That is the complete list of what can ever reach my server, because there is no other channel. There is also no login on my connector, by design. No password, no profile, no account with us. A customer arrives as a guest and becomes known to us only at the moment they book, by the name and email they gave. ## 3. Does Claude act on its own, or does the customer confirm? The customer confirms. Before Claude calls a tool from a business's connector, it shows a small card: which tool, with which values, allow or not. The platform's default for every such tool is «ask each time». A user can switch a tool to «always allow» or block it. On a company plan, the owner can block all writing tools for the whole company, while reading stays open. Two exceptions are worth knowing. In the platform's research mode, Claude may call connected tools without asking again, so a booking tool should never be set to «always allow». And when a connector draws a card inside the chat, like my booking calendar, a button on that card calls the tool without the extra question. I saw this on my own calendar on 24 August and again on 27 August with an independent probe. The click is the consent, so the card itself must ask «cancel this booking?» before anything irreversible. ## 4. What does my server keep, and where does it go? Mine keeps three fields per booking: the name, the email and the topic. A booking made through Telegram adds the Telegram id and username, handed over by Telegram itself, and nothing else. No phone, no company, no address, no payment details, because no tool asks for them. For every tool call the server writes one line in its log: which tool, with which values, how long it took, how large the answer was, and whether it failed. For a booking that line holds the same three fields and nothing more. The customer's IP address is not stored with a booking. It is written down only when a request is refused for sending too many requests, so abuse can be looked at. Records are kept for two years and then deleted. Where the three fields go is a list of four: my own database on a server I control, the email provider that sends the confirmation, my Telegram, so a person sees the booking, and the log above. The AI platform is not on that list. ## 5. Can one customer see another customer's booking? No. The only tool that touches an existing booking needs two things at once: the booking reference and the email the booking was made with. Without both, it answers nothing. A public counter on my site shows how many bookings happened this month and on which day the last one was. Never a name, an email, a topic or a time of day. ## 6. Does the AI company train on my customers' data? For personal plans the platform states it plainly: the data it may use to improve its models does not include raw content from connectors, including remote and local MCP servers, unless the user copies it into the conversation themselves. I quote that from the platform's privacy centre as of 11 September 2026. It is the platform's promise, not mine. What I can promise is what my side keeps, and that is the list in question four. One more boundary. Whatever your customer says to Claude before and after calling your tool stays with the platform, under the platform's privacy policy. Your business never receives it, so it is not yours to protect or to leak. ## 7. What should I ask whoever builds my connector? Five questions. All of them have an answer in the code, none of them in a brochure. 1. For each tool: which fields does it ask for? That is the full list of what a customer can send you. 2. Which tools change something, and what does the customer see before that happens? 3. What is in one line of the log, and when is the IP address written? 4. Where do the stored fields travel: database, email provider, notifications, anything else? 5. How does a customer prove a booking is theirs before the connector will touch it? If the answers fit on one page, you have a connector you can explain to a customer in one sentence. Mine is on the [privacy page](/privacy/), in full, including the exception about the IP address. A connector that hides its exceptions is not one a customer should install. ## Changelog - **2026-09-11**: first version. Checked against the eight tools of the production connector, its code and privacy page, and the platform's help centre and privacy centre on the same day. --- Author: Serhii Kravchenko · yesmcp.com · checked against our own live connector (eight tools, inside Claude), its privacy page and code, and the platform's help centre and privacy centre on 2026-09-11 Canonical: https://yesmcp.com/writing/what-data-can-claude-access-through-connectors/ · dateModified: 2026-09-11