data.world
data.world · Product information management · checked 2026-09-03
Rank 3 of 20 in Product information management, where the median is 26.
- 5 found
- 7 not found
- 0 not measured
We measured 12 of 12 criteria for data.world on 2026-09-03. We found 5 with a source and did not find 7 at the addresses we checked. That is a transparency score of 39 out of 100, band E.
Overview
Transparency labelsaas-ranking.com
data.world
- A
- B
- C
- D
- E
- F
Published commitments4 of 9 found
- not foundData processing agreement×3
- not foundSubprocessor list×3
- foundData location stated×3
- foundStatus page with history×2
- not foundPublic pricing×2
- not foundNotice before subprocessors change×2
- foundCertifications named×1
- not foundUptime SLA with a figure×1
- foundNamed privacy contact×1
Measured behaviour1 of 3 found
- foundHTTPS enforced with HSTS×2
- not foundNo third-party tracking before consent×2
- not foundsecurity.txt (RFC 9116)×1
Checked 2026-09-03. 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.
We do not issue badges: a badge is the first step towards a paid placement, and there is none here. The SVG is a document with the date in it, for your own files.
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 data.world has no such document.
Gaps, heaviest first
Data processing agreement
weight 3 of 3No data processing agreement found.
Checked 8 addresses on 2026-09-03.
Show the 8 addresses we checked
https://data.world/legal/dpa– reached, no match (HTTP 404)https://data.world/dpa– reached, no match (HTTP 200)https://data.world/legal/data-processing-agreement– reached, no match (HTTP 404)https://data.world/data-processing-agreement– reached, no match (HTTP 200)https://data.world/legal/data-processing-addendum– reached, no match (HTTP 404)https://data.world/legal/gdpr– reached, no match (HTTP 404)https://data.world/trust/dpa– reached, no match (HTTP 200)https://data.world/privacy/dpa– reached, no match (HTTP 404)
Subprocessor list
weight 3 of 3No subprocessor list found.
Checked 7 addresses on 2026-09-03.
Show the 7 addresses we checked
https://data.world/legal/subprocessors– reached, no match (HTTP 404)https://data.world/subprocessors– reached, no match (HTTP 200)https://data.world/sub-processors– reached, no match (HTTP 200)https://data.world/legal/sub-processors– reached, no match (HTTP 404)https://data.world/trust/subprocessors– reached, no match (HTTP 200)https://data.world/privacy/subprocessors– reached, no match (HTTP 404)https://data.world/legal/subprocessor-list– reached, no match (HTTP 404)
Public pricing
weight 2 of 3No public pricing with figures found.
Checked 5 addresses on 2026-09-03.
Show the 5 addresses we checked
https://data.world/pricing– reached, no match (HTTP 404)https://data.world/pricing/– reached, no match (HTTP 404)https://data.world/plans– reached and rendered, no matchhttps://data.world/en/pricing– reached, no match (HTTP 200)https://data.world/pricing-plans– reached, no match (HTTP 200)
No third-party tracking before consent
weight 2 of 3No consent-free first load found.
Checked 1 address on 2026-09-03.
Show the 1 address we checked
https://data.world/– third-party requests before any interaction: cmp.osano.com, js-na2.hs-scripts.com, js.hs-scripts.com, js.zi-scripts.com, r2d2-inbound-js-store-production.s3.us-east-1.amazonaws.com, ws.zoominfo.com, www.google.com, www.googletagmanager.com
Notice before subprocessors change
weight 2 of 3No commitment to give notice before subprocessors change found.
Checked 8 addresses on 2026-09-03.
Show the 8 addresses we checked
https://data.world/legal/subprocessors– reached, no match (HTTP 404)https://data.world/subprocessors– reached, no match (HTTP 200)https://data.world/sub-processors– reached, no match (HTTP 200)https://data.world/legal/dpa– reached, no match (HTTP 404)https://data.world/dpa– reached, no match (HTTP 200)https://data.world/legal/data-processing-agreement– reached, no match (HTTP 404)https://data.world/trust/subprocessors– reached, no match (HTTP 200)https://data.world/legal/sub-processors– reached, no match (HTTP 404)
Uptime SLA with a figure
weight 1 of 3No uptime figure found.
Checked 6 addresses on 2026-09-03.
Show the 6 addresses we checked
https://data.world/legal/sla– reached, no match (HTTP 404)https://data.world/sla– reached, no match (HTTP 200)https://data.world/legal/service-level-agreement– reached, no match (HTTP 404)https://data.world/trust/sla– reached, no match (HTTP 200)https://data.world/uptime– reached, no match (HTTP 200)https://data.world/legal/uptime-sla– reached, no match (HTTP 404)
security.txt (RFC 9116)
weight 1 of 3No security.txt found.
Checked 1 address on 2026-09-03.
Show the 1 address we checked
https://data.world/.well-known/security.txt– reached, no match (HTTP 200)
Evidence
The full source lists sit behind these two groups, so that the answer above stays readable.
Published, with a source 5
Data location stated
weight 3 of 3The hosting location is stated on a public page.
Source: https://data.world/legal/privacy/ · checked 2026-09-03
Status page with history
weight 2 of 3A public status page with incident history.
Source: https://status.data.world/ · checked 2026-09-03
HTTPS enforced with HSTS
weight 2 of 3HTTP redirects to HTTPS and the HSTS header is set.
Source: https://data.world/ · checked 2026-09-03
Certifications named
weight 1 of 3SOC 2 or ISO 27001 named on a public page.
Source: https://data.world/legal/security/ · checked 2026-09-03
Named privacy contact
weight 1 of 3A data protection officer or a dedicated privacy address is named.
Source: https://data.world/legal/privacy/ · checked 2026-09-03
History
Not enough completed runs yet to draw a line. The next runs fill this in.