SaaS Ranking

Ombud

ombud.com · Proposals and quoting · checked 2026-09-04

19/100FBand F

Rank 13 of 26 in Proposals and quoting, where the median is 18.5.

We measured 11 of 12 criteria for Ombud on 2026-09-04. We found 3 with a source and did not find 8 at the addresses we checked; 1 we could not measure at all. That is a transparency score of 19 out of 100, band F.

Overview

Transparency labelsaas-ranking.com

Ombud

ombud.com · Proposals and quoting

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
F 19of 100 Rank 13 of 26

Published commitments2 of 9 found

Measured behaviour1 of 2 found, 1 not measured

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 Ombud 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 processing agreement

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-09-04.

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

Show the 7 addresses we checked
  1. https://ombud.com/legal/subprocessors – reached, no match (HTTP 404)
  2. https://ombud.com/subprocessors – reached, no match (HTTP 404)
  3. https://ombud.com/sub-processors – reached, no match (HTTP 404)
  4. https://ombud.com/legal/sub-processors – reached, no match (HTTP 404)
  5. https://ombud.com/trust/subprocessors – reached, no match (HTTP 404)
  6. https://ombud.com/privacy/subprocessors – reached, no match (HTTP 404)
  7. https://ombud.com/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://www.ombud.com/privacy · checked 2026-09-04

Show the 7 addresses we checked
  1. https://ombud.com/security – reached, no match (HTTP 200)
  2. https://ombud.com/trust – reached, no match (HTTP 404)
  3. https://ombud.com/legal/privacy – reached, no match (HTTP 404)
  4. https://ombud.com/privacy – found, but behind a sign-in
  5. https://ombud.com/privacy-policy – reached, no match (HTTP 404)
  6. https://ombud.com/compliance – reached, no match (HTTP 404)
  7. https://ombud.com/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.ombud.com/ – reached, no match (HTTP 200)
  2. https://ombud.com/status – reached, no match (HTTP 404)
  3. https://ombud.com.statuspage.io/ – Could not be fetched: fetch failed.

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

Show the 5 addresses we checked
  1. https://ombud.com/pricing – reached, no match (HTTP 404)
  2. https://ombud.com/pricing/ – reached, no match (HTTP 404)
  3. https://ombud.com/plans – reached, no match (HTTP 404)
  4. https://ombud.com/en/pricing – reached, no match (HTTP 404)
  5. https://ombud.com/pricing-plans – reached, no match (HTTP 404)

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

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

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

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

Show the 1 address we checked
  1. https://ombud.com/.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 3

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

  • HSTS max-age 31536000 seconds (365 days).
    Show the exact wording

    max-age=31536000

    Read at https://ombud.com/

Source: https://ombud.com/ · checked 2026-09-04

Certifications named

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

Source: https://www.ombud.com/security · checked 2026-09-04

Named privacy contact

weight 1 of 3

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

Source: https://www.ombud.com/privacy · checked 2026-09-04

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://ombud.com/ – page.goto: net::ERR_SSL_PROTOCOL_ERROR at https://ombud.com/ Call log: - navigating to "https://ombud.com/", waiting until "domcontentloaded"

Is this wrong? Send us the URL

History

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

Compare