Alternatives to Zefort
Other Contract management vendors we measure, sorted by how much they publish that Zefort does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 25 that differ from Zefort on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Zefort has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, 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 Zefort does not” is the one that closes them.
| Vendor | Score | Publishes, and Zefort does not | Zefort publishes, and they do not | |
|---|---|---|---|---|
| Ironcladironcladapp.com | 52/100 | 3 Subprocessor list, Data location stated, Notice before subprocessors change | 1 Status page with history | Compare |
| Congaconga.com | 48/100 | 3 Subprocessor list, Data location stated, HTTPS enforced with HSTS | 2 Public pricing, Certifications named | Compare |
| Gatekeepergatekeeperhq.com | 39/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | 3 Status page with history, Certifications named, Named privacy contact | Compare |
| Spotdraftspotdraft.com | 39/100 | 2 Data location stated, HTTPS enforced with HSTS | 1 Status page with history | Compare |
| Contractbookcontractbook.com | 35/100 | 2 Subprocessor list, HTTPS enforced with HSTS | 2 Status page with history, Named privacy contact | Compare |
| Agiloftagiloft.com | 30/100 | 2 Data location stated, HTTPS enforced with HSTS | 2 Status page with history, Public pricing | Compare |
| Outlawgetoutlaw.com | 30/100 | 2 Data location stated, HTTPS enforced with HSTS | 2 Status page with history, Public pricing | Compare |
| Lexionlexion.ai | 26/100 | 2 Data location stated, HTTPS enforced with HSTS | 3 Status page with history, Public pricing, Named privacy contact | Compare |
| LinkSquareslinksquares.com | 26/100 | 2 Data location stated, HTTPS enforced with HSTS | 3 Status page with history, Public pricing, Named privacy contact | Compare |
| Evisortevisort.com | 25/100 | 2 Data location stated, HTTPS enforced with HSTS | 3 Status page with history, Public pricing, Certifications named | Compare |
| fynkfynk.com | 25/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 2 Status page with history, Certifications named | Compare |
| Summizesummize.com | 20/100 | 2 Uptime SLA with a figure, HTTPS enforced with HSTS | 2 Status page with history, Public pricing | 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.