Privacy redefined

The first messenger
without user IDs

Other apps have user IDs: Signal, Matrix, Session, Briar, Jami, Cwtch, etc.
SimpleX does not, not even random numbers.
This radically improves your privacy.

Why user IDs are bad for privacy? How does SimpleX work?

Make a private connection

The video shows how you connect to your friend via their 1-time QR-code, in person or via a video link. You can also connect by sharing an invitation link.

Why privacy matters

Preserving the privacy of your metadata — who you talk with — protects you from:

Advertising and price discrimination

Privacy saves you money

Manipulation of elections

Privacy gives you power

Prosecution due to innocent association

Privacy protects your freedom

Make sure your messenger can't access your data!

Why SimpleX is unique


You have complete privacy

SimpleX protects the privacy of your profile, contacts and metadata, hiding it from SimpleX platform servers and any observers.

Unlike any other existing messaging platform, SimpleX has no identifiers assigned to the users — not even random numbers.

Learn more


You are protected
from spam and abuse

Because you have no identifier or fixed address on the SimpleX platform, nobody can contact you unless you share a one-time or temporary user address, as a QR code or a link.

Learn more


You control your data

SimpleX stores all user data on client devices in a portable encrypted database format — it can be transferred to another device.

The end-to-end encrypted messages are held temporarily on SimpleX relay servers until received, then they are permanently deleted.

Learn more


You own SimpleX network

The SimpleX network is fully decentralised and independent of any crypto-currency or any other platform, other than the Internet.

You can use SimpleX with your own servers or with the servers provided by us — and still connect to any user.

Learn more


E2E-encrypted messages with markdown and editing

images and files

Decentralized secret groups —
only users know they exist

E2E-encrypted voice messages

Disappearing messages

audio and video calls

Portable encrypted database — move your profile to another device

Incognito mode —
unique to SimpleX Chat

What makes SimpleX private

Temporary anonymous pairwise identifiers

SimpleX uses temporary anonymous pairwise addresses and credentials for each user contact or group member.

It allows to deliver messages without user profile identifiers, providing better meta-data privacy than alternatives.

Tap to close

key exchange

Many communication platforms are vulnerable to MITM attacks by servers or network providers.

To prevent it SimpleX apps pass one-time keys out-of-band, when you share an address as a link or a QR code.

Tap to close

2-layers of
end-to-end encryption

Double-ratchet protocol —
OTR messaging with perfect forward secrecy and break-in recovery.

NaCL cryptobox in each queue to prevent traffic correlation between message queues if TLS is compromised.

Tap to close

Message integrity

To guarantee integrity the messages are sequentially numbered and include the hash of the previous message.

If any message is added, removed or changed the recipient will be alerted.

Tap to close

Additional layer of
server encryption

Additional layer of server encryption for delivery to the recipient, to prevent the correlation between received and sent server traffic if TLS is compromised.

Tap to close

Message mixing
to reduce correlation

SimpleX servers act as low latency mix nodes — the incoming and outgoing messages have different order.

Tap to close

Secure authenticated
TLS transport

Only TLS 1.2/1.3 with strong algorithms is used for client-server connections.

Server fingerprint and channel binding prevent MITM and replay attacks.

Connection resumption is disabled to prevent session attacks.

Tap to close

access via Tor

To protect your IP address you can access the servers via Tor or some other transport overlay network.

To use SimpleX via Tor please install Orbot app and enable SOCKS5 proxy (or VPN on iOS).

Tap to close

message queues

Each message queue passes messages in one direction, with the different send and receive addresses.

It reduces the attack vectors, compared with traditional message brokers, and available meta-data.

Tap to close

Multiple layers of
content padding

SimpleX uses content padding for each encryption layer to frustrate message size attacks.

It makes messages of different sizes look the same to the servers and network observers.

Tap to close

SimpleX Network

Simplex Chat provides the best privacy by combining the advantages of P2P and federated networks.

Unlike P2P networks

All messages are sent via the servers, both providing better metadata privacy and reliable asynchronous message delivery, while avoiding many problems of P2P networks.

Unlike federated networks

SimpleX relay servers do NOT store user profiles, contacts and delivered messages, do NOT connect to each other, and there is NO servers directory.

SimpleX network

servers provide unidirectional queues to connect the users, but they have no visibility of the network connection graph — only the users do.

Simplex explained

1. What users experience

You can create contacts and groups, and have two-way conversations, as in any other messenger.

How can it work with unidirectional queues and without user profile identifiers?

2. How does it work

For each connection you use two separate messaging queues to send and receive messages via different servers.

Servers only pass messages one way, without having the full picture of user's conversation or connections.

3. What servers see

The servers have separate anonymous credentials for each queue, and do not know which users they belong to.

Users can further improve metadata privacy by using Tor to access servers, preventing corellation by IP address.

Comparison with other protocols

simplex logo Signal, big platforms XMPP, Matrix P2P protocols
Requires global identity No - private Yes 1 Yes 2 Yes 3
Possibility of MITM No - secure Yes 4 Yes Yes
Dependence on DNS No - resilient Yes Yes No
Single or centralized network No - decentralized Yes No - federated 5 Yes 6
Central component or other network-wide attack No - resilient Yes Yes 2 Yes 7

  1. Usually based on a phone number, in some cases on usernames
  2. DNS-based addresses
  3. Public key or some other globally unique ID
  4. If operator’s servers are compromised
  5. Does not protect users' metadata
  6. While P2P are distributed, they are not federated - they operate as a single network
  7. P2P networks either have a central authority or the whole network can be compromised - see here

Join SimpleX

We invite you to join the conversation

Sign up to receive our updates

Get SimpleX

© 2020-2023 SimpleX | Open-Source Project