SaaS Ranking
Menu

Feedly Threat Intelligence

feedly.com · Threat intelligence · checked 2026-09-03

48/100DBand D

Rank 2 of 18 in Threat intelligence, where the median is 22.

We measured 12 of 12 criteria for Feedly Threat Intelligence 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 48 out of 100, band D.

Overview

Transparency labelsaas-ranking.com

Feedly Threat Intelligence

feedly.com · Threat intelligence

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

Published commitments5 of 9 found

Measured behaviour2 of 3 found

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 Feedly Threat Intelligence has no such document.

Gaps, heaviest first

✗

Data processing agreement

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-09-03.

Show the 8 addresses we checked
  1. https://feedly.com/legal/dpa – Not the expected content type but "application/pdf".
  2. https://feedly.com/dpa – reached, no match (HTTP 200)
  3. https://feedly.com/legal/data-processing-agreement – reached, no match (HTTP 404)
  4. https://feedly.com/data-processing-agreement – reached, no match (HTTP 200)
  5. https://feedly.com/legal/data-processing-addendum – reached, no match (HTTP 404)
  6. https://feedly.com/legal/gdpr – reached, no match (HTTP 404)
  7. https://feedly.com/trust/dpa – reached, no match (HTTP 200)
  8. https://feedly.com/privacy/dpa – reached, no match (HTTP 200)

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

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

Show the 5 addresses we checked
  1. https://feedly.com/pricing – reached and rendered, no match
  2. https://feedly.com/pricing/ – reached, no match (HTTP 200)
  3. https://feedly.com/plans – reached, no match (HTTP 200)
  4. https://feedly.com/en/pricing – reached, no match (HTTP 404)
  5. https://feedly.com/pricing-plans – reached, no match (HTTP 200)

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

Show the 1 address we checked
  1. https://feedly.com/ – third-party requests before any interaction: ad.doubleclick.net, alb.reddit.com, aplo-evnt.com, assets.apollo.io, image.mux.com, inferred.litix.io, js.hs-analytics.net, js.hs-banner.com, js.hs-scripts.com, js.hubspot.com, snap.licdn.com, stream.mux.com, www.google.com, www.googletagmanager.com, www.redditstatic.com

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

Show the 8 addresses we checked
  1. https://feedly.com/legal/subprocessors – reached, no match (HTTP 200)
  2. https://feedly.com/subprocessors – reached, no match (HTTP 200)
  3. https://feedly.com/sub-processors – reached, no match (HTTP 200)
  4. https://feedly.com/legal/dpa – Not the expected content type but "application/pdf".
  5. https://feedly.com/dpa – reached, no match (HTTP 200)
  6. https://feedly.com/legal/data-processing-agreement – reached, no match (HTTP 404)
  7. https://feedly.com/trust/subprocessors – reached, no match (HTTP 200)
  8. https://feedly.com/legal/sub-processors – 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 7
✓

Subprocessor list

weight 3 of 3

The actual list is published, not just a promise to keep one.

Source: https://feedly.com/legal/subprocessors · checked 2026-09-03

✓

Status page with history

weight 2 of 3

A public status page with incident history.

Source: https://status.feedly.com/ · checked 2026-09-03

✓

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

Source: https://feedly.com/ · checked 2026-09-03

✓

Certifications named

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

Source: https://feedly.com/legal/security · checked 2026-09-03

✓

Uptime SLA with a figure

weight 1 of 3

An availability commitment with a figure.

Source: https://feedly.com/legal/sla · checked 2026-09-03

✓

security.txt (RFC 9116)

weight 1 of 3

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

Source: https://feedly.com/.well-known/security.txt · checked 2026-09-03

✓

Named privacy contact

weight 1 of 3

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

Source: https://feedly.com/legal/privacy · checked 2026-09-03

History

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

Compare