Privacy Policy
Last updated November 10, 2026
Churchism is church operations software used by a congregation’s staff and volunteers (scheduling, people records, kids check-in, giving import, music charts, and related tools). This policy describes how that information is handled.
Who this applies to
Churchism is used by church staff, volunteers, and (where a church enables it) guests who submit a welcome or connect card. It is not a consumer social network. Each church’s data is stored for that church only.
Information we store
- Account details: name, email, role, hashed password, optional authenticator (2FA) secrets, emailed two-factor codes, and sign-in activity. Sign-in activity includes IP address, approximate location (country, region, and city from the hosting provider), device type (website, iPhone app, or Android app), and related security events so church admins can investigate unusual access. This is kept for 90 days.
- People and household records the church enters (names, contact info, membership status, notes, serving assignments).
- Kids check-in information, including pickup codes and optional medical notes the church records.
- Giving import data the church uploads (for example a Subsplash CSV) and reimbursement requests with receipts.
- Songs, charts, and attachments the church stores in Google Drive through Churchism.
- Calendar event requests and department schedules, including invite responses.
- iOS and Android push tokens so we can send serving invites and notification badges the user has allowed.
- Per-user Music Stand chart markups saved to that person’s account.
- Optional Music Stand page-turn gestures use the front camera on the phone, iPad, or browser. Face movement is processed on the device to turn pages. Face images and landmarks are not stored or uploaded.
How we use it
We use this information to operate the church’s workspace: sign-in, scheduling, notifications, reporting the church enables, and support. We do not sell personal information. We do not use it for advertising.
Sharing
Church staff with permission can see records inside their own church. Service providers that host the app (database, email delivery, Google Drive / Calendar when the church connects them, Apple Push Notification service, and Firebase Cloud Messaging) process data only to provide those services. Demo accounts used for product previews and App Store or Google Play review are isolated from a live congregation’s people and giving records.
Retention and access
A church’s administrators control their congregation’s records. You can ask that church to correct or delete your volunteer or member information. Account holders can sign out at any time. Push notifications can be disabled in iOS or Android system settings.
In the iOS or Android app, More → Settings includes Delete account. The same option is in website Settings and on the delete account page. That removes your Churchism login, sessions, push tokens, chart markups, and other data tied to that login. People records, giving, schedules, and kids check-in stay with the church that entered them. You can also email developer@tpchollister.org to request deletion. Sign-in security events are kept for 90 days, with the user link removed after the login is deleted.
Security
Passwords are stored hashed. Sessions use signed tokens. Optional two-factor authentication is available. Access inside a church is permission-based (for example giving reports are limited to roles that church assigns). We record sign-in IP, approximate location, and device type so church admins can investigate unusual access. We do not sell this data.
Children
Kids check-in is operated by the church for children in their ministries. Churchism does not offer accounts directly to children.
Contact
Privacy questions: developer@tpchollister.org