Privacy Policy
Last updated: 30 October 2026
This policy explains how BKTY LTD (“we”, “us”) handles personal data when you use MCPtoAI: the website mcptoai.com, the web app at app.mcptoai.com, MCPtoAI Desktop and the Device Agent (together, “MCPtoAI”).
1. Who we are
The controller of your personal data is BKTY LTD, a company registered in England and Wales (Company No. 12845913), 29 Watts Lane, Rugby, England, CV21 4PE.
We are registered with the Information Commissioner’s Office (ICO) under registration number ZC165481.
For any privacy question or request, email [email protected].
2. The personal data we process
Account data
Your email address, whether it has been verified, the sign-in provider you used (Google or Apple) and the unique identifier that provider assigns to you, and the date your account was created. We receive this from our sign-in service when you sign in. We never receive your Google or Apple password.
Device data
For each computer you pair: its name (the computer’s network name, for example “Alex’s MacBook”), its platform (for example macOS), the device’s public key, when it was paired and last connected, and whether it is enabled.
Conversation data
If you choose MCPtoAI Cloud for conversation history, we store conversation titles, the messages you send and replies you receive, the provider and model used, and the names, inputs and outputs of tools used in the conversation so that you can continue it across connected clients. Tool outputs can include file names, file contents, command output or results from MCP services you allowed or approved. If you choose This device only, this conversation history is stored on the selected device instead and is not stored as conversation history on BKTY LTD servers.
Messages in transit
Our relay passes messages between the web app and your device. Messages are processed in memory to deliver them. Whether conversation history is retained by MCPtoAI Cloud or only on your device depends on the history-storage option you selected.
Traffic between the web app, the hosted relay and your device is protected in transit with TLS. MCPtoAI does not currently provide end-to-end encryption, so chat traffic passes through the hosted relay while it is being delivered.
Technical and security data
Short-lived connection tickets, one-time security values used to prevent captured requests from being replayed, rate-limit counters, and server logs containing the time, address and outcome of requests and your browser’s user agent. Our servers receive traffic through Cloudflare and do not generally record your IP address in their logs; Cloudflare processes IP addresses to deliver and protect the service.
Correspondence
If you contact us, we keep your message and our reply so that we can deal with your request.
Conversation history
You can choose MCPtoAI Cloud or This device only for conversation history.
In MCPtoAI Cloud mode, your messages, tool names, statuses and requested inputs (with file contents omitted and known secrets masked), and images or videos returned during a conversation (such as screen captures) are stored on BKTY LTD servers. You can open them from signed-in browsers; access is restricted to your account.
In This device only mode, conversation history is stored in a local database on the selected device. The web app retrieves it through the authenticated device relay while that device is online; we do not store a copy in our Cloud chat-history database. Switching modes does not automatically move or delete existing conversations.
Images, videos and files
Screen captures and other media can reveal messages, documents, code or personal details visible on your screen. Enable these tools only if you are comfortable with this processing.
In MCPtoAI Cloud mode, images and videos attached to a verified Cloud conversation are stored at their original resolution in private storage linked to your account. The media storage limit is 2 GiB per account.
Files transferred outside a saved Cloud conversation are temporary and expire after 7 days. For older agents that do not report a history mode, media attached to a server-verified Cloud chat belonging to the requesting user and the same device is treated as Cloud media; otherwise it is temporary.
Images or videos you send to an AI provider are also processed by that provider under its own privacy policy.
Retention and deletion
Cloud conversation history and associated images and videos are retained until you delete the conversation or your account. Deleting a Cloud conversation also deletes its associated stored media. Temporary file transfers expire after 7 days.
Deleting your account removes server-side account data, Cloud conversations, stored media and paired-device records, subject to the retention and backup periods stated below. Local-only conversation history and settings remain on your device until you remove them there.
3. Data that stays on your device
The following is stored on your computer and is not sent to us as account or credential data:
- your AI provider API keys, kept in the supported credential store on your device (Keychain on macOS, Windows Credential Manager on Windows, and the supported local credential store on Linux);
- your device’s private signing key;
- sign-in tokens and secrets for MCP services you connect;
- your permission settings and MCP server configuration;
- the files and applications on your computer;
- conversation history when you select This device only.
If a tool reads a file or runs a command and its result is shown in a conversation, that result becomes part of that conversation. It follows the history-storage option you selected: MCPtoAI Cloud or This device only.
4. How we use your data and our lawful bases
| Purpose | Data | Lawful basis |
|---|---|---|
| Creating your account and signing you in | Account data | Contract |
| Pairing your devices and delivering messages between the web app and your devices | Device data, messages in transit | Contract |
| Storing conversation history when you choose MCPtoAI Cloud, so you can continue across connected clients | Conversation data stored in MCPtoAI Cloud | Contract |
| Keeping MCPtoAI secure, preventing abuse and fixing problems | Technical and security data, device data | Legitimate interests (protecting our users and our service) |
| Answering your requests and sending essential service messages | Account data, correspondence | Contract; legitimate interests |
| Meeting our legal obligations | Any data we are required to keep | Legal obligation |
We do not use your data for advertising, we do not sell it, and we do not use your conversations to train AI models. We do not make decisions about you based solely on automated processing that have legal or similarly significant effects.
5. AI providers and MCP services you choose
When you send a message, your device sends the conversation, including any tool results, to the AI provider you selected, using your own API key and your own account with that provider. When the AI uses an MCP tool, the request is sent to that MCP service.
These providers act on your instructions and under their own terms and privacy policies; they are not our processors. Please review their policies before you connect them. If you use a local model, for example through Ollama or LM Studio, the model request is processed on your computer. Conversation retention still follows the history-storage option you selected.
6. Service providers we use
We use the following service providers to run MCPtoAI. They process personal data on our behalf and under contract:
| Provider | Service | Location |
|---|---|---|
| Auth0 (Okta, Inc.) | Sign-in and identity management | United States |
| Cloudflare, Inc. | Network, DNS, secure connection to our servers and content delivery | Global network, including the United States |
Our own servers are operated by BKTY LTD and located in the United Kingdom. If you sign in with Google or Apple, that company handles your account with them as an independent controller under its own privacy policy.
We may also disclose personal data if the law requires it, to protect the rights and safety of our users or others, or as part of a sale or reorganisation of our business, in which case we will tell you in advance.
7. International transfers
Some of our service providers process personal data outside the UK, including in the United States. Where this happens, we rely on safeguards recognised under UK data protection law, such as the UK Extension to the EU–US Data Privacy Framework or the International Data Transfer Addendum to standard contractual clauses. You can ask us for more information about these safeguards.
8. How long we keep data
| Data | Retention |
|---|---|
| Account data | While your account exists; deleted within 30 days after you ask us to delete your account |
| Device records | Until you remove the device or your account is deleted |
| Conversation data stored in MCPtoAI Cloud | Until you delete the conversation or your account is deleted |
| Local-only conversation history | Stored on the selected device until you delete it or clear local MCPtoAI data |
| Server logs | 14 days |
| Connection tickets and one-time security values | A few minutes at most |
| Correspondence | As long as needed to deal with your request and any follow-up |
| Data on your device | Until you remove it, for example by disconnecting the device or clearing local MCPtoAI data |
| Cloud conversation images and videos | Until you delete the Cloud conversation or account |
| Temporary file transfers | 7 days |
Where data is held in backups, it is removed when those backups are overwritten, within 30 days.
9. Your rights
Under UK data protection law you have the right to:
- access the personal data we hold about you;
- have inaccurate data corrected;
- have your data deleted;
- restrict or object to how we use your data;
- receive your data in a portable format and have it transferred to someone else.
You can delete MCPtoAI Cloud conversations in the web app. Local-only conversations are deleted from the device that stores them. You can remove a device from MCPtoAI Desktop at any time. To use any of the other rights, including deleting your account, email [email protected]. We will respond within one month and may need to confirm your identity first.
If you are unhappy with how we handle your data, please contact us first so that we can try to put it right. You also have the right to complain to the Information Commissioner’s Office: ico.org.uk/make-a-complaint, telephone 0303 123 1113.
10. Cookies and similar technologies
- app.mcptoai.com uses strictly necessary cookies, set by our sign-in system, to keep you signed in and to protect sign-in against forgery. The service cannot work without them, so they do not require consent.
- mcptoai.com remembers the language you choose and your analytics preference in your browser’s local storage.
- If you choose “Allow analytics”, mcptoai.com loads Google Analytics (measurement ID G-MRM5ZCQSVV) to help us understand site usage. Google Analytics is not loaded until you consent, and you can change your choice at any time using “Analytics settings” in the footer.
- We do not use advertising cookies.
11. Security
We protect personal data with measures that include keeping API keys on your device, encrypting all connections, signing every device connection with a key unique to that device, and letting you control every action through Off, Ask and Allow permissions. Read more on our Security page.
No system is completely secure. If a personal data breach occurs that is likely to put your rights at risk, we will notify you and the ICO as required by law.
12. Children
MCPtoAI is not intended for anyone under 18, and we do not knowingly collect personal data from children. If you believe a child has created an account, please contact us and we will delete it.
13. Changes to this policy
We may update this policy as MCPtoAI develops. We will change the date at the top of this page and, if the changes are significant, let you know by email or in the app before they take effect.
14. Contact us
BKTY LTD, 29 Watts Lane, Rugby, England, CV21 4PE. Email: [email protected]. ICO registration number: ZC165481.
ChatGPT plan use (Desktop and web)
If you explicitly connect ChatGPT, MCPtoAI Desktop may use your eligible ChatGPT plan for AI requests. Web use requires a separate, off-by-default permission on your paired device and a server-wide enable switch. Web requests are relayed to your device, which sends AI requests to OpenAI; ChatGPT authentication tokens stay in the device operating-system credential store and are not transmitted to MCPtoAI servers. Conversation content and related metadata may pass through MCPtoAI relay and may be stored according to your selected conversation-history setting. OpenAI processes AI requests under its own terms. You can disable web plan use on your device and manage plan usage at https://chatgpt.com/settings/usage.