SaaS Ranking
Menu

GoFundMe Pro

classy.org · Nonprofit fundraising · checked 2026-09-03

35/100EBand E

Rank 5 of 17 in Nonprofit fundraising, where the median is 30.

We measured 12 of 12 criteria for GoFundMe Pro on 2026-09-03. We found 4 with a source and did not find 8 at the addresses we checked. That is a transparency score of 35 out of 100, band E.

Overview

Transparency labelsaas-ranking.com

GoFundMe Pro

classy.org · Nonprofit fundraising

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

Published commitments3 of 9 found

Measured behaviour1 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.

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

Gaps, heaviest first

✗

Data processing agreement

weight 3 of 3

No data processing agreement found.

Checked 8 addresses on 2026-09-03.

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

Is this wrong? Send us the URL

✗

Subprocessor list

weight 3 of 3

No subprocessor list found.

Checked 7 addresses on 2026-09-03.

Show the 7 addresses we checked
  1. https://classy.org/legal/subprocessors – reached, no match (HTTP 404)
  2. https://classy.org/subprocessors – reached, no match (HTTP 404)
  3. https://classy.org/sub-processors – reached, no match (HTTP 404)
  4. https://classy.org/legal/sub-processors – reached, no match (HTTP 404)
  5. https://classy.org/trust/subprocessors – reached, no match (HTTP 404)
  6. https://classy.org/privacy/subprocessors – reached, no match (HTTP 404)
  7. https://classy.org/legal/subprocessor-list – 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-03.

Show the 3 addresses we checked
  1. https://status.classy.org/ – The name "status.classy.org" could not be resolved.
  2. https://classy.org/status – reached, no match (HTTP 404)
  3. https://classy.org.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://classy.org/ – third-party requests before any interaction: 673-dcu-558.mktoresp.com, app.qualified.com, b.6sc.co, browser.sentry-cdn.com, bzr.openai.com, bzrcdn.openai.com, c.6sc.co, cdn.gofundme.com, connect.facebook.net, distillery.wistia.com, embed-cloudfront.wistia.com, embed-ssl.wistia.com, fast.wistia.com, fast.wistia.net, ipv6.6sc.co, j.6sc.co, js.qualified.com, munchkin.marketo.net, pagead2.googlesyndication.com, pro.gofundme.com, region1.google-analytics.com, scout-cdn.salesloft.com, scout.salesloft.com, script.crazyegg.com, snap.licdn.com, staging.classy-test.org, transcend-cdn.com, www.facebook.com, 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-03.

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

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://classy.org/security – reached, no match (HTTP 404)
  2. https://classy.org/trust – reached, no match (HTTP 404)
  3. https://classy.org/trust-center – reached, no match (HTTP 404)
  4. https://classy.org/compliance – reached, no match (HTTP 404)
  5. https://classy.org/legal/security – reached, no match (HTTP 404)
  6. https://trust.classy.org/ – The name "trust.classy.org" 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-03.

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

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://classy.org/.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.

Published, with a source 4
✓

Data location stated

weight 3 of 3

The hosting location is stated on a public page.

Source: https://pro.gofundme.com/c/legal/privacy-notice/ · checked 2026-09-03

✓

Public pricing

weight 2 of 3

Actual numbers on a public page.

Source: https://pro.gofundme.com/c/pricing/ · checked 2026-09-03

✓

HTTPS enforced with HSTS

weight 2 of 3

HTTP redirects to HTTPS and the HSTS header is set.

Source: https://classy.org/ · checked 2026-09-03

✓

Named privacy contact

weight 1 of 3

A data protection officer or a dedicated privacy address is named.

Source: https://pro.gofundme.com/c/legal/privacy-notice/ · checked 2026-09-03

History

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

Compare