Opal
opal.dev · Privileged access management · checked 2026-09-03
Rank 10 of 21 in Privileged access management, where the median is 22.
- 3 found
- 9 not found
- 0 not measured
We measured 12 of 12 criteria for Opal 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
Opal
- A
- B
- C
- D
- E
- F
Published commitments2 of 9 found
- not foundData processing agreement×3
- not foundSubprocessor list×3
- foundData location stated×3
- not foundStatus page with history×2
- not foundPublic pricing×2
- not foundNotice before subprocessors change×2
- foundCertifications named×1
- not foundUptime SLA with a figure×1
- not foundNamed privacy contact×1
Measured behaviour1 of 3 found
- foundHTTPS enforced with HSTS×2
- not foundNo third-party tracking before consent×2
- not foundsecurity.txt (RFC 9116)×1
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 Opal has no such document.
Gaps, heaviest first
Data processing agreement
weight 3 of 3No data processing agreement found.
Checked 8 addresses on 2026-09-03.
Show the 8 addresses we checked
https://opal.dev/legal/dpa– reached, no match (HTTP 404)https://opal.dev/dpa– reached, no match (HTTP 404)https://opal.dev/legal/data-processing-agreement– reached, no match (HTTP 404)https://opal.dev/data-processing-agreement– reached, no match (HTTP 404)https://opal.dev/legal/data-processing-addendum– reached, no match (HTTP 404)https://opal.dev/legal/gdpr– reached, no match (HTTP 404)https://opal.dev/trust/dpa– reached, no match (HTTP 404)https://opal.dev/privacy/dpa– reached, no match (HTTP 404)
Subprocessor list
weight 3 of 3No subprocessor list found.
Checked 7 addresses on 2026-09-03.
Show the 7 addresses we checked
https://opal.dev/legal/subprocessors– reached, no match (HTTP 404)https://opal.dev/subprocessors– reached, no match (HTTP 404)https://opal.dev/sub-processors– reached, no match (HTTP 404)https://opal.dev/legal/sub-processors– reached, no match (HTTP 404)https://opal.dev/trust/subprocessors– reached, no match (HTTP 404)https://opal.dev/privacy/subprocessors– reached, no match (HTTP 404)https://opal.dev/legal/subprocessor-list– reached, no match (HTTP 404)
Status page with history
weight 2 of 3No public status page found.
Checked 3 addresses on 2026-09-03.
Show the 3 addresses we checked
https://status.opal.dev/– reached, no match (HTTP 200)https://opal.dev/status– reached, no match (HTTP 404)https://opal.dev.statuspage.io/– Could not be fetched: fetch failed.
Public pricing
weight 2 of 3No public pricing with figures found.
Checked 5 addresses on 2026-09-03.
Show the 5 addresses we checked
https://opal.dev/pricing– reached and rendered, no matchhttps://opal.dev/pricing/– reached, no match (HTTP 200)https://opal.dev/plans– reached, no match (HTTP 404)https://opal.dev/en/pricing– reached, no match (HTTP 404)https://opal.dev/pricing-plans– reached, no match (HTTP 404)
No third-party tracking before consent
weight 2 of 3No consent-free first load found.
Checked 1 address on 2026-09-03.
Show the 1 address we checked
https://opal.dev/– third-party requests before any interaction: ad.doubleclick.net, cdn.drda.io, cdn.jsdelivr.net, events.framer.com, fonts.googleapis.com, fonts.gstatic.com, framerusercontent.com, js.hs-analytics.net, js.hs-banner.com, js.hs-scripts.com, js.hsadspixel.net, js.hscollectedforms.net, js.hubspot.com, js.storylane.io, paladin-homepage-final.vercel.app, screens-for-web-vercel.vercel.app, snap.licdn.com, static.hotjar.com, www.google.com, www.googletagmanager.com, www.redditstatic.com
Notice before subprocessors change
weight 2 of 3No commitment to give notice before subprocessors change found.
Checked 8 addresses on 2026-09-03.
Show the 8 addresses we checked
https://opal.dev/legal/subprocessors– reached, no match (HTTP 404)https://opal.dev/subprocessors– reached, no match (HTTP 404)https://opal.dev/sub-processors– reached, no match (HTTP 404)https://opal.dev/legal/dpa– reached, no match (HTTP 404)https://opal.dev/dpa– reached, no match (HTTP 404)https://opal.dev/legal/data-processing-agreement– reached, no match (HTTP 404)https://opal.dev/trust/subprocessors– reached, no match (HTTP 404)https://opal.dev/legal/sub-processors– reached, no match (HTTP 404)
Uptime SLA with a figure
weight 1 of 3No uptime figure found.
Checked 6 addresses on 2026-09-03.
Show the 6 addresses we checked
https://opal.dev/legal/sla– reached, no match (HTTP 404)https://opal.dev/sla– reached, no match (HTTP 404)https://opal.dev/legal/service-level-agreement– reached, no match (HTTP 404)https://opal.dev/trust/sla– reached, no match (HTTP 404)https://opal.dev/uptime– reached, no match (HTTP 404)https://opal.dev/legal/uptime-sla– reached, no match (HTTP 404)
security.txt (RFC 9116)
weight 1 of 3No security.txt found.
Checked 1 address on 2026-09-03.
Show the 1 address we checked
https://opal.dev/.well-known/security.txt– reached, no match (HTTP 404)
Named privacy contact
weight 1 of 3No named privacy contact found.
Checked 7 addresses on 2026-09-03.
Show the 7 addresses we checked
https://opal.dev/legal/privacy– reached, no match (HTTP 404)https://opal.dev/privacy– reached, no match (HTTP 404)https://opal.dev/privacy-policy– reached, no match (HTTP 404)https://opal.dev/legal/privacy-policy– reached, no match (HTTP 200)https://opal.dev/legal/privacy-notice– reached, no match (HTTP 404)https://opal.dev/trust/privacy– reached, no match (HTTP 404)https://opal.dev/datenschutz– reached, no match (HTTP 404)
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 3The hosting location is stated on a public page.
Source: https://www.opal.dev/legal/trust-center · checked 2026-09-03
HTTPS enforced with HSTS
weight 2 of 3HTTP redirects to HTTPS and the HSTS header is set.
Source: https://opal.dev/ · checked 2026-09-03
Certifications named
weight 1 of 3SOC 2 or ISO 27001 named on a public page.
Source: https://www.opal.dev/legal/trust-center · checked 2026-09-03
History
Not enough completed runs yet to draw a line. The next runs fill this in.