Transparency alternatives to HumanSignal
Other Data labelling vendors we measure, sorted by how much we found at them and not at HumanSignal. This is a comparison of disclosure, not of features or fitness.
12 shown of 38 that differ from HumanSignal on at least one criterion we measured for both. Public transparency score, not a product or security rating.
HumanSignal has 7 gaps in what we could measure: Subprocessor list, Data location stated, 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 HumanSignal” is the one that closes them.
| Vendor | Score | Found there, not found at HumanSignal | Found at HumanSignal, not found there | |
|---|---|---|---|---|
| Scale AIscale.comSee also Transparency alternatives to Scale AI | 52/100 | 4 Subprocessor list, security.txt (RFC 9116), Notice before subprocessors change, +1 | 2 Data processing agreement, Public pricing | Compare |
| SuperAnnotatesuperannotate.comSee also Transparency alternatives to SuperAnnotate | 57/100 | 3 Subprocessor list, Data location stated, Notice before subprocessors change | 2 Data processing agreement, Public pricing | Compare |
| V7v7labs.comSee also Transparency alternatives to V7 | 43/100 | 3 Data location stated, security.txt (RFC 9116), Named privacy contact | 2 Data processing agreement, Status page with history | Compare |
| Snorkelsnorkel.aiSee also Transparency alternatives to Snorkel | 13/100 | 3 Uptime SLA with a figure, security.txt (RFC 9116), Named privacy contact | 5 Data processing agreement, Status page with history, Public pricing, +2 | Compare |
| Hivethehive.aiSee also Transparency alternatives to Hive | 43/100 | 2 Data location stated, Named privacy contact | 2 Data processing agreement, Certifications named | Compare |
| iMeritimerit.netSee also Transparency alternatives to iMerit | 32/100 | 2 Data location stated, Named privacy contact | 3 Data processing agreement, Status page with history, Certifications named | Compare |
| Understand.aiunderstand.aiSee also Transparency alternatives to Understand.ai | 26/100 | 2 Data location stated, Named privacy contact | 4 Data processing agreement, Status page with history, Public pricing, +1 | Compare |
| Tolokatoloka.aiSee also Transparency alternatives to Toloka | 22/100 | 2 security.txt (RFC 9116), Named privacy contact | 3 Data processing agreement, Status page with history, Public pricing | Compare |
| Encordencord.comSee also Transparency alternatives to Encord | 26/100 | 1 Data location stated | 3 Data processing agreement, Status page with history, Public pricing | Compare |
| LXTlxt.aiSee also Transparency alternatives to LXT | 26/100 | 1 Data location stated | 3 Data processing agreement, Status page with history, Public pricing | Compare |
| Appenappen.comSee also Transparency alternatives to Appen | 22/100 | 1 Named privacy contact | 3 Data processing agreement, Public pricing, Certifications named | Compare |
| Kognickognic.comSee also Transparency alternatives to Kognic | 22/100 | 1 Named privacy contact | 3 Data processing agreement, 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.