Product
One Channel. One team. One purpose.
M2 keeps each project in its own communication space. Start without a global account, invite the right people, and close the Channel when the work ends.
From invitation to private conversation.
A Host creates a Channel and shares a signed invitation. Participants join without registering a phone number, email address, or global M2 profile. Each Channel keeps its own membership and local context.
Messages, voice and files
Send encrypted text, voice messages, and supported files. The Files view brings received material together, while protected-file controls keep supported content inside the intended experience.
A lifecycle that follows the work.
Members exchange messages and files.
History remains readable, while new sending stops.
The Host can purchase another month using the Channel’s existing capacity.
The local Channel context is removed from that device.
Local control, signed updates.
Local history follows M2’s encrypted storage design. A passcode can add an app lock, and notification previews can be controlled in Settings.
Before opening, M2 checks the trusted release manifest. If a newer compatible release is mandatory, it verifies package identity, version, APK hash and signer before Android presents the installation confirmation.
What M2 is not
M2 is not a public social network, a permanent archive, or a silent software installer. It is an Android-first path for small, compartmented teams.