M2

Privacy at M2

M2 keeps communication identity small and separates messaging from ordinary website and email services.

What M2 does not require

Ordinary Channel participation does not require a phone number, email address, real-name account, or global M2 profile.

Messaging data

Messages and supported files are encrypted on the device. Encrypted server copies are removed after delivery is confirmed or within 48 hours if delivery does not complete.

Website visits

This public website is delivered through Cloudflare, so website requests reach Cloudflare and may create standard connection metadata.

Google Analytics is optional. If you choose Allow analytics, Google receives page, browser, device, connection, aggregate page-interaction, and branded APK download-click information and sets Analytics cookies so Mirage Project can count visits, understand which pages are useful, and count arm64 and universal downloads separately. Download events contain only the artifact type, M2 release, button placement, and branded filename; they do not contain M2 Codes, invitations, callback data, or user identifiers. Advertising storage, advertising personalization, and Google Signals stay disabled.

You can decline analytics or change your choice from the footer. Analytics does not run on invitation, retired callback, cancellation, or error pages. The site uses no session replay, remote fonts, or advertising pixels.

The M2 app may briefly display network information while it establishes a protected connection. M2 does not use that information to create a user profile.

Downloads and notifications

Download requests reach Cloudflare. Firebase may send a generic wake signal so M2 can check for encrypted work; message content is not placed in that notification.

Purchase inquiries and email

New M2 purchases are handled by direct inquiry through info@mirageproject.org. Email is an ordinary communication channel.

Do not send M2 Codes, invitations, passwords, or Channel content by email.