SaaS Ranking
Menu

incident.io

incident.io · Incident management · checked 2026-09-04

65/100CBand C

Rank 2 of 23 in Incident management, where the median is 30.

We measured 12 of 12 criteria for incident.io on 2026-09-04. We found 8 with a source and did not find 4 at the addresses we checked. That is a transparency score of 65 out of 100, band C.

Overview

Transparency labelsaas-ranking.com

incident.io

incident.io · Incident management

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

Published commitments6 of 9 found

Measured behaviour2 of 3 found

Checked 2026-09-04. 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 incident.io 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 location stated

weight 3 of 3

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

Seen at https://incident.io/legal/privacy · checked 2026-09-04

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

Show the 3 addresses we checked
  1. https://status.incident.io/ – reached, no match (HTTP 200)
  2. https://incident.io/status – reached, no match (HTTP 404)
  3. https://incident.io.statuspage.io/ – Could not be fetched: fetch failed.

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

Show the 1 address we checked
  1. https://incident.io/ – third-party requests before any interaction: ajax.googleapis.com, cdn.iubenda.com, embeds.iubenda.com, noembed.com, osai-cdn.onescreen.ai, pagead2.googlesyndication.com, region1.analytics.google.com, s3-us-west-2.amazonaws.com, sc.lfeeder.com, stats.g.doubleclick.net, www.google.de, www.googletagmanager.com, www.redditstatic.com

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://incident.io/legal/privacy · checked 2026-09-04

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

Data processing agreement

weight 3 of 3

Published and readable without a login.

Source: https://incident.io/legal/data-processing-agreement · checked 2026-09-04

✓

Subprocessor list

weight 3 of 3

The actual list is published, not just a promise to keep one.

Source: https://incident.io/legal/sub-processors · checked 2026-09-04

✓

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://incident.io/pricing · checked 2026-09-04

✓

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

  • HSTS max-age 63072000 seconds (730 days).
    Show the exact wording

    max-age=63072000; includeSubDomains; preload

    Read at https://incident.io/
  • HSTS options includeSubDomains, preload.
    Show the 2 exact wordings

    max-age=63072000; includeSubDomains; preload

    Read at https://incident.io/

    max-age=63072000; includeSubDomains; preload

    Read at https://incident.io/

Source: https://incident.io/ · checked 2026-09-04

✓

Notice before subprocessors change

weight 2 of 3

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

Source: https://incident.io/legal/data-processing-agreement · checked 2026-09-04

✓

Certifications named

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

  • Named on that page SOC 2.
    Show the exact wording

    We're SOC 2 Type I & II and GDPR compliant to ensure your data stays safe.

    Read at https://incident.io/security

Source: https://incident.io/security · checked 2026-09-04

✓

Uptime SLA with a figure

weight 1 of 3

An availability commitment with a figure.

  • Highest uptime figure on that page 99.99 %.
    Show the exact wording

    rm Availability 99.9% 99.9% (b) Triggering of Notification following Ingestion of an Incident 99.9% 99.99% 3.1.1.

    Read at https://incident.io/legal/sla

Source: https://incident.io/legal/sla · checked 2026-09-04

✓

security.txt (RFC 9116)

weight 1 of 3

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

Source: https://incident.io/.well-known/security.txt · checked 2026-09-04

History

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

Compare