Highradius
highradius.com · Debt collection software · checked 2026-09-03
Rank 1 of 21 in Debt collection software, where the median is 13.
- 7 found
- 5 not found
- 0 not measured
We measured 12 of 12 criteria for Highradius on 2026-09-03. We found 7 with a source and did not find 5 at the addresses we checked. That is a transparency score of 57 out of 100, band C.
Overview
Transparency labelsaas-ranking.com
Highradius
- A
- B
- C
- D
- E
- F
Published commitments6 of 9 found
- not foundData processing agreement×3
- foundSubprocessor list×3
- foundData location stated×3
- not foundStatus page with history×2
- foundPublic pricing×2
- not foundNotice before subprocessors change×2
- foundCertifications named×1
- foundUptime SLA with a figure×1
- 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 Highradius 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://highradius.com/legal/dpa– reached, no match (HTTP 200)https://highradius.com/dpa– reached, no match (HTTP 200)https://highradius.com/legal/data-processing-agreement– reached, no match (HTTP 200)https://highradius.com/data-processing-agreement– reached, no match (HTTP 200)https://highradius.com/legal/data-processing-addendum– reached, no match (HTTP 200)https://highradius.com/legal/gdpr– reached, no match (HTTP 200)https://highradius.com/trust/dpa– reached, no match (HTTP 200)https://highradius.com/privacy/dpa– reached, no match (HTTP 200)
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.highradius.com/– The name "status.highradius.com" could not be resolved.https://highradius.com/status– reached, no match (HTTP 200)https://highradius.com.statuspage.io/– Could not be fetched: fetch failed.
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://highradius.com/– third-party requests before any interaction: api.factors.ai, api.hubapi.com, api.hubspot.com, app.factors.ai, app.qualified.com, bat.bing.com, cdn-cookieyes.com, cdn.amplitude.com, ddwl4m2hdecbv.cloudfront.net, directory.cookieyes.com, fonts.googleapis.com, fonts.gstatic.com, forms-na1.hsforms.com, forms.hsforms.com, g10696554090.co, g792337341.co, js.hs-banner.com, js.hs-scripts.com, js.hsadspixel.net, js.hsforms.net, js.qualified.com, js.usemessages.com, js.zi-scripts.com, log.cookieyes.com, ob.buzzfufighter.com, obs.buzzfufighter.com, px.ads.linkedin.com, r2.leadsy.ai, rum-static.pingdom.net, snap.licdn.com, tracking-api.g2.com, tracking.g2crowd.com, unpkg.com, www.clarity.ms, www.googletagmanager.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://highradius.com/legal/subprocessors– reached, no match (HTTP 200)https://highradius.com/subprocessors– reached, no match (HTTP 200)https://highradius.com/sub-processors– reached, no match (HTTP 200)https://highradius.com/legal/dpa– reached, no match (HTTP 200)https://highradius.com/dpa– reached, no match (HTTP 200)https://highradius.com/legal/data-processing-agreement– reached, no match (HTTP 200)https://highradius.com/trust/subprocessors– reached, no match (HTTP 200)https://highradius.com/legal/sub-processors– reached, no match (HTTP 200)
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://highradius.com/.well-known/security.txt– reached, no match (HTTP 200)
Evidence
The full source lists sit behind these two groups, so that the answer above stays readable.
Published, with a source 7
Subprocessor list
weight 3 of 3The actual list is published, not just a promise to keep one.
Source: https://www.highradius.com/subprocessors/ · checked 2026-09-03
Data location stated
weight 3 of 3The hosting location is stated on a public page.
Source: https://www.highradius.com/privacy-policy/ · checked 2026-09-03
Public pricing
weight 2 of 3Actual numbers on a public page.
Source: https://www.highradius.com/pricing/ · checked 2026-09-03
HTTPS enforced with HSTS
weight 2 of 3HTTP redirects to HTTPS and the HSTS header is set.
Source: https://highradius.com/ · checked 2026-09-03
Certifications named
weight 1 of 3SOC 2 or ISO 27001 named on a public page.
Source: https://trust.highradius.com/ · checked 2026-09-03
Uptime SLA with a figure
weight 1 of 3An availability commitment with a figure.
Source: https://www.highradius.com/ · checked 2026-09-03
Named privacy contact
weight 1 of 3A data protection officer or a dedicated privacy address is named.
Source: https://www.highradius.com/privacy-policy/ · checked 2026-09-03
History
Not enough completed runs yet to draw a line. The next runs fill this in.