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