SaaS Ranking

Split

split.io · Feature flags and experimentation · checked 2026-09-03

52/100DBand D

Rank 5 of 16 in Feature flags and experimentation, where the median is 37.

We measured 11 of 12 criteria for Split on 2026-09-03. We found 6 with a source and did not find 5 at the addresses we checked; 1 we could not measure at all. That is a transparency score of 52 out of 100, band D.

Overview

Transparency labelsaas-ranking.com

Split

split.io · Feature flags and experimentation

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

Published commitments5 of 9 found

Measured behaviour1 of 2 found, 1 not measured

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 Split has no such document.

Gaps, heaviest first

Data processing agreement

weight 3 of 3

We found this behind a sign-in, so it is not published openly.

Seen at https://trust.harness.io/?utm_campaign=fme&utm_source=split_io&utm_medium=redirect&utm_content=wildcard · checked 2026-09-03

Show the 8 addresses we checked
  1. https://split.io/legal/dpa – reached, no match (HTTP 200)
  2. https://split.io/dpa – reached, no match (HTTP 404)
  3. https://split.io/legal/data-processing-agreement – reached, no match (HTTP 200)
  4. https://split.io/data-processing-agreement – reached, no match (HTTP 404)
  5. https://split.io/legal/data-processing-addendum – reached, no match (HTTP 200)
  6. https://split.io/legal/gdpr – reached, no match (HTTP 200)
  7. https://split.io/trust/dpa – found, but behind a sign-in
  8. https://split.io/privacy/dpa – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Subprocessor list

weight 3 of 3

We found this behind a sign-in, so it is not published openly.

Seen at https://trust.harness.io/?utm_campaign=fme&utm_source=split_io&utm_medium=redirect&utm_content=wildcard · checked 2026-09-03

Show the 7 addresses we checked
  1. https://split.io/legal/subprocessors – reached, no match (HTTP 200)
  2. https://split.io/subprocessors – reached, no match (HTTP 404)
  3. https://split.io/sub-processors – reached, no match (HTTP 404)
  4. https://split.io/legal/sub-processors – reached, no match (HTTP 200)
  5. https://split.io/trust/subprocessors – found, but behind a sign-in
  6. https://split.io/privacy/subprocessors – reached, no match (HTTP 404)
  7. https://split.io/legal/subprocessor-list – reached, no match (HTTP 200)

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-03.

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

Is this wrong? Send us the URL

Uptime SLA with a figure

weight 1 of 3

We found this behind a sign-in, so it is not published openly.

Seen at https://trust.harness.io/?utm_campaign=fme&utm_source=split_io&utm_medium=redirect&utm_content=wildcard · checked 2026-09-03

Show the 6 addresses we checked
  1. https://split.io/legal/sla – reached, no match (HTTP 200)
  2. https://split.io/sla – reached, no match (HTTP 404)
  3. https://split.io/legal/service-level-agreement – reached, no match (HTTP 200)
  4. https://split.io/trust/sla – found, but behind a sign-in
  5. https://split.io/uptime – reached, no match (HTTP 404)
  6. https://split.io/legal/uptime-sla – reached, no match (HTTP 200)

Is this wrong? Send us the URL

security.txt (RFC 9116)

weight 1 of 3

No security.txt found.

Checked 1 address on 2026-09-03.

Show the 1 address we checked
  1. https://split.io/.well-known/security.txt – 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 6

Data location stated

weight 3 of 3

The hosting location is stated on a public page.

Source: https://www.harness.io/legal/subscription-terms · checked 2026-09-03

Status page with history

weight 2 of 3

A public status page with incident history.

Source: https://status.harness.io/ · checked 2026-09-03

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

Source: https://split.io/ · checked 2026-09-03

Notice before subprocessors change

weight 2 of 3

The vendor commits publicly to giving notice before the list changes.

Source: https://trust.harness.io/?utm_campaign=fme&utm_source=split_io&utm_medium=redirect&utm_content=wildcard · checked 2026-09-03

Certifications named

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

Source: https://trust.harness.io/?utm_campaign=fme&utm_source=split_io&utm_medium=redirect&utm_content=individual · checked 2026-09-03

Named privacy contact

weight 1 of 3

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

Source: https://trust.harness.io/?utm_campaign=fme&utm_source=split_io&utm_medium=redirect&utm_content=wildcard · checked 2026-09-03

Not measured by us 1

No third-party tracking before consent

weight 2 of 3

Not measured. The page could not be loaded in a browser, so this was not measured.

Show the 1 address we checked
  1. https://split.io/ – page.waitForTimeout: Page crashed

Is this wrong? Send us the URL

History

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

Compare