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