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