Security
This page describes what protects your key, and — just as important — what does not.
What is stored, and where
Your 24-word phrase is encrypted with your password using PBKDF2-SHA256 at 600,000 iterations and AES-GCM-256, through the browser's own WebCrypto implementation. The result lives in this browser's local storage. The password is never stored.
If you choose "stay unlocked until this tab closes", the decrypted phrase is held in that tab's session storage and dropped when the tab closes. Locking the wallet, or the idle timeout, removes the key from memory.
What this cannot protect against
- A browser wallet shares a process with web pages. Malicious code running in this page while the wallet is unlocked can reach an unlocked key. Encryption at rest does not help there.
- Browser extensions with page access can read and alter what you see, including a recipient address.
- Anyone with access to your unlocked device and tab can sign.
- Clearing site data destroys the vault. Without the phrase or an encrypted backup it is gone.
There has been no external security audit of this code. Nobody has reviewed it on your behalf. Treat it as software you are choosing to trust yourself.
Check the domain
Confirm the address bar reads tongram.net before unlocking. A wallet interface is a natural phishing target; a lookalike domain will happily show you the same screens.
Reporting a vulnerability
A disclosure channel is not published yet. Until one is, please do not post exploit details publicly — there is no process here to respond to them safely.
Supported browsers
Recent Chrome, Safari, Firefox and Edge, plus the Telegram in-app browser. WebCrypto and the History API are required; a browser without them cannot run the wallet.