ChurchOps Privacy Policy

ChurchOps helps teams run operational workflows.

ChurchOps is used by church teams to manage staff access, schedules, board workflows, budgets, requests, reimbursements, time tracking, notifications, and optional external workflows. The app is available on iPhone and Mac.

What information ChurchOps may collect or store

• Account information such as name, email address, phone number, profile photo, and team membership.
• Staff and team records such as roles, departments, schedules, approvals, requests, reimbursements, and related workflow data created inside ChurchOps.
• Subscription and billing state needed to determine whether a team has active access.
• Device or app data needed to deliver notifications, protect the service, diagnose crashes, and keep the app functioning.
• Optional integration data when a team connects supported services such as Google Drive or Planning Center-style workflows.
• User-submitted files and attachments stored through the product, including documents, receipts, and profile images.

How ChurchOps uses information

• To authenticate users and link them to the correct team workspace.
• To store, synchronize, and display team operational data across supported devices.
• To deliver push notifications, inbox items, approvals, reminders, and workflow updates.
• To enforce subscription access and seat usage for the team plan.
• To troubleshoot product issues, monitor reliability, and improve service quality.
• To power optional connected workflows such as document syncing or external service handoffs that a team explicitly enables.

Third-party services and integrations

ChurchOps uses third-party providers to operate the app.

ChurchOps may share data with these providers only as needed to deliver the features a team uses.

YouTube data in Count and the Staff Portal

A church administrator may choose to connect the church’s own YouTube channel. ChurchOps uses YouTube API Services and requests read-only access to the selected channel and its YouTube Analytics reports. The administrator reviews the channel before activating the connection. This access does not permit ChurchOps to upload, edit, or delete videos or control a livestream.

We access and store the channel’s ID, name and handle; broadcast and video identifiers, titles, links and start/end times; and available aggregate viewing statistics, including current, average and peak concurrent viewers, video views, watch time and average view duration. We also store encrypted authorization credentials on our servers so the connection can refresh without repeated sign-in.

We use this data to display and refresh livestream reports, match broadcasts to church services, and show online viewing statistics alongside in-person attendance. Viewing statistics are not treated as a count of unique people or added automatically to in-person totals. Connection records and reports are kept within the connected church’s workspace and made available to its authorized staff. Guest counters cannot manage the connection or read stream history. Firebase and Google Cloud process and store this information for ChurchOps; we do not sell YouTube data or use it for advertising.

While connected, cached YouTube reports are periodically refreshed. Cached stream data that has not been refreshed within 29 days is scheduled for removal. Disconnecting immediately stops access through ChurchOps, removes the stored connection credentials and hides its reports; remaining cached reports and service links are queued for deletion. A church administrator can disconnect in Count’s YouTube settings or the Staff Portal’s Attendance setup. You can also revoke ChurchOps access from your Google Account permissions. For deletion requests or connection help, contact hello@church-ops.com.

ChurchOps’ use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including its Limited Use requirements. See also the Google Privacy Policy and YouTube Terms of Service.

How long data may be kept and what deletion means

ChurchOps keeps account and team data for as long as it is needed to operate the workspace, comply with legal obligations, resolve disputes, prevent abuse, or enforce agreements.

• Users can request account deletion in the app from Settings > Delete Account.
• When a standard user deletes their account, ChurchOps removes the Firebase Auth account and linked ChurchOps data that belongs to that user, including supported team-linked records tied to the account.
• If the last active team owner deletes their account, ChurchOps requires an additional confirmation because the workspace itself may also be permanently deleted.
• Some operational, billing, security, audit, or legal records may be retained for a limited period when reasonably necessary.
• Apple subscriptions are managed separately from account deletion and remain active until they are canceled through Apple account subscription management.

Security and service protection

ChurchOps uses access controls, authenticated backend services, app integrity tooling, and provider security features to help protect the product. No online service can promise absolute security, but ChurchOps takes reasonable steps to protect stored data and access.

Your options inside ChurchOps

• Update account profile information from inside the app.
• Delete your account from inside the app.
• Contact support for privacy, billing, or deletion questions.
• Manage Apple subscriptions through the in-app billing screen or Apple account subscription management.

Contact ChurchOps

For privacy questions, support requests, or deletion-related issues, contact hello@church-ops.com.