Transparency alternatives to Text In Church
Other Church and community management vendors we measure, sorted by how much they publish that Text In Church does not. This is a comparison of disclosure, not of features or fitness.
12 shown of 40 that differ from Text In Church on at least one criterion we measured for both. Public transparency score, not a product or security rating.
Text In Church has 6 gaps in what we could measure: Data processing agreement, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Named privacy contact. The column “publishes and Text In Church does not” is the one that closes them.
| Vendor | Score | Publishes, and Text In Church does not | Text In Church publishes, and they do not | |
|---|---|---|---|---|
| Planning Centerplanningcenter.com | 57/100 | 2 Certifications named, Named privacy contact | 1 Data location stated | Compare |
| ChurchWiseAIchurchwiseai.com | 39/100 | 2 Certifications named, Named privacy contact | 3 Subprocessor list, Status page with history, Notice before subprocessors change | Compare |
| Pushpaypushpay.com | 39/100 | 2 security.txt (RFC 9116), Named privacy contact | 3 Subprocessor list, Status page with history, Notice before subprocessors change | Compare |
| Churchsuitechurchsuite.com | 26/100 | 2 Certifications named, security.txt (RFC 9116) | 4 Subprocessor list, Data location stated, Status page with history, +1 | Compare |
| CHMeetingschmeetings.com | 35/100 | 1 Named privacy contact | 3 Subprocessor list, Status page with history, Notice before subprocessors change | Compare |
| Multitracksmultitracks.com | 35/100 | 1 Named privacy contact | 3 Subprocessor list, HTTPS enforced with HSTS, Notice before subprocessors change | Compare |
| Subsplashsubsplash.com | 32/100 | 1 Named privacy contact | 3 Subprocessor list, Data location stated, Notice before subprocessors change | Compare |
| Aplosaplos.com | 22/100 | 1 Certifications named | 4 Subprocessor list, Data location stated, HTTPS enforced with HSTS, +1 | Compare |
| Tithe.lytithe.ly | 22/100 | 1 Named privacy contact | 4 Subprocessor list, Data location stated, Public pricing, +1 | Compare |
| Worship Toolsworshiptools.com | 22/100 | 1 security.txt (RFC 9116) | 4 Subprocessor list, Data location stated, Status page with history, +1 | Compare |
| Faithlifefaithlife.com | 17/100 | 1 Certifications named | 5 Subprocessor list, Status page with history, Public pricing, +2 | Compare |
| MOHIDmohid.net | 17/100 | 1 No third-party tracking before consent | 5 Subprocessor list, Data location stated, Status page with history, +2 | 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.