Transparency alternatives to Multitracks
Other Church and community management vendors we measure, sorted by how much we found at them and not at Multitracks. This is a comparison of disclosure, not of features or fitness.
12 shown of 41 that differ from Multitracks on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Multitracks has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, 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. The column “Found there, not found at Multitracks” is the one that closes them.
| Vendor | Score | Found there, not found at Multitracks | Found at Multitracks, not found there | |
|---|---|---|---|---|
| Planning Centerplanningcenter.comSee also Transparency alternatives to Planning Center | 57/100 | 4 Subprocessor list, Certifications named, HTTPS enforced with HSTS, +1 | 1 Data location stated | Compare |
| Text In Churchtextinchurch.comSee also Transparency alternatives to Text In Church | 61/100 | 3 Subprocessor list, HTTPS enforced with HSTS, Notice before subprocessors change | 1 Named privacy contact | Compare |
| Churchsuitechurchsuite.comSee also Transparency alternatives to Churchsuite | 26/100 | 3 Certifications named, HTTPS enforced with HSTS, security.txt (RFC 9116) | 3 Data location stated, Status page with history, Named privacy contact | Compare |
| ChurchWiseAIchurchwiseai.comSee also Transparency alternatives to ChurchWiseAI | 39/100 | 2 Certifications named, HTTPS enforced with HSTS | 1 Status page with history | Compare |
| Pushpaypushpay.comSee also Transparency alternatives to Pushpay | 22/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 3 Data location stated, Status page with history, Named privacy contact | Compare |
| Worship Toolsworshiptools.comSee also Transparency alternatives to Worship Tools | 22/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 3 Data location stated, Status page with history, Named privacy contact | Compare |
| Loop Communityloopcommunity.comSee also Transparency alternatives to Loop Community | 13/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 4 Data location stated, Status page with history, Public pricing, +1 | Compare |
| SongSelectsongselect.ccli.comSee also Transparency alternatives to SongSelect | 13/100 | 2 HTTPS enforced with HSTS, security.txt (RFC 9116) | 4 Data location stated, Status page with history, Public pricing, +1 | Compare |
| Servant Keeperservantkeeper.comSee also Transparency alternatives to Servant Keeper | 39/100 | 1 HTTPS enforced with HSTS | 1 Named privacy contact | Compare |
| CHMeetingschmeetings.comSee also Transparency alternatives to CHMeetings | 35/100 | 1 HTTPS enforced with HSTS | 1 Status page with history | Compare |
| Subsplashsubsplash.comSee also Transparency alternatives to Subsplash | 32/100 | 1 HTTPS enforced with HSTS | 1 Data location stated | Compare |
| Bible Appyouversion.comSee also Transparency alternatives to Bible App | 30/100 | 1 HTTPS enforced with HSTS | 2 Public pricing, Named privacy contact | 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.