Telegard is a 24/7 guard for Telegram accounts. It watches every active session of a connected account, asks you in a Telegram bot when an unknown login appears and terminates logins you never made — automatically, within seconds. Every connected account is also kept in Telegard’s service archive, which the service terms disclose and /mydata in the bot shows.

The guard sees the new session, messages you in the bot with “Was this you?” and two buttons: “It’s me” and “Not me — terminate”. “Not me”, or silence for the review window (5 minutes by default), terminates the session and the audit log records device, IP and reason.

No installation is required. Telegard is a web dashboard, a Telegram Mini App and a bot (@TelegardAppBot). You can additionally install the web app as a PWA on iOS, Android or desktop to get push alerts as a second alarm channel.

Channel and group owners, crypto and trading accounts, business accounts where support and sales live in Telegram, and public people whose name can be used for scams. Companies use Telegard Teams for employees’ work accounts.

Log into the dashboard through the bot, then connect the account by phone number, the Telegram login code and your two-step password if you have one — the same flow as any Telegram app. A “Telegard” device appears in your Devices list: that is the guard.

Yes. Each account connects separately and gets its own guard, rules, alerts and audit log. Accounts can be organised into groups.

English, Russian, Spanish, French and German — in the dashboard, the Mini App and the bot messages.

Telegard logs in like any Telegram app and protects you with the list of sessions; impostor protection also reads your contacts and who unknown senders are. Every connected account is also kept in Telegard’s service archive — the chat list, Saved Messages and chats Telegard staff choose to archive. The session key is encrypted with AES-256-GCM, and Disconnect deletes it together with the archive and logs the guard out. Shared channel and supergroup copies remain for other linked accounts until their retention expires or the last link is removed; legal hold can extend retention.

Some of them, and it says so up front. The guard itself only reads the session list, and impostor protection reads your contacts and who unknown senders are. But every connected account is also kept in Telegard’s service archive: the list of your chats, groups and channels, everything in Saved Messages (text and files, including the last 7 days before connecting), and the messages of any chat Telegard staff choose to archive. Telegard Teams adds a separate company archive, only for work accounts in a Teams group.

Telegard administrators, in the admin panel. It is not shown in your dashboard and never to other users or to a company, and every chat opened by support is written to the access log. It is kept for up to 365 days; /mydata in the bot shows what it holds and exports a copy, and Disconnect removes this account’s archive links and access. Channels and supergroups use a single shared copy across Telegard. Each account only sees messages archived through its own connection. Disconnecting removes that account’s links and access; the shared copy remains for other linked accounts, under the longest retention period of their teams or any legal hold, and is deleted after the last link is removed. Private chats, bots, basic groups and Saved Messages stay separate.

The encrypted guard session, snapshots of your session list (device, client, IP, location, activity), your rule settings, the audit log, the roster of people you know when impostor protection is on, and the service archive: your chat list, Saved Messages and any chat Telegard staff choose to archive, kept for up to 365 days.

On servers in the EU (Germany).

No plaintext logins are stored anywhere. Each account is an AES-256-GCM ciphertext in a separate vault, and the part of the system that faces the internet never decrypts it and has no database access to the vault. The key is held by a single internal process with no public interface, and can be kept wrapped under the owner’s password so it never sits in plaintext on disk. Any account can be wiped in one click.

Not at the moment. The security model is documented publicly on this site: session encryption, web/worker isolation, no message access, one-click disconnect.

That is the guard itself. Telegram only lets an authorized session see and manage other sessions — there is no other way to do it. The device is auto-labelled as trusted.

Never. The login code is entered only on the connect screen of the dashboard or Mini App. Anyone asking for your code in a chat is a scammer.

Press Disconnect in the account settings. It logs the guard out of your Telegram and deletes every stored record about the account, the service archive included. Shared channel and supergroup copies remain for other linked accounts until their retention expires or the last link is removed; legal hold can extend retention.

Nothing happens to your account. The guard only adds protection; without it you are simply back to plain Telegram. Sessions are never touched while the guard is offline.

The time you have to answer “Was this you?” before an unknown session is terminated. Default 5 minutes; you can set it from 0 seconds (terminate instantly) to 60 minutes.

You get a bot message with “It’s me”. One tap — the device is labelled as yours and stays. If you ignore it for the review window, the session is terminated; just log in again and confirm.

Telegram forbids any fresh session — including ours — from terminating other sessions for 24 hours after login. During that window Telegard still sees every new login, warns you instantly, marks the termination as pending and retries it by itself the moment Telegram allows it.

Every rule has three modes. Ignore: the event is logged, nothing happens. Ask: the bot asks “It’s me / Not me”; silence for the review window terminates the session. Terminate: the session is ended immediately and you get a notification.

If the device or client app changes under the same session — for example a MacBook with Telegram Desktop suddenly reports itself as Windows with another client — that is a copied session file. Telegard terminates it on sight.

If the same session is seen in two places no flight could connect in that time — Moscow at 10:00 and Amsterdam at 10:10 — the guard asks whether it was your VPN or a hijack. Trusted countries, regions and networks are skipped.

Add your VPN exit country, or the region it lands in, to the trusted list once. Impossible-travel checks skip trusted locations. You can also trust your network operator (ASN).

Yes. Tune the rules once and save them as a preset, then apply it to any account in one click — or start from a built-in one: Strict (terminate everything), Balanced or Watch-only.

Labelled devices are never touched by any rule. The first check builds a baseline: every session you already have is kept, and nothing is terminated until you turn the guard on.

Yes. Telegard does not care how you log in — it watches the sessions that result from it.

Every session event and every guard decision: who logged in, from where, when, what the guard did and why, with timestamps.

Through the bot @TelegardAppBot with buttons, and optionally through web push from the installed PWA as a backup channel. Both can be switched on or off.

Yes — that is impostor protection, a separate switch in the protection settings. Telegard keeps a roster of who your account already knows (your Telegram contacts, everyone you have a dialog with, and you) and compares every unknown sender against it before you answer. A copy of a familiar identity is reported in the bot, or blocked outright if you choose that mode.

It folds the name down to plain Latin first, so a Cyrillic “о” or a Greek “ι” hidden inside a Latin word stops disguising anything, and invisible characters are stripped. It also catches an added role word (“Pavel | Support”), a username bent by one edit (an extra underscore, a trailing digit, a zero for an o), the profile photo of a known contact matched by perceptual hash, Telegram’s own scam and fake flags, and a brand-new account. A verified account is never accused.

No. Telegram usernames are unique and ASCII-only — letters, digits and underscores — so nobody can take a handle you already hold, and there are no lookalike alphabets to hide in. An impostor has to bend it instead: add an underscore, a digit or a word like “_official”. That bending is exactly what Telegard measures. Display names and photos have no such restriction, which is why they are the main vector.

No. It looks at who the sender is — their name, username, profile photo and Telegram’s flags — and never at what they wrote.

Not directly, and no tool honestly can: those messages go to your contacts, never to your account, so Telegard never sees them. It catches impostors who write to the protected account itself or appear in a group it is in — including clones of you in those groups.

Telegram shows the list and lets you terminate sessions by hand, but does not warn you about a new login with buttons, does not terminate unknown sessions automatically, does not detect a copied session file and does not check impossible travel. Telegard adds all of that on top of the same list.

No. 2FA stops password-based logins, but three of the four common takeovers bypass it: QR / “confirm login” phishing, stolen desktop session files and SIM swap ask for no password at all. Keep 2FA on and add the guard.

No. Use both. 2FA closes one door; Telegard watches the sessions that appear through the others.

An antivirus tries to stop the session file from being copied. Telegard catches the result — a session that changed device or appeared where it should not — and terminates it, no matter how the attacker got in.

The check is free, always. The 24/7 guard (automatic termination, bot alerts, stolen-session and travel rules, audit log) is free during beta. Telegard Teams is free during beta at 0 per seat.

Paid plans are announced 30 days ahead. Early organizations get 50% off the first year.

A full session scan, risk findings with critical ones first, manual termination — and Telegard logs out after the check.

The same guard applied to a company’s work Telegram accounts, plus an archive of every chat (deleted and edited messages kept, files encrypted per group), full-text search and export, retention and legal hold, DLP rules, reply-time analytics with AI digests, and a reactive assistant: drafts for people, autonomous replies only for AI-agent accounts, always disclosed, never writing first. Free during the beta; an account group is the organization, nothing else to set up.

Turn on “Teams” for an account group in the dashboard, then either connect the account yourself (the account becomes a work account at once; the employee sees the “Telegard” session in Telegram → Devices) or send the employee an invite link /join/<token>, through which they connect the account themselves in the company’s group.

Consent is the login itself: the employee enters the Telegram code on the account, and Telegram shows the “Telegard” session in Devices with its own “Was this you?” prompt. There is no extra bot confirmation. To stop, the employee terminates that session in Telegram → Devices; archiving stops at once and stored chats are deleted after 30 days unless a legal hold is set. /mydata in the bot shows what is stored and exports a copy.

Only on a confirmed managed account, in the Chats tab, and every view is written to the access log. The employee can ask the bot with /mydata what is stored about their account. A company never sees accounts outside its own Teams groups.

Everything is built and in beta: the archive with deleted and edited messages, full-text search, export, retention and legal hold, DLP rules, analytics and digests, and the reactive assistant. Beta means it is free and still being verified in real use.

Teams is part of the same application and the same database. The archive is a set of tables both processes work with; only the worker process holds the session keys, the encrypted media files with their key, and the AI key, and the web process has no database right to write, rewrite or delete message text. A company’s archive holds only accounts of its own groups with Teams on; separately, every connected account is kept in Telegard’s own service archive.

From any device where Telegram is still open: Settings → Devices → Terminate all other sessions, then change the two-step password. If no device is left, sign in by phone number and reset the password. Check devices again, warn your contacts, and if SMS stopped arriving contact your operator about a SIM swap. The full guide is at telegard.app/recovery.

Someone terminated the guard’s session — if it was not you, someone else has access to your Telegram. Follow the recovery guide, then connect the account again and switch the guard to Armed.

Yes, if the guard is armed: the attacker’s session is an unknown login and is terminated after the review window. In the first 24 hours after the guard connected Telegram blocks termination, so act from a device you still hold first.