Privacy, defined
Why PrivaMesh is the most private messenger
Most apps call themselves private. PrivaMesh is built to minimise what anyone can hold: no account database, no phone number, and a delivery path designed so the metadata is hard to link - not a promise that it does not exist.
Privacy is not a feature you bolt on. It is an architecture. A messenger is only as private as the weakest point where your data becomes visible - and for almost every “private messenger,” that point is a server. PrivaMesh is built to have no such point. This is what makes it, structurally, a truly private messenger rather than a private-ish one.
No account database, and one worker we name
There is no account database and no message store. Your messages are encrypted blobs living in Solana transaction memos, and the RPC endpoint is swappable and self-hostable. What we do run is a fee worker that sponsors each transaction so you never have to hold SOL: it sees an account and a timestamp, never plaintext and never a recipient. That is the whole of our infrastructure, and naming it is the point - a claim you can check beats one you have to trust. See every component and what it can observe, or read what PrivaMesh does not protect you from.
No phone number, no email, no identity to leak
Traditional apps tie your account to a phone number, which ties it to your real-world identity. PrivaMesh does not. Your account is a BIP-39 seed phrase that maps to a self-custodial Solana keypair. There is no phone number and no email to collect, correlate, or leak. This is what an encrypted messenger without a phone number actually looks like - an anonymous messaging app where the account is a key you generate, not an identity you hand over. See how seed-phrase accounts work.
Metadata protection, not just message encryption
End-to-end encryption hides what you say. It does nothing to hide who you talk to, when, and how often - the metadata that often matters more than the content. PrivaMesh treats metadata as a first-class threat:
- Stealth addresses - every message goes to a fresh one-time address, so watching the chain reveals no social graph.
- Cover traffic - decoy messages hide when you actually send, defeating timing analysis.
- Gas wallet - a throwaway fee payer means the wallet paying is never the wallet messaging.
That combination makes PrivaMesh a messenger that doesn’t collect metadata - because there is no collector, and the on-chain footprint is deliberately unlinkable. Explore metadata protection.
Forward secrecy and post-compromise security
PrivaMesh uses an X3DH handshake over Curve25519 and a Double Ratchet built on HKDF and HMAC-SHA256. Every message is sealed with AES-256-GCM under a key that is used once and then deleted. If an attacker ever compromises a key, they cannot decrypt your past messages (forward secrecy) and the ratchet heals to lock them out of future ones (post-compromise security). Read the encryption explainer.
Honest about the trade-offs
Real privacy comes with real trade-offs, and hiding them would be dishonest. Your seed phrase restores your funds and identity - but not your chat history. That is a deliberate consequence of forward secrecy: old message keys are destroyed, so no one, including you, can reconstruct past messages from the seed. Sending messages costs a small Solana network fee in SOL. And anonymity depends on funding your wallet with good hygiene - how you get SOL in can matter as much as the app itself. We tell you this up front because a messenger that hides its trade-offs is hiding something.
The short version
A privacy-first messenger should not require you to trust its operator. PrivaMesh doesn’t have one. Trust math, not companies.
Privacy FAQ
What makes a messenger truly private?
Three things most apps get partly right: content encryption, metadata resistance, and keeping the operator out of the message path. PrivaMesh does all three - messages are end-to-end encrypted, stealth addresses reduce linkability and optional cover traffic makes timing correlation harder, and we run no account database or message store.
Is PrivaMesh more private than Signal?
Signal has best-in-class content encryption but still runs servers that see connection metadata and requires a phone number. PrivaMesh removes both - no server to see anything, no phone number to tie to your identity.
Can PrivaMesh read my messages?
No. Encryption and decryption happen on your device with keys only you hold in the iOS Keychain, and no PrivaMesh server sits in the message path. The one worker we run pays network fees; it sees an account and a timestamp, never plaintext and never a recipient.