SaaS Ranking
Menu

Joe Security: what they publish

joesecurity.org · Threat intelligence · checked 2026-10-15

13/100FBand F

Rank 21 of 35 in Threat intelligence, where the median is 17.

Public transparency score, not a product or security rating. Latest check: 2026-10-15. How the score works.

Evidence at a glance

Choose a check to see its source, date and scope.

Not found means not found at the addresses we checked. Not measured means we could not complete the check.

Start a vendor reviewDownload evidence (CSV)

Overview

3 days since the newest dated result, 3 since the oldest. 12 of 12 criteria have a measured result in the last 30 days. Failed checks and undated results are excluded.

Evidence freshness is a statement about our measurement and is kept apart from the transparency score, which is frozen at v1. How good our own measurement is.

Transparency labelsaas-ranking.com

Joe Security

joesecurity.org · Threat intelligence

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
F 13of 100 Rank 21 of 35

Published commitments1 of 9 found

Measured behaviour1 of 3 found

Checked 2026-10-15. 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.

Downloads include all checks, source URLs, dates and the snapshot ID for your procurement file. We do not issue badges.

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 Joe Security has no such document.

Where Joe Security sits in Threat intelligence

  1. A0 0%
  2. B1 3%
  3. C0 0%
  4. D3 9%
  5. E9 26%
  6. F22 63%
35 vendors with a score; 3 more without a score because we could measure too little. Bands have fixed thresholds, see how the score works.

The band of Joe Security is marked. Vendors without a score are the ones where we could measure too few criteria to rank them – a gap on our side, counted separately.

What Joe Security states

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 (DPA)

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-10-15.

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

Is this wrong? Send us the URL

Across the market: Data processing agreement in Threat intelligence: 5 of 36 companies

✗

Subprocessors: the published list

weight 3 of 3

No subprocessor list found.

Checked 7 addresses on 2026-10-15.

Show the 7 addresses we checked
  1. https://joesecurity.org/legal/subprocessors – reached, no match (HTTP 404)
  2. https://joesecurity.org/subprocessors – reached, no match (HTTP 404)
  3. https://joesecurity.org/sub-processors – reached, no match (HTTP 404)
  4. https://joesecurity.org/legal/sub-processors – reached, no match (HTTP 404)
  5. https://joesecurity.org/trust/subprocessors – reached, no match (HTTP 404)
  6. https://joesecurity.org/privacy/subprocessors – reached, no match (HTTP 404)
  7. https://joesecurity.org/legal/subprocessor-list – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Across the market: Subprocessor list in Threat intelligence: 3 of 36 companies

✗

Data location: where they say data is hosted

weight 3 of 3

No statement about data location found.

Checked 7 addresses on 2026-10-15.

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

Is this wrong? Send us the URL

Across the market: Data location stated in Threat intelligence: 11 of 36 companies

✗

Status page with incident history

weight 2 of 3

No public status page found.

Checked 3 addresses on 2026-10-15.

Show the 3 addresses we checked
  1. https://status.joesecurity.org/ – The name "status.joesecurity.org" could not be resolved.
  2. https://joesecurity.org/status – reached, no match (HTTP 404)
  3. https://joesecurity.org.statuspage.io/ – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Across the market: Status page with history in Threat intelligence: 5 of 36 companies

✗

Public pricing with figures

weight 2 of 3

No public pricing with figures found.

Checked 5 addresses on 2026-10-15.

Show the 5 addresses we checked
  1. https://joesecurity.org/pricing – reached, no match (HTTP 404)
  2. https://joesecurity.org/pricing/ – reached, no match (HTTP 404)
  3. https://joesecurity.org/plans – reached, no match (HTTP 404)
  4. https://joesecurity.org/en/pricing – reached, no match (HTTP 404)
  5. https://joesecurity.org/pricing-plans – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Across the market: Public pricing in Threat intelligence: 6 of 35 companies

✗weight 2 of 3

Third-party requests seen on the first load, before any interaction.

  • Third-party hosts we saw on the first load 2 cookiebot.com, googletagmanager.com.
    Show the 2 exact wordings

    consent.cookiebot.com, consentcdn.cookiebot.com

    Read at https://joesecurity.org/

    www.googletagmanager.com

    Read at https://joesecurity.org/

Checked 1 address on 2026-10-15.

Show the 1 address we checked
  1. https://joesecurity.org/ – third-party requests before any interaction: consent.cookiebot.com, consentcdn.cookiebot.com, www.googletagmanager.com

Is this wrong? Send us the URL

Across the market: No third-party tracking before consent in Threat intelligence: 4 of 38 companies

✗

Notice before subprocessors change

weight 2 of 3

No commitment to give notice before subprocessors change found.

Checked 8 addresses on 2026-10-15.

Show the 8 addresses we checked
  1. https://joesecurity.org/legal/subprocessors – reached, no match (HTTP 404)
  2. https://joesecurity.org/subprocessors – reached, no match (HTTP 404)
  3. https://joesecurity.org/sub-processors – reached, no match (HTTP 404)
  4. https://joesecurity.org/legal/dpa – reached, no match (HTTP 404)
  5. https://joesecurity.org/dpa – reached, no match (HTTP 404)
  6. https://joesecurity.org/legal/data-processing-agreement – reached, no match (HTTP 404)
  7. https://joesecurity.org/trust/subprocessors – reached, no match (HTTP 404)
  8. https://joesecurity.org/legal/sub-processors – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Across the market: Notice before subprocessors change in Threat intelligence: 4 of 35 companies

✗

Uptime SLA with a figure

weight 1 of 3

No uptime figure found.

Checked 6 addresses on 2026-10-15.

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

Is this wrong? Send us the URL

Across the market: Uptime SLA with a figure in Threat intelligence: 3 of 35 companies

✗

security.txt (RFC 9116)

weight 1 of 3

No security.txt found.

Checked 1 address on 2026-10-15.

Show the 1 address we checked
  1. https://joesecurity.org/.well-known/security.txt – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Across the market: security.txt (RFC 9116) in Threat intelligence: 5 of 36 companies

✗

Named privacy contact (DPO or privacy address)

weight 1 of 3

No named privacy contact found.

Checked 7 addresses on 2026-10-15.

Show the 7 addresses we checked
  1. https://joesecurity.org/legal/privacy – reached, no match (HTTP 404)
  2. https://joesecurity.org/privacy – reached, no match (HTTP 404)
  3. https://joesecurity.org/privacy-policy – reached, no match (HTTP 404)
  4. https://joesecurity.org/legal/privacy-policy – reached, no match (HTTP 404)
  5. https://joesecurity.org/legal/privacy-notice – reached, no match (HTTP 404)
  6. https://joesecurity.org/trust/privacy – reached, no match (HTTP 404)
  7. https://joesecurity.org/datenschutz – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Across the market: Named privacy contact in Threat intelligence: 12 of 36 companies

Evidence

The full source lists sit behind these two groups, so that the answer above stays readable.

Published, with a source 2
✓

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

Source: https://joesecurity.org/ · checked 2026-10-15

Across the market: HTTPS enforced with HSTS in Threat intelligence: 25 of 37 companies

✓

Certifications named (SOC 2, ISO 27001)

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

  • Named on that page ISO/IEC 27001 (named without a certification claim).
    Show the exact wording

    ISO 27001 Joe Security is fully ISO 27001 certified Europe All Data Centers are ISO 27001 certified and locat

    Read at https://joesecurity.org/security

Source: https://joesecurity.org/security · checked 2026-10-15

Across the market: Certifications named in Threat intelligence: 7 of 37 companies

History

100 0 2026-10-08: 13 of 1002026-10-15: 13 of 100 2026-10-08 2026-10-15
Score over the last 2 runs we measured Joe Security in: 13 (2026-10-08), 13 (2026-10-15).

Prepare your vendor review

A source is a starting point. Check the product, plan, legal entity and date before treating it as evidence for your purchase. These questions do not change the transparency score.

Joe Security

2 found · 10 not found · 0 not measured across 12 public checks.

12 of 12 criteria have a measured result from the last 30 days. Oldest dated result: 2026-10-15.

Investigate 10 open evidence questions
  1. Data processing agreement

    Please share the current data processing agreement for the product and plan we are considering, including its annexes and signing process.

    Inspect this check
  2. Subprocessor list

    Which subprocessors apply to our product, what does each process, and in which countries? Please share the current list.

    Inspect this check
  3. Data location stated

    Which locations apply to our primary data, backups and support access? Which region can we select for this plan?

    Inspect this check
  4. Status page with history

    Where can we review incident history for the service we will use, and how do we subscribe to incident updates?

    Inspect this check
  5. Public pricing

    Please confirm the total cost for our seats and usage, including minimum commitments, add-ons, overages and renewal terms.

    Inspect this check
  6. Uptime SLA with a figure

    Which availability commitment applies to our plan? Please include the measurement window, exclusions and credit claim process.

    Inspect this check
  7. No third-party tracking before consent

    Which third-party requests occur before a visitor makes a choice, and for what purpose? Please distinguish the public website from the product.

    Inspect this check
  8. security.txt (RFC 9116)

    Where should we report a vulnerability, and what acknowledgement and follow-up process should we expect?

    Inspect this check
  9. Notice before subprocessors change

    How will you notify us before a subprocessor changes, with how much notice, and what response options apply to our contract?

    Inspect this check
  10. Named privacy contact

    Which privacy contact handles requests for our account, and what escalation path should we use?

    Inspect this check

Compare

A shortlist holds up to six vendors across categories and lives entirely in the address of its page: share the link, bookmark it, put it in a ticket. Nothing is stored, so we do not know it exists.