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. It never reads your messages.

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 uses one thing: the list of sessions. Messages, contacts and media are never requested. The session key is encrypted with AES-256-GCM, and Disconnect deletes it and logs the guard out.

No. Telegard never reads, stores or indexes messages, contacts or media. The guard only reads the session list. The single exception is Telegard Teams, where a company can view the chats of a work account only after the employee confirmed it from that account.

Only the encrypted guard session, snapshots of your session list (device, client, IP, location, activity), your rule settings and the audit log. Never your chats.

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.

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.

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 company features with employee consent: one-click offboarding with client handover, profile protection, an access log, a chats view, and an archive/DLP/analytics roadmap. Beta, free.

Turn on “Teams” for an account group in the dashboard, then either connect the account yourself (the bot asks the employee’s account to confirm) or send the employee an invite link /join/<token>, through which they connect the account themselves in the company’s group.

Yes. Monitoring starts only after the employee confirms it from the work account itself; that confirmation is the record of consent. Without it the account only gets the guard, without any company features.

Only on a confirmed managed account, in the Chats tab, and every view is written to the access log the employee can see. Personal Telegard accounts are never readable.

The archive with deleted and edited messages, full-text search, export, retention and legal hold is in progress. Analytics, digests and an AI assistant are planned. No dates are promised.

Teams runs as a separate process on a separate database. A chat is stored only for an account with a recorded consent — a rule checked by tests on every change.

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.