SaaS Ranking

Alternatives to CHMeetings

Other Church and community management vendors we measure, sorted by how much they publish that CHMeetings does not. This is a comparison of disclosure, not of features or fitness.

12 shown of 25 that differ from CHMeetings on at least one criterion we measured for both. Public transparency score, not a product or security rating.

CHMeetings has 8 gaps in what we could measure: Data processing agreement, Subprocessor list, Status page with history, Certifications named, Uptime SLA with a figure, No third-party tracking before consent, security.txt (RFC 9116), Notice before subprocessors change. The column “publishes and CHMeetings does not” is the one that closes them.

VendorScorePublishes, and CHMeetings does notCHMeetings publishes, and they do not
Churchsuitechurchsuite.com 26/100 2 Certifications named, security.txt (RFC 9116) 2 Data location stated, Named privacy contact Compare
Aplosaplos.com 22/100 2 Status page with history, Certifications named 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact Compare
Church Community Builderchurchcommunitybuilder.com 43/100 1 Status page with history nothing Compare
Pushpaypushpay.com 39/100 1 security.txt (RFC 9116) nothing Compare
Multitracksmultitracks.com 35/100 1 Status page with history 1 HTTPS enforced with HSTS Compare
Tithe.lytithe.ly 35/100 1 Status page with history 1 Public pricing Compare
Worship Toolsworshiptools.com 35/100 1 security.txt (RFC 9116) 1 Named privacy contact Compare
Bible Appyouversion.com 30/100 1 Status page with history 2 Public pricing, Named privacy contact Compare
Breezebreezechms.com 26/100 1 Status page with history 2 Data location stated, Named privacy contact Compare
Churchdeskchurchdesk.com 17/100 1 Status page with history 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact Compare
Elvantoelvanto.com 17/100 1 Status page with history 3 Data location stated, HTTPS enforced with HSTS, Named privacy contact Compare
Faithlifefaithlife.com 17/100 1 Certifications named 3 Public pricing, HTTPS enforced with HSTS, 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.