Cust
cust.co · Customer success and onboarding · checked 2026-09-04
Rank 14 of 28 in Customer success and onboarding, where the median is 39.
- 5 found
- 7 not found
- 0 not measured
We measured 12 of 12 criteria for Cust on 2026-09-04. We found 5 with a source and did not find 7 at the addresses we checked. That is a transparency score of 39 out of 100, band E.
Overview
Transparency labelsaas-ranking.com
Cust
- A
- B
- C
- D
- E
- F
Published commitments4 of 9 found
- foundData processing agreement×3
- not foundSubprocessor list×3
- not foundData location stated×3
- not foundStatus page with history×2
- foundPublic pricing×2
- foundNotice before subprocessors change×2
- foundCertifications named×1
- not foundUptime SLA with a figure×1
- not foundNamed privacy contact×1
Measured behaviour1 of 3 found
- not foundHTTPS enforced with HSTS×2
- not foundNo third-party tracking before consent×2
- foundsecurity.txt (RFC 9116)×1
Checked 2026-09-04. 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.
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 Cust 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.
- Named on that page SOC 2 Type II.
Show the exact wording
Read our full LLM Security & Data Privacy Architecture SOC 2 Type II attested Cust is SOC 2 Type II attested, validating that our security, availability, and co
Read at https://cust.co/security/ - Third-party hosts we saw on the first load 9 amazonaws.com, doubleclick.net, facebook.com, facebook.net, google.com, google.de, googleapis.com, googletagmanager.com, gstatic.com.
Show the 9 exact wordings
s3-us-west-2.amazonaws.com
Read at https://cust.co/stats.g.doubleclick.net
Read at https://cust.co/www.facebook.com
Read at https://cust.co/connect.facebook.net
Read at https://cust.co/region1.analytics.google.com
Read at https://cust.co/www.google.de
Read at https://cust.co/fonts.googleapis.com
Read at https://cust.co/www.googletagmanager.com
Read at https://cust.co/fonts.gstatic.com
Read at https://cust.co/ - The file expires 2027-07-31. It was still valid when we checked on 2026-09-04.
Show the exact wording
Expires: 2027-07-31T00:00:00.000Z
Read at https://cust.co/.well-known/security.txt
Gaps, heaviest first
Subprocessor list
weight 3 of 3No subprocessor list found.
Checked 7 addresses on 2026-09-04.
Show the 7 addresses we checked
https://cust.co/legal/subprocessors– reached, no match (HTTP 404)https://cust.co/subprocessors– reached, no match (HTTP 404)https://cust.co/sub-processors– reached, no match (HTTP 404)https://cust.co/legal/sub-processors– reached, no match (HTTP 404)https://cust.co/trust/subprocessors– reached, no match (HTTP 404)https://cust.co/privacy/subprocessors– reached, no match (HTTP 404)https://cust.co/legal/subprocessor-list– reached, no match (HTTP 404)
Data location stated
weight 3 of 3No statement about data location found.
Checked 7 addresses on 2026-09-04.
Show the 7 addresses we checked
https://cust.co/security– reached, no match (HTTP 200)https://cust.co/trust– reached, no match (HTTP 404)https://cust.co/legal/privacy– reached, no match (HTTP 404)https://cust.co/privacy– reached, no match (HTTP 200)https://cust.co/privacy-policy– reached, no match (HTTP 200)https://cust.co/compliance– reached, no match (HTTP 404)https://cust.co/legal/privacy-policy– reached, no match (HTTP 404)
Status page with history
weight 2 of 3No public status page found.
Checked 3 addresses on 2026-09-04.
Show the 3 addresses we checked
https://status.cust.co/– reached, no match (HTTP 200)https://cust.co/status– reached, no match (HTTP 404)https://cust.co.statuspage.io/– Could not be fetched: fetch failed.
HTTPS enforced with HSTS
weight 2 of 3No enforced HTTPS with HSTS found.
Checked 2 addresses on 2026-09-04.
Show the 2 addresses we checked
http://cust.co/– redirects to https://cust.co/https://cust.co/– no HSTS header
No third-party tracking before consent
weight 2 of 3No consent-free first load found.
- Third-party hosts we saw on the first load 9 amazonaws.com, doubleclick.net, facebook.com, facebook.net, google.com, google.de, googleapis.com, googletagmanager.com, gstatic.com.
Show the 9 exact wordings
s3-us-west-2.amazonaws.com
Read at https://cust.co/stats.g.doubleclick.net
Read at https://cust.co/www.facebook.com
Read at https://cust.co/connect.facebook.net
Read at https://cust.co/region1.analytics.google.com
Read at https://cust.co/www.google.de
Read at https://cust.co/fonts.googleapis.com
Read at https://cust.co/www.googletagmanager.com
Read at https://cust.co/fonts.gstatic.com
Read at https://cust.co/
Checked 1 address on 2026-09-04.
Show the 1 address we checked
https://cust.co/– third-party requests before any interaction: connect.facebook.net, fonts.googleapis.com, fonts.gstatic.com, region1.analytics.google.com, s3-us-west-2.amazonaws.com, stats.g.doubleclick.net, www.facebook.com, www.google.de, www.googletagmanager.com
Uptime SLA with a figure
weight 1 of 3No uptime figure found.
Checked 6 addresses on 2026-09-04.
Show the 6 addresses we checked
https://cust.co/legal/sla– reached, no match (HTTP 404)https://cust.co/sla– reached, no match (HTTP 404)https://cust.co/legal/service-level-agreement– reached, no match (HTTP 404)https://cust.co/trust/sla– reached, no match (HTTP 404)https://cust.co/uptime– reached, no match (HTTP 404)https://cust.co/legal/uptime-sla– reached, no match (HTTP 404)
Named privacy contact
weight 1 of 3No named privacy contact found.
Checked 7 addresses on 2026-09-04.
Show the 7 addresses we checked
https://cust.co/legal/privacy– reached, no match (HTTP 404)https://cust.co/privacy– reached, no match (HTTP 200)https://cust.co/privacy-policy– reached, no match (HTTP 200)https://cust.co/legal/privacy-policy– reached, no match (HTTP 404)https://cust.co/legal/privacy-notice– reached, no match (HTTP 404)https://cust.co/trust/privacy– reached, no match (HTTP 404)https://cust.co/datenschutz– reached, no match (HTTP 404)
Evidence
The full source lists sit behind these two groups, so that the answer above stays readable.
Published, with a source 5
Data processing agreement
weight 3 of 3Published and readable without a login.
Source: https://cust.co/dpa/ · checked 2026-09-04
Public pricing
weight 2 of 3Actual numbers on a public page.
Source: https://cust.co/pricing/ · checked 2026-09-04
Notice before subprocessors change
weight 2 of 3The vendor commits publicly to giving notice before the list changes.
Source: https://cust.co/dpa/ · checked 2026-09-04
Certifications named
weight 1 of 3SOC 2 or ISO 27001 named on a public page.
- Named on that page SOC 2 Type II.
Show the exact wording
Read our full LLM Security & Data Privacy Architecture SOC 2 Type II attested Cust is SOC 2 Type II attested, validating that our security, availability, and co
Read at https://cust.co/security/
Source: https://cust.co/security/ · checked 2026-09-04
security.txt (RFC 9116)
weight 1 of 3Served at /.well-known/security.txt.
- The file expires 2027-07-31. It was still valid when we checked on 2026-09-04.
Show the exact wording
Expires: 2027-07-31T00:00:00.000Z
Read at https://cust.co/.well-known/security.txt
Source: https://cust.co/.well-known/security.txt · checked 2026-09-04
History
Not enough completed runs yet to draw a line. The next runs fill this in.