Privacy

Bot tokens

A bot token is a secret, and this site is built so that it never receives one. The token checker and the webhook checker send the token from your browser directly to api.telegram.org. It is held in the page's memory only — not in a cookie, not in local storage, not in the address bar — and is gone when you press Clear or close the tab. No endpoint of this site accepts a token: the lookup refuses anything shaped like one before reading it, and a token pasted into the contact form is cut out before the message is stored.

Tools that run in your browser

The ID converter, the message link parser, the getUpdates inspector and the MarkdownV2 escaper are JavaScript on the page. What you type or paste into them is not sent anywhere.

The public lookup

When you look up a public @username, the name is sent to our server and passed to the lookup service that asks Telegram's Bot API. The answer is cached for up to 24 hours so the same name is not asked twice. For the statistics on the home page we count each lookup — the time, how long it took, whether a chat was found and its type. The name and the ID are not part of that count.

Rate limits

To stop abuse, lookups and the contact form are limited per connection. For this we keep a one-way, salted hash of your IP address for up to 24 hours — never the address itself.

Visiting

Telegram Chat ID sets no tracking cookies. If analytics are switched on, a self-hosted Umami instance counts page views without cookies and honours Do Not Track. Your light or dark choice is saved in your browser only.

Contact form

When you write to us we store your name, email address, subject and message so we can answer, and forward them to the site owner's inbox. Messages are never sold or shared.

Admin

The only cookie is the site owner's admin session, set when the owner signs in.

Questions

Write to contact@telegramchatid.xyz.