SaaS Ranking

Origami Risk

origamirisk.com · Business continuity · checked 2026-09-04

17/100FBand F

Rank 5 of 15 in Business continuity, where the median is 13.

We measured 12 of 12 criteria for Origami Risk on 2026-09-04. We found 3 with a source and did not find 9 at the addresses we checked. That is a transparency score of 17 out of 100, band F.

Overview

Transparency labelsaas-ranking.com

Origami Risk

origamirisk.com · Business continuity

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

Published commitments2 of 9 found

Measured behaviour1 of 3 found

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 Origami Risk 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://origamirisk.com/legal/dpa – reached, no match (HTTP 404)
  2. https://origamirisk.com/dpa – reached, no match (HTTP 404)
  3. https://origamirisk.com/legal/data-processing-agreement – reached, no match (HTTP 200)
  4. https://origamirisk.com/data-processing-agreement – reached, no match (HTTP 200)
  5. https://origamirisk.com/legal/data-processing-addendum – reached, no match (HTTP 404)
  6. https://origamirisk.com/legal/gdpr – reached, no match (HTTP 404)
  7. https://origamirisk.com/trust/dpa – reached, no match (HTTP 404)
  8. https://origamirisk.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://origamirisk.com/legal/subprocessors – reached, no match (HTTP 404)
  2. https://origamirisk.com/subprocessors – reached, no match (HTTP 404)
  3. https://origamirisk.com/sub-processors – reached, no match (HTTP 404)
  4. https://origamirisk.com/legal/sub-processors – reached, no match (HTTP 404)
  5. https://origamirisk.com/trust/subprocessors – reached, no match (HTTP 404)
  6. https://origamirisk.com/privacy/subprocessors – reached, no match (HTTP 404)
  7. https://origamirisk.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.origamirisk.com/privacy-policy/ · checked 2026-09-04

Show the 7 addresses we checked
  1. https://origamirisk.com/security – reached, no match (HTTP 404)
  2. https://origamirisk.com/trust – reached, no match (HTTP 200)
  3. https://origamirisk.com/legal/privacy – found, but behind a sign-in
  4. https://origamirisk.com/privacy – found, but behind a sign-in
  5. https://origamirisk.com/privacy-policy – found, but behind a sign-in
  6. https://origamirisk.com/compliance – reached, no match (HTTP 200)
  7. https://origamirisk.com/legal/privacy-policy – found, but behind a sign-in

Is this wrong? Send us the URL

Status page with history

weight 2 of 3

We found this behind a sign-in, so it is not published openly.

Seen at https://status.origamirisk.com/access/login · checked 2026-09-04

Show the 3 addresses we checked
  1. https://status.origamirisk.com/ – found, but behind a sign-in
  2. https://origamirisk.com/status – reached, no match (HTTP 404)
  3. https://origamirisk.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://origamirisk.com/pricing – reached, no match (HTTP 404)
  2. https://origamirisk.com/pricing/ – reached, no match (HTTP 404)
  3. https://origamirisk.com/plans – reached, no match (HTTP 404)
  4. https://origamirisk.com/en/pricing – reached, no match (HTTP 404)
  5. https://origamirisk.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-04.

Show the 1 address we checked
  1. https://origamirisk.com/ – third-party requests before any interaction: 862-kwb-364.mktoresp.com, ad.doubleclick.net, api.claydar.com, api.company-target.com, assets.adoberesources.net, bat.bing.com, bat.bing.net, browser.sentry-cdn.com, cdn.bizible.com, cdn.claydar.com, cdn.us.heap-api.com, dsum-sec.casalemedia.com, embed-ssl.wistia.com, fast.wistia.com, fast.wistia.net, fonts.googleapis.com, fonts.gstatic.com, id.rlcdn.com, image2.pubmatic.com, munchkin.marketo.net, partners.tremorhub.com, pixel.rubiconproject.com, project-hummingbird-hummingbird-websocket-nodejs-de-112831.cloud.adobe.io, px.ads.linkedin.com, region1.analytics.google.com, s.company-target.com, snap.licdn.com, static.claydar.com, stats.g.doubleclick.net, t.contentsquare.net, tag-logger.demandbase.com, tag.demandbase.com, www.clarity.ms, www.google-analytics.com, www.google.com, www.google.de, www.googletagmanager.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-04.

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

Show the 6 addresses we checked
  1. https://origamirisk.com/security – reached, no match (HTTP 404)
  2. https://origamirisk.com/trust – reached, no match (HTTP 200)
  3. https://origamirisk.com/trust-center – reached, no match (HTTP 404)
  4. https://origamirisk.com/compliance – reached, no match (HTTP 200)
  5. https://origamirisk.com/legal/security – reached, no match (HTTP 404)
  6. https://trust.origamirisk.com/ – reached, no match (HTTP 200)

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://origamirisk.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.

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

Uptime SLA with a figure

weight 1 of 3

An availability commitment with a figure.

  • Highest uptime figure on that page 99.99 %.
    Show the exact wording

    s are stored off site via Amazon S3, which has multiple redundancy and 99.999999999% durability and 99.99% availability of objects over a given year.

    Read at https://www.origamirisk.com/serviceterms/sla/

Source: https://www.origamirisk.com/serviceterms/sla/ · 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.origamirisk.com/privacy-policy/ · checked 2026-09-04

History

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

Compare