SEAL for Telegram
Drop a file in chat. Get an encrypted link back.
Verified delivery, a signed audit trail, and a kill switch, from a chat you already have open.

Proof of delivery. Not hope of delivery.
Some files carry consequences: a patient record, a case file, a term sheet. Send one as a plain attachment and you learn nothing. Did it arrive, who opened it, where did it travel next? SEAL for Telegram answers with evidence. The bot encrypts your file before it reaches SEAL storage and returns a link you control: every access lands in a cryptographically signed audit log, when it was opened and from which country, so delivery is something you can show, not something you assume.
And control does not end at sending. Put a password on the file. Give it a lifetime, five minutes or seven days. Let it die after a single download, or revoke it at any moment and the encrypted bytes are physically destroyed. For the strictest handoffs, require a signed NDA before the download starts, and the signature joins your audit trail. The SEAL backend stays zero-knowledge throughout: it stores ciphertext, never keys, never contents.
A signed access log records every open: time and country. Proof you can show, not a delivery you assume.
Lifetime from 5 minutes to 7 days, single-download mode, or revoke at any moment. Gone means destroyed.
Require a password, or a signed NDA before download, and the signature lands in your audit trail.
From chat message to sealed link.
Send a file to @Sealnetbot
Any document, photo, archive or video. Sending is implicit: no command needed, the bot treats every file as “seal this”.
The bot encrypts and mints a seal
AES-256-GCM content encryption with encrypted filename and metadata, before anything reaches SEAL storage. Your saved defaults (expiry, password, single-use, download caps, geo allowlist) apply automatically.
Two links come back
A share link with a QR code for your recipient, and a manage link for you. The recipient opens the file on seal.net in one click, with no account and no Telegram required on their side.
Receiving is implicit too
Paste any seal.net share link into the chat and the bot returns the decrypted files. NDA-gated seals and links sealed to an address hand off to the browser, where the signing ceremony and the recipient’s inbox live.
Set defaults once with /settings (TTL, password, single-use, max opens, geo, owner email) and every future send uses them. The full command set (list, status, files, append, share mint/list/revoke, import, keygen, revoke) is in the documentation.
The Mini App encrypts on your phone.
Chat flows are convenient, and honesty about their price matters: the bot encrypts on its host, so a file you drop in chat transits Telegram’s infrastructure in plaintext before it is sealed. For documents that must never touch anyone’s servers unencrypted, launch the SEAL Mini App from the bot.
The Mini App runs the same client-side encryption engine as seal.net, inside Telegram’s webview on your device. Files are encrypted locally, plaintext never leaves the phone, and the key rides the link fragment: the same guarantee the web app gives, without leaving Telegram.
Zero-knowledge backend. Honest edges.
SEAL’s servers cannot read your files. They store ciphertext, check its length and enforce access rules (expiry, download caps, geography, revocation) without ever holding a key; the recipient checks the content. Owner tokens for seals created in chat are encrypted at rest on the bot; notifications are HMAC-signed; the bot checks the signature of Telegram’s data when the Mini App hands it a subscription.
What SEAL cannot vouch for is Telegram itself. That is exactly why the Mini App exists, and why this page tells you the difference instead of hiding it.
Questions, answered.
- Who is this for?
- Anyone whose files carry weight: doctors sending records, lawyers sharing case files, brokers passing deal documents, and anyone for whom a plain attachment feels careless. No IT department required: if you can use a chat, you can use SEAL.
- Is SEAL for Telegram free?
- Yes. The free tier gives every seal up to 1 GB and up to 7 days of life, with the full access-rule set. One-time upgrades extend a single seal to 5–500 GB for 3–12 months.
- Does my recipient need Telegram or an account?
- No. The share link opens on seal.net in any browser. Recipients need no account, no app and no Telegram.
- What happens when a seal expires?
- Access closes and the encrypted bytes are physically deleted from storage. Expiry is enforced by a burn job, not just hidden behind a 410 page.
- Can I take back a file I already sent?
- Yes, at any time: /revoke in the chat or the Revoke button on your manage page. Recipients see “Seal Revoked” and the ciphertext is destroyed.
- Which access rules can I set from the chat?
- Expiry (5 minutes to 7 days), password (OTP), single-use, maximum opens, a country allowlist, and an NDA gate with your owner email. Per send, or saved as defaults with /settings.
One seal. Every platform.