M2 Security Whitepaper

How M2 protects identity, messages, network origin, and server-held data.

No central user profile

M2 lets people join a Channel without registering a phone number, email address, real name, or account for the wider service. Each Channel keeps its own membership and context.

End-to-end encryption

Messages and supported files are encrypted on the device for the intended recipients. Local history uses encrypted storage, and invitation material should be shared carefully.

Tor and Onion routing

Embedded Tor connects M2 messaging to a v3 Onion Service. This reduces direct network-origin exposure to the messaging service.

Delivery and deletion

The server holds encrypted copies only while delivery is pending. Copies are deleted after delivery is confirmed, and undelivered copies expire within 48 hours.

Software updates

M2 checks trusted compatible updates before Android asks you to install them.

Security considerations

Protect the device, keep invitations private, and use separate Channels for unrelated work. A compromised endpoint or an authorized recipient can still expose information they can see, and Tor cannot prevent every form of traffic analysis.