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