This notice explains how Mutte.ltd handles information when you visit this website, try its fictional demo or contact us. It does not cover the messaging service.
Effective 11 September 2026 · Website privacy notice
A fictional, temporary demo.
The phone demonstration uses fictional people and conversations. Its controls change only the preview on this page. It doesn’t create an account, send a message or upload anything.
Your demo choices stay in the page’s temporary memory and reset when you reload it. The demo doesn’t save those choices in cookies or browser storage. Images come with the website; text uses your device’s system fonts.
Cloudflare delivers and protects this website. Requests include technical information such as your IP address, requested URL and browser information. We use this processing to keep the website available and secure, based on our legitimate interests in providing the site and preventing abuse.
Cloudflare may receive connection-failure diagnostics through browser network-error reporting. Website Worker request logs, traces and Logpush are disabled. Cloudflare’s own technical-data retention follows its policies; our correspondence retention rule does not apply to those records.
Website analytics is disabled. No analytics script loads and we do not build visitor profiles.
For private support or questions about your personal information, email contact@mutte.me. We receive your email address and the information you choose to send so we can respond to your request. Please don’t include passwords, encryption keys or message contents.
Email sent to this address is forwarded by Cloudflare Email Routing to our Gmail inbox, provided by Google. See Cloudflare’s privacy policy and Google’s privacy policy for their information-handling practices.
Contributions are not open. This website collects no payment details and loads no checkout scripts.
GitHub links take you to a separate service. Bug reports submitted there are public; security reports use its private vulnerability channel. GitHub handles information you submit under its own privacy statement. Maintainers can read the reports you send them.
Follow the reporting guidance before sharing screenshots or diagnostics. Don’t put personal account details, message contents or secrets in a public issue.
The app we’re building.
End-to-end encryption is the intended baseline for public release. Device trust, group membership, recovery and independent security review still have release requirements to meet.
The current alpha should not be treated as certified production-ready messaging. Encryption also doesn’t mean that a service sees no account or routing metadata.
This website explanation is not the final privacy notice for the messaging service. That notice must describe the actual app and its account, device, message-routing and support data.
Requests and retention.
The operator manages the contact inbox. We use the address and information you send to answer you and resolve support or security matters, based on our legitimate interests in responding to requests and maintaining software security. We process privacy requests where needed to meet our legal obligations. Contacting us is voluntary; without enough information we may be unable to answer.
We delete ordinary correspondence and attachments within 90 days after resolution. We retain necessary material for unresolved security or legal matters only while needed and review it until deletion is possible. Public GitHub issues may remain as technical history; do not include personal information. Private reports are kept while remediation requires them, then unnecessary personal material is removed.
Cloudflare, Google and GitHub may process information outside the European Economic Area under their own terms and applicable transfer safeguards, described in their linked privacy information. Contact us for details relevant to a request. These provider services have their own retention rules; our 90-day rule covers correspondence we manage.
Your privacy choices.
Depending on the applicable processing, you may request access, correction, deletion, restriction or portability, and object to processing based on legitimate interests. If consent is used, you may withdraw it without affecting earlier lawful processing. We do not use this website’s information for automated decisions with legal or similarly significant effects.
We normally respond within one month; if an applicable extension is needed, we will explain why. We may ask for proportionate information to verify a request. You can complain to the Spanish data protection authority (AEPD) or another competent supervisory authority.
To diagnose backend failures, Mutte can send limited technical reports to Better Stack: a fixed failure category, time, source-code file and line, and service build version. Reports exclude message contents, attachments, account and device identifiers, request details, credentials and raw error text.
Better Stack processes these backend reports in the United States with a 90-day retention setting. It also receives the server connection’s network metadata. This reporting adds no browser tracking script, cookies or session recording.
iPhone crash reports use Apple’s diagnostic-sharing and TestFlight systems. Availability depends on the distribution channel and Apple’s sharing settings. These reports may contain technical app and device diagnostics; they do not use the backend report format described above.
