SaaS Ranking
Menu

IPRally

iprally.com · Patent and trademark management · checked 2026-09-04

48/100DBand D

Rank 2 of 23 in Patent and trademark management, where the median is 13.

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

Overview

Transparency labelsaas-ranking.com

IPRally

iprally.com · Patent and trademark management

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

Published commitments3 of 9 found

Measured behaviour2 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 IPRally 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

✗

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://iprally.com/legal/subprocessors – reached, no match (HTTP 404)
  2. https://iprally.com/subprocessors – reached, no match (HTTP 404)
  3. https://iprally.com/sub-processors – reached, no match (HTTP 404)
  4. https://iprally.com/legal/sub-processors – reached, no match (HTTP 404)
  5. https://iprally.com/trust/subprocessors – reached, no match (HTTP 404)
  6. https://iprally.com/privacy/subprocessors – reached, no match (HTTP 404)
  7. https://iprally.com/legal/subprocessor-list – 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-04.

Show the 3 addresses we checked
  1. https://status.iprally.com/ – reached, no match (HTTP 200)
  2. https://iprally.com/status – reached, no match (HTTP 404)
  3. https://iprally.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://iprally.com/pricing – reached, no match (HTTP 404)
  2. https://iprally.com/pricing/ – reached, no match (HTTP 404)
  3. https://iprally.com/plans – reached, no match (HTTP 404)
  4. https://iprally.com/en/pricing – reached, no match (HTTP 404)
  5. https://iprally.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://iprally.com/ – third-party requests before any interaction: ad.doubleclick.net, ajax.googleapis.com, api-eu1.hubapi.com, buttons-config.sharethis.com, cdn.cookielaw.org, cdn.jsdelivr.net, cdn.prod.website-files.com, challenges.cloudflare.com, cta-eu1.hubspot.com, d3e54v103j8qbb.cloudfront.net, fonts.googleapis.com, fonts.gstatic.com, forms-eu1.hscollectedforms.net, forms-eu1.hsforms.com, hubspotonwebflow.com, hubspotv2.use1-marketplace-1p-apps-prod-red.if.webflow.services, js-eu1.hs-analytics.net, js-eu1.hs-banner.com, js-eu1.hs-scripts.com, js-eu1.hsadspixel.net, js-eu1.hscollectedforms.net, js-eu1.hubspot.com, js.hs-scripts.com, l.sharethis.com, perf-eu1.hsforms.com, platform-api.sharethis.com, www.google-analytics.com, www.google.com, www.googletagmanager.com

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://iprally.com/security – reached, no match (HTTP 404)
  2. https://iprally.com/trust – reached, no match (HTTP 404)
  3. https://iprally.com/trust-center – reached, no match (HTTP 404)
  4. https://iprally.com/compliance – reached, no match (HTTP 404)
  5. https://iprally.com/legal/security – reached, no match (HTTP 404)
  6. https://trust.iprally.com/ – reached, no match (HTTP 200)

Is this wrong? Send us the URL

✗

Uptime SLA with a figure

weight 1 of 3

No uptime figure found.

Checked 6 addresses on 2026-09-04.

Show the 6 addresses we checked
  1. https://iprally.com/legal/sla – reached, no match (HTTP 404)
  2. https://iprally.com/sla – reached, no match (HTTP 404)
  3. https://iprally.com/legal/service-level-agreement – reached, no match (HTTP 404)
  4. https://iprally.com/trust/sla – reached, no match (HTTP 404)
  5. https://iprally.com/uptime – reached, no match (HTTP 404)
  6. https://iprally.com/legal/uptime-sla – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

Named privacy contact

weight 1 of 3

No named privacy contact found.

Checked 7 addresses on 2026-09-04.

Show the 7 addresses we checked
  1. https://iprally.com/legal/privacy – reached, no match (HTTP 404)
  2. https://iprally.com/privacy – reached, no match (HTTP 404)
  3. https://iprally.com/privacy-policy – reached, no match (HTTP 200)
  4. https://iprally.com/legal/privacy-policy – reached, no match (HTTP 200)
  5. https://iprally.com/legal/privacy-notice – reached, no match (HTTP 404)
  6. https://iprally.com/trust/privacy – reached, no match (HTTP 404)
  7. https://iprally.com/datenschutz – 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
✓

Data processing agreement

weight 3 of 3

Published and readable without a login.

Source: https://iprally.com/support-and-legal/data-processing-agreement · checked 2026-09-04

✓

Data location stated

weight 3 of 3

The hosting location is stated on a public page.

Source: https://iprally.com/support-and-legal/privacy-policy · checked 2026-09-04

✓

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

  • HSTS max-age 31536000 seconds (365 days).
    Show the exact wording

    max-age=31536000

    Read at https://iprally.com/

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

✓

Notice before subprocessors change

weight 2 of 3

The vendor commits publicly to giving notice before the list changes.

Source: https://iprally.com/support-and-legal/data-processing-agreement · checked 2026-09-04

✓

security.txt (RFC 9116)

weight 1 of 3

Served at /.well-known/security.txt.

  • The file expires 2026-09-02. That date had passed when we checked on 2026-09-04, so the file was stale (RFC 9116).
    Show the exact wording

    Expires: 2026-09-02T12:00:00.000Z

    Read at https://iprally.com/.well-known/security.txt

Source: https://iprally.com/.well-known/security.txt · checked 2026-09-04

History

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

Compare