SaaS Ranking
Menu

Klaxon

klaxon.io · Mass notification and critical events · checked 2026-09-24

10/100FBand F

Rank 26 of 39 in Mass notification and critical events, where the median is 13.

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

Overview

1 day since the newest finding, 1 since the oldest. 12 of 12 criteria measured in the last 30 days.

Evidence freshness is a statement about our measurement and is kept apart from the transparency score, which is frozen at v1. How good our own measurement is.

Transparency labelsaas-ranking.com

Klaxon

klaxon.io · Mass notification and critical events

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

Published commitments0 of 9 found

Measured behaviour1 of 2 found, 1 not measured

Checked 2026-09-24. 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 Klaxon has no such document.

Where Klaxon sits in Mass notification and critical events

  1. A0 0%
  2. B0 0%
  3. C0 0%
  4. D2 5%
  5. E6 15%
  6. F31 79%
39 vendors with a score; 2 more without a score because we could measure too little. Bands have fixed thresholds, see how the score works.

The band of Klaxon is marked. Vendors without a score are the ones where we could measure too few criteria to rank them – a gap on our side, counted separately.

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

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

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

Is this wrong? Send us the URL

✗

Data location stated

weight 3 of 3

No statement about data location found.

Checked 7 addresses on 2026-09-24.

Show the 7 addresses we checked
  1. https://klaxon.io/security – reached, no match (HTTP 404)
  2. https://klaxon.io/trust – reached, no match (HTTP 404)
  3. https://klaxon.io/legal/privacy – reached, no match (HTTP 404)
  4. https://klaxon.io/privacy – reached, no match (HTTP 404)
  5. https://klaxon.io/privacy-policy – reached, no match (HTTP 404)
  6. https://klaxon.io/compliance – reached, no match (HTTP 404)
  7. https://klaxon.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-24.

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

Show the 5 addresses we checked
  1. https://klaxon.io/pricing – reached, no match (HTTP 404)
  2. https://klaxon.io/pricing/ – reached, no match (HTTP 404)
  3. https://klaxon.io/plans – reached, no match (HTTP 404)
  4. https://klaxon.io/en/pricing – reached, no match (HTTP 404)
  5. https://klaxon.io/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-24.

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

Show the 6 addresses we checked
  1. https://klaxon.io/security – reached, no match (HTTP 404)
  2. https://klaxon.io/trust – reached, no match (HTTP 404)
  3. https://klaxon.io/trust-center – reached, no match (HTTP 404)
  4. https://klaxon.io/compliance – reached, no match (HTTP 404)
  5. https://klaxon.io/legal/security – reached, no match (HTTP 404)
  6. https://trust.klaxon.io/ – The name "trust.klaxon.io" 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-24.

Show the 6 addresses we checked
  1. https://klaxon.io/legal/sla – reached, no match (HTTP 404)
  2. https://klaxon.io/sla – reached, no match (HTTP 404)
  3. https://klaxon.io/legal/service-level-agreement – reached, no match (HTTP 404)
  4. https://klaxon.io/trust/sla – reached, no match (HTTP 404)
  5. https://klaxon.io/uptime – reached, no match (HTTP 404)
  6. https://klaxon.io/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-24.

Show the 1 address we checked
  1. https://klaxon.io/.well-known/security.txt – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

Named privacy contact

weight 1 of 3

No named privacy contact found.

Checked 7 addresses on 2026-09-24.

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

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

  • HSTS max-age 10886400 seconds (126 days).
    Show the exact wording

    max-age=10886400; includeSubDomains; preload

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

    max-age=10886400; includeSubDomains; preload

    Read at https://klaxon.io/

    max-age=10886400; includeSubDomains; preload

    Read at https://klaxon.io/

Source: https://klaxon.io/ · checked 2026-09-24

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

Is this wrong? Send us the URL

History

100 0 2026-09-16: 10 of 1002026-09-17: 10 of 1002026-09-24: 10 of 100 2026-09-16 2026-09-24
Score over the last 3 runs we measured Klaxon in: 10 (2026-09-16), 10 (2026-09-17), 10 (2026-09-24).

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.