Transparency alternatives to Templafy
Other Document management vendors we measure, sorted by how much we found at them and not at Templafy. This is a comparison of disclosure, not of features or fitness.
12 shown of 65 that differ from Templafy on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Templafy has 4 gaps in what we could measure: HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Named privacy contact. The column “Found there, not found at Templafy” is the one that closes them.
| Vendor | Score | Found there, not found at Templafy | Found at Templafy, not found there | |
|---|---|---|---|---|
| CloudFilescloudfiles.ioSee also Transparency alternatives to CloudFiles | 70/100 | 3 No third-party tracking before consent, security.txt (RFC 9116), Named privacy contact | 3 Status page with history, Public pricing, Uptime SLA with a figure | Compare |
| Smallpdfsmallpdf.comSee also Transparency alternatives to Smallpdf | 57/100 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | 4 Subprocessor list, Status page with history, Public pricing, +1 | Compare |
| Laserfichelaserfiche.comSee also Transparency alternatives to Laserfiche | 52/100 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | 4 Data processing agreement, Subprocessor list, Uptime SLA with a figure, +1 | Compare |
| Fabasoftfabasoft.comSee also Transparency alternatives to Fabasoft | 35/100 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | 6 Data processing agreement, Subprocessor list, Status page with history, +3 | Compare |
| Thereforetherefore.netSee also Transparency alternatives to Therefore | 22/100 | 3 HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116) | 8 Data processing agreement, Subprocessor list, Data location stated, +5 | Compare |
| Doxisdoxis.comSee also Transparency alternatives to Doxis | 17/100 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | 8 Data processing agreement, Subprocessor list, Data location stated, +5 | Compare |
| SER Groupsergroup.comSee also Transparency alternatives to SER Group | 17/100 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | 8 Data processing agreement, Subprocessor list, Data location stated, +5 | Compare |
| Intralinksintralinks.comSee also Transparency alternatives to Intralinks | 70/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 3 Public pricing, Certifications named, Uptime SLA with a figure | Compare |
| Onehubonehub.comSee also Transparency alternatives to Onehub | 57/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 4 Subprocessor list, Data location stated, Certifications named, +1 | Compare |
| Ademeroademero.comSee also Transparency alternatives to Ademero | 39/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 5 Subprocessor list, Data location stated, Status page with history, +2 | Compare |
| PaperOfficepaperoffice.comSee also Transparency alternatives to PaperOffice | 39/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 5 Data processing agreement, Subprocessor list, Status page with history, +2 | Compare |
| Docbytedocbyte.comSee also Transparency alternatives to Docbyte | 26/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 7 Data processing agreement, Subprocessor list, Status page with history, +4 | 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.