SaaS Ranking
Menu

Litmus

litmus.io · IoT platforms and connectivity · checked 2026-09-03

32/100EBand E

Rank 5 of 20 in IoT platforms and connectivity, where the median is 22.

We measured 11 of 12 criteria for Litmus on 2026-09-03. We found 4 with a source and did not find 7 at the addresses we checked; 1 we could not measure at all. That is a transparency score of 32 out of 100, band E.

Overview

Transparency labelsaas-ranking.com

Litmus

litmus.io · IoT platforms and connectivity

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

Published commitments3 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 Litmus has no such document.

Gaps, heaviest first

✗

Data processing agreement

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-09-03.

Show the 8 addresses we checked
  1. https://litmus.io/legal/dpa – reached, no match (HTTP 404)
  2. https://litmus.io/dpa – reached, no match (HTTP 404)
  3. https://litmus.io/legal/data-processing-agreement – reached, no match (HTTP 404)
  4. https://litmus.io/data-processing-agreement – reached, no match (HTTP 404)
  5. https://litmus.io/legal/data-processing-addendum – reached, no match (HTTP 404)
  6. https://litmus.io/legal/gdpr – reached, no match (HTTP 404)
  7. https://litmus.io/trust/dpa – reached, no match (HTTP 404)
  8. https://litmus.io/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-03.

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

Is this wrong? Send us the URL

✗

Data location stated

weight 3 of 3

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

Seen at https://litmus.io/privacy-policy · checked 2026-09-03

Show the 7 addresses we checked
  1. https://litmus.io/security – reached, no match (HTTP 404)
  2. https://litmus.io/trust – reached, no match (HTTP 404)
  3. https://litmus.io/legal/privacy – reached, no match (HTTP 404)
  4. https://litmus.io/privacy – reached, no match (HTTP 404)
  5. https://litmus.io/privacy-policy – found, but behind a sign-in
  6. https://litmus.io/compliance – reached, no match (HTTP 404)
  7. https://litmus.io/legal/privacy-policy – 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-03.

Show the 1 address we checked
  1. https://litmus.io/ – third-party requests before any interaction: 45437139.hs-sites.com, 7052064.fs1.hubspotusercontent-na1.net, ad.doubleclick.net, api.claydar.com, api.hubapi.com, api.hubspot.com, app.hubspot.com, app.termly.io, cdn.claydar.com, cta-service-cms2.hubspot.com, forms.hscollectedforms.net, g.clarity.ms, images.ctfassets.net, js.hs-analytics.net, js.hs-banner.com, js.hs-scripts.com, js.hsadspixel.net, js.hscollectedforms.net, js.hsforms.net, js.hubspot.com, js.usemessages.com, js.zi-scripts.com, o4508456184578048.ingest.us.sentry.io, perf-na1.hsforms.com, px.ads.linkedin.com, region1.analytics.google.com, scout-cdn.salesloft.com, scout.salesloft.com, scripts.clarity.ms, snap.licdn.com, static.claydar.com, static.cloudflareinsights.com, static.hsappstatic.net, static.hubspot.com, stats.g.doubleclick.net, track.hubspot.com, ws.zoominfo.com, www.clarity.ms, www.google.com, www.google.de, www.googletagmanager.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-03.

Show the 8 addresses we checked
  1. https://litmus.io/legal/subprocessors – reached, no match (HTTP 404)
  2. https://litmus.io/subprocessors – reached, no match (HTTP 404)
  3. https://litmus.io/sub-processors – reached, no match (HTTP 404)
  4. https://litmus.io/legal/dpa – reached, no match (HTTP 404)
  5. https://litmus.io/dpa – reached, no match (HTTP 404)
  6. https://litmus.io/legal/data-processing-agreement – reached, no match (HTTP 404)
  7. https://litmus.io/trust/subprocessors – reached, no match (HTTP 404)
  8. https://litmus.io/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-03.

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

Is this wrong? Send us the URL

✗

Named privacy contact

weight 1 of 3

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

Seen at https://litmus.io/privacy-policy · checked 2026-09-03

Show the 7 addresses we checked
  1. https://litmus.io/legal/privacy – reached, no match (HTTP 404)
  2. https://litmus.io/privacy – reached, no match (HTTP 404)
  3. https://litmus.io/privacy-policy – found, but behind a sign-in
  4. https://litmus.io/legal/privacy-policy – reached, no match (HTTP 404)
  5. https://litmus.io/legal/privacy-notice – reached, no match (HTTP 404)
  6. https://litmus.io/trust/privacy – reached, no match (HTTP 404)
  7. https://litmus.io/datenschutz – 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
✓

Status page with history

weight 2 of 3

A public status page with incident history.

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

✓

Public pricing

weight 2 of 3

Actual numbers on a public page.

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

✓

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

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

✓

Certifications named

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

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

Not measured by us 1
–

security.txt (RFC 9116)

weight 1 of 3

Not measured. The vendor’s server blocked or rate-limited our crawler, so this was not measured.

Show the 1 address we checked
  1. https://litmus.io/.well-known/security.txt – blocked or unavailable (HTTP 500)

Is this wrong? Send us the URL

History

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

Compare