Security and responsible use
A safer operating model for authorized Telegram communication
Security is built around server-side secrets, isolated account data, controlled access, and transparent delivery records. The platform is intended only for groups and channels that the connected account is authorized to use.
Protected credentials and sessions
Passwords are stored as one-way hashes. Telegram sessions are encrypted at rest and are never returned to the frontend. Verification codes and two-step verification passwords are not retained as reusable credentials.
User and account isolation
Backend queries scope accounts, destinations, templates, destination sets, and automations to the authenticated user. Within a workspace, destination records remain tied to the Telegram account that discovered them.
Access and login controls
Username and password authentication is protected by CAPTCHA support, repeated-attempt cooldowns, token invalidation, role checks, and administrator-only controls. Private dashboard pages are explicitly excluded from search indexing.
Telegram safeguards remain in force
TelegramAutomation does not bypass rate limits, flood controls, bans, mute restrictions, or destination permissions. A permission failure can stop delivery to that destination and classify it for operator review.
- Use only accounts and destinations you are authorized to manage.
- Choose conservative intervals and relevant messages.
- Review delivery results and remove invalid destinations promptly.
Prepare a controlled deployment
Follow the automation guide for a practical permissions, testing, scheduling, and monitoring checklist.