Privacy & Data

What we access

When you connect Telegram, MCP Hub accesses your chat list and messages on demand — only when an MCP tool is called by your AI assistant. In future phases we will extract facts, track tasks, and build a knowledge base from your conversations.

What we store

• Account info — your Google email and display name (from sign-in).
• Telegram session key — encrypted with AES-256-GCM. This is the only Telegram credential we store.
• Connector metadata — phone number, Telegram username (for display on the dashboard).
• Extracted knowledge (future) — facts, tasks, and summaries from your conversations. You will be able to view, edit, and delete these.

What we never do

• We never share your data with other users. All queries are scoped to your account.
• We never log message content. Only operation metadata (user ID, timestamps, error codes) appears in logs.
• We never sell or monetize your data.

Voice transcription

When your AI assistant asks to read a voice message, the audio is sent to Google's Gemini API for transcription and the transcript is returned to your assistant. The audio is processed on demand and is not stored by MCP Hub. If transcription is not configured (self-hosted without an API key), voice messages simply cannot be read.

When your assistant sends a voice message from text, that text is sent to Google's Cloud Text-to-Speech API to synthesize the audio, which is then posted to your chosen chat. The text is processed on demand and is not stored.

VK

If an administrator has given you access and you connect VK, you sign in inside a private browser hosted for you. It runs in its own container on a server shared with other people's browsers, kept apart from them, and keeps your VK session and what VK caches there, not encrypted, so whoever administers that server could read them. We keep which VK account is linked to you. Your AI assistant reads your chats through that browser on demand, and message text is not stored by MCP Hub.

Disconnect on the dashboard stops that browser and deletes its profile and history from the server. It does not sign you out of VK on your other devices.

Encryption

Telegram session data is encrypted at rest with AES-256-GCM. The encryption key is stored in Google Cloud Secret Manager, separate from the database. Even with direct database access, sessions cannot be decrypted without the key.

Your controls

• Disconnect — revoke Telegram access and delete the session key instantly from the dashboard.
• Delete all data — permanently remove your account, all connectors, sessions, and any extracted knowledge.
• View & edit (future) — review and modify extracted facts and tasks.

Self-hosting

MCP Hub is open source. You can run your own instance with docker compose, using your own Telegram API credentials and encryption keys. Your data never touches our servers. See the repository for instructions.

Open source

The full source code is available at github.com/ai-church/mcp. Audit the code yourself — every database query, every API call, every encryption operation.