Our approach to privacy

Private by design, not by policy

We built a messaging platform that cannot read your messages, because the architecture makes it technically impossible.

Built on three principles

Every technical decision follows these guidelines.

Zero-knowledge architecture

The server acts as a blind router, handling encrypted data without decryption capability.

Messages encrypted before transmission
Servers never receive decryption keys
Technical impossibility of reading content

Minimal data collection

We collect only what's necessary for message delivery, never for analysis or profiling.

No behavioral tracking
No message content analysis
No third-party data sharing

Transparent implementation

Using established cryptographic standards that can be verified and audited.

Open cryptographic protocols
Verifiable implementation
No proprietary encryption

How end-to-end encryption works

Messages are encrypted on your device before transmission.

Local key generation

Your device generates an encryption key pair. The private key never leaves your device.

// Generated and stored on device

const keyPair = generateKeyPair()

Public key: shared for encryption
Private key: stays on your device

Message encryption

Each message is encrypted with a unique key, which is then encrypted with the recipient's public key.

Message

Plaintext on device

Encryption

Using recipient's public key

Encrypted message

Sent to server

Server-side routing

Servers handle encrypted data without the ability to decrypt it.

Message routing server

Cannot decrypt

Encrypted message

e2g7a...c9f3

Recipient identifier

user_123

Server cannot access message content

Technical implementation

Cryptographic standards

X25519

Key exchange

Curve25519 elliptic curve

XSalsa20-Poly1305

Message encryption

Authenticated encryption

Argon2id

Key derivation

Memory-hard hashing

Security properties

Forward secrecy: Each message uses unique encryption
Authentication: Message integrity verification
Zero-knowledge: Server cannot decrypt messages
Device-based: Keys generated and stored locally

Open standards

We use established, audited cryptographic libraries and follow documented standards.

libsodiumWebCrypto APIEstablished standards

Infrastructure approach

Minimal server processing: Focus on routing, not content

Encrypted storage: Data at rest is encrypted

No message scanning: Servers handle data opaquely

Stateless design: No persistent decryption capability

Privacy features

Beyond basic encryption

Disappearing messages

Messages that delete automatically after being read.

Timer starts when message is read
No server-side processing required
Local deletion confirmation

Verification

Verify encryption keys with contact-specific fingerprint.

Unique fingerprint representation with emojis
In-person verification option
Key integrity confirmation

Device security

Local encryption for private key storage.

Password-protected key access
Local decryption only
No key transmission

Private messaging should be simple

We built a platform that respects your privacy by design, not just in policy.