SaaS Ranking
Menu

Security and compliance / Threat intelligence

Searchlight Cyber

What Searchlight Cyber publishes on slcyber.io, measured on 2026-09-02. Every line links the page we found it on, or lists the addresses we checked.

Transparency 13/100 FBand F

Rank 7 of 8 in Threat intelligencecategory median 26checked 2026-09-02

10 gaps found: 10 criteria not found at the addresses we checked. 2 found10 not found0 not measured

Public transparency score, not a product or security rating.

Transparency labelsaas-ranking.com

Searchlight Cyber

slcyber.io · Threat intelligence

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

Published commitments1 of 9 found

Measured behaviour1 of 3 found

Checked 2026-09-02. 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.

Show the full transparency label

Transparency labelsaas-ranking.com

Searchlight Cyber

slcyber.io · Threat intelligence

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

Published commitments1 of 9 found

Measured behaviour1 of 3 found

Checked 2026-09-02. 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.

Not found, heaviest first

✗

Data processing agreement

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-09-02.

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

Is this wrong? Send us the URL

✗

Subprocessor list

weight 3 of 3

No subprocessor list found.

Checked 7 addresses on 2026-09-02.

Show the 7 addresses we checked
  1. https://slcyber.io/legal/subprocessors – reached, no match (HTTP 404)
  2. https://slcyber.io/subprocessors – reached, no match (HTTP 404)
  3. https://slcyber.io/sub-processors – reached, no match (HTTP 404)
  4. https://slcyber.io/legal/sub-processors – reached, no match (HTTP 404)
  5. https://slcyber.io/trust/subprocessors – reached, no match (HTTP 404)
  6. https://slcyber.io/privacy/subprocessors – reached, no match (HTTP 404)
  7. https://slcyber.io/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-02.

Show the 7 addresses we checked
  1. https://slcyber.io/security – reached, no match (HTTP 404)
  2. https://slcyber.io/trust – reached, no match (HTTP 404)
  3. https://slcyber.io/legal/privacy – reached, no match (HTTP 404)
  4. https://slcyber.io/privacy – reached, no match (HTTP 404)
  5. https://slcyber.io/privacy-policy – reached, no match (HTTP 200)
  6. https://slcyber.io/compliance – reached, no match (HTTP 404)
  7. https://slcyber.io/legal/privacy-policy – 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-02.

Show the 3 addresses we checked
  1. https://status.slcyber.io/ – The name "status.slcyber.io" could not be resolved.
  2. https://slcyber.io/status – reached, no match (HTTP 404)
  3. https://slcyber.io.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-02.

Show the 5 addresses we checked
  1. https://slcyber.io/pricing – reached, no match (HTTP 404)
  2. https://slcyber.io/pricing/ – reached, no match (HTTP 404)
  3. https://slcyber.io/plans – reached, no match (HTTP 404)
  4. https://slcyber.io/en/pricing – reached, no match (HTTP 404)
  5. https://slcyber.io/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-02.

Show the 1 address we checked
  1. https://slcyber.io/ – third-party requests before any interaction: api-eu1.hubapi.com, bat.bing.com, bat.bing.net, cdn.jsdelivr.net, cdn.prod.website-files.com, cdnjs.cloudflare.com, cm.g.doubleclick.net, connect.facebook.net, consent.cookiebot.com, consentcdn.cookiebot.com, cta-eu1.hubspot.com, d.adroll.com, d3e54v103j8qbb.cloudfront.net, dsum-sec.casalemedia.com, eb2.3lift.com, forms-eu1.hscollectedforms.net, ib.adnxs.com, ibc-flow.techtarget.com, image2.pubmatic.com, 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, ml314.com, pagead2.googlesyndication.com, perf-eu1.hsforms.com, pixel.rubiconproject.com, pixel.tapad.com, ps.eyeota.net, px.ads.linkedin.com, region1.google-analytics.com, s.adroll.com, scripts.clarity.ms, scripts.miscreants.dev, seo-fixer.writesonic.com, snap.licdn.com, sync.outbrain.com, sync.taboola.com, trk.techtarget.com, us-u.openx.net, www.clarity.ms, www.googletagmanager.com, x.bidswitch.net

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

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

Show the 6 addresses we checked
  1. https://slcyber.io/security – reached, no match (HTTP 404)
  2. https://slcyber.io/trust – reached, no match (HTTP 404)
  3. https://slcyber.io/trust-center – reached, no match (HTTP 404)
  4. https://slcyber.io/compliance – reached, no match (HTTP 404)
  5. https://slcyber.io/legal/security – reached, no match (HTTP 404)
  6. https://trust.slcyber.io/ – The name "trust.slcyber.io" 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-02.

Show the 6 addresses we checked
  1. https://slcyber.io/legal/sla – reached, no match (HTTP 404)
  2. https://slcyber.io/sla – reached, no match (HTTP 404)
  3. https://slcyber.io/legal/service-level-agreement – reached, no match (HTTP 404)
  4. https://slcyber.io/trust/sla – reached, no match (HTTP 404)
  5. https://slcyber.io/uptime – reached, no match (HTTP 404)
  6. https://slcyber.io/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-02.

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

Is this wrong? Send us the URL

Published evidence 2
✓

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

Source: https://slcyber.io/ · checked 2026-09-02

✓

Named privacy contact

weight 1 of 3

A data protection officer or a dedicated privacy address is named.

Source: https://www.slcyber.io/privacy-policy · checked 2026-09-02

Keep going