Alternatives to Yousign
Other E-signature vendors we measure, sorted by how much they publish that Yousign does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 21 that differ from Yousign on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Yousign has 6 gaps in what we could measure: Data processing agreement, Status page with history, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent. The column “publishes and Yousign does not” is the one that closes them.
| Vendor | Score | Publishes, and Yousign does not | Yousign publishes, and they do not | |
|---|---|---|---|---|
| BoldSignboldsign.com | 83/100 | 4 Data processing agreement, Status page with history, Certifications named, +1 | nothing | Compare |
| SignEasysigneasy.com | 52/100 | 4 Data processing agreement, Status page with history, Certifications named, +1 | 3 Subprocessor list, Data location stated, security.txt (RFC 9116) | Compare |
| GetAcceptgetaccept.com | 52/100 | 3 Data processing agreement, Certifications named, HTTPS enforced with HSTS | 3 Subprocessor list, Public pricing, security.txt (RFC 9116) | Compare |
| Penneopenneo.com | 52/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Dropbox Signdropbox.com | 50/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | 2 Subprocessor list, security.txt (RFC 9116) | Compare |
| Signaturitsignaturit.com | 40/100 | 3 Status page with history, HTTPS enforced with HSTS, No third-party tracking before consent | 3 Subprocessor list, Data location stated, security.txt (RFC 9116) | Compare |
| Scrivescrive.com | 39/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | 3 Subprocessor list, Public pricing, security.txt (RFC 9116) | Compare |
| Namirialnamirial.com | 26/100 | 3 Status page with history, HTTPS enforced with HSTS, No third-party tracking before consent | 4 Subprocessor list, Data location stated, Public pricing, +1 | Compare |
| FP Signfp-sign.com | 22/100 | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | 4 Subprocessor list, Data location stated, Public pricing, +1 | Compare |
| eversigneversign.com | 65/100 | 2 Data processing agreement, HTTPS enforced with HSTS | 1 security.txt (RFC 9116) | Compare |
| Sign.comsign.com | 48/100 | 2 Data processing agreement, HTTPS enforced with HSTS | 3 Subprocessor list, Public pricing, security.txt (RFC 9116) | Compare |
| DocuSigndocusign.com | 45/100 | 2 Status page with history, HTTPS enforced with HSTS | 2 Subprocessor list, 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.