SaaS Ranking

Sales and marketing / Conversational AI

Certainly

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

Transparency 65/100 CBand C

Rank 1 of 11 in Conversational AIcategory median 22checked 2026-09-02

4 gaps found: 4 criteria not found at the addresses we checked. 8 found4 not found0 not measured

Public transparency score, not a product or security rating.

Transparency labelsaas-ranking.com

Certainly

certainly.io · Conversational AI

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

Published commitments7 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

Certainly

certainly.io · Conversational AI

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

Published commitments7 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

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://certainly.io/legal/subprocessors – reached, no match (HTTP 200)
  2. https://certainly.io/subprocessors – reached, no match (HTTP 200)
  3. https://certainly.io/sub-processors – reached, no match (HTTP 200)
  4. https://certainly.io/legal/sub-processors – reached, no match (HTTP 200)
  5. https://certainly.io/trust/subprocessors – reached, no match (HTTP 200)
  6. https://certainly.io/privacy/subprocessors – reached, no match (HTTP 200)
  7. https://certainly.io/legal/subprocessor-list – 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-02.

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

No consent-free first load found.

Checked 1 address on 2026-09-02.

Show the 1 address we checked
  1. https://certainly.io/ – third-party requests before any interaction: 1.1.1.1, api.hubapi.com, ytxcootcfxwcmnqgdnjd.supabase.co

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://certainly.io/.well-known/security.txt – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Published evidence 8

Data processing agreement

weight 3 of 3

Published and readable without a login.

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

Data location stated

weight 3 of 3

The hosting location is stated on a public page.

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

Public pricing

weight 2 of 3

Actual numbers on a public page.

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

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

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

Notice before subprocessors change

weight 2 of 3

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

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

Certifications named

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

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

Uptime SLA with a figure

weight 1 of 3

An availability commitment with a figure.

Source: https://certainly.io/legal/sla · checked 2026-09-02

Named privacy contact

weight 1 of 3

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

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

Keep going