Privacy policy

Last updated November 12, 2026

tg-mcp connects your Telegram account to an AI app such as ChatGPT, Claude or Gemini. This page says what the public instance at connector.tgmcp.dev and this website do with your data. It is run by Kirill Bobykin, an independent developer. tg-mcp is not affiliated with Telegram, OpenAI, Anthropic or Google.

If you run your own copy of tg-mcp, you are the operator of that copy and this policy does not cover it.

What is never stored

• Your messages, photos, voice notes and other media.
• Your chat list, contacts and profile details.
• Your Telegram cloud password.

When your AI asks for something, the server fetches it from Telegram, passes it to your AI app and keeps it only in memory while answering. A download link for a file lives in memory for 5 minutes and 3 downloads, and the file streams from Telegram without touching the disk. A message waiting for your confirmation before it is sent lives in memory for up to 10 minutes.

What is stored

• Your Telegram user id, a number Telegram assigns to your account.
• Your Telegram session, encrypted. It holds only the authorization keys and the home data center, no messages. The key that decrypts it is not stored: it lives only in the sign-in tokens your AI app holds, so the server can't open the session without one of them.
• Sign-in tokens, in a form that can't be used on its own. For each token the server keeps a public id, a value that checks it, an encrypted copy of the session key and the expiry time.
• The permissions you chose when you signed in (read, drafts, sending). If you allowed sending, the list of chats you allowed and whether each message needs your confirmation, encrypted the same way as the session.
• The AI apps you connected: the name each app registered under and the addresses it asked to be sent back to after sign-in.

Cookies

This website sets no cookies and runs no analytics. The server's sign-in page sets tgm_login, which ties the sign-in to your browser and expires after 10 minutes. If you allow sending, the browser you signed in with also gets tgm_confirm_…, which lets only that browser confirm a message; it lasts as long as your sign-in, and the server keeps only a value that checks it.

Logs

The server logs ids and sizes, never message content, tokens or sessions. It logs your IP address when it refuses a sign-in attempt because of rate limits. The reverse proxy in front of it records requests, including the IP address. Logs are rotated by size, and old entries are overwritten.

Who else sees your data

• Telegram, which the server talks to on your behalf through the official Telegram API.
• Your AI provider (OpenAI, Anthropic, Google or another) receives what the AI reads to answer you, the same as if you had pasted it into the chat. Their own privacy policy applies to it.
• The hosting provider of the server, [HOSTING PROVIDER], which runs the machine but has no key to your session.
• GitHub hosts this website, and Google Fonts serves its fonts. Both receive your IP address when you open it.

Nothing is sold, shared for advertising or used to train AI models.

Disconnecting and deletion

In Telegram, open Settings → Devices and end the Unofficial MCP Server session. That logs the server out for real, and the encrypted session left in the database can no longer be used. Removing tg-mcp from your AI app alone is not always enough: some apps only forget their keys.

To have the records above deleted, write to [CONTACT EMAIL].

Changes

This page lives in the public repository, so every change to it is in the history. How the session key lives only in tokens is explained in ADR-0003.