SaaS Ranking

OhDear

ohdear.app · Incident management · checked 2026-09-05

61/100CBand C

Rank 5 of 32 in Incident management, where the median is 30.

We measured 12 of 12 criteria for OhDear on 2026-09-05. We found 7 with a source and did not find 5 at the addresses we checked. That is a transparency score of 61 out of 100, band C.

Overview

Transparency labelsaas-ranking.com

OhDear

ohdear.app · Incident management

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

Published commitments6 of 9 found

Measured behaviour1 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 OhDear 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

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.ohdear.app/ – reached, no match (HTTP 200)
  2. https://ohdear.app/status – reached, no match (HTTP 404)
  3. https://ohdear.app.statuspage.io/ – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

HTTPS enforced with HSTS

weight 2 of 3

No enforced HTTPS with HSTS found.

Checked 2 addresses on 2026-09-05.

Show the 2 addresses we checked
  1. http://ohdear.app/ – redirects to https://ohdear.app/
  2. https://ohdear.app/ – no HSTS header

Is this wrong? Send us the URL

No third-party tracking before consent

weight 2 of 3

No consent-free first load found.

  • Third-party hosts we saw on the first load 1 usefathom.com.
    Show the exact wording

    cdn.usefathom.com

    Read at https://ohdear.app/

Checked 1 address on 2026-09-05.

Show the 1 address we checked
  1. https://ohdear.app/ – third-party requests before any interaction: cdn.usefathom.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://ohdear.app/legal/subprocessors – reached, no match (HTTP 404)
  2. https://ohdear.app/subprocessors – reached, no match (HTTP 200)
  3. https://ohdear.app/sub-processors – reached, no match (HTTP 404)
  4. https://ohdear.app/legal/dpa – reached, no match (HTTP 404)
  5. https://ohdear.app/dpa – reached, no match (HTTP 404)
  6. https://ohdear.app/legal/data-processing-agreement – reached, no match (HTTP 404)
  7. https://ohdear.app/trust/subprocessors – reached, no match (HTTP 404)
  8. https://ohdear.app/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://ohdear.app/legal/sla – reached, no match (HTTP 404)
  2. https://ohdear.app/sla – reached, no match (HTTP 404)
  3. https://ohdear.app/legal/service-level-agreement – reached, no match (HTTP 404)
  4. https://ohdear.app/trust/sla – reached, no match (HTTP 404)
  5. https://ohdear.app/uptime – reached, no match (HTTP 404)
  6. https://ohdear.app/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 7

Data processing agreement

weight 3 of 3

Published and readable without a login.

Source: https://ohdear.app/data-processing-agreement · checked 2026-09-05

Subprocessor list

weight 3 of 3

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

Source: https://ohdear.app/subprocessors · checked 2026-09-05

Data location stated

weight 3 of 3

The hosting location is stated on a public page.

  • Locations named next to the hosting wording Belgium.
    Show the exact wording

    Infrastructure We rely on providers with proper certifications: Primary hosting: Combell (Belgium) - ISO 9001, ISO 27001, ISO 27701 certified Performance metrics: ClickHouse Cloud - SOC 2 Type II,

    Read at https://ohdear.app/security

Source: https://ohdear.app/security · checked 2026-09-05

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://ohdear.app/pricing · 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 9001, ISO/IEC 27001 (named without a certification claim), ISO/IEC 27701 (unclear from the sentence), SOC 2 (named without a certification claim), SOC 2 Type II (a named provider of theirs).
    Show the 5 exact wordings

    nfrastructure We rely on providers with proper certifications: Primary hosting: Combell (Belgium) - ISO 9001, ISO 27001, ISO 27701 certified Performance metrics: ClickHouse Cloud - SOC 2 Type II, ISO....

    Read at https://ohdear.app/security

    Security: TLS Encryption & ISO 27001 EU Hosting | Oh Dear Skip to content Light Dark System Log In Oh Dear Home Features Features Availa

    Read at https://ohdear.app/security

    on providers with proper certifications: Primary hosting: Combell (Belgium) - ISO 9001, ISO 27001, ISO 27701 certified Performance metrics: ClickHouse Cloud - SOC 2 Type II, ISO 27001 CDN & Protection...

    Read at https://ohdear.app/security

    Why No SOC 2 (Yet)?

    Read at https://ohdear.app/security

    ombell (Belgium) - ISO 9001, ISO 27001, ISO 27701 certified Performance metrics: ClickHouse Cloud - SOC 2 Type II, ISO 27001 CDN & Protection: Cloudflare - SOC 2 Type II, ISO 27001 Monitoring nodes: A...

    Read at https://ohdear.app/security

Source: https://ohdear.app/security · checked 2026-09-05

security.txt (RFC 9116)

weight 1 of 3

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

Source: https://ohdear.app/.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.

  • What the privacy page carries Dedicated privacy address.
    Show the exact wording

    [address]@ohdear.app

    Read at https://ohdear.app/privacy

Source: https://ohdear.app/privacy · 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.