Transparency alternatives to Documenso
Other E-signature vendors we measure, sorted by how much we found at them and not at Documenso. This is a comparison of disclosure, not of features or fitness.
12 shown of 28 that differ from Documenso on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Documenso 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 “Found there, not found at Documenso” is the one that closes them.
| Vendor | Score | Found there, not found at Documenso | Found at Documenso, not found there | |
|---|---|---|---|---|
| BoldSignboldsign.comSee also Transparency alternatives to BoldSign | 83/100 | 5 Data processing agreement, Subprocessor list, Data location stated, +2 | nothing | Compare |
| eversigneversign.comSee also Transparency alternatives to eversign | 70/100 | 5 Data processing agreement, Subprocessor list, Data location stated, +2 | 2 Certifications named, security.txt (RFC 9116) | Compare |
| GetAcceptgetaccept.comSee also Transparency alternatives to GetAccept | 52/100 | 4 Data processing agreement, Data location stated, Notice before subprocessors change, +1 | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Penneopenneo.comSee also Transparency alternatives to Penneo | 52/100 | 4 Subprocessor list, Data location stated, Status page with history, +1 | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Youtrustyoutrust.comSee also Transparency alternatives to Youtrust | 52/100 | 4 Subprocessor list, Data location stated, Notice before subprocessors change, +1 | 2 Certifications named, HTTPS enforced with HSTS | Compare |
| SignEasysigneasy.comSee also Transparency alternatives to SignEasy | 52/100 | 3 Data processing agreement, Status page with history, Notice before subprocessors change | 1 security.txt (RFC 9116) | Compare |
| Dropbox Signdropbox.comSee also Transparency alternatives to Dropbox Sign | 48/100 | 3 Data location stated, Status page with history, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Nitrogonitro.comSee also Transparency alternatives to Nitro | 48/100 | 3 Data location stated, Status page with history, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| Scrivescrive.comSee also Transparency alternatives to Scrive | 39/100 | 3 Data location stated, Status page with history, Named privacy contact | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Sign.comsign.comSee also Transparency alternatives to Sign.com | 35/100 | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | 3 Public pricing, Certifications named, security.txt (RFC 9116) | Compare |
| SignWellsignwell.comSee also Transparency alternatives to SignWell | 43/100 | 2 Data location stated, Status page with history | 1 security.txt (RFC 9116) | Compare |
| Skribbleskribble.comSee also Transparency alternatives to Skribble | 39/100 | 2 Data location stated, Named privacy contact | 1 Certifications named | 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.