Alternatives to Proton Drive
Other Cloud storage vendors we measure, sorted by how much they publish that Proton Drive does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 19 that differ from Proton Drive on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Proton Drive has 6 gaps in what we could measure: Subprocessor list, Data location stated, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Named privacy contact. The column “publishes and Proton Drive does not” is the one that closes them.
| Vendor | Score | Publishes, and Proton Drive does not | Proton Drive publishes, and they do not | |
|---|---|---|---|---|
| Dropboxdropbox.com | 48/100 | 3 Data location stated, Certifications named, Named privacy contact | 3 Data processing agreement, security.txt (RFC 9116), Notice before subprocessors change | Compare |
| Egnyteegnyte.com | 48/100 | 3 Subprocessor list, Data location stated, Named privacy contact | 4 Data processing agreement, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | Compare |
| Tresorittresorit.com | 43/100 | 3 Data location stated, Certifications named, Named privacy contact | 3 Data processing agreement, Public pricing, Notice before subprocessors change | Compare |
| Koofrkoofr.eu | 35/100 | 3 Data location stated, No third-party tracking before consent, Named privacy contact | 5 Data processing agreement, Status page with history, HTTPS enforced with HSTS, +2 | Compare |
| Nextcloudnextcloud.com | 30/100 | 3 Data location stated, Certifications named, Named privacy contact | 5 Data processing agreement, Status page with history, Public pricing, +2 | Compare |
| IDriveidrive.com | 55/100 | 2 Data location stated, Certifications named | 2 Status page with history, security.txt (RFC 9116) | Compare |
| Sync.comsync.com | 50/100 | 2 Data location stated, Certifications named | 2 Data processing agreement, security.txt (RFC 9116) | Compare |
| Filenfilen.io | 39/100 | 2 Data location stated, No third-party tracking before consent | 4 Data processing agreement, Status page with history, security.txt (RFC 9116), +1 | Compare |
| Megamega.io | 36/100 | 2 Data location stated, Named privacy contact | 3 Data processing agreement, Status page with history, Notice before subprocessors change | Compare |
| pCloudpcloud.com | 30/100 | 2 Data location stated, Uptime SLA with a figure | 4 Data processing agreement, Status page with history, HTTPS enforced with HSTS, +1 | Compare |
| ownCloudowncloud.com | 40/100 | 1 Data location stated | 2 Data processing agreement, Status page with history | Compare |
| Wasabiwasabi.com | 30/100 | 1 Certifications named | 3 Data processing agreement, security.txt (RFC 9116), Notice before subprocessors change | 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.