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