Alternatives to Qwilr
Other Proposals and quoting vendors we measure, sorted by how much they publish that Qwilr does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 33 that differ from Qwilr on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Qwilr has 7 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change. The column “publishes and Qwilr does not” is the one that closes them.
| Vendor | Score | Publishes, and Qwilr does not | Qwilr publishes, and they do not | |
|---|---|---|---|---|
| AutoRFPautorfp.ai | 74/100 | 6 Data processing agreement, Subprocessor list, Data location stated, +3 | 3 Status page with history, security.txt (RFC 9116), Named privacy contact | Compare |
| Responsiveresponsive.io | 61/100 | 5 Data processing agreement, Data location stated, Certifications named, +2 | 3 Status page with history, security.txt (RFC 9116), Named privacy contact | Compare |
| Scoroscoro.com | 65/100 | 4 Subprocessor list, Data location stated, Certifications named, +1 | 1 Status page with history | Compare |
| Loopioloopio.com | 39/100 | 4 Data processing agreement, Subprocessor list, Certifications named, +1 | 4 Status page with history, Public pricing, HTTPS enforced with HSTS, +1 | Compare |
| Arphiearphie.ai | 39/100 | 3 Data processing agreement, Certifications named, Notice before subprocessors change | 3 Status page with history, Public pricing, security.txt (RFC 9116) | Compare |
| Roomleroomle.com | 39/100 | 3 Subprocessor list, Data location stated, Certifications named | 4 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | Compare |
| Proposifyproposify.com | 43/100 | 2 Data location stated, Certifications named | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Tactontacton.com | 30/100 | 2 Data processing agreement, Notice before subprocessors change | 4 Status page with history, Public pricing, security.txt (RFC 9116), +1 | Compare |
| Vendavovendavo.com | 26/100 | 2 Data location stated, Certifications named | 4 Status page with history, Public pricing, security.txt (RFC 9116), +1 | Compare |
| PROSpros.com | 48/100 | 1 Data location stated | nothing | Compare |
| Omnia Retailomniaretail.com | 43/100 | 1 Data location stated | 1 security.txt (RFC 9116) | Compare |
| Buynomicsbuynomics.com | 26/100 | 1 Data location stated | 3 Status page with history, Public pricing, 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.