SaaS Ranking
Menu

Sayari

sayari.com · Supply chain risk · checked 2026-09-05

30/100EBand E

Rank 7 of 31 in Supply chain risk, where the median is 17.

We measured 12 of 12 criteria for Sayari on 2026-09-05. We found 4 with a source and did not find 8 at the addresses we checked. That is a transparency score of 30 out of 100, band E.

Overview

Transparency labelsaas-ranking.com

Sayari

sayari.com · Supply chain risk

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

Published commitments4 of 9 found

Measured behaviour0 of 3 found

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

The evidence pack carries every criterion with its source, the addresses we checked, the date and the data snapshot id – the four things a procurement file needs and a screenshot loses. We do not issue badges: a badge is the first step towards a paid placement, and there is none here.

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 Sayari 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-05.

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

Is this wrong? Send us the URL

✗

Data location stated

weight 3 of 3

We found this behind a sign-in, so it is not published openly.

Seen at https://sayari.com/privacy/ · checked 2026-09-05

Show the 7 addresses we checked
  1. https://sayari.com/security – reached, no match (HTTP 404)
  2. https://sayari.com/trust – reached, no match (HTTP 200)
  3. https://sayari.com/legal/privacy – reached, no match (HTTP 404)
  4. https://sayari.com/privacy – found, but behind a sign-in
  5. https://sayari.com/privacy-policy – found, but behind a sign-in
  6. https://sayari.com/compliance – reached, no match (HTTP 404)
  7. https://sayari.com/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-05.

Show the 3 addresses we checked
  1. https://status.sayari.com/ – Could not be fetched: fetch failed.
  2. https://sayari.com/status – reached, no match (HTTP 404)
  3. https://sayari.com.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-05.

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

Is this wrong? Send us the URL

✗

HTTPS enforced with HSTS

weight 2 of 3

No enforced HTTPS with HSTS found.

Checked 2 addresses on 2026-09-05.

Show the 2 addresses we checked
  1. http://sayari.com/ – redirects to https://sayari.com/
  2. https://sayari.com/ – no HSTS header

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

Show the 1 address we checked
  1. https://sayari.com/ – third-party requests before any interaction: ad.doubleclick.net, api.hubapi.com, bat.bing.com, connect.facebook.net, forms-na1.hsforms.com, forms.hsforms.com, js.hs-analytics.net, js.hs-banner.com, js.hs-scripts.com, js.hsadspixel.net, js.hsforms.net, js.hubspot.com, region1.analytics.google.com, scripts.clarity.ms, snap.licdn.com, stats.g.doubleclick.net, www.clarity.ms, www.google.com, www.google.de, www.googletagmanager.com

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

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

Show the 1 address we checked
  1. https://sayari.com/.well-known/security.txt – 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 4
✓

Subprocessor list

weight 3 of 3

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

Source: https://sayari.com/subprocessors/ · checked 2026-09-05

✓

Notice before subprocessors change

weight 2 of 3

The vendor commits publicly to giving notice before the list changes.

Source: https://sayari.com/subprocessors/ · checked 2026-09-05

✓

Certifications named

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

  • Named on that page Cyber Essentials (named without a certification claim), ISO/IEC 27001 (unclear from the sentence), SOC 2 Type II (named without a certification claim).
    Show the 3 exact wordings

    CYBER ESSENTIALS PLUS UK Government Cyber Security UK government-backed certification affirming our proactive stance

    Read at https://sayari.com/trust/

    ISO 27001:2022 Information Security Management Certified systematic approach to managing sensitive informatio

    Read at https://sayari.com/trust/

    SOC 2 TYPE 2 Service Organization Controls Independently audited compliance with AICPA trust service crit

    Read at https://sayari.com/trust/

Source: https://sayari.com/trust/ · checked 2026-09-05

✓

Named privacy contact

weight 1 of 3

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

Source: https://sayari.com/privacy/ · checked 2026-09-05

History

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

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.