Guide

Telegram Bot Privacy Mode: What It Does and How to Change It

2026-10-30

Telegram Bot Privacy Mode: What It Does and How to Change It

Telegram bot privacy mode is a filter on group chats. When it is on, which is the default, your bot sees only the messages meant for it: commands, mentions and replies. When it is off, the bot sees every message in the group, like an ordinary member. If your bot answers in a direct message but goes quiet in a group, this setting is almost always why.

This guide explains exactly what the filter lets through, how to check and change it, what to do when the change does not seem to work, and how it relates to rate limits and to the privacy of the people in your group. We wrote it with AI assistants in mind, because that is where the setting causes the most confusion.

TL;DR

  • Privacy mode is on by default. A bot in a group receives only commands, mentions, replies to its own messages and a few other addressed messages.
  • To change it, use BotFather, then remove the bot from the group and add it again. Without re-adding, the change does not apply.
  • Making the bot a group administrator also lets it see messages, so check its role if behavior seems inconsistent.
  • Privacy mode is not encryption and not a permission system. It limits what the bot receives, not what the bot does with it.
  • Telegram limits bots to about one message per second in a chat and 20 messages per minute in a group, so a chatty assistant needs pacing.

Table of Contents

What privacy mode actually does

Telegram's Bots FAQ describes privacy mode as a filter on what a bot receives from groups. With it enabled, the bot gets explicitly addressed commands, certain general commands, messages sent via the bot, and replies to messages meant for it. Everything else in the group never reaches your code.

Three categories always get through, whatever the setting:

  • Service messages, such as someone joining or leaving.
  • Messages in private chats with the bot.
  • Messages from channels where the bot is a member.

Telegram also explains the design reasoning on its Bot Features page: the mode protects user privacy and also makes bots more efficient, because they process fewer inputs. That second point matters in practice. A bot that has to read every message in a busy group spends compute, and if it is an AI assistant, money, on text nobody addressed to it.

What a bot sees in each mode

Message in a groupPrivacy mode onPrivacy mode off
Command addressed to the bot (for example `/ask@yourbot`)ReceivedReceived
Message that mentions the bot by usernameReceivedReceived
Reply to one of the bot's own messagesReceivedReceived
Ordinary chat between membersNot receivedReceived
Service messages (joins, leaves)ReceivedReceived
Messages from other botsGenerally not receivedGenerally not received

The last row surprises people. Per the Bots FAQ, bots ordinarily do not see messages from other bots, regardless of privacy mode, to prevent bot-to-bot loops. Telegram's bot-to-bot documentation describes limited exceptions: a bot may receive another bot's message when it contains a command mention addressed to it or replies directly to one of its messages, and at least one of the bots has Bot-to-Bot Communication Mode enabled.

Privacy mode is not permissions and not encryption

These three ideas get mixed up constantly, and mixing them up leads to bad decisions.

Privacy mode controls what the bot receives from a group. It is a filter on input.

Permissions control what the bot can do in the group: delete messages, pin, invite users, and so on. Those come from the administrator rights you grant. A bot with no admin rights can still read everything if privacy mode is off.

Encryption concerns how data travels and is stored. Telegram's regular chats, including group chats and bot chats, are not end-to-end encrypted by default. Telegram's FAQ is also candid that a bot is a stranger to you: seeing a message is not the same as being trustworthy, and a bot is run by whoever operates it.

Privacy mode, bot permissions, and encryption compared

So turning privacy mode on reduces exposure, but it says nothing about where the bot stores the messages it does receive, or whether the operator logs them. That is a hosting and data-handling question, which we come back to below.

How to check your bot's privacy mode

You have three reliable ways to see the current state.

  1. Look at the group member list. Telegram's FAQ says the list shows "has no access to messages" next to a bot in the default restricted mode, and "has access to messages" once privacy mode is disabled.
  2. Ask the Bot API. The getMe method returns a field called can_read_all_group_messages. According to the Bot API documentation, it is true when privacy mode is disabled. This is the best check for scripts and monitoring.
  3. Test it. Post an ordinary message in the group without mentioning the bot. If your logs show nothing, the filter is on.

The getMe check is worth building into your startup routine. It takes one call and tells you immediately whether a deployment will be deaf in groups.

How to turn privacy mode off (or back on)

The Bot Features page says group privacy is enabled by default for bots added to groups, except bots added as administrators. Disabling it makes the bot receive all group messages, and the bot must be re-added to the group for the change to take effect.

Here is the sequence:

  1. Open a chat with BotFather in Telegram.
  2. Send /mybots and pick the bot you want to change.
  3. Open Bot Settings, then Group Privacy.
  4. Choose Turn off to let the bot read all messages, or Turn on to restrict it again.
  5. Remove the bot from each group where it is already a member.
  6. Add it back.
  7. Confirm with the member list label or with getMe.

Step 5 and 6 are the ones people skip. Telegram applies the setting when the bot joins, so a bot that was already in the group keeps its old behavior until you re-add it.

The administrator shortcut

Because bots added as administrators are exempt from the default restriction, promoting the bot to admin also lets it see group messages. That can be convenient, but it hands the bot rights you may not want it to have. If you only need message visibility, disable privacy mode and keep the bot a regular member. If the bot needs to moderate, promote it and grant only the specific rights it requires.

If the bot is still silent in the group

When the setting looks right but nothing arrives, work through this list in order.

  1. Was the bot re-added after the change? This is the cause far more often than anything else.
  2. Is it the right bot? Teams often have a test bot and a production bot with similar usernames. Check that the one in the group is the one you configured.
  3. Does getMe report can_read_all_group_messages as true? If not, the setting did not save. Repeat the BotFather steps.
  4. Is another process polling the same token? If two instances call getUpdates, or a webhook is set while you poll, updates go to the wrong place or fail with conflicts. Use one delivery method per token.
  5. Is your code filtering the messages out? Some frameworks ignore group text unless it matches a command handler. Log raw updates before any filtering.
  6. Are you expecting messages from another bot? As covered above, those are not delivered by default, whatever the privacy setting.
  7. Is the group a supergroup or a channel? Channels behave differently from groups: bots receive posts from channels where they are members, but the discussion in a linked group is a separate chat with its own membership.

If you want a bot that behaves well in a group without reading everything, there is a middle path. Leave privacy mode on and design the interaction around mentions and replies. Users address the assistant explicitly, and the bot never sees side conversations. For an AI assistant this is often the better product decision, not just the safer one.

Privacy mode and the people in your group

A decision to turn privacy mode off is a decision about other people's messages. Members of the group did not necessarily agree to have an AI read their conversation, and some of them will notice the "has access to messages" label.

Telegram's FAQ gives sensible baseline advice for anyone dealing with bots: never give a bot passwords, Telegram login codes or bank account numbers, be careful with files that bots send, and avoid untrusted bots in sensitive groups. As a group owner, add to that:

  • Know who operates the bot. A bot is code running on somebody's server. If you cannot say whose, do not give it access to the whole conversation.
  • Minimize what it sees. Keep privacy mode on unless the use case truly needs full visibility, and keep sensitive discussions in groups without bots.
  • Ask what is stored and for how long. Message logs, conversation memory and backups are all retention. A bot that has persistent memory keeps things on purpose, so decide what it should remember.
  • Tell your members. One pinned message saying what the assistant reads and what it keeps removes most of the discomfort.

For developers, there is a separate privacy risk that has nothing to do with the group setting: your bot token. Anyone holding it can act as the bot. We cover that in our guide to Telegram bot security.

Rate limits: the other thing that makes a bot look broken

Once privacy mode is off and your assistant sees a whole conversation, it is tempting to let it respond often. Telegram will stop you. The Bots FAQ sets out the limits:

SituationLimit
One chatAvoid more than about one message per second
One groupNo more than 20 messages per minute
Free broadcastAbout 30 messages per second
Paid broadcastUp to 1,000 messages per second, with Telegram's eligibility and Stars requirements

Exceeding the single-chat or broadcast limits can return an HTTP 429 error. Treat that as a signal to back off, not to retry in a tight loop. A reasonable pattern for an assistant:

  • Queue outgoing messages per chat and space them out.
  • Honor the retry delay the API returns with a 429.
  • Combine short consecutive replies into one message.
  • Prefer editing a streaming reply over sending many small ones, and keep edits infrequent.
  • Log every 429 so you can see when a group is saturating the bot.

The 20-per-minute group cap is the one that bites AI assistants. A model that streams long answers in many chunks, in a group where several people ask questions at once, can hit it quickly. Pacing and batching solve most of it. Telegram's bot-to-bot documentation also stresses deduplication, per-chat and per-bot limits, and maximum interaction depth to stop automated reply loops, which is a good design habit even if you never connect two bots.

For a team that wants these concerns handled by someone else, our write-up on Telegram AI bot hosting covers the operational checklist, and the one on safer Telegram automation for teams covers deduplication.

Our perspective: treat privacy mode as a product decision

We run managed hosting for OpenClaw, an open-source AI assistant, and Telegram is one of the most common places people connect it. The pattern we see in support questions is predictable. The assistant works perfectly in a direct message, someone adds it to a group, and it appears to ignore everyone. The cause is the default filter, not a fault in the assistant or the server.

Our perspective: treat privacy mode as a product decision — overview diagram

Our view is that the default is a good one, and that most group assistants should keep it. An assistant that responds when addressed is easier to trust, cheaper to run, and less likely to surprise your members. Turn privacy mode off when the assistant has a job that needs context from the whole conversation, such as summarizing a thread, tracking decisions or answering questions that refer to earlier messages. In that case, make it a deliberate choice, tell the group, and decide what the assistant's memory is allowed to retain.

The other half of privacy is where the assistant lives. Privacy mode governs what Telegram delivers to your bot. It does not govern what happens afterward. That is why we run each OpenClaw agent on its own dedicated, encrypted cloud server rather than a shared one, with daily encrypted backups, so the messages your assistant receives stay in an environment that belongs to you. If you want to see how the connection is built, our developer's guide to connecting an AI assistant to Telegram walks through it.

> *— Iosif Peterfi*

Run it without the sysadmin work

If you would rather spend your time on what the assistant does than on servers, tokens and uptime, ClawBase deploys OpenClaw on a dedicated server in one click and connects it to Telegram, Discord, Slack and WhatsApp. Plans start at $16 per month for LITE, or $199 per year, with PRO at $33 per month ($399 per year) and MAX at $66 per month ($799 per year). The entry plan includes a 7-day free trial. You can see the details on the ClawBase pricing page, or browse what OpenClaw agents can do first.

Clawbase

After that, the group behavior is still yours to decide: the privacy mode steps above apply to your bot's token in BotFather, whichever way you host it.

FAQ

Does privacy mode stop a bot's creator from reading my messages?

No. Privacy mode only limits which group messages Telegram delivers to the bot. Anything the bot does receive, including every message you send it in a private chat, is visible to whoever operates it. Check who runs a bot before sharing anything sensitive.

Do I need to re-add the bot after changing group privacy?

Yes. Telegram's Bot Features page says the bot must be re-added to the group for the change to take effect. Remove it, add it again, then confirm with the member list label or the can_read_all_group_messages field from getMe.

Why does my bot work in private chat but not in groups?

Privacy mode is on by default, and private chats are exempt from it. In a group the bot only receives commands, mentions and replies to its own messages. Mention it, reply to it, or disable privacy mode and re-add it.

What are the Telegram bot rate limits?

Per Telegram's Bots FAQ, avoid more than about one message per second in a single chat and stay under 20 messages per minute in a group. Free broadcasts run at about 30 messages per second. Going over can produce HTTP 429 errors, so queue messages and respect the retry delay.

Can a bot see messages from other bots in a group?

Generally no, whatever the privacy setting. Telegram blocks this to prevent loops. Limited exceptions exist for commands addressed to the bot or direct replies, and they need Bot-to-Bot Communication Mode enabled on at least one of the bots.

Sources

Recommended