Accountless participation
Ordinary Channel members do not register a phone number, email address or real-name profile.
Security
What M2 protects—and what it does not.
M2 reduces identity, content, network and retention exposure with controls that work together. The model is explained here in plain language, with technical evidence available below.
Four layers of protection.
No single feature carries the whole security model. M2 combines a Channel-scoped identity, encryption on the device, Tor-routed messaging and short-lived server copies.
Device-level encryption
Messages and supported files are encrypted for the intended recipients; local history uses encrypted storage.
Tor and Onion routing
The messaging gateway is reached through embedded Tor and a v3 Onion Service, not a direct originating clearnet connection.
Limited retention
Confirmed delivery starts server-side ciphertext deletion. Undelivered encrypted payloads expire within 48 hours.
SenderEncrypt on deviceChannel recipient context
→TransportTor + v3 Onion ServiceNo direct clearnet origin at the gateway
→RelayEncrypted payloadDelete after receipt · 48-hour ceiling
→RecipientDecrypt on deviceEncrypted local history
Signed software updates
The Android client trusts a dedicated release Worker, separate from this website. A mandatory update is offered only after the app verifies an increasing compatible version, the M2 package identity, the immutable APK hash and the established production signing certificate. Android PackageInstaller always asks the user to confirm.
Practical operating guidance
Protect the device, keep operational and personal identities separate where practical, use a new Channel for unrelated work, and keep invitations and M2 Codes controlled. Use another system when retained records or audit evidence are required.
Limits to keep in mind
Encryption and Tor cannot protect information displayed on a compromised or monitored device. An authorized recipient can copy or photograph content, and Tor does not eliminate every form of traffic analysis or coercion. These are normal boundaries for deciding when and how to use M2.
Current assurance
The release publishes checksums, signer evidence, an SBOM, provenance, source archive and update-compatibility evidence. Automated and API 36 emulator tests are complete for this release. An independent third-party audit and current physical-device execution have not been completed.
Technical verification
Packageio.areschannel.ares_channel
Signing certificate SHA-25674026cfb0d144a1fe4d81bdec0014cedc53aaf3e72714dbd824cd1f36d9f856d
Update manifesthttps://ares-channel-download.ksh966ksh.workers.dev/latest/manifest.json