Transparency alternatives to Araize
Other Nonprofit fundraising vendors we measure, sorted by how much they publish that Araize does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 35 that differ from Araize on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Araize has 11 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Public pricing, Certifications named, Uptime SLA with a figure, HTTPS enforced with HSTS, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change, Named privacy contact. The column “publishes and Araize does not” is the one that closes them.
| Vendor | Score | Publishes, and Araize does not | Araize publishes, and they do not | |
|---|---|---|---|---|
| Beaconbeaconcrm.org | 48/100 | 6 Subprocessor list, Status page with history, Public pricing, +3 | 1 Data location stated | Compare |
| Handbidhandbid.com | 48/100 | 6 Data processing agreement, Public pricing, Certifications named, +3 | 1 Data location stated | Compare |
| Donorfydonorfy.com | 48/100 | 4 Data processing agreement, Public pricing, Certifications named, +1 | nothing | Compare |
| Donorboxdonorbox.org | 39/100 | 4 Status page with history, Public pricing, Certifications named, +1 | nothing | Compare |
| Bloomerangbloomerang.co | 30/100 | 4 Status page with history, Public pricing, Certifications named, +1 | 1 Data location stated | Compare |
| Blackbaudblackbaud.com | 26/100 | 4 Status page with history, Certifications named, HTTPS enforced with HSTS, +1 | 1 Data location stated | Compare |
| Funraisefunraise.org | 39/100 | 3 Status page with history, Public pricing, HTTPS enforced with HSTS | nothing | Compare |
| VerticalChangeverticalchange.com | 39/100 | 3 Status page with history, Public pricing, HTTPS enforced with HSTS | nothing | Compare |
| Raisenowraisenow.com | 26/100 | 3 Status page with history, Public pricing, HTTPS enforced with HSTS | 1 Data location stated | Compare |
| JustGivingjustgiving.com | 22/100 | 3 Public pricing, HTTPS enforced with HSTS, security.txt (RFC 9116) | 1 Data location stated | Compare |
| Keelakeela.co | 22/100 | 3 Public pricing, HTTPS enforced with HSTS, Named privacy contact | 1 Data location stated | Compare |
| Mightycausemightycause.com | 22/100 | 3 Public pricing, HTTPS enforced with HSTS, Named privacy contact | 1 Data location stated | 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.