SaaS Ranking
Menu

Judge.me

judge.me · Loyalty and rewards · checked 2026-09-04

26/100EBand E

Rank 15 of 30 in Loyalty and rewards, where the median is 26.

We measured 12 of 12 criteria for Judge.me on 2026-09-04. 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

Judge.me

judge.me · Loyalty and rewards

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
E 26of 100 Rank 15 of 30

Published commitments1 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 Judge.me 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

✗

Data processing agreement

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-09-04.

Show the 8 addresses we checked
  1. https://judge.me/legal/dpa – reached, no match (HTTP 404)
  2. https://judge.me/dpa – blocked or unavailable (HTTP 403)
  3. https://judge.me/legal/data-processing-agreement – reached, no match (HTTP 404)
  4. https://judge.me/data-processing-agreement – reached, no match (HTTP 404)
  5. https://judge.me/legal/data-processing-addendum – reached, no match (HTTP 404)
  6. https://judge.me/legal/gdpr – reached, no match (HTTP 404)
  7. https://judge.me/trust/dpa – reached, no match (HTTP 404)
  8. https://judge.me/privacy/dpa – blocked or unavailable (HTTP 403)

Is this wrong? Send us the URL

✗

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://judge.me/legal/subprocessors – reached, no match (HTTP 404)
  2. https://judge.me/subprocessors – reached, no match (HTTP 404)
  3. https://judge.me/sub-processors – reached, no match (HTTP 404)
  4. https://judge.me/legal/sub-processors – reached, no match (HTTP 404)
  5. https://judge.me/trust/subprocessors – reached, no match (HTTP 404)
  6. https://judge.me/privacy/subprocessors – blocked or unavailable (HTTP 403)
  7. https://judge.me/legal/subprocessor-list – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

Data location stated

weight 3 of 3

No statement about data location found.

Checked 7 addresses on 2026-09-04.

Show the 7 addresses we checked
  1. https://judge.me/security – reached, no match (HTTP 404)
  2. https://judge.me/trust – reached, no match (HTTP 200)
  3. https://judge.me/legal/privacy – reached, no match (HTTP 404)
  4. https://judge.me/privacy – blocked or unavailable (HTTP 403)
  5. https://judge.me/privacy-policy – blocked or unavailable (HTTP 403)
  6. https://judge.me/compliance – blocked or unavailable (HTTP 403)
  7. https://judge.me/legal/privacy-policy – reached, no match (HTTP 404)

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://judge.me/pricing – blocked or unavailable (HTTP 403)
  2. https://judge.me/pricing/ – blocked or unavailable (HTTP 403)
  3. https://judge.me/plans – reached, no match (HTTP 404)
  4. https://judge.me/en/pricing – reached, no match (HTTP 404)
  5. https://judge.me/pricing-plans – blocked or unavailable (HTTP 403)

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-04.

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

Show the 6 addresses we checked
  1. https://judge.me/security – reached, no match (HTTP 404)
  2. https://judge.me/trust – reached, no match (HTTP 200)
  3. https://judge.me/trust-center – reached, no match (HTTP 404)
  4. https://judge.me/compliance – blocked or unavailable (HTTP 403)
  5. https://judge.me/legal/security – reached, no match (HTTP 404)
  6. https://trust.judge.me/ – The name "trust.judge.me" could not be resolved.

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://judge.me/legal/sla – reached, no match (HTTP 404)
  2. https://judge.me/sla – reached, no match (HTTP 404)
  3. https://judge.me/legal/service-level-agreement – reached, no match (HTTP 404)
  4. https://judge.me/trust/sla – reached, no match (HTTP 404)
  5. https://judge.me/uptime – reached, no match (HTTP 404)
  6. https://judge.me/legal/uptime-sla – reached, no match (HTTP 404)

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-04.

Show the 1 address we checked
  1. https://judge.me/.well-known/security.txt – 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://judge.me/legal/privacy – reached, no match (HTTP 404)
  2. https://judge.me/privacy – blocked or unavailable (HTTP 403)
  3. https://judge.me/privacy-policy – blocked or unavailable (HTTP 403)
  4. https://judge.me/legal/privacy-policy – reached, no match (HTTP 404)
  5. https://judge.me/legal/privacy-notice – reached, no match (HTTP 404)
  6. https://judge.me/trust/privacy – reached, no match (HTTP 404)
  7. https://judge.me/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 3
✓

Status page with history

weight 2 of 3

A public status page with incident history.

Source: https://status.judge.me/ · 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; includeSubDomains

    Read at https://judge.me/
  • HSTS options includeSubDomains.
    Show the exact wording

    max-age=31536000; includeSubDomains

    Read at https://judge.me/

Source: https://judge.me/ · checked 2026-09-04

✓

No third-party tracking before consent

weight 2 of 3

No third-party requests before any interaction.

Source: https://judge.me/ · checked 2026-09-04

History

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

Compare