Transparency alternatives to Closinglock
Other Title and closing vendors we measure, sorted by how much we found at them and not at Closinglock. This is a comparison of disclosure, not of features or fitness.
12 shown of 18 that differ from Closinglock on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Closinglock has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Closinglock” is the one that closes them.
| Vendor | Score | Found there, not found at Closinglock | Found at Closinglock, not found there | |
|---|---|---|---|---|
| Proofproof.comSee also Transparency alternatives to Proof | 43/100 | 3 Status page with history, Public pricing, Named privacy contact | 1 security.txt (RFC 9116) | Compare |
| CertifIDcertifid.comSee also Transparency alternatives to CertifID | 35/100 | 3 Status page with history, Public pricing, Named privacy contact | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Snapdocssnapdocs.comSee also Transparency alternatives to Snapdocs | 35/100 | 3 Subprocessor list, Status page with history, Certifications named | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Qualiaqualia.comSee also Transparency alternatives to Qualia | 22/100 | 3 Status page with history, Certifications named, Named privacy contact | 2 Data location stated, HTTPS enforced with HSTS | Compare |
| NotaryCamnotarycam.comSee also Transparency alternatives to NotaryCam | 26/100 | 2 Public pricing, Certifications named | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Stavvystavvy.comSee also Transparency alternatives to Stavvy | 30/100 | 1 Status page with history | 1 security.txt (RFC 9116) | Compare |
| RamQuestramquest.comSee also Transparency alternatives to RamQuest | 17/100 | 1 Status page with history | 2 Data location stated, security.txt (RFC 9116) | Compare |
| AtCloseatclose.comSee also Transparency alternatives to AtClose | 13/100 | 1 Named privacy contact | 2 Data location stated, security.txt (RFC 9116) | Compare |
| DocMagicdocmagic.comSee also Transparency alternatives to DocMagic | 13/100 | 1 Named privacy contact | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Endpointendpoint.comSee also Transparency alternatives to Endpoint | 9/100 | nothing we found there and not here | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Rexerarexera.comSee also Transparency alternatives to Rexera | 9/100 | nothing we found there and not here | 2 Data location stated, security.txt (RFC 9116) | Compare |
| Apexiem Search-Itapexiem.comSee also Transparency alternatives to Apexiem Search-It | 0/100 | nothing we found there and not here | 3 Data location stated, HTTPS enforced with HSTS, security.txt (RFC 9116) | 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.