SaaS Ranking
Menu

Security and compliance / API security

Cequence

What Cequence publishes on cequence.ai, measured on 2026-09-02. Every line links the page we found it on, or lists the addresses we checked.

Transparency 26/100 EBand E

Rank 5 of 12 in API securitycategory median 24checked 2026-09-02

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

Public transparency score, not a product or security rating.

Transparency labelsaas-ranking.com

Cequence

cequence.ai · API security

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

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

Cequence

cequence.ai · API security

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

Published commitments3 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://cequence.ai/legal/dpa – reached, no match (HTTP 200)
  2. https://cequence.ai/dpa – reached, no match (HTTP 200)
  3. https://cequence.ai/legal/data-processing-agreement – reached, no match (HTTP 200)
  4. https://cequence.ai/data-processing-agreement – reached, no match (HTTP 200)
  5. https://cequence.ai/legal/data-processing-addendum – reached, no match (HTTP 200)
  6. https://cequence.ai/legal/gdpr – reached, no match (HTTP 200)
  7. https://cequence.ai/trust/dpa – reached, no match (HTTP 200)
  8. https://cequence.ai/privacy/dpa – reached, no match (HTTP 200)

Is this wrong? Send us the URL

✗

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

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

Show the 7 addresses we checked
  1. https://cequence.ai/security – reached, no match (HTTP 200)
  2. https://cequence.ai/trust – reached, no match (HTTP 200)
  3. https://cequence.ai/legal/privacy – reached, no match (HTTP 200)
  4. https://cequence.ai/privacy – reached, no match (HTTP 200)
  5. https://cequence.ai/privacy-policy – reached, no match (HTTP 200)
  6. https://cequence.ai/compliance – reached, no match (HTTP 200)
  7. https://cequence.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-02.

Show the 3 addresses we checked
  1. https://status.cequence.ai/ – The name "status.cequence.ai" could not be resolved.
  2. https://cequence.ai/status – reached, no match (HTTP 200)
  3. https://cequence.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

No consent-free first load found.

Checked 1 address on 2026-09-02.

Show the 1 address we checked
  1. https://cequence.ai/ – third-party requests before any interaction: 490-rqf-960.mktoresp.com, ad.doubleclick.net, b.6sc.co, c.6sc.co, c.clarity.ms, cdn-gkclf.nitrocdn.com, cequencedev.wpengine.com, fonts.googleapis.com, googleads.g.doubleclick.net, ipv6.6sc.co, j.6sc.co, munchkin.marketo.net, px.ads.linkedin.com, region1.analytics.google.com, scripts.clarity.ms, snap.licdn.com, stats.g.doubleclick.net, to.getnitropack.com, tracking-api.g2.com, u.clarity.ms, www.clarity.ms, www.google.com, www.google.de, www.googletagmanager.com

Is this wrong? Send us the URL

✗

Notice before subprocessors change

weight 2 of 3

No commitment to give notice before subprocessors change found.

Checked 8 addresses on 2026-09-02.

Show the 8 addresses we checked
  1. https://cequence.ai/legal/subprocessors – reached, no match (HTTP 200)
  2. https://cequence.ai/subprocessors – reached, no match (HTTP 200)
  3. https://cequence.ai/sub-processors – reached, no match (HTTP 200)
  4. https://cequence.ai/legal/dpa – reached, no match (HTTP 200)
  5. https://cequence.ai/dpa – reached, no match (HTTP 200)
  6. https://cequence.ai/legal/data-processing-agreement – reached, no match (HTTP 200)
  7. https://cequence.ai/trust/subprocessors – reached, no match (HTTP 200)
  8. https://cequence.ai/legal/sub-processors – reached, no match (HTTP 200)

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://cequence.ai/.well-known/security.txt – reached, no match (HTTP 200)

Is this wrong? Send us the URL

✗

Named privacy contact

weight 1 of 3

No named privacy contact found.

Checked 7 addresses on 2026-09-02.

Show the 7 addresses we checked
  1. https://cequence.ai/legal/privacy – reached, no match (HTTP 200)
  2. https://cequence.ai/privacy – reached, no match (HTTP 200)
  3. https://cequence.ai/privacy-policy – reached, no match (HTTP 200)
  4. https://cequence.ai/legal/privacy-policy – reached, no match (HTTP 200)
  5. https://cequence.ai/legal/privacy-notice – reached, no match (HTTP 200)
  6. https://cequence.ai/trust/privacy – reached, no match (HTTP 200)
  7. https://cequence.ai/datenschutz – reached, no match (HTTP 200)

Is this wrong? Send us the URL

Published evidence 4
✓

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://www.cequence.ai/ · checked 2026-09-02

✓

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

Source: https://cequence.ai/ · checked 2026-09-02

✓

Certifications named

weight 1 of 3

SOC 2 or ISO 27001 named on a public page.

Source: https://trust.cequence.ai/ · checked 2026-09-02

✓

Uptime SLA with a figure

weight 1 of 3

An availability commitment with a figure.

Source: https://www.cequence.ai/ · checked 2026-09-02

Keep going