What this connector does with your data.

What we collect

We record anonymous usage counts — when a connection is made and how often tools are called — to find out whether this is worth continuing. We do not record message content, channel names, or what you asked. Your Telegram account is identified only by an irreversible keyed hash. Processing runs on Amplitude's EU infrastructure, and records are kept for 12 months.

• No channel names or message content in any event payload.
• A keyed hash (HMAC with a server-side secret) identifies your account — never a plain hash of the user id.
• Retention is set to 12 months in Amplitude, matching this policy.

Cookies and session recording on this website

This landing page and this privacy page load Amplitude's browser analytics only after you click Accept on the cookie notice, so we can see where people stop reading. Until then no analytics script runs, no cookie is set, and nothing is written to local storage. Declining is closing the notice without accepting; the site and the connector work identically either way.

• Page views, clicks and navigation on these two pages are captured.
• Sessions on these two pages are recorded as a replay of pointer movement, scrolling and clicks, kept by the same processor, in the same region, for the same 12 months.
• The login screen never records anything — it shows a QR code and, with two-factor on, a password field, so it is excluded by construction. The SDK does load there, and after a successful login the visit is linked to your pseudonymous id.

Deleting what we hold

Ask and it goes — message us on Telegram and everything tied to your account is deleted from Amplitude. There is nothing to delete anywhere else: no database, no stored messages, no account with us.

• Tell us the Telegram account the connector runs as, so we can derive the same keyed hash and find the records. We cannot search by anything else — that is the point of the hash.
• Clearing this site's data in your browser drops the consent and the device identifier, which stops the browser-side collection from your side.

What we don't collect or access

Enforced in code, not policy:

• No private chats, groups, or DMs. Absent from the data entirely — only public channels and open supergroups are visible.
• No stored messages. No database. Every question hits Telegram fresh; the answer isn't kept.
• No joining, leaving, or marking read, and nothing sent to anyone but you. Two messages go to your own account and nowhere else: a one-time greeting when you sign in, which subscribes that account to the notification bot, and any note you later ask for. Neither takes a recipient argument — there is no field that could name anyone else.
• No channel discovery. No global search, no username lookup — only what's already in your list.

Where your messages go

Message content is sent to whichever AI provider you connect — Anthropic, if you're using Claude — to answer your question. Their retention terms apply, not ours. Your Telegram credentials are held inside the access token your AI client stores; treat that client's security as part of your account's security.

Revoking access

The connection shows up in Telegram under Settings → Devices, like any other linked device. Terminate the session there and this stops working immediately — no request to us required.