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