Olvid vs Threema

Choose two to four messengers. Every property comes from the same traceable catalogue; unknowns remain explicit.

Property	Olvid	Threema
Account identifier	OlvidCryptographic identity; no mandatory phone or email. [1] [2]	ThreemaRandom Threema ID; optional phone and email. [1] [2]
Phone required by service	OlvidNot required. [1] [2]	ThreemaOptional for discovery. [1] [2]
E2EE	OlvidFormally studied protocol under limited assumptions; not an audit of the entire 2026 system. [1] [2]	ThreemaE2EE; properties depend on the client, particularly desktop beta. [1] [2]
Metadata exposure	OlvidRouting keys, sizes and timing visible in the formal model. [1] [2]	ThreemaID, connection data and optional identifiers; store purchase may link identities. [1] [2]
IP exposure to peer	OlvidDocumented TURN-only calls: IP hidden from the peer, visible to the relay. [1] [2]	ThreemaCheck calling mode and relay per client and configuration. [1] [2]
Multi-device	OlvidLicensed multi-device; old history not automatically transferred. [1] [2]	ThreemaDesktop 2.0 beta: up to two computers, no PFS; older client depends on the phone. [1] [2]
Main strength	OlvidNo mandatory number; documented TURN-only calls. [1] [2]	ThreemaID without mandatory phone or email; mobile maturity. [1] [2]
Main weakness	OlvidNo network anonymity; calls and multi-device require a licence. [1] [2]	ThreemaDesktop beta limits, account data and linkable purchases. [1] [2]
Best suited for	OlvidAvoid sharing a number with the contact; verify cryptographic identity. [1] [2] [3] [4]	ThreemaPeer-facing pseudonymity without a mandatory number. [1] [2] [3] [4]
Confidence and scope	OlvidScope-limited documentary evidence; production metadata and distributed binaries not experimentally verified. [1]	ThreemaClient-specific properties; no PFS in Desktop 2.0 beta, retest status needs verification. [1] [2]

Technical details: identity, keys, push, devices, audits and evidence

Property	Olvid	Threema
Email requirement	OlvidNot required. [1] [2]	ThreemaOptional for discovery. [1] [2]
Username / discovery	OlvidUnknown: not established for the version and configuration in question.	ThreemaUnknown: not established for the version and configuration in question.
Number visible to contact	OlvidNo mandatory number to share. [1] [2]	ThreemaNot needed when no number is linked / shared. [1] [2]
Global user ID	OlvidCryptographic identity; server sees routing keys in the analysed model. [1] [2]	ThreemaPersistent random ID; optional linked identifiers add correlation. [1] [2]
Forward secrecy	OlvidUnknown: not established for the version and configuration in question.	ThreemaDesktop 2.0 beta does not support PFS; do not generalise to other clients. [1] [2]
Post-compromise security	OlvidUnknown: not established for the version and configuration in question.	ThreemaUnknown: not established for the version and configuration in question.
Key verification	OlvidVerify identity or fingerprint in person / through a separate channel. [1] [2]	ThreemaVerify identity / fingerprint through a separate channel. [1] [2]
Relay / TURN	OlvidDocumented call candidates are TURN-only; no current packet capture performed. [1] [2]	ThreemaCall relay properties must be checked on the client being used. [1] [2]
What the provider learns	OlvidRouting and network information; actual production retention and access unknown. [1] [2]	ThreemaID and connection data; aggregate account-data disclosures are published. [1] [2]
What the contact learns	OlvidThe contact receives messages and the profile you share, and can keep a copy. [1] [2]	ThreemaThe contact receives messages and the profile you share, and can keep a copy. [1] [2]
What the network / ISP learns	OlvidThe network sees destinations, timing and volume; Tor or a relay changes the observer. [1] [2]	ThreemaThe network sees destinations, timing and volume; Tor or a relay changes the observer. [1] [2]
Push notifications	OlvidUnknown: not established for the version and configuration in question.	ThreemaUnknown: not established for the version and configuration in question.
Apple / Google exposure	OlvidStore, installation and push can create metadata; exact profile linkage depends on the OS and was not tested here. [1] [2]	ThreemaStore, installation and push can create metadata; exact profile linkage depends on the OS and was not tested here. [1] [2]
Groups	OlvidUnknown: not established for the version and configuration in question.	ThreemaUnknown: not established for the version and configuration in question.
Calls	OlvidCalls require a licence after the trial. [1] [2]	ThreemaUnknown: not established for the version and configuration in question.
Backups	OlvidUnknown: not established for the version and configuration in question.	ThreemaUnknown: not established for the version and configuration in question.
Source code and binaries	OlvidRepositories and component-specific scopes recorded in Phase 2; no current binary rebuilt bit-for-bit here. [1] [2]	ThreemaRepositories and component-specific scopes recorded in Phase 2; no current binary rebuilt bit-for-bit here. [1] [2]
Audits	OlvidHistorical CSPN/Synacktiv work and 2026 formal analysis; distinct scopes and versions. [1] [2] [3]	ThreemaCure53 and Ibex analyses: distinct scopes; desktop retest status needs verification. [1] [2] [3]
Public law-enforcement evidence	OlvidNo individual disclosure case established here; this does not prove an absence of requests or data. [1] [2]	Threema2025 and H1 2026 reports: aggregate account-data disclosures; not evidence of message-content disclosure. [1] [2] [3]
iOS	OlvidYes, client listed in the study. [1] [2]	ThreemaYes, client listed in the study. [1] [2]
Android	OlvidYes, client listed in the study. [1]	ThreemaYes, client listed in the study. [1]
Windows	OlvidYes, client listed in the study. [1] [2]	ThreemaBeta; desktop-specific limits. [1] [2]
macOS	OlvidYes, client listed in the study. [1] [2]	ThreemaBeta; desktop-specific limits. [1] [2]
Linux	OlvidYes, client listed in the study. [1] [2]	ThreemaBeta; desktop-specific limits. [1] [2]
Avoid if…	OlvidYou require network anonymity or free multi-device after the trial. [1] [2] [3] [4]	ThreemaYou require PFS on Desktop 2.0 beta or network anonymity. [1] [2] [3] [4]
Recommended configuration	OlvidVerify identity / fingerprint out of band; assess licensing and history before adding a desktop. [1] [2] [3] [4]	ThreemaDo not link phone or email without need; verify fingerprints and each client’s limits. [1] [2] [3] [4]
Remaining unknowns	OlvidCurrent network behaviour, distributed binaries and forensic evidence remain incomplete; check version, OS and configuration. [1] [2]	ThreemaCurrent network behaviour, distributed binaries and forensic evidence remain incomplete; check version, OS and configuration. [1] [2]
Ease of use	OlvidCross-platform; licensing and old history are concrete constraints. [1] [2] [3] [4]	ThreemaEstablished mobile client; desktop experience remains beta and limited. [1] [2] [3] [4]
Network anonymity	OlvidNo general resistance to a global passive observer is demonstrated. [1] [2]	ThreemaNo general resistance to a global passive observer is demonstrated. [1] [2]

Customise this comparison

• Compromised / unlocked device and spyware.
• Copying, screenshots or disclosure by the contact.
• Initial Discord traces, reused alias, avatar, voice or files.
• Global correlation; relay, ISP, telecom, store and backup data depending on the path.