Best messengers by use case

Everyday secure messaging

E2EE and everyday use, with identity and client-specific limits.

1. Signal: Mandatory number known to the provider and telecom layer.
   Conditions: Visibility and discovery: Nobody; fresh username, neutral profile, verified Safety Number, relayed calls when needed.
2. Threema: Desktop beta limits, account data and linkable purchases.
   Conditions: Do not link phone or email without need; verify fingerprints and each client’s limits.
3. Olvid: No network anonymity; calls and multi-device require a licence.
   Conditions: Verify identity / fingerprint out of band; assess licensing and history before adding a desktop.

Confidence: Medium for well-documented properties; lower for production metadata and untested versions.

[1] [2]

Pseudonymous strangers

Separate identities; Signal needs hardened settings and retains the number at the service.

1. SimpleX: More multi-device friction; relays and notifications require care.
   Conditions: Fresh profile, single-use invitation, no reused identity; TURN; deliberate iOS notification choice.
2. Signal: Mandatory number known to the provider and telecom layer.
   Conditions: Visibility and discovery: Nobody; fresh username, neutral profile, verified Safety Number, relayed calls when needed.
3. Threema: Desktop beta limits, account data and linkable purchases.
   Conditions: Do not link phone or email without need; verify fingerprints and each client’s limits.

Confidence: Medium for well-documented properties; lower for production metadata and untested versions.

[1] [2]

Without a phone number at the service

Separate identities; Signal needs hardened settings and retains the number at the service.

1. SimpleX: More multi-device friction; relays and notifications require care.
   Conditions: Fresh profile, single-use invitation, no reused identity; TURN; deliberate iOS notification choice.
2. Threema: Desktop beta limits, account data and linkable purchases.
   Conditions: Do not link phone or email without need; verify fingerprints and each client’s limits.
3. Olvid: No network anonymity; calls and multi-device require a licence.
   Conditions: Verify identity / fingerprint out of band; assess licensing and history before adding a desktop.

Confidence: Medium for well-documented properties; lower for production metadata and untested versions.

[1] [2]

iPhone + PC

E2EE and everyday use, with identity and client-specific limits.

1. Signal: Mandatory number known to the provider and telecom layer.
   Conditions: Visibility and discovery: Nobody; fresh username, neutral profile, verified Safety Number, relayed calls when needed.
2. SimpleX: More multi-device friction; relays and notifications require care.
   Conditions: Fresh profile, single-use invitation, no reused identity; TURN; deliberate iOS notification choice.
3. Olvid: No network anonymity; calls and multi-device require a licence.
   Conditions: Verify identity / fingerprint out of band; assess licensing and history before adding a desktop.
4. Threema: Desktop beta limits, account data and linkable purchases.
   Conditions: Do not link phone or email without need; verify fingerprints and each client’s limits.

Confidence: Medium for well-documented properties; lower for production metadata and untested versions.

[1] [2]

Malicious contacts

Force relayed calls; the relay then sees IP and duration.

1. SimpleX: More multi-device friction; relays and notifications require care.
   Conditions: Fresh profile, single-use invitation, no reused identity; TURN; deliberate iOS notification choice.
2. Olvid: No network anonymity; calls and multi-device require a licence.
   Conditions: Verify identity / fingerprint out of band; assess licensing and history before adding a desktop.
3. Signal: Mandatory number known to the provider and telecom layer.
   Conditions: Visibility and discovery: Nobody; fresh username, neutral profile, verified Safety Number, relayed calls when needed.

Confidence: Medium for well-documented properties; lower for production metadata and untested versions.

[1] [2]

Metadata minimisation

Reduce centralised identifiers; relays, networks and endpoints remain observers.

1. SimpleX: More multi-device friction; relays and notifications require care.
   Conditions: Fresh profile, single-use invitation, no reused identity; TURN; deliberate iOS notification choice.
2. Cwtch: No iOS; niche ecosystem and more limited assurance.
   Conditions: Control devices, identities, notifications and files; verify client, version and calling path.
3. Briar: No iOS or calls; essential maintenance since July 2026.
   Conditions: Control devices, identities, notifications and files; verify client, version and calling path.

Confidence: Medium for well-documented properties; lower for production metadata and untested versions.

[1] [2]

Limited network anonymity

Tor or configured relays against a limited observer, without a global-observer guarantee. Verify the actual Tor / relay path; TURN alone does not hide IP from the ISP.

1. Cwtch: No iOS; niche ecosystem and more limited assurance.
   Conditions: Control devices, identities, notifications and files; verify client, version and calling path.
2. Briar: No iOS or calls; essential maintenance since July 2026.
   Conditions: Control devices, identities, notifications and files; verify client, version and calling path.
3. SimpleX: More multi-device friction; relays and notifications require care.
   Conditions: Fresh profile, single-use invitation, no reused identity; TURN; deliberate iOS notification choice.

Confidence: Medium for well-documented properties; lower for production metadata and untested versions.

[1] [2]

Censorship resistance

Diversify transports or servers; country, operator, bridges and maintenance matter.

1. Briar: No iOS or calls; essential maintenance since July 2026.
   Conditions: Control devices, identities, notifications and files; verify client, version and calling path.
2. Cwtch: No iOS; niche ecosystem and more limited assurance.
   Conditions: Control devices, identities, notifications and files; verify client, version and calling path.
3. Matrix / Element: Self-hosting does not remove metadata, push or unencrypted-room risks.
   Conditions: Control devices, identities, notifications and files; verify client, version and calling path.

Confidence: Medium for well-documented properties; lower for production metadata and untested versions.

[1] [2]

Mature usability and adoption

Adoption and simplicity take priority; WhatsApp retains substantial metadata exposure.

1. Signal: Mandatory number known to the provider and telecom layer.
   Conditions: Visibility and discovery: Nobody; fresh username, neutral profile, verified Safety Number, relayed calls when needed.
2. WhatsApp: Strong linkage to phone number, accounts and metadata.
   Conditions: Control devices, identities, notifications and files; verify client, version and calling path.

Confidence: Medium for well-documented properties; lower for production metadata and untested versions.

[1] [2]

Teams / self-hosting

Teams with server, device, encryption and history configuration.

1. Matrix / Element: Self-hosting does not remove metadata, push or unencrypted-room risks.
   Conditions: Control devices, identities, notifications and files; verify client, version and calling path.
2. Wire: Linkable account email; product audit is not backend / binary verification.
   Conditions: Control devices, identities, notifications and files; verify client, version and calling path.

Confidence: Medium for well-documented properties; lower for production metadata and untested versions.

[1] [2]