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