Transparency alternatives to Cority
Other ESG reporting vendors we measure, sorted by how much we found at them and not at Cority. This is a comparison of disclosure, not of features or fitness.
12 shown of 27 that differ from Cority on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Cority has 6 gaps in what we could measure: Subprocessor list, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “Found there, not found at Cority” is the one that closes them.
| Vendor | Score | Found there, not found at Cority | Found at Cority, not found there | |
|---|---|---|---|---|
| Cozerocozero.ioSee also Transparency alternatives to Cozero | 65/100 | 4 Subprocessor list, HTTPS enforced with HSTS, Notice before subprocessors change, +1 | 3 Status page with history, Public pricing, Uptime SLA with a figure | Compare |
| Normativenormative.ioSee also Transparency alternatives to Normative | 39/100 | 4 Subprocessor list, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | 5 Data processing agreement, Data location stated, Status page with history, +2 | Compare |
| Watershedwatershed.comSee also Transparency alternatives to Watershed | 26/100 | 4 HTTPS enforced with HSTS, security.txt (RFC 9116), Notice before subprocessors change, +1 | 6 Data processing agreement, Data location stated, Status page with history, +3 | Compare |
| EcoOnlineecoonline.comSee also Transparency alternatives to EcoOnline | 26/100 | 3 Subprocessor list, HTTPS enforced with HSTS, Named privacy contact | 6 Data processing agreement, Data location stated, Status page with history, +3 | Compare |
| EcoVadisecovadis.comSee also Transparency alternatives to EcoVadis | 39/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 3 Data processing agreement, Status page with history, Uptime SLA with a figure | Compare |
| Persefonipersefoni.comSee also Transparency alternatives to Persefoni | 39/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 3 Data processing agreement, Public pricing, Uptime SLA with a figure | Compare |
| Plan Aplana.earthSee also Transparency alternatives to Plan A | 30/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 4 Data processing agreement, Status page with history, Public pricing, +1 | Compare |
| Apidayapiday.comSee also Transparency alternatives to Apiday | 26/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 5 Data processing agreement, Status page with history, Public pricing, +2 | Compare |
| Benchmark Gensuitebenchmarkgensuite.comSee also Transparency alternatives to Benchmark Gensuite | 26/100 | 2 HTTPS enforced with HSTS, Notice before subprocessors change | 5 Data processing agreement, Data location stated, Status page with history, +2 | Compare |
| Coolsetcoolset.comSee also Transparency alternatives to Coolset | 26/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 5 Data processing agreement, Status page with history, Public pricing, +2 | Compare |
| Diligent ESGdiligent.comSee also Transparency alternatives to Diligent ESG | 26/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 4 Data processing agreement, Data location stated, Public pricing, +1 | Compare |
| Quenticquentic.comSee also Transparency alternatives to Quentic | 26/100 | 2 HTTPS enforced with HSTS, Named privacy contact | 5 Data processing agreement, Status page with history, Public pricing, +2 | 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.