Transparency alternatives to Drooms Lending
Other Lending and mortgage software vendors we measure, sorted by how much we found at them and not at Drooms Lending. This is a comparison of disclosure, not of features or fitness.
12 shown of 47 that differ from Drooms Lending on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Drooms Lending has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, 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 Drooms Lending” is the one that closes them.
| Vendor | Score | Found there, not found at Drooms Lending | Found at Drooms Lending, not found there | |
|---|---|---|---|---|
| Mambumambu.comSee also Transparency alternatives to Mambu | 30/100 | 3 Status page with history, Notice before subprocessors change, Named privacy contact | 3 Public pricing, Certifications named, security.txt (RFC 9116) | Compare |
| Moxomoxo.comSee also Transparency alternatives to Moxo | 30/100 | 3 Data location stated, Status page with history, Named privacy contact | 3 Public pricing, HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Floifyfloify.comSee also Transparency alternatives to Floify | 43/100 | 2 Data location stated, Status page with history | 1 Certifications named | Compare |
| Encompassicemortgagetechnology.comSee also Transparency alternatives to Encompass | 30/100 | 2 Data location stated, Status page with history | 3 Public pricing, Certifications named, security.txt (RFC 9116) | Compare |
| Q2q2.comSee also Transparency alternatives to Q2 | 30/100 | 2 Data location stated, Named privacy contact | 2 Public pricing, Certifications named | Compare |
| Banxwarebanxware.comSee also Transparency alternatives to Banxware | 26/100 | 2 Data location stated, Named privacy contact | 3 Public pricing, Certifications named, security.txt (RFC 9116) | Compare |
| PCFS Solutionspcfssolutions.comSee also Transparency alternatives to PCFS Solutions | 26/100 | 2 Data location stated, Named privacy contact | 3 Public pricing, Certifications named, security.txt (RFC 9116) | Compare |
| Blendblend.comSee also Transparency alternatives to Blend | 22/100 | 2 Status page with history, Named privacy contact | 3 Public pricing, Certifications named, security.txt (RFC 9116) | Compare |
| Lendboxlendbox.ioSee also Transparency alternatives to Lendbox | 35/100 | 1 Data location stated | 1 Certifications named | Compare |
| Lendingpadlendingpad.comSee also Transparency alternatives to Lendingpad | 22/100 | 1 Status page with history | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Europaceeuropace.deSee also Transparency alternatives to Europace | 17/100 | 1 No third-party tracking before consent | 3 Public pricing, Certifications named, security.txt (RFC 9116) | Compare |
| Meridianlinkmeridianlink.comSee also Transparency alternatives to Meridianlink | 17/100 | 1 Status page with history | 3 Public pricing, Certifications named, 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.