Transparency alternatives to Toloka
Other Data labelling vendors we measure, sorted by how much we found at them and not at Toloka. This is a comparison of disclosure, not of features or fitness.
12 shown of 38 that differ from Toloka on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Toloka has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change. The column “Found there, not found at Toloka” is the one that closes them.
| Vendor | Score | Found there, not found at Toloka | Found at Toloka, not found there | |
|---|---|---|---|---|
| SuperAnnotatesuperannotate.comSee also Transparency alternatives to SuperAnnotate | 57/100 | 4 Subprocessor list, Data location stated, Status page with history, +1 | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Scale AIscale.comSee also Transparency alternatives to Scale AI | 52/100 | 3 Subprocessor list, Status page with history, Notice before subprocessors change | nothing | Compare |
| Hivethehive.aiSee also Transparency alternatives to Hive | 43/100 | 3 Data location stated, Status page with history, Public pricing | 2 Certifications named, security.txt (RFC 9116) | Compare |
| HumanSignalhumansignal.comSee also Transparency alternatives to HumanSignal | 43/100 | 3 Data processing agreement, Status page with history, Public pricing | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| V7v7labs.comSee also Transparency alternatives to V7 | 43/100 | 2 Data location stated, Public pricing | nothing | Compare |
| Datasaurdatasaur.aiSee also Transparency alternatives to Datasaur | 30/100 | 2 Status page with history, Public pricing | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| CVATcvat.aiSee also Transparency alternatives to CVAT | 26/100 | 2 Status page with history, Public pricing | 3 Certifications named, security.txt (RFC 9116), Named privacy contact | Compare |
| Kilikili-technology.comSee also Transparency alternatives to Kili | 26/100 | 2 Status page with history, Public pricing | 3 Certifications named, security.txt (RFC 9116), Named privacy contact | Compare |
| Segments.aisegments.aiSee also Transparency alternatives to Segments.ai | 22/100 | 2 Data location stated, Public pricing | 4 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116), +1 | Compare |
| iMeritimerit.netSee also Transparency alternatives to iMerit | 32/100 | 1 Data location stated | 1 Certifications named | Compare |
| Encordencord.comSee also Transparency alternatives to Encord | 26/100 | 1 Data location stated | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| LXTlxt.aiSee also Transparency alternatives to LXT | 26/100 | 1 Data location stated | 2 security.txt (RFC 9116), Named privacy contact | 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.