Cwtch vs Briar

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

Property	Cwtch	Briar
Account identifier	CwtchLocal / onion profile; no phone or email required. [1] [2]	BriarLocal identity; contacts in person or through invitation. [1] [2]
Phone required by service	CwtchNot required. [1] [2]	BriarNot required by this local-identity model. [1] [2]
E2EE	CwtchE2EE through onion services according to published design. [1] [2]	BriarE2EE; Tor and local Android transports. [1] [2]
Metadata exposure	CwtchReduced central concentration; presence and traffic correlation remain possible. [1] [2]	BriarLess centralisation; local / Tor network and endpoints remain observable. [1] [2]
IP exposure to peer	CwtchMessages through onion; no established calls; Tor does not defeat a global observer. [1] [2]	BriarTor or local transports; no calls; global correlation remains unresolved. [1] [2]
Multi-device	CwtchUnknown: not established for the version and configuration in question.	BriarSeparate Android and beta desktop clients; desktop does not provide an iPhone client. [1] [2]
Main strength	CwtchOnion architecture without a single central account server. [1] [2]	BriarAndroid resilience without Internet, Tor and proximity exchange. [1] [2]
Main weakness	CwtchNo iOS; niche ecosystem and more limited assurance. [1] [2]	BriarNo iOS or calls; essential maintenance since July 2026. [1] [2]
Best suited for	CwtchUsers on supported platforms who accept Tor and a specialised tool. [1] [2] [3] [4]	BriarTwo Android contacts when offline resilience matters. [1] [2] [3] [4]
Confidence and scope	CwtchMore limited current assurance and audits; Tor does not establish global resistance. [1] [2]	BriarScope-limited audits; essential maintenance only since July 2026 and a separate beta desktop client. [1] [2]

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

Property	Cwtch	Briar
Email requirement	CwtchNot required. [1] [2]	BriarUnknown: not established for the version and configuration in question.
Username / discovery	CwtchUnknown: not established for the version and configuration in question.	BriarUnknown: not established for the version and configuration in question.
Number visible to contact	CwtchNo required number. [1] [2]	BriarNo required number to share. [1] [2]
Global user ID	CwtchPersistent onion identity; no single central account. [1] [2]	BriarNo single central account; local identity. [1] [2]
Forward secrecy	CwtchUnknown: not established for the version and configuration in question.	BriarUnknown: not established for the version and configuration in question.
Post-compromise security	CwtchUnknown: not established for the version and configuration in question.	BriarUnknown: not established for the version and configuration in question.
Key verification	CwtchUnknown: not established for the version and configuration in question.	BriarUnknown: not established for the version and configuration in question.
Relay / TURN	CwtchOnion / Tor services with distributed visibility. [1] [2]	BriarTor / bridges or local Bluetooth / Wi-Fi depending on Android scenario. [1] [2]
What the provider learns	CwtchNo single central provider; relays and peers have local visibility. [1] [2]	BriarNo single central service; peers and transports remain in the model. [1] [2]
What the contact learns	CwtchThe contact receives messages and the profile you share, and can keep a copy. [1] [2]	BriarThe contact receives messages and the profile you share, and can keep a copy. [1] [2]
What the network / ISP learns	CwtchThe network sees destinations, timing and volume; Tor or a relay changes the observer. [1] [2]	BriarThe network sees destinations, timing and volume; Tor or a relay changes the observer. [1] [2]
Push notifications	CwtchUnknown: not established for the version and configuration in question.	BriarUnknown: not established for the version and configuration in question.
Apple / Google exposure	CwtchStore, installation and push can create metadata; exact profile linkage depends on the OS and was not tested here. [1] [2]	BriarStore, installation and push can create metadata; exact profile linkage depends on the OS and was not tested here. [1] [2]
Groups	CwtchUnknown: not established for the version and configuration in question.	BriarUnknown: not established for the version and configuration in question.
Calls	CwtchNo current calls established in the study. [1] [2]	BriarNo established voice calls. [1] [2]
Backups	CwtchUnknown: not established for the version and configuration in question.	BriarUnknown: not established for the version and configuration in question.
Source code and binaries	CwtchRepositories and component-specific scopes recorded in Phase 2; no current binary rebuilt bit-for-bit here. [1] [2]	BriarRepositories and component-specific scopes recorded in Phase 2; no current binary rebuilt bit-for-bit here. [1] [2]
Audits	CwtchUnknown: not established for the version and configuration in question.	BriarCure53 and ROS/OTF: bounded dates, versions and retests in the register. [1] [2] [3]
Public law-enforcement evidence	CwtchNo individual disclosure case established here; this does not prove an absence of requests or data. [1] [2]	BriarNo individual disclosure case established here; this does not prove an absence of requests or data. [1] [2]
iOS	CwtchNo official client established in the study. [1] [2]	BriarNo official client established in the study. [1] [2]
Android	CwtchYes, client listed in the study. [1]	BriarYes, client listed in the study. [1]
Windows	CwtchYes, client listed in the study. [1] [2]	BriarBeta; desktop-specific limits. [1] [2]
macOS	CwtchYes, client listed in the study. [1] [2]	BriarBeta; desktop-specific limits. [1] [2]
Linux	CwtchYes, client listed in the study. [1] [2]	BriarBeta; desktop-specific limits. [1] [2]
Avoid if…	CwtchYou use iPhone or need calls. [1] [2] [3] [4]	BriarYou use iPhone, need calls or seamless multi-device. [1] [2] [3] [4]
Recommended configuration	CwtchControl devices, identities, notifications and files; verify client, version and calling path. [1] [2]	BriarControl devices, identities, notifications and files; verify client, version and calling path. [1] [2]
Remaining unknowns	CwtchCurrent network behaviour, distributed binaries and forensic evidence remain incomplete; check version, OS and configuration. [1] [2]	BriarCurrent network behaviour, distributed binaries and forensic evidence remain incomplete; check version, OS and configuration. [1] [2]
Ease of use	CwtchSpecialised tool; setup and adoption are less straightforward. [1] [2] [3] [4]	BriarSpecialised use; usability, power and feature limits. [1] [2] [3] [4]
Network anonymity	CwtchTor reduces some local visibility; no general resistance to global correlation. [1] [2]	BriarTor / local: useful against some observers; no global guarantee. [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.