SaaS Ranking
Menu

Threema Work

threema.ch · Customer communities · checked 2026-09-05

Not enough data: 7 of 12 criteria measured, so no transparency score

We measured 7 of 12 criteria for Threema Work on 2026-09-05. We found 1 with a source and did not find 6 at the addresses we checked; 5 we could not measure at all. Below our threshold there is no score and no rank, and that is a statement about our measurement.

Overview

Transparency labelsaas-ranking.com

Threema Work

threema.ch · Customer communities

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
Not enough data7 of 12 measured, no score

Published commitments1 of 7 found, 2 not measured

Measured behaviour3 not measured

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. We could measure 7 of 12 criteria, which is below our threshold, so there is no rank. That is a statement about our measurement, not about Threema Work.

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 Threema Work has no such document.

Gaps, heaviest first

✗

Subprocessor list

weight 3 of 3

No subprocessor list found.

Checked 7 addresses on 2026-09-05.

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

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

Show the 3 addresses we checked
  1. https://status.threema.ch/ – reached, no match (HTTP 200)
  2. https://threema.ch/status – reached, no match (HTTP 404)
  3. https://threema.ch.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-05.

Show the 5 addresses we checked
  1. https://threema.ch/pricing – reached, no match (HTTP 404)
  2. https://threema.ch/pricing/ – reached, no match (HTTP 404)
  3. https://threema.ch/plans – reached, no match (HTTP 404)
  4. https://threema.ch/en/pricing – reached and rendered, no match
  5. https://threema.ch/pricing-plans – blocked or unavailable (HTTP 429)

Is this wrong? Send us the URL

✗

Certifications named

weight 1 of 3

No named certification found.

Checked 6 addresses on 2026-09-05.

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

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

Data processing agreement

weight 3 of 3

Published and readable without a login.

Source: https://threema.com/en/dpa · checked 2026-09-05

Not measured by us 5
–

HTTPS enforced with HSTS

weight 2 of 3

Not measured. The HTTPS endpoint could not be reached, so this was not measured.

Show the 2 addresses we checked
  1. http://threema.ch/ – HTTP 500, no redirect to HTTPS
  2. https://threema.ch/ – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

–

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

Is this wrong? Send us the URL

–

Notice before subprocessors change

weight 2 of 3

Not measured. None of the addresses could be reached, so this was not measured.

Show the 8 addresses we checked
  1. https://threema.ch/legal/subprocessors – Could not be fetched: fetch failed.
  2. https://threema.ch/subprocessors – Could not be fetched: fetch failed.
  3. https://threema.ch/sub-processors – Could not be fetched: fetch failed.
  4. https://threema.ch/legal/dpa – Could not be fetched: fetch failed.
  5. https://threema.ch/dpa – Could not be fetched: fetch failed.
  6. https://threema.ch/legal/data-processing-agreement – Could not be fetched: fetch failed.
  7. https://threema.ch/trust/subprocessors – Could not be fetched: fetch failed.
  8. https://threema.ch/legal/sub-processors – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

–

security.txt (RFC 9116)

weight 1 of 3

Not measured. None of the addresses could be reached, so this was not measured.

Show the 1 address we checked
  1. https://threema.ch/.well-known/security.txt – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

–

Named privacy contact

weight 1 of 3

Not measured. None of the addresses could be reached, so this was not measured.

Show the 7 addresses we checked
  1. https://threema.ch/legal/privacy – Could not be fetched: fetch failed.
  2. https://threema.ch/privacy – Could not be fetched: fetch failed.
  3. https://threema.ch/privacy-policy – Could not be fetched: fetch failed.
  4. https://threema.ch/legal/privacy-policy – Could not be fetched: fetch failed.
  5. https://threema.ch/legal/privacy-notice – Could not be fetched: fetch failed.
  6. https://threema.ch/trust/privacy – Could not be fetched: fetch failed.
  7. https://threema.ch/datenschutz – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

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.