Transparency alternatives to Runbox
Other Email hosting vendors we measure, sorted by how much we found at them and not at Runbox. This is a comparison of disclosure, not of features or fitness.
12 shown of 37 that differ from Runbox on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Runbox has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Runbox” is the one that closes them.
| Vendor | Score | Found there, not found at Runbox | Found at Runbox, not found there | |
|---|---|---|---|---|
| Tutatuta.comSee also Transparency alternatives to Tuta | 48/100 | 4 Data location stated, Certifications named, HTTPS enforced with HSTS, +1 | 1 Status page with history | Compare |
| StartMailstartmail.comSee also Transparency alternatives to StartMail | 43/100 | 3 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116) | 1 No third-party tracking before consent | Compare |
| Stalwartstalw.artSee also Transparency alternatives to Stalwart | 39/100 | 3 Data processing agreement, Data location stated, security.txt (RFC 9116) | 2 Status page with history, No third-party tracking before consent | Compare |
| Gandigandi.netSee also Transparency alternatives to Gandi | 30/100 | 3 Data location stated, Certifications named, security.txt (RFC 9116) | 2 Public pricing, No third-party tracking before consent | Compare |
| df.eudf.euSee also Transparency alternatives to df.eu | 26/100 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | 2 Public pricing, No third-party tracking before consent | Compare |
| Yandex 360yandex.comSee also Transparency alternatives to Yandex 360 | 22/100 | 3 Data processing agreement, security.txt (RFC 9116), Named privacy contact | 3 Status page with history, Public pricing, No third-party tracking before consent | Compare |
| Open-Xchangeox.ioSee also Transparency alternatives to Open-Xchange | 17/100 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | 3 Status page with history, Public pricing, No third-party tracking before consent | Compare |
| Stratostrato.deSee also Transparency alternatives to Strato | 17/100 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | 3 Status page with history, Public pricing, No third-party tracking before consent | Compare |
| Fastmailfastmail.comSee also Transparency alternatives to Fastmail | 30/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 1 Status page with history | Compare |
| Hushmailhushmail.comSee also Transparency alternatives to Hushmail | 30/100 | 2 Data location stated, HTTPS enforced with HSTS | 2 Status page with history, No third-party tracking before consent | Compare |
| All-Inklall-inkl.comSee also Transparency alternatives to All-Inkl | 22/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 2 Status page with history, Public pricing | Compare |
| Atmailatmail.comSee also Transparency alternatives to Atmail | 22/100 | 2 Data location stated, HTTPS enforced with HSTS | 3 Status page with history, Public pricing, No third-party tracking before consent | Compare |
Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.