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