SaaS Ranking
Menu

Crowdcast

crowdcast.io · Event management · checked 2026-09-13

43/100DBand D

Rank 6 of 48 in Event management, where the median is 22.

We measured 12 of 12 criteria for Crowdcast on 2026-09-13. We found 5 with a source and did not find 7 at the addresses we checked. That is a transparency score of 43 out of 100, band D.

Overview

0 days since the newest finding, 0 since the oldest. 12 of 12 criteria measured in the last 30 days.

Evidence freshness is a statement about our measurement and is kept apart from the transparency score, which is frozen at v1. How good our own measurement is.

Transparency labelsaas-ranking.com

Crowdcast

crowdcast.io · Event management

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

Published commitments3 of 9 found

Measured behaviour2 of 3 found

Checked 2026-09-13. 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.

The evidence pack carries every criterion with its source, the addresses we checked, the date and the data snapshot id – the four things a procurement file needs and a screenshot loses. We do not issue badges: a badge is the first step towards a paid placement, and there is none here.

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

Where Crowdcast sits in Event management

  1. A0 0%
  2. B1 2%
  3. C1 2%
  4. D6 13%
  5. E13 27%
  6. F27 56%
48 vendors with a score; 8 more without a score because we could measure too little. Bands have fixed thresholds, see how the score works.

The band of Crowdcast is marked. Vendors without a score are the ones where we could measure too few criteria to rank them – a gap on our side, counted separately.

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.

Gaps, heaviest first

✗

Data processing agreement

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-09-13.

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

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

Show the 7 addresses we checked
  1. https://crowdcast.io/security – reached, no match (HTTP 200)
  2. https://crowdcast.io/trust – reached, no match (HTTP 200)
  3. https://crowdcast.io/legal/privacy – reached, no match (HTTP 404)
  4. https://crowdcast.io/privacy – reached, no match (HTTP 200)
  5. https://crowdcast.io/privacy-policy – reached, no match (HTTP 200)
  6. https://crowdcast.io/compliance – reached, no match (HTTP 200)
  7. https://crowdcast.io/legal/privacy-policy – reached, no match (HTTP 404)

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

Show the 3 addresses we checked
  1. https://status.crowdcast.io/ – reached, no match (HTTP 200)
  2. https://crowdcast.io/status – reached, no match (HTTP 200)
  3. https://crowdcast.io.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

Third-party requests seen on the first load, before any interaction.

Checked 1 address on 2026-09-13.

Show the 1 address we checked
  1. https://crowdcast.io/ – third-party requests before any interaction: fonts.googleapis.com, fonts.gstatic.com, p.typekit.net, plausible.io, statuspage.incident.io, use.typekit.net, widget.intercom.io

Is this wrong? Send us the URL

✗

Certifications named

weight 1 of 3

No named certification found.

Checked 6 addresses on 2026-09-13.

Show the 6 addresses we checked
  1. https://crowdcast.io/security – reached, no match (HTTP 200)
  2. https://crowdcast.io/trust – reached, no match (HTTP 200)
  3. https://crowdcast.io/trust-center – reached, no match (HTTP 200)
  4. https://crowdcast.io/compliance – reached, no match (HTTP 200)
  5. https://crowdcast.io/legal/security – reached, no match (HTTP 404)
  6. https://trust.crowdcast.io/ – The name "trust.crowdcast.io" could not be resolved.

Is this wrong? Send us the URL

✗

Uptime SLA with a figure

weight 1 of 3

No uptime figure found.

Checked 6 addresses on 2026-09-13.

Show the 6 addresses we checked
  1. https://crowdcast.io/legal/sla – reached, no match (HTTP 404)
  2. https://crowdcast.io/sla – reached, no match (HTTP 200)
  3. https://crowdcast.io/legal/service-level-agreement – reached, no match (HTTP 404)
  4. https://crowdcast.io/trust/sla – reached, no match (HTTP 404)
  5. https://crowdcast.io/uptime – reached, no match (HTTP 200)
  6. https://crowdcast.io/legal/uptime-sla – reached, no match (HTTP 404)

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

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

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 5
✓

Subprocessor list

weight 3 of 3

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

Source: https://www.crowdcast.io/subprocessors · checked 2026-09-13

✓

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://www.crowdcast.io/pricing · checked 2026-09-13

✓

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

  • HSTS max-age 63072000 seconds (730 days).
    Show the exact wording

    max-age=63072000

    Read at https://crowdcast.io/

Source: https://crowdcast.io/ · checked 2026-09-13

✓

Notice before subprocessors change

weight 2 of 3

The vendor commits publicly to giving notice before the list changes.

Source: https://www.crowdcast.io/subprocessors · checked 2026-09-13

✓

security.txt (RFC 9116)

weight 1 of 3

Served at /.well-known/security.txt.

Source: https://www.crowdcast.io/.well-known/security.txt · checked 2026-09-13

History

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

Compare

A shortlist holds up to six vendors across categories and lives entirely in the address of its page: share the link, bookmark it, put it in a ticket. Nothing is stored, so we do not know it exists.