Transparency alternatives to GRÜN Software
Other Nonprofit fundraising vendors we measure, sorted by how much we found at them and not at GRÜN Software. This is a comparison of disclosure, not of features or fitness.
12 shown of 36 that differ from GRÜN Software on at least one criterion we measured for both. Public transparency score, not a product or security rating.
GRÜN Software has 9 gaps in what we could measure: Data processing agreement, Subprocessor list, Data location stated, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, Notice before subprocessors change. The column “Found there, not found at GRÜN Software” is the one that closes them.
| Vendor | Score | Found there, not found at GRÜN Software | Found at GRÜN Software, not found there | |
|---|---|---|---|---|
| Handbidhandbid.comSee also Transparency alternatives to Handbid | 48/100 | 5 Data processing agreement, Public pricing, Certifications named, +2 | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Beaconbeaconcrm.orgSee also Transparency alternatives to Beacon | 52/100 | 4 Subprocessor list, Status page with history, Public pricing, +1 | nothing | Compare |
| Donorfydonorfy.comSee also Transparency alternatives to Donorfy | 48/100 | 4 Data processing agreement, Data location stated, Public pricing, +1 | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Donorboxdonorbox.orgSee also Transparency alternatives to Donorbox | 39/100 | 4 Data location stated, Status page with history, Public pricing, +1 | 2 HTTPS enforced with HSTS, Named privacy contact | Compare |
| Funraisefunraise.orgSee also Transparency alternatives to Funraise | 39/100 | 3 Data location stated, Status page with history, Public pricing | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| VerticalChangeverticalchange.comSee also Transparency alternatives to VerticalChange | 39/100 | 3 Data location stated, Status page with history, Public pricing | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Bloomerangbloomerang.coSee also Transparency alternatives to Bloomerang | 30/100 | 3 Status page with history, Public pricing, Certifications named | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Neon Oneneonone.comSee also Transparency alternatives to Neon One | 30/100 | 3 Data location stated, Status page with history, Public pricing | 3 HTTPS enforced with HSTS, security.txt (RFC 9116), Named privacy contact | Compare |
| Givebuttergivebutter.comSee also Transparency alternatives to Givebutter | 30/100 | 2 Data location stated, Public pricing | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Keelakeela.coSee also Transparency alternatives to Keela | 30/100 | 2 Status page with history, Public pricing | 1 security.txt (RFC 9116) | Compare |
| OneCauseonecause.comSee also Transparency alternatives to OneCause | 30/100 | 2 Data location stated, Public pricing | 2 security.txt (RFC 9116), Named privacy contact | Compare |
| Blackbaudblackbaud.comSee also Transparency alternatives to Blackbaud | 26/100 | 2 Status page with history, Certifications named | 1 security.txt (RFC 9116) | Compare |
Only criteria we could measure for both are counted. Where we could measure one and not the other, the row is silent: that would be a statement about our measurement, not about either vendor. Every single result with its source is on the two profiles.