SaaS Ranking
Menu

Toloka

toloka.ai · Data labelling · checked 2026-09-05

22/100FBand F

Rank 22 of 39 in Data labelling, where the median is 22.

We measured 12 of 12 criteria for Toloka on 2026-09-05. We found 4 with a source and did not find 8 at the addresses we checked. That is a transparency score of 22 out of 100, band F.

Overview

Transparency labelsaas-ranking.com

Toloka

toloka.ai · Data labelling

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
F 22of 100 Rank 22 of 39

Published commitments2 of 9 found

Measured behaviour2 of 3 found

Checked 2026-09-05. Every line links the page we found it on. A cross means we found nothing at the addresses we checked, not that the vendor has no such document. A transparency score, not a product rating.

The evidence pack carries every criterion with its source, the addresses we checked, the date and the data snapshot id – the four things a procurement file needs and a screenshot loses. We do not issue badges: a badge is the first step towards a paid placement, and there is none here.

The label is the whole measurement in one object: every criterion with its weight, the band, and the date. Public transparency score, not a product or security rating.

Every line in it links the page we found the result on, or lists the addresses we checked. A cross means we found nothing there, not that Toloka has no such document.

What they state

The exact figures and names we read off the pages linked below, with the sentence they stand in. This is what they publish, not what we verified about their systems.

Gaps, heaviest first

✗

Data processing agreement

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-09-05.

Show the 8 addresses we checked
  1. https://toloka.ai/legal/dpa – reached, no match (HTTP 404)
  2. https://toloka.ai/dpa – reached, no match (HTTP 404)
  3. https://toloka.ai/legal/data-processing-agreement – reached, no match (HTTP 404)
  4. https://toloka.ai/data-processing-agreement – reached, no match (HTTP 404)
  5. https://toloka.ai/legal/data-processing-addendum – reached, no match (HTTP 404)
  6. https://toloka.ai/legal/gdpr – reached, no match (HTTP 404)
  7. https://toloka.ai/trust/dpa – reached, no match (HTTP 404)
  8. https://toloka.ai/privacy/dpa – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

Subprocessor list

weight 3 of 3

No subprocessor list found.

Checked 7 addresses on 2026-09-05.

Show the 7 addresses we checked
  1. https://toloka.ai/legal/subprocessors – reached, no match (HTTP 404)
  2. https://toloka.ai/subprocessors – reached, no match (HTTP 404)
  3. https://toloka.ai/sub-processors – reached, no match (HTTP 404)
  4. https://toloka.ai/legal/sub-processors – reached, no match (HTTP 404)
  5. https://toloka.ai/trust/subprocessors – reached, no match (HTTP 404)
  6. https://toloka.ai/privacy/subprocessors – reached, no match (HTTP 404)
  7. https://toloka.ai/legal/subprocessor-list – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

Data location stated

weight 3 of 3

No statement about data location found.

Checked 7 addresses on 2026-09-05.

Show the 7 addresses we checked
  1. https://toloka.ai/security – reached, no match (HTTP 200)
  2. https://toloka.ai/trust – reached, no match (HTTP 404)
  3. https://toloka.ai/legal/privacy – reached, no match (HTTP 404)
  4. https://toloka.ai/privacy – reached, no match (HTTP 404)
  5. https://toloka.ai/privacy-policy – reached, no match (HTTP 404)
  6. https://toloka.ai/compliance – reached, no match (HTTP 404)
  7. https://toloka.ai/legal/privacy-policy – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

Status page with history

weight 2 of 3

No public status page found.

Checked 3 addresses on 2026-09-05.

Show the 3 addresses we checked
  1. https://status.toloka.ai/ – The name "status.toloka.ai" resolves to a private or local address (10.4.0.125) and is not fetched.
  2. https://toloka.ai/status – reached, no match (HTTP 404)
  3. https://toloka.ai.statuspage.io/ – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

✗

Public pricing

weight 2 of 3

No public pricing with figures found.

Checked 5 addresses on 2026-09-05.

Show the 5 addresses we checked
  1. https://toloka.ai/pricing – reached, no match (HTTP 404)
  2. https://toloka.ai/pricing/ – reached, no match (HTTP 404)
  3. https://toloka.ai/plans – reached, no match (HTTP 404)
  4. https://toloka.ai/en/pricing – reached and rendered, no match
  5. https://toloka.ai/pricing-plans – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

No third-party tracking before consent

weight 2 of 3

No consent-free first load found.

Checked 1 address on 2026-09-05.

Show the 1 address we checked
  1. https://toloka.ai/ – third-party requests before any interaction: alb.reddit.com, analytics.twitter.com, app.sourceloop.ai, bat.bing.com, bat.bing.net, events.framer.com, framer-components.toloka.cloud, framerusercontent.com, js-eu1.hs-scripts.com, n.clarity.ms, pixel-config.reddit.com, px.ads.linkedin.com, region1.analytics.google.com, sc.lfeeder.com, scripts.clarity.ms, snap.licdn.com, static.ads-twitter.com, stats.g.doubleclick.net, t.co, tlkfrontprod.azureedge.net, www.clarity.ms, www.google.com, www.google.de, www.googletagmanager.com, www.redditstatic.com

Is this wrong? Send us the URL

✗

Notice before subprocessors change

weight 2 of 3

No commitment to give notice before subprocessors change found.

Checked 8 addresses on 2026-09-05.

Show the 8 addresses we checked
  1. https://toloka.ai/legal/subprocessors – reached, no match (HTTP 404)
  2. https://toloka.ai/subprocessors – reached, no match (HTTP 404)
  3. https://toloka.ai/sub-processors – reached, no match (HTTP 404)
  4. https://toloka.ai/legal/dpa – reached, no match (HTTP 404)
  5. https://toloka.ai/dpa – reached, no match (HTTP 404)
  6. https://toloka.ai/legal/data-processing-agreement – reached, no match (HTTP 404)
  7. https://toloka.ai/trust/subprocessors – reached, no match (HTTP 404)
  8. https://toloka.ai/legal/sub-processors – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

Uptime SLA with a figure

weight 1 of 3

No uptime figure found.

Checked 6 addresses on 2026-09-05.

Show the 6 addresses we checked
  1. https://toloka.ai/legal/sla – reached, no match (HTTP 404)
  2. https://toloka.ai/sla – reached, no match (HTTP 404)
  3. https://toloka.ai/legal/service-level-agreement – reached, no match (HTTP 404)
  4. https://toloka.ai/trust/sla – reached, no match (HTTP 404)
  5. https://toloka.ai/uptime – reached, no match (HTTP 404)
  6. https://toloka.ai/legal/uptime-sla – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Evidence

The full source lists sit behind these two groups, so that the answer above stays readable.

Published, with a source 4
✓

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

  • HSTS max-age 31536000 seconds (365 days).
    Show the exact wording

    max-age=31536000

    Read at https://toloka.ai/

Source: https://toloka.ai/ · checked 2026-09-05

✓

Certifications named

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

  • Named on that page ISO/IEC 27001 (named without a certification claim), ISO/IEC 27701 (named without a certification claim), SOC 2 Type II (named without a certification claim).
    Show the 3 exact wordings

    ISO 27001 The international standard provides a framework for information risk management to guarantee confid

    Read at https://toloka.ai/security

    ISO 27701 This standard ensures the secure collection, handling, storage, and destruction of personally ident

    Read at https://toloka.ai/security

    SOC 2 Type II Toloka addresses risks associated with information security, access control, vendor managem

    Read at https://toloka.ai/security

Source: https://toloka.ai/security · checked 2026-09-05

✓

security.txt (RFC 9116)

weight 1 of 3

Served at /.well-known/security.txt.

  • The file expires 2026-02-11. That date had passed when we checked on 2026-09-05, so the file was stale (RFC 9116).
    Show the exact wording

    Expires: 2026-02-11T23:00:00.000Z

    Read at https://toloka.ai/.well-known/security.txt

Source: https://toloka.ai/.well-known/security.txt · checked 2026-09-05

✓

Named privacy contact

weight 1 of 3

A data protection officer or a dedicated privacy address is named.

Source: https://toloka.ai/legal/privacy-notice · checked 2026-09-05

History

Not enough completed runs yet to draw a line. The next runs fill this in.

Compare

A shortlist holds up to six vendors across categories and lives entirely in the address of its page: share the link, bookmark it, put it in a ticket. Nothing is stored, so we do not know it exists.