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