Transparency alternatives to Proposify
Other Proposals and quoting vendors we measure, sorted by how much we found at them and not at Proposify. This is a comparison of disclosure, not of features or fitness.
12 shown of 46 that differ from Proposify on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Proposify has 7 gaps in what we could measure: Data processing agreement, Subprocessor list, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Proposify” is the one that closes them.
| Vendor | Score | Found there, not found at Proposify | Found at Proposify, not found there | |
|---|---|---|---|---|
| AutoRFPautorfp.aiSee also Transparency alternatives to AutoRFP | 74/100 | 4 Data processing agreement, Subprocessor list, Uptime SLA with a figure, +1 | 1 Status page with history | Compare |
| Scoroscoro.comSee also Transparency alternatives to Scoro | 65/100 | 4 Subprocessor list, security.txt (RFC 9116), Notice before subprocessors change, +1 | 1 Status page with history | Compare |
| Loopioloopio.comSee also Transparency alternatives to Loopio | 39/100 | 4 Data processing agreement, Subprocessor list, Uptime SLA with a figure, +1 | 4 Data location stated, Status page with history, Public pricing, +1 | Compare |
| QorusDocsqorusdocs.comSee also Transparency alternatives to QorusDocs | 61/100 | 3 Data processing agreement, Subprocessor list, Notice before subprocessors change | 2 Status page with history, Public pricing | Compare |
| Responsiveresponsive.ioSee also Transparency alternatives to Responsive | 61/100 | 3 Data processing agreement, Uptime SLA with a figure, Notice before subprocessors change | 1 Status page with history | Compare |
| Foveatefoveate.comSee also Transparency alternatives to Foveate | 48/100 | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | 3 Status page with history, Certifications named, HTTPS enforced with HSTS | Compare |
| Arphiearphie.aiSee also Transparency alternatives to Arphie | 39/100 | 3 Data processing agreement, Notice before subprocessors change, Named privacy contact | 3 Data location stated, Status page with history, Public pricing | Compare |
| D-Tools Cloudd-tools.comSee also Transparency alternatives to D-Tools Cloud | 35/100 | 3 Subprocessor list, Notice before subprocessors change, Named privacy contact | 4 Data location stated, Status page with history, Public pricing, +1 | Compare |
| Qwilrqwilr.comSee also Transparency alternatives to Qwilr | 48/100 | 2 security.txt (RFC 9116), Named privacy contact | 1 Certifications named | Compare |
| Mercuramercura.ioSee also Transparency alternatives to Mercura | 43/100 | 2 Data processing agreement, Uptime SLA with a figure | 2 Status page with history, HTTPS enforced with HSTS | Compare |
| Roomleroomle.comSee also Transparency alternatives to Roomle | 43/100 | 2 Subprocessor list, security.txt (RFC 9116) | 2 Status page with history, HTTPS enforced with HSTS | Compare |
| PROSpros.comSee also Transparency alternatives to PROS | 39/100 | 2 security.txt (RFC 9116), Named privacy contact | 2 Public pricing, Certifications named | 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.