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