SaaS Ranking
Menu

Descope

descope.com · Password and identity · checked 2026-09-03

39/100EBand E

Rank 12 of 21 in Password and identity, where the median is 40.

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

Overview

Transparency labelsaas-ranking.com

Descope

descope.com · Password and identity

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

Published commitments4 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.

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 Descope 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://descope.com/legal/dpa – reached, no match (HTTP 404)
  2. https://descope.com/dpa – reached, no match (HTTP 404)
  3. https://descope.com/legal/data-processing-agreement – reached, no match (HTTP 404)
  4. https://descope.com/data-processing-agreement – reached, no match (HTTP 404)
  5. https://descope.com/legal/data-processing-addendum – reached, no match (HTTP 404)
  6. https://descope.com/legal/gdpr – reached, no match (HTTP 404)
  7. https://descope.com/trust/dpa – reached, no match (HTTP 404)
  8. https://descope.com/privacy/dpa – 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.descope.com/privacy · checked 2026-09-03

Show the 7 addresses we checked
  1. https://descope.com/security – reached, no match (HTTP 404)
  2. https://descope.com/trust – reached, no match (HTTP 404)
  3. https://descope.com/legal/privacy – found, but behind a sign-in
  4. https://descope.com/privacy – found, but behind a sign-in
  5. https://descope.com/privacy-policy – found, but behind a sign-in
  6. https://descope.com/compliance – reached, no match (HTTP 404)
  7. https://descope.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-03.

Show the 3 addresses we checked
  1. https://status.descope.com/ – reached, no match (HTTP 200)
  2. https://descope.com/status – reached, no match (HTTP 404)
  3. https://descope.com.statuspage.io/ – Could not be fetched: fetch failed.

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://descope.com/ – third-party requests before any interaction: assets.revenuehero.io, cmp.osano.com, images.ctfassets.net, www.google.com, 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-03.

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

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://descope.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 5
✓

Subprocessor list

weight 3 of 3

The actual list is published, not just a promise to keep one.

Source: https://www.descope.com/sub-processors · checked 2026-09-03

✓

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://www.descope.com/pricing · checked 2026-09-03

✓

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

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

✓

Uptime SLA with a figure

weight 1 of 3

An availability commitment with a figure.

Source: https://www.descope.com/sla · 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.descope.com/privacy · checked 2026-09-03

History

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

Compare