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