Telegram bot privacy mode controls how much of a group's conversation a bot receives. With privacy mode on, which is the default for every new bot, the bot only gets messages that are clearly meant for it, such as commands and replies to its own messages. With privacy mode off, or when the bot is a group admin, it receives every message in the group. That one setting explains why some bots seem to ignore you and why others can moderate everything.

This guide explains exactly what a bot sees in each case, how developers change the setting, and what group admins and members should know.

What a bot receives with privacy mode on

In a group, a bot in privacy mode receives:

  • Commands addressed to it, such as /help@yourbot.
  • General commands, such as /start, in some cases, for example when it was the last bot to send a message in the group.
  • Replies to its own messages, and to messages that explicitly ask for a reply to the bot.
  • Messages sent via the bot in inline mode.
  • Service messages, such as members joining or leaving.

Ordinary conversation between members does not reach the bot. That makes privacy mode a sensible default for bots that only respond to commands, like a dice roller, a reminder bot or a lookup tool.

Privacy mode applies to groups. In a private chat with a user, a bot always receives the messages that user sends it. In a channel where the bot is an admin, it receives the channel's posts.

What changes when privacy mode is off, or the bot is an admin

When privacy mode is disabled, the bot receives all messages in groups it belongs to. The same is true for any bot that has been made an admin of the group, regardless of its privacy setting. This is why moderation, anti-spam and keyword bots ask to be admins: they cannot filter messages they never see.

One exception holds in all cases: bots do not receive messages sent by other bots in a group. That prevents bots from triggering each other in endless loops.

SituationMessages the bot receives in a group
Regular member, privacy mode onCommands meant for it, replies to it, inline messages via it, service messages
Regular member, privacy mode offAll messages from human members
Admin, any privacy settingAll messages from human members

How developers change privacy mode

Only the bot's owner can change the setting, through @BotFather:

  1. Open @BotFather and send /setprivacy.
  2. Choose your bot from the list.
  3. Select Enable or Disable.
  4. If the bot is already in groups, remove it and add it again. The new setting may not apply to groups the bot joined before the change.

Your code can check the current state: the Bot API's getMe method reports whether the bot can read all group messages. For more on setting up a bot, see how to create a Telegram bot with BotFather.

Should you turn it off?

Only if your bot genuinely needs to read conversation. Ask yourself whether the feature could work with commands, replies or inline mode instead. Bots with privacy mode on are easier for admins to trust and easier for you to justify. If the bot needs full access only in groups where it moderates, requesting admin rights is often a cleaner design than disabling privacy mode globally, because admins then make a deliberate choice.

What group admins should check

When you add a bot, you decide how much of your group it can see. Before adding one:

  • Look at the member list. Telegram indicates whether a bot has access to messages or not, so you can see a bot's visibility at a glance.
  • Remember that admin status grants full access. Promoting a bot, even with minimal rights, means it receives every message. See how to add a bot and give it the right permissions.
  • Prefer command-only bots for simple tasks. A bot that only answers /weather has no reason to read the whole chat.
  • Trust the operator, not just the bot. What happens to messages after the bot receives them depends on the developer's servers and policies.

Moderation bots are the main case where full access is necessary and reasonable; our guide to Telegram anti-spam bots explains why.

What privacy mode does not do

The name can be misleading, so it helps to be clear about its limits:

  • It is not encryption. Group chats on Telegram are cloud chats, not end-to-end encrypted, whether or not bots are present.
  • It does not control what a bot does with messages it does receive. A command-only bot still stores whatever its developer chooses to store.
  • It does not hide your messages from human admins or members of the group.
  • It does not apply to private chats with the bot, where the bot always sees what you send it.

For members, the practical takeaway is simple: in a group with admin bots, assume that what you write may be processed by those bots' operators. That is one more reason to avoid sharing personal data in public groups, even well-moderated ones you found through a directory like the Grupla directory.

Troubleshooting common privacy mode issues

  • "My bot ignores messages in the group." Privacy mode is on. Use commands or replies, disable privacy mode and re-add the bot, or make it an admin.
  • "I disabled privacy mode but nothing changed." Remove the bot from the group and add it again.
  • "My bot doesn't see another bot's messages." That is expected; bots do not receive messages from other bots in groups.
  • "Commands go to the wrong bot." With several bots in one group, address commands explicitly as /command@botusername.

Frequently asked questions

Is privacy mode on by default?

Yes. Every new bot starts with privacy mode enabled. The developer has to switch it off in @BotFather.

Can an admin bot read all messages even with privacy mode on?

Yes. Bots that are admins in a group receive all messages from members, regardless of the privacy mode setting.

Can group members tell whether a bot reads their messages?

Partly. Telegram shows in the member list whether a bot has access to messages. What the bot's operator does with them, however, is not visible from inside Telegram.