SaaS Ranking

Curogram

curogram.com · Telehealth platforms · checked 2026-09-03

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

We measured 6 of 12 criteria for Curogram on 2026-09-03. We found 2 with a source and did not find 4 at the addresses we checked; 6 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

Curogram

curogram.com · Telehealth platforms

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

Published commitments1 of 4 found, 5 not measured

Measured behaviour1 of 2 found, 1 not measured

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 6 of 12 criteria, which is below our threshold, so there is no rank. That is a statement about our measurement, not about Curogram.

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 Curogram 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.curogram.com/ – reached, no match (HTTP 200)
  2. https://curogram.com/status – blocked or unavailable (HTTP 500)
  3. https://curogram.com.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-03.

Show the 1 address we checked
  1. https://curogram.com/ – third-party requests before any interaction: 507386.fs1.hubspotusercontent-na2.net, 7052064.fs1.hubspotusercontent-na1.net, a.plerdy.com, ad.doubleclick.net, amplify.outbrain.com, analytics.ahrefs.com, api.hubapi.com, aplo-evnt.com, app.hubspot.com, assets.apollo.io, cdn2.hubspot.net, connect.facebook.net, cta-service-cms2.hubspot.com, d.adroll.com, ddwl4m2hdecbv.cloudfront.net, edge-ord.clouds-stacks.com, fonts.gstatic.com, forms-na1.hsforms.com, googleads.g.doubleclick.net, i.ytimg.com, jnn-pa.googleapis.com, js.hs-analytics.net, js.hs-banner.com, js.hsadspixel.net, js.hsforms.net, js.hubspot.com, no-cache.hubspot.com, perf-na1.hsforms.com, perf.hsforms.com, px.ads.linkedin.com, region1.analytics.google.com, resources.xg4ken.com, s.adroll.com, snap.licdn.com, static.doubleclick.net, stats.g.doubleclick.net, track.hubspot.com, tracking-api.g2.com, www.facebook.com, www.google-analytics.com, www.google.com, www.google.de, www.googletagmanager.com, www.youtube.com

Is this wrong? Send us the URL

Certifications named

weight 1 of 3

No named certification found.

Checked 6 addresses on 2026-09-03.

Show the 6 addresses we checked
  1. https://curogram.com/security – blocked or unavailable (HTTP 500)
  2. https://curogram.com/trust – Could not be fetched: fetch failed.
  3. https://curogram.com/trust-center – Could not be fetched: fetch failed.
  4. https://curogram.com/compliance – Could not be fetched: fetch failed.
  5. https://curogram.com/legal/security – Could not be fetched: fetch failed.
  6. https://trust.curogram.com/ – 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-03.

Show the 7 addresses we checked
  1. https://curogram.com/legal/privacy – Could not be fetched: fetch failed.
  2. https://curogram.com/privacy – reached, no match (HTTP 200)
  3. https://curogram.com/privacy-policy – Could not be fetched: fetch failed.
  4. https://curogram.com/legal/privacy-policy – Could not be fetched: fetch failed.
  5. https://curogram.com/legal/privacy-notice – Could not be fetched: fetch failed.
  6. https://curogram.com/trust/privacy – Could not be fetched: fetch failed.
  7. https://curogram.com/datenschutz – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Evidence

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

Published, with a source 2

Data location stated

weight 3 of 3

The hosting location is stated on a public page.

Source: https://curogram.com/privacy · checked 2026-09-03

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

Source: https://curogram.com/ · checked 2026-09-03

Not measured by us 6

Data processing agreement

weight 3 of 3

Not measured. None of the addresses could be reached, so this was not measured.

Show the 8 addresses we checked
  1. https://curogram.com/legal/dpa – Could not be fetched: fetch failed.
  2. https://curogram.com/dpa – Could not be fetched: fetch failed.
  3. https://curogram.com/legal/data-processing-agreement – Could not be fetched: fetch failed.
  4. https://curogram.com/data-processing-agreement – Could not be fetched: fetch failed.
  5. https://curogram.com/legal/data-processing-addendum – Could not be fetched: fetch failed.
  6. https://curogram.com/legal/gdpr – Could not be fetched: fetch failed.
  7. https://curogram.com/trust/dpa – Could not be fetched: fetch failed.
  8. https://curogram.com/privacy/dpa – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Subprocessor list

weight 3 of 3

Not measured. None of the addresses could be reached, so this was not measured.

Show the 7 addresses we checked
  1. https://curogram.com/legal/subprocessors – Could not be fetched: fetch failed.
  2. https://curogram.com/subprocessors – Could not be fetched: fetch failed.
  3. https://curogram.com/sub-processors – Could not be fetched: fetch failed.
  4. https://curogram.com/legal/sub-processors – Could not be fetched: fetch failed.
  5. https://curogram.com/trust/subprocessors – Could not be fetched: fetch failed.
  6. https://curogram.com/privacy/subprocessors – Could not be fetched: fetch failed.
  7. https://curogram.com/legal/subprocessor-list – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Public pricing

weight 2 of 3

Not measured. The vendor’s server blocked or rate-limited our crawler, so this was not measured.

Show the 5 addresses we checked
  1. https://curogram.com/pricing – blocked or unavailable (HTTP 500)
  2. https://curogram.com/pricing/ – blocked or unavailable (HTTP 500)
  3. https://curogram.com/plans – Could not be fetched: fetch failed.
  4. https://curogram.com/en/pricing – Could not be fetched: fetch failed.
  5. https://curogram.com/pricing-plans – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Notice before subprocessors change

weight 2 of 3

Not measured. None of the addresses could be reached, so this was not measured.

Show the 8 addresses we checked
  1. https://curogram.com/legal/subprocessors – Could not be fetched: fetch failed.
  2. https://curogram.com/subprocessors – Could not be fetched: fetch failed.
  3. https://curogram.com/sub-processors – Could not be fetched: fetch failed.
  4. https://curogram.com/legal/dpa – Could not be fetched: fetch failed.
  5. https://curogram.com/dpa – Could not be fetched: fetch failed.
  6. https://curogram.com/legal/data-processing-agreement – Could not be fetched: fetch failed.
  7. https://curogram.com/trust/subprocessors – Could not be fetched: fetch failed.
  8. https://curogram.com/legal/sub-processors – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

Uptime SLA with a figure

weight 1 of 3

Not measured. The vendor’s server blocked or rate-limited our crawler, so this was not measured.

Show the 6 addresses we checked
  1. https://curogram.com/legal/sla – Could not be fetched: fetch failed.
  2. https://curogram.com/sla – Could not be fetched: fetch failed.
  3. https://curogram.com/legal/service-level-agreement – Could not be fetched: fetch failed.
  4. https://curogram.com/trust/sla – Could not be fetched: fetch failed.
  5. https://curogram.com/uptime – blocked or unavailable (HTTP 500)
  6. https://curogram.com/legal/uptime-sla – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

security.txt (RFC 9116)

weight 1 of 3

Not measured. None of the addresses could be reached, so this was not measured.

Show the 1 address we checked
  1. https://curogram.com/.well-known/security.txt – Could not be fetched: fetch failed.

Is this wrong? Send us the URL

History

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

Compare