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