Transparency alternatives to Weagree
Other Contract management vendors we measure, sorted by how much they publish that Weagree does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 32 that differ from Weagree on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Weagree has 8 gaps in what we could measure: Subprocessor list, Status page with history, Public pricing, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “publishes and Weagree does not” is the one that closes them.
| Vendor | Score | Publishes, and Weagree does not | Weagree publishes, and they do not | |
|---|---|---|---|---|
| ContractSafecontractsafe.com | 70/100 | 4 Subprocessor list, Public pricing, HTTPS enforced with HSTS, +1 | 1 Named privacy contact | Compare |
| Ironcladironcladapp.com | 52/100 | 3 Subprocessor list, Public pricing, Notice before subprocessors change | 1 Data processing agreement | Compare |
| Gatekeepergatekeeperhq.com | 39/100 | 3 Public pricing, HTTPS enforced with HSTS, Notice before subprocessors change | 3 Data location stated, Certifications named, Named privacy contact | Compare |
| Congaconga.com | 35/100 | 3 Subprocessor list, Status page with history, HTTPS enforced with HSTS | 3 Data processing agreement, Data location stated, Certifications named | Compare |
| Contractbookcontractbook.com | 35/100 | 3 Subprocessor list, Public pricing, HTTPS enforced with HSTS | 3 Data processing agreement, Data location stated, Named privacy contact | Compare |
| DocJurisdocjuris.com | 26/100 | 3 Status page with history, Public pricing, HTTPS enforced with HSTS | 4 Data processing agreement, Data location stated, Certifications named, +1 | Compare |
| fynkfynk.com | 22/100 | 3 Public pricing, HTTPS enforced with HSTS, security.txt (RFC 9116) | 4 Data processing agreement, Data location stated, Certifications named, +1 | Compare |
| Contractifycontractify.io | 22/100 | 2 Subprocessor list, HTTPS enforced with HSTS | 4 Data processing agreement, Data location stated, Certifications named, +1 | Compare |
| Avokaadoavokaado.io | 17/100 | 2 Status page with history, HTTPS enforced with HSTS | 4 Data processing agreement, Data location stated, Certifications named, +1 | Compare |
| Ntractsntracts.com | 17/100 | 2 Status page with history, HTTPS enforced with HSTS | 4 Data processing agreement, Data location stated, Certifications named, +1 | Compare |
| Sirionsirion.ai | 17/100 | 2 HTTPS enforced with HSTS, No third-party tracking before consent | 4 Data processing agreement, Data location stated, Certifications named, +1 | Compare |
| Summizesummize.com | 17/100 | 2 Uptime SLA with a figure, HTTPS enforced with HSTS | 3 Data processing agreement, Data location stated, Named privacy contact | 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.