Transparency alternatives to Foveate
Other Proposals and quoting vendors we measure, sorted by how much we found at them and not at Foveate. This is a comparison of disclosure, not of features or fitness.
12 shown of 46 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 “Found there, not found at Foveate” is the one that closes them.
| Vendor | Score | Found there, not found at Foveate | Found at Foveate, not found there | |
|---|---|---|---|---|
| AutoRFPautorfp.aiSee also Transparency alternatives to AutoRFP | 74/100 | 4 Subprocessor list, Certifications named, Uptime SLA with a figure, +1 | 1 Named privacy contact | Compare |
| Scoroscoro.comSee also Transparency alternatives to Scoro | 65/100 | 4 Subprocessor list, Certifications named, HTTPS enforced with HSTS, +1 | 1 Data processing agreement | Compare |
| QorusDocsqorusdocs.comSee also Transparency alternatives to QorusDocs | 61/100 | 3 Subprocessor list, Certifications named, HTTPS enforced with HSTS | 2 Public pricing, Named privacy contact | Compare |
| Responsiveresponsive.ioSee also Transparency alternatives to Responsive | 61/100 | 3 Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS | 1 Named privacy contact | Compare |
| Qwilrqwilr.comSee also Transparency alternatives to Qwilr | 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.comSee also Transparency alternatives to Proposify | 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.comSee also Transparency alternatives to Loopio | 39/100 | 3 Subprocessor list, Certifications named, Uptime SLA with a figure | 3 Data location stated, Public pricing, Notice before subprocessors change | Compare |
| PROSpros.comSee also Transparency alternatives to PROS | 39/100 | 3 Status page with history, HTTPS enforced with HSTS, security.txt (RFC 9116) | 3 Data processing agreement, Public pricing, Notice before subprocessors change | Compare |
| Mercuramercura.ioSee also Transparency alternatives to Mercura | 43/100 | 2 Certifications named, Uptime SLA with a figure | 2 Notice before subprocessors change, Named privacy contact | Compare |
| Omnia Retailomniaretail.comSee also Transparency alternatives to Omnia Retail | 43/100 | 2 Status page with history, HTTPS enforced with HSTS | 2 Data processing agreement, Notice before subprocessors change | Compare |
| Arphiearphie.aiSee also Transparency alternatives to Arphie | 39/100 | 2 Certifications named, HTTPS enforced with HSTS | 2 Data location stated, Public pricing | Compare |
| D-Tools Cloudd-tools.comSee also Transparency alternatives to D-Tools Cloud | 35/100 | 2 Subprocessor list, HTTPS enforced with HSTS | 3 Data processing agreement, 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.