Tuta

End-to-end encryption in Tuta Mail is built in rather than bolted on, so the secure email service lets you communicate with anyone across every device you use. This repository holds the client source, which means the code handling your messages can be read and compiled by anyone who wants to check what it does.

Clients cover the places people actually read mail. Android builds are distributed through Google Play and through F-Droid for anyone avoiding proprietary stores, and there is an iOS app, a desktop client and a browser client. Building a client and developing on the codebase are documented as separate tasks, each with its own guide.

The project runs on a few clearly stated conventions.

• Building: a dedicated document covers compiling the clients from this repository.
• Developing: a hacking guide describes the workflow for anyone changing the code.
• Translating: a translation guide explains how to contribute a new language.
• Feature requests: these go through Reddit or support mail rather than the issue tracker.
• No generated contributions: issues and comments produced with help from large language models are closed or deleted without further explanation.

That last rule is unusually explicit, and maintainers say they prefer an incomplete or machine-translated report to an AI-assisted one. A public roadmap shows what the team plans next, and the community forum sits on Reddit. Anyone weighing up the service can read the roadmap and the client code together, since what a mail client really does is visible here.