Tor Onion Services
Every user runs a hidden service. Traffic is routed through 3 random nodes, making it impossible to trace who is talking to whom.
Core principlesTrue anonymity
True anonymity
by design
Built to protect identity against metadata analysis and censorship.
Identity Keys
Your User ID is an Ed25519 public key. No phone numbers. No emails. No central registry. You exist only as a cryptographic proof.
End-to-End Encryption
Messages use ChaCha20-Poly1305. Only the recipient can read them. Forward secrecy keeps past messages safe.
Serverless Topology
No central server to hack or subpoena. Messages move directly from your device to theirs via Tor.
Protocol
Smart identity merge
Most P2P messengers duplicate chats when a friend reinstalls. Burner IM detects when a contact gets a new key but keeps the same onion address (or the reverse), so you can merge history without losing trust.
fn merge_identity(old_key, new_key) {
verify_onion_signature();
update_contact_record();
}Security
Nuke it from orbit
Encryption is not enough. You need control.
- 01Granular wipe: one message, a chat, or a contact gone forever.
- 02Panic button: new identity key. Your old self vanishes from the network.
Local DB
Your data, your device
Isar stores everything locally. Tor down? History stays on your phone. Nothing in the cloud.
Not another
messenger
Burner IM vs the usual "secure" apps.
| Feature | Burner IM | Signal / WA | Telegram |
|---|---|---|---|
| Network topology | P2P (Tor) | Central server | Cloud server |
| Identity | Crypto key | Phone number | Phone number |
| Metadata | Zero | Time, IP, graph | Everything |
| Anonymity | Onion service | Linked to ID | None |
| Storage | Local only | Local + cloud | Cloud |
Questions?
Straight answers. No marketing fog.