Skip to content

Real-Time Communication

Real-Time Communication cover image

These are our recommendations for encrypted real-time communication.

Types of Communication Networks

Encrypted Messengers

These messengers are great for securing your sensitive communications.



Signal logo

Signal is a mobile app developed by Signal Messenger LLC. The app provides instant messaging, as well as voice and video calling.

All communications are E2EE. Contact lists are encrypted using your Signal PIN and the server does not have access to them. Personal profiles are also encrypted and only shared with contacts you chat with.



Signal supports private groups. The server has no record of your group memberships, group titles, group avatars, or group attributes. Signal has minimal metadata when Sealed Sender is enabled. The sender address is encrypted along with the message body, and only the recipient address is visible to the server. Sealed Sender is only enabled for people in your contacts list, but can be enabled for all recipients with the increased risk of receiving spam. Signal requires your phone number as a personal identifier.

The protocol was independently audited in 2016. The specification for the Signal protocol can be found in their documentation.

We have some additional tips on configuring and hardening your Signal installation:

Signal Configuration and Hardening

SimpleX Chat


Simplex logo

SimpleX Chat is an instant messenger that is decentralized and doesn't depend on any unique identifiers such as phone numbers or usernames. Users of SimpleX Chat can scan a QR code or click an invite link to participate in group conversations.



SimpleX Chat was audited by Trail of Bits in October 2022.

Currently SimpleX Chat only provides a client for Android and iOS. Basic group chatting functionality, direct messaging, editing of messages and markdown are supported. E2EE Audio and Video calls are also supported.

Your data can be exported, and imported onto another device, as there are no central servers where this is backed up.



Briar logo

Briar is an encrypted instant messenger that connects to other clients using the Tor Network. Briar can also connect via Wi-Fi or Bluetooth when in local proximity. Briar’s local mesh mode can be useful when internet availability is a problem.



To add a contact on Briar, you must both add each other first. You can either exchange briar:// links or scan a contact’s QR code if they are nearby.

The client software was independently audited, and the anonymous routing protocol uses the Tor network which has also been audited.

Briar has a fully published specification.

Briar supports Forward Secrecy by using the Bramble Handshake and Transport protocol.

Additional Options


These messengers do not have Forward Secrecy, and while they fulfill certain needs that our previous recommendations may not, we do not recommend them for long-term or sensitive communications. Any key compromise among message recipients would affect the confidentiality of all past communications.



Element logo

Element is the reference client for the Matrix protocol, an open standard for secure decentralized real-time communication.

Messages and files shared in private rooms (those which require an invite) are by default E2EE as are one to one voice and video calls.



Profile pictures, reactions, and nicknames are not encrypted.

Group voice and video calls are not E2EE, and use Jitsi, but this is expected to change with Native Group VoIP Signalling. Group calls have no authentication currently, meaning that non-room participants can also join the calls. We recommend that you do not use this feature for private meetings.

The Matrix protocol itself theoretically supports PFS, however this is not currently supported in Element due to it breaking some aspects of the user experience such as key backups and shared message history.

The protocol was independently audited in 2016. The specification for the Matrix protocol can be found in their documentation. The Olm cryptographic ratchet used by Matrix is an implementation of Signal’s Double Ratchet algorithm.



Session logo

Session is a decentralized messenger with a focus on private, secure, and anonymous communications. Session offers support for direct messages, group chats, and voice calls.

Session uses the decentralized Oxen Service Node Network to store and route messages. Every encrypted message is routed through three nodes in the Oxen Service Node Network, making it virtually impossible for the nodes to compile meaningful information on those using the network.



Session allows for E2EE in one-on-one chats or closed groups which allow for up to 100 members. Open groups have no restriction on the number of members, but are open by design.

Session does not support PFS, which is when an encryption system automatically and frequently changes the keys it uses to encrypt and decrypt information, such that if the latest key is compromised it exposes a smaller portion of sensitive information.

Oxen requested an independent audit for Session in March of 2020. The audit concluded in April of 2021, “The overall security level of this application is good and makes it usable for privacy-concerned people.”

Session has a whitepaper describing the technicals of the app and protocol.


Please note we are not affiliated with any of the projects we recommend. In addition to our standard criteria, we have developed a clear set of requirements to allow us to provide objective recommendations. We suggest you familiarize yourself with this list before choosing to use a project, and conduct your own research to ensure it's the right choice for you.

This section is new

We are working on establishing defined criteria for every section of our site, and this may be subject to change. If you have any questions about our criteria, please ask on our forum and don't assume we didn't consider something when making our recommendations if it is not listed here. There are many factors considered and discussed when we recommend a project, and documenting every single one is a work-in-progress.

  • Must have open-source clients.
  • Must use E2EE for private messages by default.
  • Must support E2EE for all messages.
  • Must have been independently audited.


Our best-case criteria represents what we would like to see from the perfect project in this category. Our recommendations may not include any or all of this functionality, but those which do may rank higher than others on this page.

  • Should have Forward Secrecy.
  • Should have open-source servers.
  • Should be decentralized, i.e. federated or P2P.
  • Should use E2EE for all messages by default.
  • Should support Linux, macOS, Windows, Android, and iOS.