Transparency alternatives to IDrive
Other Cloud storage vendors we measure, sorted by how much we found at them and not at IDrive. This is a comparison of disclosure, not of features or fitness.
12 shown of 22 that differ from IDrive on at least one criterion we measured for both. Public transparency score, not a product or security rating.
IDrive has 5 gaps in what we could measure: Subprocessor list, Status page with history, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116). The column “Found there, not found at IDrive” is the one that closes them.
| Vendor | Score | Found there, not found at IDrive | Found at IDrive, not found there | |
|---|---|---|---|---|
| Egnyteegnyte.comSee also Transparency alternatives to Egnyte | 52/100 | 2 Subprocessor list, Status page with history | 3 Data processing agreement, Data location stated, Certifications named | Compare |
| Proton Driveproton.meSee also Transparency alternatives to Proton Drive | 43/100 | 2 Status page with history, security.txt (RFC 9116) | 4 Data location stated, Certifications named, HTTPS enforced with HSTS, +1 | Compare |
| Tresorittresorit.comSee also Transparency alternatives to Tresorit | 43/100 | 2 Status page with history, security.txt (RFC 9116) | 3 Data processing agreement, Public pricing, Notice before subprocessors change | Compare |
| Jottacloudjottacloud.comSee also Transparency alternatives to Jottacloud | 22/100 | 2 Status page with history, security.txt (RFC 9116) | 6 Data processing agreement, Data location stated, Public pricing, +3 | Compare |
| Dropboxdropbox.comSee also Transparency alternatives to Dropbox | 48/100 | 1 Status page with history | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Sync.comsync.comSee also Transparency alternatives to Sync.com | 43/100 | 1 Status page with history | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | Compare |
| Wasabiwasabi.comSee also Transparency alternatives to Wasabi | 43/100 | 1 Status page with history | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | Compare |
| Filenfilen.ioSee also Transparency alternatives to Filen | 39/100 | 1 No third-party tracking before consent | 4 Data processing agreement, Certifications named, Notice before subprocessors change, +1 | Compare |
| Koofrkoofr.euSee also Transparency alternatives to Koofr | 35/100 | 1 No third-party tracking before consent | 4 Data processing agreement, Certifications named, HTTPS enforced with HSTS, +1 | Compare |
| ownCloudowncloud.comSee also Transparency alternatives to ownCloud | 35/100 | 1 security.txt (RFC 9116) | 4 Data processing agreement, Certifications named, Notice before subprocessors change, +1 | Compare |
| RushFilesrushfiles.comSee also Transparency alternatives to RushFiles | 26/100 | 1 Status page with history | 5 Data processing agreement, Data location stated, Certifications named, +2 | Compare |
| Livedrivelivedrive.comSee also Transparency alternatives to Livedrive | 22/100 | 1 Status page with history | 5 Data processing agreement, Data location stated, HTTPS enforced with HSTS, +2 | 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.