Tuta cloud
Fair 4.0 Easy 3.3 Secure 5.0
| Pillar | Criterion | Score | Evidence |
|---|---|---|---|
| Easy | Day-one UX Can non-technical staff use it without a project? | 3 | Simple UI; staff must use Tuta apps, not any mail client. Source |
| Easy | Operate Admin burden, updates, backups and language coverage. | 5 | Fully hosted; admin load is low. Source |
| Easy | Integrate SSO, mail/CalDAV, APIs and common NGO connectors. | 2 | Weak IMAP/CalDAV story; SSO options are limited. Source |
| Fair | Lock-in / exit Can you leave with your data in open formats, at known cost? | 3 | Export available; leaving means Tuta-format migration work. Source |
| Fair | Sovereignty EU legal entity, EU hosting, and exposure to extra-EU lawful access? | 5 | German GmbH and German hosting. Source |
| Fair | Openness Open source or open standards? Are independent implementations possible? | 4 | Clients are GPL; server is proprietary; no IMAP by design. Source |
| Secure | IT security Authentication, encryption, patch cadence and independent audit. | 5 | E2EE and regular client releases. Source |
| Secure | User security 2FA, roles, phishing resistance and safe defaults. | 5 | 2FA and encrypted search within the client. Source |
| Secure | Personal data GDPR fit: DPA, residency, sub-processors and Schrems II posture. | 5 | German GDPR posture with encrypted-at-rest mail. Source |