Transparency alternatives to ContractSafe
Other Contract management vendors we measure, sorted by how much we found at them and not at ContractSafe. This is a comparison of disclosure, not of features or fitness.
12 shown of 32 that differ from ContractSafe on at least one criterion we measured for both. Public transparency score, not a product or security rating.
ContractSafe has 5 gaps in what we could measure: Status page with history, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Named privacy contact. The column “Found there, not found at ContractSafe” is the one that closes them.
| Vendor | Score | Found there, not found at ContractSafe | Found at ContractSafe, not found there | |
|---|---|---|---|---|
| Congaconga.comSee also Transparency alternatives to Conga | 35/100 | 2 Status page with history, Named privacy contact | 5 Data processing agreement, Data location stated, Public pricing, +2 | Compare |
| Ironcladironcladapp.comSee also Transparency alternatives to Ironclad | 52/100 | 1 Named privacy contact | 2 Data processing agreement, HTTPS enforced with HSTS | Compare |
| Gatekeepergatekeeperhq.comSee also Transparency alternatives to Gatekeeper | 48/100 | 1 Status page with history | 3 Subprocessor list, Data location stated, Certifications named | Compare |
| Weagreeweagree.comSee also Transparency alternatives to Weagree | 35/100 | 1 Named privacy contact | 4 Subprocessor list, Public pricing, HTTPS enforced with HSTS, +1 | Compare |
| Jurojuro.comSee also Transparency alternatives to Juro | 30/100 | 1 Named privacy contact | 4 Data processing agreement, Subprocessor list, HTTPS enforced with HSTS, +1 | Compare |
| Spotdraftspotdraft.comSee also Transparency alternatives to Spotdraft | 30/100 | 1 Named privacy contact | 4 Data processing agreement, Subprocessor list, Public pricing, +1 | Compare |
| Zefortzefort.comSee also Transparency alternatives to Zefort | 30/100 | 1 Status page with history | 4 Data processing agreement, Subprocessor list, Data location stated, +1 | Compare |
| DocJurisdocjuris.comSee also Transparency alternatives to DocJuris | 26/100 | 1 Status page with history | 5 Data processing agreement, Subprocessor list, Data location stated, +2 | Compare |
| Agiloftagiloft.comSee also Transparency alternatives to Agiloft | 22/100 | 1 Named privacy contact | 5 Data processing agreement, Subprocessor list, Public pricing, +2 | Compare |
| fynkfynk.comSee also Transparency alternatives to fynk | 22/100 | 1 security.txt (RFC 9116) | 5 Data processing agreement, Subprocessor list, Data location stated, +2 | Compare |
| Ntractsntracts.comSee also Transparency alternatives to Ntracts | 17/100 | 1 Status page with history | 6 Data processing agreement, Subprocessor list, Data location stated, +3 | Compare |
| Summizesummize.comSee also Transparency alternatives to Summize | 17/100 | 1 Uptime SLA with a figure | 5 Data processing agreement, Subprocessor list, Data location stated, +2 | 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.