Transparency alternatives to The Drive AI
Other Document management vendors we measure, sorted by how much they publish that The Drive AI does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 59 that differ from The Drive AI on at least one criterion we measured for both. Public transparency score, not a product or security rating.
The Drive AI has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “publishes and The Drive AI does not” is the one that closes them.
| Vendor | Score | Publishes, and The Drive AI does not | The Drive AI publishes, and they do not | |
|---|---|---|---|---|
| Templafytemplafy.com | 74/100 | 6 Data processing agreement, Subprocessor list, Data location stated, +3 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| CloudFilescloudfiles.io | 70/100 | 6 Data processing agreement, Subprocessor list, Data location stated, +3 | 2 Public pricing, HTTPS enforced with HSTS | Compare |
| Intralinksintralinks.com | 70/100 | 6 Data processing agreement, Subprocessor list, Data location stated, +3 | 3 Public pricing, Certifications named, security.txt (RFC 9116) | Compare |
| Onehubonehub.com | 57/100 | 4 Data processing agreement, Status page with history, Notice before subprocessors change, +1 | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Smallpdfsmallpdf.com | 57/100 | 4 Data processing agreement, Data location stated, Notice before subprocessors change, +1 | 1 Public pricing | Compare |
| Laserfichelaserfiche.com | 52/100 | 3 Data location stated, Status page with history, Named privacy contact | nothing | Compare |
| DynaFiledynafile.com | 43/100 | 3 Data location stated, Status page with history, Notice before subprocessors change | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Folderitfolderit.com | 43/100 | 3 Subprocessor list, Data location stated, Named privacy contact | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Ademeroademero.com | 35/100 | 3 Status page with history, Uptime SLA with a figure, Named privacy contact | 2 Certifications named, security.txt (RFC 9116) | Compare |
| Papermarkpapermark.com | 43/100 | 2 Data location stated, Notice before subprocessors change | 1 security.txt (RFC 9116) | Compare |
| Fabasoftfabasoft.com | 30/100 | 2 Data location stated, Named privacy contact | 2 Public pricing, Certifications named | Compare |
| Kenestokenesto.com | 26/100 | 2 Data location stated, Named privacy contact | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | 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.