Transparency alternatives to Consense
Other Quality management vendors we measure, sorted by how much we found at them and not at Consense. This is a comparison of disclosure, not of features or fitness.
12 shown of 84 that differ from Consense on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Consense has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change. The column “Found there, not found at Consense” is the one that closes them.
| Vendor | Score | Found there, not found at Consense | Found at Consense, not found there | |
|---|---|---|---|---|
| Ketryxketryx.comSee also Transparency alternatives to Ketryx | 43/100 | 4 Data processing agreement, Public pricing, Certifications named, +1 | 1 security.txt (RFC 9116) | Compare |
| Arenaarenasolutions.comSee also Transparency alternatives to Arena | 26/100 | 4 Status page with history, Public pricing, Certifications named, +1 | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | Compare |
| SimplerQMSsimplerqms.comSee also Transparency alternatives to SimplerQMS | 48/100 | 3 Data processing agreement, Data location stated, No third-party tracking before consent | 1 security.txt (RFC 9116) | Compare |
| Qualioqualio.comSee also Transparency alternatives to Qualio | 43/100 | 3 Data processing agreement, Status page with history, Notice before subprocessors change | 1 security.txt (RFC 9116) | Compare |
| AM System Classicamsystem.comSee also Transparency alternatives to AM System Classic | 39/100 | 3 Data processing agreement, Status page with history, Notice before subprocessors change | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Cognidoxcognidox.comSee also Transparency alternatives to Cognidox | 39/100 | 3 Data location stated, Public pricing, Certifications named | 1 security.txt (RFC 9116) | Compare |
| myoshmyosh.comSee also Transparency alternatives to myosh | 39/100 | 3 Data location stated, Public pricing, Certifications named | 1 security.txt (RFC 9116) | Compare |
| Certainty Softwarecertaintysoftware.comSee also Transparency alternatives to Certainty Software | 35/100 | 3 Data location stated, Public pricing, Certifications named | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Grand Avenue Softwaregrandavenue.comSee also Transparency alternatives to Grand Avenue Software | 35/100 | 3 Data processing agreement, Public pricing, Notice before subprocessors change | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | Compare |
| Propelpropelsoftware.comSee also Transparency alternatives to Propel | 35/100 | 3 Status page with history, Public pricing, Certifications named | 1 security.txt (RFC 9116) | Compare |
| Skytrustskytrust.com.auSee also Transparency alternatives to Skytrust | 26/100 | 3 Data location stated, Public pricing, Certifications named | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | Compare |
| SoftComplysoftcomply.comSee also Transparency alternatives to SoftComply | 26/100 | 3 Public pricing, Certifications named, Notice before subprocessors change | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 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.