RiskRecon
riskrecon.com · Compliance automation · checked 2026-09-03
Rank 18 of 21 in Compliance automation, where the median is 26.
- 1 found
- 10 not found
- 1 not measured
We measured 11 of 12 criteria for RiskRecon on 2026-09-03. 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
Transparency labelsaas-ranking.com
RiskRecon
- A
- B
- C
- D
- E
- F
Published commitments0 of 9 found
- not foundData processing agreement×3
- not foundSubprocessor list×3
- not foundData location stated×3
- not foundStatus page with history×2
- not foundPublic pricing×2
- not foundNotice before subprocessors change×2
- not foundCertifications named×1
- not foundUptime SLA with a figure×1
- not foundNamed privacy contact×1
Measured behaviour1 of 2 found, 1 not measured
- foundHTTPS enforced with HSTS×2
- not measuredNo 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 RiskRecon 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://riskrecon.com/legal/dpa– reached, no match (HTTP 404)https://riskrecon.com/dpa– reached, no match (HTTP 404)https://riskrecon.com/legal/data-processing-agreement– reached, no match (HTTP 404)https://riskrecon.com/data-processing-agreement– reached, no match (HTTP 404)https://riskrecon.com/legal/data-processing-addendum– reached, no match (HTTP 404)https://riskrecon.com/legal/gdpr– reached, no match (HTTP 404)https://riskrecon.com/trust/dpa– reached, no match (HTTP 404)https://riskrecon.com/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://riskrecon.com/legal/subprocessors– reached, no match (HTTP 404)https://riskrecon.com/subprocessors– reached, no match (HTTP 404)https://riskrecon.com/sub-processors– reached, no match (HTTP 404)https://riskrecon.com/legal/sub-processors– reached, no match (HTTP 404)https://riskrecon.com/trust/subprocessors– reached, no match (HTTP 404)https://riskrecon.com/privacy/subprocessors– reached, no match (HTTP 404)https://riskrecon.com/legal/subprocessor-list– reached, no match (HTTP 404)
Data location stated
weight 3 of 3No statement about data location found.
Checked 7 addresses on 2026-09-03.
Show the 7 addresses we checked
https://riskrecon.com/security– reached, no match (HTTP 404)https://riskrecon.com/trust– reached, no match (HTTP 404)https://riskrecon.com/legal/privacy– reached, no match (HTTP 404)https://riskrecon.com/privacy– reached, no match (HTTP 404)https://riskrecon.com/privacy-policy– blocked or unavailable (HTTP 403)https://riskrecon.com/compliance– reached, no match (HTTP 404)https://riskrecon.com/legal/privacy-policy– 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.riskrecon.com/– The name "status.riskrecon.com" could not be resolved.https://riskrecon.com/status– reached, no match (HTTP 404)https://riskrecon.com.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://riskrecon.com/pricing– reached, no match (HTTP 404)https://riskrecon.com/pricing/– reached, no match (HTTP 404)https://riskrecon.com/plans– reached, no match (HTTP 404)https://riskrecon.com/en/pricing– reached, no match (HTTP 404)https://riskrecon.com/pricing-plans– reached, no match (HTTP 404)
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://riskrecon.com/legal/subprocessors– reached, no match (HTTP 404)https://riskrecon.com/subprocessors– reached, no match (HTTP 404)https://riskrecon.com/sub-processors– reached, no match (HTTP 404)https://riskrecon.com/legal/dpa– reached, no match (HTTP 404)https://riskrecon.com/dpa– reached, no match (HTTP 404)https://riskrecon.com/legal/data-processing-agreement– reached, no match (HTTP 404)https://riskrecon.com/trust/subprocessors– reached, no match (HTTP 404)https://riskrecon.com/legal/sub-processors– reached, no match (HTTP 404)
Certifications named
weight 1 of 3No named certification found.
Checked 6 addresses on 2026-09-03.
Show the 6 addresses we checked
https://riskrecon.com/security– reached, no match (HTTP 404)https://riskrecon.com/trust– reached, no match (HTTP 404)https://riskrecon.com/trust-center– reached, no match (HTTP 404)https://riskrecon.com/compliance– reached, no match (HTTP 404)https://riskrecon.com/legal/security– reached, no match (HTTP 404)https://trust.riskrecon.com/– The name "trust.riskrecon.com" could not be resolved.
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://riskrecon.com/legal/sla– reached, no match (HTTP 404)https://riskrecon.com/sla– reached, no match (HTTP 404)https://riskrecon.com/legal/service-level-agreement– reached, no match (HTTP 404)https://riskrecon.com/trust/sla– reached, no match (HTTP 404)https://riskrecon.com/uptime– reached, no match (HTTP 404)https://riskrecon.com/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://riskrecon.com/.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://riskrecon.com/legal/privacy– reached, no match (HTTP 404)https://riskrecon.com/privacy– reached, no match (HTTP 404)https://riskrecon.com/privacy-policy– blocked or unavailable (HTTP 403)https://riskrecon.com/legal/privacy-policy– reached, no match (HTTP 404)https://riskrecon.com/legal/privacy-notice– reached, no match (HTTP 404)https://riskrecon.com/trust/privacy– reached, no match (HTTP 404)https://riskrecon.com/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 1
HTTPS enforced with HSTS
weight 2 of 3HTTP redirects to HTTPS and the HSTS header is set.
Source: https://riskrecon.com/ · checked 2026-09-03
Not measured by us 1
No third-party tracking before consent
weight 2 of 3Not measured. The page could not be loaded in a browser, so this was not measured.
Show the 1 address we checked
https://riskrecon.com/– page.goto: net::ERR_CONNECTION_RESET at https://riskrecon.com/ Call log: - navigating to "https://riskrecon.com/", waiting until "domcontentloaded"
History
Not enough completed runs yet to draw a line. The next runs fill this in.