SaaS Ranking

Sales and marketing / Sales engagement

Clearbit

What Clearbit publishes on clearbit.com, 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 2 of 12 in Sales engagementcategory median 45.5checked 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

Clearbit

clearbit.com · Sales engagement

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

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

Clearbit

clearbit.com · Sales engagement

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

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

Data processing agreement

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-09-02.

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

Is this wrong? Send us the URL

Public pricing

weight 2 of 3

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

Seen at https://app.clearbit.com/auth/login · checked 2026-09-02

Show the 5 addresses we checked
  1. https://clearbit.com/pricing – reached and rendered, no match
  2. https://clearbit.com/pricing/ – reached, no match (HTTP 200)
  3. https://clearbit.com/plans – found, but behind a sign-in
  4. https://clearbit.com/en/pricing – reached, no match (HTTP 404)
  5. https://clearbit.com/pricing-plans – reached, no match (HTTP 404)

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://clearbit.com/ – third-party requests before any interaction: api.segment.io, cdn.segment.com, client-registry.mutinycdn.com, fonts.googleapis.com, fonts.gstatic.com, forms.hscollectedforms.net, forms.hsforms.com, js-na1.hs-scripts.com, js.hs-analytics.net, js.hs-banner.com, js.hscollectedforms.net, o13610.ingest.sentry.io, tag.clearbitscripts.com, x.clearbitjs.com

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

Is this wrong? Send us the URL

Published evidence 8

Subprocessor list

weight 3 of 3

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

Source: https://clearbit.com/subprocessors · checked 2026-09-02

Data location stated

weight 3 of 3

The hosting location is stated on a public page.

Source: https://clearbit.com/trust · checked 2026-09-02

Status page with history

weight 2 of 3

A public status page with incident history.

Source: https://status.clearbit.com/ · checked 2026-09-02

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

Source: https://clearbit.com/ · 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://clearbit.com/subprocessors · checked 2026-09-02

Certifications named

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

Source: https://clearbit.com/trust · checked 2026-09-02

Uptime SLA with a figure

weight 1 of 3

An availability commitment with a figure.

Source: https://clearbit.com/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://clearbit.com/privacy-policy · checked 2026-09-02

Keep going