What You See vs. What the Server Sees
On your device: a normal conversation. On the wire: indistinguishable noise.
A Conversation That Never Existed
No accounts. No phone numbers. No metadata. Two inboxes, a shared secret, and silence.
Create Ghost Inboxes
Both sides create one in the browser — no account, no phone number
Exchange Secrets
Swap inbox secrets over any channel you already trust
Linked Private Thread
Link the inboxes and chat. Encryption happens on your device; the server sees noise.
Forensically Destroyed
The ephemeral key is shredded first, then the blob is overwritten. Nothing to recover.
Privacy by Architecture, Not by Promise
A subpoena yields nothing readable. The design has nothing to give.
Zero-Knowledge
Encryption keys never leave your device. The server cannot read your messages — not by policy, by math.
No Identity
No phone number. No email. No name. Your "identity" is a key pair generated locally and discarded.
No Metadata
We do not log who you spoke to, when, or how often. There is nothing to leak because nothing is collected.
Self-Destruct
Messages delete after reading. No history. No backups. No recovery — by design, not by accident.
Two-Way Anonymous
Both participants remain unknown to each other beyond the conversation itself. No profiles, no contact lists.
Open Verifiable
Crypto primitives are public standards: XChaCha20-Poly1305 with HKDF-SHA512 — the cipher behind Signal, WireGuard and Cloudflare. No secret sauce.
Phantom is built on a principle rather than a promise: the service should have no ability to read, retain, or hand over your conversations. Every message is encrypted in your browser with XChaCha20-Poly1305 — the cipher behind Signal, WireGuard and Cloudflare — using HKDF-SHA512 key derivation. Keys never leave your device, and the server only ever sees encrypted blobs sitting at opaque addresses.
Conversations run on Ghost Inboxes. Both sides create one, exchange secrets, and link them into a private thread — no account, no phone number, no app install, no contact graph. Messages auto-expire on a schedule you or the receiver set, and view-once content is destroyed after a single read.
Deletion is forensic rather than cosmetic. Each message is wrapped with a unique ephemeral key held separately; the key is destroyed first, which leaves the data mathematically dead, and the blob is then overwritten before deletion as defence in depth. The same treatment applies to Ghost Inbox drops and view-once content, on both client and server.
The architecture also removes your IP address from the equation. Every request passes through an edge privacy relay that strips your IP and replaces it with a one-way cryptographic identifier before it reaches the backend, so rate limiting and abuse protection work without anyone knowing who you are — no Tor, no VPN, no configuration. Forwarding headers, proxy metadata, browser fingerprints and client hints are stripped at the edge, and response times are normalized with random delays to resist timing correlation.
Key Features
Ghost Inbox
Both sides create a Ghost Inbox and exchange secrets, then link them into a private encrypted thread — no accounts, no phone numbers, no app install, no contact graph.
Self-Destructing Messages
Every message auto-expires on a schedule you set per chat, or one the receiver chooses. View-once content is permanently destroyed after a single read.
Forensic Deletion
Each message is wrapped with a unique ephemeral key stored separately. The key is destroyed first — leaving the data mathematically dead — and the blob is overwritten before deletion.
Your IP, Never Seen
An edge privacy relay strips your IP and replaces it with a one-way cryptographic identifier before any request reaches the backend. No Tor, no VPN, no configuration.
Zero Metadata
No accounts, no phone numbers, no IP logs, no contact graph. The server sees only encrypted blobs at opaque addresses — there is nothing to subpoena.
Fortress Mode
Lock the whole app behind a passphrase or biometrics, with auto-lock on inactivity, screenshot masking in the app switcher, and an instant panic wipe.
Hardware Security Keys
Protect the app lock with a YubiKey or any FIDO2 key, and optionally require a physical key to encrypt an individual message.
Works Offline
Compose, encrypt and queue messages with no connection at all — the crypto runs on your device. Everything syncs the moment you reconnect, including pending deletions.
On Every Platform
A native Windows desktop app with no Electron bloat, a native Android app, and an installable PWA that runs from the browser — the same zero-knowledge encryption on each.