SaaS Ranking

Exiger

exiger.com · Supply chain risk · checked 2026-09-03

26/100EBand E

Rank 9 of 24 in Supply chain risk, where the median is 20.

We measured 12 of 12 criteria for Exiger on 2026-09-03. We found 3 with a source and did not find 9 at the addresses we checked. That is a transparency score of 26 out of 100, band E.

Overview

Transparency labelsaas-ranking.com

Exiger

exiger.com · Supply chain risk

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

Published commitments2 of 9 found

Measured behaviour1 of 3 found

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.

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 Exiger 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://exiger.com/legal/dpa – reached, no match (HTTP 404)
  2. https://exiger.com/dpa – No answer within 10 seconds.
  3. https://exiger.com/legal/data-processing-agreement – No answer within 10 seconds.
  4. https://exiger.com/data-processing-agreement – reached, no match (HTTP 404)
  5. https://exiger.com/legal/data-processing-addendum – No answer within 10 seconds.
  6. https://exiger.com/legal/gdpr – No answer within 10 seconds.
  7. https://exiger.com/trust/dpa – reached, no match (HTTP 404)
  8. https://exiger.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-03.

Show the 7 addresses we checked
  1. https://exiger.com/legal/subprocessors – reached, no match (HTTP 404)
  2. https://exiger.com/subprocessors – reached, no match (HTTP 404)
  3. https://exiger.com/sub-processors – reached, no match (HTTP 404)
  4. https://exiger.com/legal/sub-processors – reached, no match (HTTP 404)
  5. https://exiger.com/trust/subprocessors – reached, no match (HTTP 404)
  6. https://exiger.com/privacy/subprocessors – reached, no match (HTTP 404)
  7. https://exiger.com/legal/subprocessor-list – 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-03.

Show the 3 addresses we checked
  1. https://status.exiger.com/ – The name "status.exiger.com" could not be resolved.
  2. https://exiger.com/status – reached, no match (HTTP 404)
  3. https://exiger.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-03.

Show the 5 addresses we checked
  1. https://exiger.com/pricing – reached, no match (HTTP 404)
  2. https://exiger.com/pricing/ – reached, no match (HTTP 404)
  3. https://exiger.com/plans – reached, no match (HTTP 404)
  4. https://exiger.com/en/pricing – reached, no match (HTTP 404)
  5. https://exiger.com/pricing-plans – 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://exiger.com/ – third-party requests before any interaction: consent.cookiebot.com, consentcdn.cookiebot.com, forms-na1.hsforms.com, forms.hsforms.com, js.hs-scripts.com, js.hsforms.net, pagead2.googlesyndication.com, player.vimeo.com, region1.google-analytics.com, www.google.com, www.googletagmanager.com, www.gstatic.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://exiger.com/legal/subprocessors – reached, no match (HTTP 404)
  2. https://exiger.com/subprocessors – reached, no match (HTTP 404)
  3. https://exiger.com/sub-processors – reached, no match (HTTP 404)
  4. https://exiger.com/legal/dpa – reached, no match (HTTP 404)
  5. https://exiger.com/dpa – reached, no match (HTTP 404)
  6. https://exiger.com/legal/data-processing-agreement – reached, no match (HTTP 404)
  7. https://exiger.com/trust/subprocessors – reached, no match (HTTP 404)
  8. https://exiger.com/legal/sub-processors – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Certifications named

weight 1 of 3

No named certification found.

Checked 6 addresses on 2026-09-03.

Show the 6 addresses we checked
  1. https://exiger.com/security – reached, no match (HTTP 404)
  2. https://exiger.com/trust – Not the expected content type but "image/jpeg".
  3. https://exiger.com/trust-center – reached, no match (HTTP 404)
  4. https://exiger.com/compliance – reached, no match (HTTP 200)
  5. https://exiger.com/legal/security – reached, no match (HTTP 404)
  6. https://trust.exiger.com/ – The name "trust.exiger.com" could not be resolved.

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://exiger.com/legal/sla – reached, no match (HTTP 404)
  2. https://exiger.com/sla – reached, no match (HTTP 404)
  3. https://exiger.com/legal/service-level-agreement – reached, no match (HTTP 404)
  4. https://exiger.com/trust/sla – reached, no match (HTTP 404)
  5. https://exiger.com/uptime – reached, no match (HTTP 404)
  6. https://exiger.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-03.

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

Data location stated

weight 3 of 3

The hosting location is stated on a public page.

Source: https://www.exiger.com/privacy-and-legal-center/ · checked 2026-09-03

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

Source: https://exiger.com/ · checked 2026-09-03

Named privacy contact

weight 1 of 3

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

Source: https://www.exiger.com/privacy-and-legal-center/ · checked 2026-09-03

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.