MUTE Protocol
← Back
MUTE collects no personal data. No name, no email, no phone number, no analytics, no tracking. Messages are end-to-end encrypted; we cannot read them, and we do not want to.
MUTE Protocol ("MUTE", "we", "us") is an end-to-end encrypted messaging application developed and maintained by Oraldo Nova. We are based in Switzerland. The app is distributed through the Apple App Store and Google Play Store under bundle identifier com.muteprotocol.mute.
We want to be unambiguous about what MUTE does not collect, store, or process:
For MUTE to function as an encrypted relay, the following minimal data passes through our infrastructure:
When you first open MUTE, the app generates a cryptographic key pair (X25519 for key agreement, Ed25519 for signatures) entirely on your device. Your public key is registered on our relay servers so that other users can establish encrypted sessions with you. Your private key never leaves your device.
Messages, voice notes, photos, videos, and call signaling data are encrypted on your device using XSalsa20-Poly1305 authenticated encryption with per-session keys derived via X25519. Our relay servers forward these payloads but cannot decrypt them. We do not log message content, and we technically could not read it even if compelled.
To deliver notifications when MUTE is closed, your device provides us with a push token issued by Apple Push Notification service (APNs) or Firebase Cloud Messaging (FCM). This token is mapped to your public key on our relay. The notification payload itself contains no message content — only an opaque trigger that wakes the app to fetch the encrypted message.
If a recipient is offline, encrypted messages are temporarily stored on our relay for up to 7 days. After 7 days, they are securely deleted. We never have access to the plaintext.
MUTE uses the following third-party infrastructure for transport only:
None of these services receive plaintext message content. Apple and Google receive only the opaque push token and a wake-up trigger; Hetzner hosts the encrypted relay payloads as ciphertext across three independent data centers in three countries.
For users with technical interest:
Because we do not collect personally identifiable information, most data subject rights under GDPR (EU), CCPA (California), and similar regulations are technically already satisfied — there is no personal record to access, correct, or delete.
If you wish to remove your public key and any associated push token from our relay, you can do so by:
For any other request, contact us at the address below.
MUTE is not directed at children under 13. We do not knowingly collect any data from children under 13. If we learn that a user is under 13, no action is necessary on our part because we do not collect personal data from any user — but we encourage parents and guardians to ensure their minors do not use messaging applications without supervision.
MUTE is available worldwide. Our relay servers are distributed across three countries on two continents: Finland, Germany, and Singapore. By using the app, you consent to encrypted message routing through this distributed infrastructure regardless of your location. Cross-region message delivery is handled by an authenticated cluster bus; messages remain end-to-end encrypted at all times.
We implement defense-in-depth security on our infrastructure: TLS 1.3 transport, Ed25519-authenticated WebSocket connections, HMAC-SHA1 TURN credentials, rate-limited HTTP endpoints, and forensic memory wipes. Nevertheless, no system is perfectly secure. Users handling extremely sensitive information should evaluate their threat model independently.
If we change this policy, we will update the "Last updated" date at the top of this page. Material changes will be communicated through an in-app notice on next launch.
Questions about this policy or about MUTE in general:
Email: muteprotocol.team@gmail.com
Website: muteprotocol.com