Transparency alternatives to eSignly
Other E-signature vendors we measure, sorted by how much they publish that eSignly does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 29 that differ from eSignly on at least one criterion we measured for both. Public transparency score, not a product or security rating.
eSignly has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and eSignly does not” is the one that closes them.
| Vendor | Score | Publishes, and eSignly does not | eSignly publishes, and they do not | |
|---|---|---|---|---|
| BoldSignboldsign.com | 83/100 | 6 Data processing agreement, Subprocessor list, Data location stated, +3 | 1 Uptime SLA with a figure | Compare |
| eversigneversign.com | 70/100 | 5 Data processing agreement, Subprocessor list, Data location stated, +2 | 2 Certifications named, Uptime SLA with a figure | Compare |
| Youtrustyoutrust.com | 52/100 | 5 Subprocessor list, Data location stated, security.txt (RFC 9116), +2 | 3 Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS | Compare |
| GetAcceptgetaccept.com | 52/100 | 4 Data processing agreement, Data location stated, Notice before subprocessors change, +1 | 2 Public pricing, Uptime SLA with a figure | Compare |
| Penneopenneo.com | 52/100 | 4 Subprocessor list, Data location stated, Status page with history, +1 | 2 Public pricing, Uptime SLA with a figure | Compare |
| SignEasysigneasy.com | 52/100 | 3 Data processing agreement, Status page with history, Notice before subprocessors change | 1 Uptime SLA with a figure | Compare |
| Dropbox Signdropbox.com | 48/100 | 3 Data location stated, Status page with history, Named privacy contact | 1 Uptime SLA with a figure | Compare |
| Nitrogonitro.com | 48/100 | 3 Data location stated, Status page with history, Named privacy contact | 1 Uptime SLA with a figure | Compare |
| Scrivescrive.com | 39/100 | 3 Data location stated, Status page with history, Named privacy contact | 2 Public pricing, Uptime SLA with a figure | Compare |
| Skribbleskribble.com | 39/100 | 3 Data location stated, security.txt (RFC 9116), Named privacy contact | 2 Certifications named, Uptime SLA with a figure | Compare |
| Sign.comsign.com | 35/100 | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | 3 Public pricing, Certifications named, Uptime SLA with a figure | Compare |
| Signicatsignicat.com | 26/100 | 3 Status page with history, security.txt (RFC 9116), Named privacy contact | 3 Public pricing, Certifications named, Uptime SLA with a figure | 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.