SaaS Ranking

Yellow.ai

yellow.ai · Conversational AI · checked 2026-09-13

55/100CBand C

Rank 6 of 43 in Conversational AI, where the median is 26.

We measured 11 of 12 criteria for Yellow.ai on 2026-09-13. We found 7 with a source and did not find 4 at the addresses we checked; 1 we could not measure at all. That is a transparency score of 55 out of 100, band C.

Overview

1 day since the newest finding, 1 since the oldest. 12 of 12 criteria measured in the last 30 days.

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

Yellow.ai

yellow.ai · Conversational AI

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

Published commitments6 of 9 found

Measured behaviour1 of 2 found, 1 not measured

Checked 2026-09-13. 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 Yellow.ai has no such document.

Where Yellow.ai sits in Conversational AI

  1. A0 0%
  2. B0 0%
  3. C6 14%
  4. D5 12%
  5. E13 30%
  6. F19 44%
43 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 Yellow.ai 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 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

Subprocessor list

weight 3 of 3

No subprocessor list found.

Checked 7 addresses on 2026-09-13.

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

Show the 7 addresses we checked
  1. https://yellow.ai/security – reached, no match (HTTP 200)
  2. https://yellow.ai/trust – Not the expected content type but "image/webp".
  3. https://yellow.ai/legal/privacy – reached, no match (HTTP 200)
  4. https://yellow.ai/privacy – reached, no match (HTTP 404)
  5. https://yellow.ai/privacy-policy – reached, no match (HTTP 200)
  6. https://yellow.ai/compliance – reached, no match (HTTP 404)
  7. https://yellow.ai/legal/privacy-policy – reached, no match (HTTP 200)

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

Show the 3 addresses we checked
  1. https://status.yellow.ai/ – reached, no match (HTTP 200)
  2. https://yellow.ai/status – reached, no match (HTTP 404)
  3. https://yellow.ai.statuspage.io/ – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

No third-party tracking before consent

weight 2 of 3

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

  • Third-party hosts we saw on the first load 6 amazonaws.com, betterstackdata.com, googleapis.com, gstatic.com, interactlabs.ai, yellowmessenger.com.
    Show the 6 exact wordings

    r4-ym-uploads.s3-us-west-2.amazonaws.com

    Read at https://yellow.ai/

    s2429490.us-east-9.betterstackdata.com

    Read at https://yellow.ai/

    fonts.googleapis.com

    Read at https://yellow.ai/

    fonts.gstatic.com

    Read at https://yellow.ai/

    logs.grafana.interactlabs.ai, prod-v2.assets.interactlabs.ai, prod-v2.chicken.interactlabs.ai, repro.interactlabs.ai, script.interactlabs.ai

    Read at https://yellow.ai/

    cdn.yellowmessenger.com

    Read at https://yellow.ai/

Checked 1 address on 2026-09-13.

Show the 1 address we checked
  1. https://yellow.ai/ – third-party requests before any interaction: cdn.yellowmessenger.com, fonts.googleapis.com, fonts.gstatic.com, logs.grafana.interactlabs.ai, prod-v2.assets.interactlabs.ai, prod-v2.chicken.interactlabs.ai, r4-ym-uploads.s3-us-west-2.amazonaws.com, repro.interactlabs.ai, s2429490.us-east-9.betterstackdata.com, script.interactlabs.ai

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

Data processing agreement

weight 3 of 3

Published and readable without a login.

Source: https://yellow.ai/dpa/ · checked 2026-09-13

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://yellow.ai/pricing/ · checked 2026-09-13

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

  • HSTS max-age 31536000 seconds (365 days).
    Show the exact wording

    max-age=31536000; includeSubDomains; preload

    Read at https://yellow.ai/
  • HSTS options includeSubDomains, preload.
    Show the 2 exact wordings

    max-age=31536000; includeSubDomains; preload

    Read at https://yellow.ai/

    max-age=31536000; includeSubDomains; preload

    Read at https://yellow.ai/

Source: https://yellow.ai/ · checked 2026-09-13

Notice before subprocessors change

weight 2 of 3

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

Source: https://yellow.ai/dpa/ · checked 2026-09-13

Certifications named

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

  • Named on that page HIPAA (not counted: the sentence does not carry it), ISO/IEC 27001 (not counted: the sentence does not carry it), ISO/IEC 27701 (not counted: the sentence does not carry it), PCI DSS (not counted: the sentence does not carry it), 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 5 exact wordings

    Deploy with confidence, deliver value faster HIPAA ISO 27001 ISO 27701 SOC 2 Type II PCI-DSS V 4.0.1 Our robust guardrails and Responsible AI principl

    Read at https://yellow.ai/

    Deploy with confidence, deliver value faster HIPAA ISO 27001 ISO 27701 SOC 2 Type II PCI-DSS V 4.0.1 Our robust guardrails and Responsible AI principles protect

    Read at https://yellow.ai/

    Deploy with confidence, deliver value faster HIPAA ISO 27001 ISO 27701 SOC 2 Type II PCI-DSS V 4.0.1 Our robust guardrails and Responsible AI principles protect sensitive

    Read at https://yellow.ai/

    Deploy with confidence, deliver value faster HIPAA ISO 27001 ISO 27701 SOC 2 Type II PCI-DSS V 4.0.1 Our robust guardrails and Responsible AI principles protect sensitive data while ensuring i

    Read at https://yellow.ai/

    Deploy with confidence, deliver value faster HIPAA ISO 27001 ISO 27701 SOC 2 Type II PCI-DSS V 4.0.1 Our robust guardrails and Responsible AI principles protect sensitive data

    Read at https://yellow.ai/

Source: https://yellow.ai/ · checked 2026-09-13

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

    Yellow.ai will make commercially reasonable efforts to provide Customer with an Uptime of 99.5% for Hosted Software.

    Read at https://yellow.ai/sla/

Source: https://yellow.ai/sla/ · checked 2026-09-13

Named privacy contact

weight 1 of 3

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

Source: https://yellow.ai/privacy-policy/ · checked 2026-09-13

Not measured by us 1

security.txt (RFC 9116)

weight 1 of 3

Not measured. The vendor’s robots.txt excludes us from at least one of these addresses, so this was not measured.

Show the 1 address we checked
  1. https://yellow.ai/.well-known/security.txt – excluded by robots.txt

Is this wrong? Send us the URL

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.