How TeleTraff protects the panel and accounts
This page lists only what already works in the panel. Account security also depends on the operator: the password, the proxies and who gets access.
Updated:
Core principles
A proxy before the first connection
An account never connects to Telegram without an assigned proxy. Telegram does not see the server address.
Encrypted secrets
Account 2FA passwords and proxy passwords are encrypted when saved. Backups of session files are encrypted too.
Protected sign-in
The password is stored only as a hash. Failed attempts lock sign-in, a captcha guards the form, and 2FA can be turned on.
Session control
In settings, on the Security tab, you see active sign-ins. You can end any of them, or all except the current one.
What exactly is protected
Signing in to the panel
The password is never stored in plain text, only its hash. Session tokens are stored the same way.
Failed sign-in attempts are counted per network and per account. Each next lockout is longer, up to 24 hours.
A Cloudflare Turnstile captcha guards the sign-in form, and the server checks the answer.
Two-factor protection (a code from an authenticator app) can be turned on in settings. It is off by default.
When you sign in through the Telegram bot, the request shows the device and address the sign-in came from.
Requests that change data are checked against forgery from other sites (CSRF).
Telegram accounts and proxies
The panel never connects an account to Telegram without a proxy: the proxy first, then the first connection. The server address is not exposed.
The account 2FA password and the proxy password are encrypted, each field separately.
The 2FA password is shown only on a separate request and only to people with that right. The browser does not cache it.
Backups of session files are stored encrypted.
Workspaces
Every request is limited to your workspace. Accounts, proxies, jobs and lists of another workspace are out of reach.
Automated tests check that one workspace cannot read or change another workspace's data.
API keys
A key is shown once, when it is created. Only its hash is stored.
A key has scopes: read, messages, campaigns, webhooks, starting jobs, changes, deletion. Grant only the ones you need.
A key can be revoked at any time.
Payments
Card and SBP payments happen on the payment provider's page. TeleTraff does not receive or store card numbers.
Crypto: through CryptoBot or a transfer on TON, TRON or BSC.
Logs and reliability
Passwords, tokens and session strings are hidden when the panel shows logs and job results.
Data is backed up regularly, and service health is checked automatically.
A result in Telegram is confirmed by the actual job state. The panel does not show success without confirmation.
What the operator does
Use a unique password and turn on 2FA for the panel sign-in.
End unknown sessions and revoke API keys you no longer need.
Telegram account security also depends on Telegram itself, on proxy quality and on who you give access to.
Reporting an incident
If you notice an unknown sign-in, unexpected data change or another potential issue, stop sensitive operations and contact support.
Do not include passwords, sign-in codes, keys, session files or full payment credentials. Support will request only the minimum information needed to investigate.