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