---
title: "Responsible use"
locale: en
url: https://tlg.builera.app/en/docs/safety/acceptable-use
verified: 2026-10-24
app_version: "2.0"
---

# Responsible use

Use authorized accounts and data, respect recipients, and do not use automation to send unwanted content.


Telegram-Auto helps you operate personal Telegram accounts in a workspace. Automation does not replace the account owner's consent, permission to contact recipients, or your obligation to follow Telegram's terms.

## Use only authorized accounts

Only add accounts you own or accounts whose owners have authorized you to operate them. Your team needs to agree on who can read conversations, send messages, and change settings.

Do not buy or sell accounts, import purchased sessions, or create fake accounts in bulk. Do not use a colleague's access after they have withdrawn permission.

A sign-in session grants account access. It is not an ordinary data file to pass around in messages. An account appearing in a workspace does not mean every member should use it.

## Respect recipients

A personal account is not a tool for distributing spam. You need an appropriate basis for contacting someone, and your content must match the recipient's expectations.

- Do not treat seeing someone in a group as consent to receive advertising.
- Do not use multiple accounts to send the same content to the same person.
- Do not keep reaching out after a recipient asks you to stop.
- Do not move someone who has opted out to another campaign or account to keep contacting them.
- Do not automatically add people to groups in bulk.

The app detects opt-out requests, including forms such as STOP. When someone is added to the do not contact list, the block applies throughout the workspace, not just to one campaign. Automatic detection cannot understand every expression for you. Act on clear stop requests that you read.

See [Do not contact list](https://tlg.builera.app/en/docs/concepts/do-not-contact) to understand its scope.

## What the app checks and rejects

| Situation | How the app handles it |
|---|---|
| The recipient is on the do not contact list | The safety gate prevents the contact task from proceeding. |
| The account is stopped, restricted, or ineligible | The job is held or rejected for the corresponding reason. |
| A valid proxy, session, or suitable machine is missing | Jobs are not assigned as though the account were ready. |
| An AI connection lacks permissions, scopes, or budget | The call cannot run outside its granted scope. |
| Telegram requires a wait or verification | The app respects the requirement and does not complete verification on its own. |
| Demo workspace | No real Telegram effects are performed. |

Software cannot detect every behavior prohibited by the acceptable-use policy. Passing technical checks does not prove that a recipient has consented.

## Automation gets no exceptions

Messages you type, templates you write, and commands from external systems all pass through the same safety gate. **Free** mode does not skip the do not contact list, safety states, or Telegram's wait requirements.

The app has no built-in AI that decides content on its own. External AI acts only through a connection with its own permissions. You still need to check the purpose, recipients, and assigned actions.

> [!IMPORTANT]
> If Telegram asks you to accept terms, complete verification, or resolve a restriction, use Telegram's official process. Do not switch accounts or network routes to continue behavior that was just blocked.

## Related

- [Telegram limits](https://tlg.builera.app/en/docs/safety/telegram-limits)
- [AI connections](https://tlg.builera.app/en/docs/integrations/ai-connections)
- [Internal accounts](https://tlg.builera.app/en/docs/concepts/internal-accounts)
- [Keep access secrets safe](https://tlg.builera.app/en/docs/safety/keep-secrets)