Scope of responsibility (operator, platform, users)

What this page is

A decision-focused description of how responsibility is commonly separated among:

Telegram (the platform)
A bot operator (the party running the bot)
End users (people interacting with the bot)

What this page is not

Legal advice
A guarantee of safety, compliance, or outcomes
A statement about any specific bot’s behavior

Definitions and scope

Platform: Telegram’s infrastructure, policies, and enforcement mechanisms.
Bot operator: The party who configures, deploys, or controls the bot’s code and data processing.
End user: A person who chooses to interact with the bot and provides inputs.

Decision points

Whether a bot exists for a given purpose
What features are enabled or disabled by default
What data is collected, stored, and shared
How the bot responds to sensitive or high-risk requests

Responsibility boundaries

Platform responsibility (typical)
Setting and enforcing platform-wide rules and abuse reporting channels
Providing technical primitives and access controls
Operator responsibility (typical)
Defining the bot’s capabilities, defaults, and safeguards
Communicating scope and limits of the bot to users
Choosing data retention and access controls for any data the operator stores
User responsibility (typical)
Choosing whether to use the bot and what information to provide
Using the bot within applicable rules and policies

These boundaries can overlap. When boundaries are unclear, state assumptions explicitly (for example: who controls hosting, who can access logs, and what features are enabled).

Typical evidence to document

Public description of the bot’s purpose and limits
Feature list and default settings
Data map: inputs, storage, retention, sharing
Abuse-handling approach (what is detected, what is blocked, what is logged)

Open questions

Who has operational control (keys, hosting accounts, admin access)?
What information is stored outside Telegram (if any)?
What user expectations are created by the bot’s wording and UI?