Transparency alternatives to Roomle
Other Proposals and quoting vendors we measure, sorted by how much we found at them and not at Roomle. This is a comparison of disclosure, not of features or fitness.
12 shown of 46 that differ from Roomle on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Roomle has 7 gaps in what we could measure: Data processing agreement, Status page with history, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Roomle” is the one that closes them.
| Vendor | Score | Found there, not found at Roomle | Found at Roomle, not found there | |
|---|---|---|---|---|
| AutoRFPautorfp.aiSee also Transparency alternatives to AutoRFP | 74/100 | 4 Data processing agreement, Uptime SLA with a figure, HTTPS enforced with HSTS, +1 | 1 security.txt (RFC 9116) | Compare |
| Responsiveresponsive.ioSee also Transparency alternatives to Responsive | 61/100 | 4 Data processing agreement, Uptime SLA with a figure, HTTPS enforced with HSTS, +1 | 2 Subprocessor list, security.txt (RFC 9116) | Compare |
| Arphiearphie.aiSee also Transparency alternatives to Arphie | 39/100 | 4 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change, +1 | 4 Subprocessor list, Data location stated, Public pricing, +1 | Compare |
| Scoroscoro.comSee also Transparency alternatives to Scoro | 65/100 | 3 HTTPS enforced with HSTS, Notice before subprocessors change, Named privacy contact | nothing | Compare |
| QorusDocsqorusdocs.comSee also Transparency alternatives to QorusDocs | 61/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | 2 Public pricing, security.txt (RFC 9116) | Compare |
| Foveatefoveate.comSee also Transparency alternatives to Foveate | 48/100 | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | 3 Subprocessor list, Certifications named, security.txt (RFC 9116) | Compare |
| Qwilrqwilr.comSee also Transparency alternatives to Qwilr | 48/100 | 3 Status page with history, HTTPS enforced with HSTS, Named privacy contact | 2 Subprocessor list, Certifications named | Compare |
| Omnia Retailomniaretail.comSee also Transparency alternatives to Omnia Retail | 43/100 | 3 Status page with history, HTTPS enforced with HSTS, Named privacy contact | 3 Subprocessor list, Certifications named, security.txt (RFC 9116) | Compare |
| Loopioloopio.comSee also Transparency alternatives to Loopio | 39/100 | 3 Data processing agreement, Uptime SLA with a figure, Named privacy contact | 3 Data location stated, Public pricing, security.txt (RFC 9116) | Compare |
| PROSpros.comSee also Transparency alternatives to PROS | 39/100 | 3 Status page with history, HTTPS enforced with HSTS, Named privacy contact | 3 Subprocessor list, Public pricing, Certifications named | Compare |
| D-Tools Cloudd-tools.comSee also Transparency alternatives to D-Tools Cloud | 35/100 | 3 HTTPS enforced with HSTS, Notice before subprocessors change, Named privacy contact | 4 Data location stated, Public pricing, Certifications named, +1 | Compare |
| Tactontacton.comSee also Transparency alternatives to Tacton | 30/100 | 3 Data processing agreement, HTTPS enforced with HSTS, Notice before subprocessors change | 5 Subprocessor list, Data location stated, Public pricing, +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.