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