SaaS Ranking
Menu

Curity

curity.io · API security · checked 2026-09-03

Not enough data: 5 of 12 criteria measured, so no transparency score

We measured 5 of 12 criteria for Curity on 2026-09-03. We found 0 with a source and did not find 5 at the addresses we checked; 7 we could not measure at all. Below our threshold there is no score and no rank, and that is a statement about our measurement.

Overview

Transparency labelsaas-ranking.com

Curity

curity.io · API security

  1. A
  2. B
  3. C
  4. D
  5. E
  6. F
Not enough data5 of 12 measured, no score

Published commitments0 of 2 found, 7 not measured

Measured behaviour0 of 3 found

Checked 2026-09-03. 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. We could measure 5 of 12 criteria, which is below our threshold, so there is no rank. That is a statement about our measurement, not about Curity.

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 Curity has no such document.

Gaps, heaviest first

✗

Status page with history

weight 2 of 3

No public status page found.

Checked 3 addresses on 2026-09-03.

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

Is this wrong? Send us the URL

✗

Public pricing

weight 2 of 3

No public pricing with figures found.

Checked 5 addresses on 2026-09-03.

Show the 5 addresses we checked
  1. https://curity.io/pricing – reached and rendered, no match
  2. https://curity.io/pricing/ – reached, no match (HTTP 200)
  3. https://curity.io/plans – reached, no match (HTTP 404)
  4. https://curity.io/en/pricing – reached, no match (HTTP 404)
  5. https://curity.io/pricing-plans – reached, no match (HTTP 404)

Is this wrong? Send us the URL

✗

HTTPS enforced with HSTS

weight 2 of 3

No enforced HTTPS with HSTS found.

Checked 2 addresses on 2026-09-03.

Show the 2 addresses we checked
  1. http://curity.io/ – redirects to https://curity.io/
  2. https://curity.io/ – no HSTS header

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

Show the 1 address we checked
  1. https://curity.io/ – third-party requests before any interaction: policy.app.cookieinformation.com, www.googletagmanager.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-03.

Show the 1 address we checked
  1. https://curity.io/.well-known/security.txt – reached, no match (HTTP 404)

Is this wrong? Send us the URL

Evidence

The full source lists sit behind these two groups, so that the answer above stays readable.

Not measured by us 7
–

Data processing agreement

weight 3 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 8 addresses we checked
  1. https://curity.io/legal/dpa – excluded by robots.txt
  2. https://curity.io/dpa – reached, no match (HTTP 404)
  3. https://curity.io/legal/data-processing-agreement – excluded by robots.txt
  4. https://curity.io/data-processing-agreement – reached, no match (HTTP 404)
  5. https://curity.io/legal/data-processing-addendum – excluded by robots.txt
  6. https://curity.io/legal/gdpr – excluded by robots.txt
  7. https://curity.io/trust/dpa – reached, no match (HTTP 404)
  8. https://curity.io/privacy/dpa – reached, no match (HTTP 404)

Is this wrong? Send us the URL

–

Subprocessor list

weight 3 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 7 addresses we checked
  1. https://curity.io/legal/subprocessors – excluded by robots.txt
  2. https://curity.io/subprocessors – reached, no match (HTTP 404)
  3. https://curity.io/sub-processors – reached, no match (HTTP 404)
  4. https://curity.io/legal/sub-processors – excluded by robots.txt
  5. https://curity.io/trust/subprocessors – reached, no match (HTTP 404)
  6. https://curity.io/privacy/subprocessors – reached, no match (HTTP 404)
  7. https://curity.io/legal/subprocessor-list – excluded by robots.txt

Is this wrong? Send us the URL

–

Data location stated

weight 3 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 7 addresses we checked
  1. https://curity.io/security – reached, no match (HTTP 404)
  2. https://curity.io/trust – reached, no match (HTTP 404)
  3. https://curity.io/legal/privacy – excluded by robots.txt
  4. https://curity.io/privacy – reached, no match (HTTP 404)
  5. https://curity.io/privacy-policy – reached, no match (HTTP 404)
  6. https://curity.io/compliance – reached, no match (HTTP 404)
  7. https://curity.io/legal/privacy-policy – excluded by robots.txt

Is this wrong? Send us the URL

–

Notice before subprocessors change

weight 2 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 8 addresses we checked
  1. https://curity.io/legal/subprocessors – excluded by robots.txt
  2. https://curity.io/subprocessors – reached, no match (HTTP 404)
  3. https://curity.io/sub-processors – reached, no match (HTTP 404)
  4. https://curity.io/legal/dpa – excluded by robots.txt
  5. https://curity.io/dpa – reached, no match (HTTP 404)
  6. https://curity.io/legal/data-processing-agreement – excluded by robots.txt
  7. https://curity.io/trust/subprocessors – reached, no match (HTTP 404)
  8. https://curity.io/legal/sub-processors – excluded by robots.txt

Is this wrong? Send us the URL

–

Certifications named

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 6 addresses we checked
  1. https://curity.io/security – reached, no match (HTTP 404)
  2. https://curity.io/trust – reached, no match (HTTP 404)
  3. https://curity.io/trust-center – reached, no match (HTTP 404)
  4. https://curity.io/compliance – reached, no match (HTTP 404)
  5. https://curity.io/legal/security – excluded by robots.txt
  6. https://trust.curity.io/ – blocked or unavailable (HTTP 403)

Is this wrong? Send us the URL

–

Uptime SLA with a figure

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 6 addresses we checked
  1. https://curity.io/legal/sla – excluded by robots.txt
  2. https://curity.io/sla – reached, no match (HTTP 404)
  3. https://curity.io/legal/service-level-agreement – excluded by robots.txt
  4. https://curity.io/trust/sla – reached, no match (HTTP 404)
  5. https://curity.io/uptime – reached, no match (HTTP 404)
  6. https://curity.io/legal/uptime-sla – excluded by robots.txt

Is this wrong? Send us the URL

–

Named privacy contact

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 7 addresses we checked
  1. https://curity.io/legal/privacy – excluded by robots.txt
  2. https://curity.io/privacy – reached, no match (HTTP 404)
  3. https://curity.io/privacy-policy – reached, no match (HTTP 404)
  4. https://curity.io/legal/privacy-policy – excluded by robots.txt
  5. https://curity.io/legal/privacy-notice – excluded by robots.txt
  6. https://curity.io/trust/privacy – reached, no match (HTTP 404)
  7. https://curity.io/datenschutz – reached, no match (HTTP 404)

Is this wrong? Send us the URL

History

Not enough completed runs yet to draw a line. The next runs fill this in.

Compare