SaaS Ranking
Menu

Feedly Threat Intelligence: what they publish

feedly.com · Threat intelligence · checked 2026-10-16

48/100DBand D

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

Public transparency score, not a product or security rating. Latest check: 2026-10-16. 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

2 days since the newest dated result, 2 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

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 35

Published commitments5 of 9 found

Measured behaviour2 of 3 found

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

Where Feedly Threat Intelligence 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 Feedly Threat Intelligence 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 Feedly Threat Intelligence 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-16.

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

Across the market: Data processing agreement in Threat intelligence: 5 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-16.

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

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

✗

Public pricing with figures

weight 2 of 3

No public pricing with figures found.

Checked 5 addresses on 2026-10-16.

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

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.

Checked 1 address on 2026-10-16.

Show the 1 address we checked
  1. https://feedly.com/ – third-party requests before any interaction: ad.doubleclick.net, alb.reddit.com, chunk-oci-us-ashburn-1-vop1.edgemv.mux.com, cta-service-cms2.hubspot.com, image.mux.com, inferred.litix.io, js.hs-analytics.net, js.hs-banner.com, js.hs-scripts.com, js.hubspot.com, manifest-oci-us-ashburn-1-vop1.edgemv.mux.com, perf-na1.hsforms.com, px.ads.linkedin.com, region1.analytics.google.com, snap.licdn.com, stats.g.doubleclick.net, stream.mux.com, track.hubspot.com, widget.intercom.io, www.google.com, www.google.de, www.googletagmanager.com, www.redditstatic.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-16.

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

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

Evidence

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

Published, with a source 7
✓

Subprocessors: the published 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-10-16

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

✓

Status page with incident history

weight 2 of 3

A public status page with incident history.

Source: https://status.feedly.com/ · checked 2026-10-16

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

✓

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

  • HSTS max-age 15552000 seconds (180 days).
    Show the exact wording

    max-age=15552000

    Read at https://feedly.com/

Source: https://feedly.com/ · checked 2026-10-16

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 (not counted: the sentence does not carry it), PCI DSS (not counted: the sentence does not carry it), SOC 2 (unclear from the sentence), SOC 2 Type II (not counted: the sentence does not carry it). The sentence we kept does not carry this finding on its own, so it counts in no list and no figure.
    Show the 4 exact wordings

    be operated by Equinix that comply with SOC 1 type II/SOC 2 type II/PCI DSS/NIST 800-53/FI and are ISO 27001 certified.

    Read at https://feedly.com/legal/security

    rs Production data centers will be operated by Equinix that comply with SOC 1 type II/SOC 2 type II/PCI DSS/NIST 800-53/FI and are ISO 27001 certified.

    Read at https://feedly.com/legal/security

    Legal Terms of Use Privacy Policy Security Other products News Reader Market Intelligence © 2026 • SOC 2 Certified

    Read at https://feedly.com/legal/security

    Data Centers Production data centers will be operated by Equinix that comply with SOC 1 type II/SOC 2 type II/PCI DSS/NIST 800-53/FI and are ISO 27001 certified.

    Read at https://feedly.com/legal/security

Source: https://feedly.com/legal/security · checked 2026-10-16

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

✓

Uptime SLA with a figure

weight 1 of 3

An availability commitment with a figure.

  • Highest uptime figure on that page 99.5 %.
    Show the exact wording

    Service Level Agreement We take reasonable steps to maintain the Service for 99.5% uptime (except for scheduled downtime) (“Service Availability Minimums”), and respond to support re

    Read at https://feedly.com/legal/sla

Source: https://feedly.com/legal/sla · checked 2026-10-16

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

✓

security.txt (RFC 9116)

weight 1 of 3

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

Source: https://feedly.com/.well-known/security.txt · checked 2026-10-16

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

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

Source: https://feedly.com/legal/privacy · checked 2026-10-16

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

History

100 0 2026-10-09: 48 of 1002026-10-16: 48 of 100 2026-10-09 2026-10-16
Score over the last 2 runs we measured Feedly Threat Intelligence in: 48 (2026-10-09), 48 (2026-10-16).

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.

Feedly Threat Intelligence

7 found · 5 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-16.

Investigate 5 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. 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
  3. Public pricing

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

    Inspect this check
  4. 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
  5. 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

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.