Privacy Policy

Information we handle

We handle account and profile information such as your name, email, contact details, photo, household connections, and church roles. You or authorized church staff may provide this information. Household and ministry records may include information about children supplied by their parents, guardians, or authorized staff.

We also handle content and activity you submit: posts, comments, photos, files, group participation, volunteer assignments, availability, event responses, facility requests, and notification preferences. This information may reveal your religious affiliation or other personal details. Share only information appropriate for the intended audience.

Technical information can include session identifiers, device and browser details, push-notification tokens, delivery records, and security or error logs. Hosting and communication providers may process IP addresses and related connection information to operate and protect the service.

How we use and share information

We use information to sign you in, show content to its intended audience, coordinate church activities, send requested notifications, provide support, prevent misuse, and maintain the app. Authorized church leaders and administrators can access information needed for their responsibilities. Other members see information according to the app's permissions and visibility settings; a private church workspace is not a promise that every item is visible only to you.

Service providers process information needed to deliver these features. These include Supabase for authentication, database and file storage; Vercel for hosting; configured email providers such as Resend or Amazon SES; Twilio and carriers for text messages; push-notification services; and Sentry for error monitoring. Providers may process information outside your state or country.

We do not sell personal information. We do not use or share it for marketing, promotions, or profiling without both your specific consent and church leadership's approval. Service providers receive information for operating and supporting church services. We may disclose information when required by law or when necessary to address abuse, fraud, or threats to safety.

YouTube and sermon clips

The app uses YouTube API Services to show church videos and playlists. When an authorized channel manager connects the church's Google account, the server stores authorization tokens and accesses channel, video, playlist, publishing-status, and caption information needed to prepare and publish church clips. We do not ask for or store the Google account's password.

For enabled Sunday automation, the public service URL and a clipping prompt go to Opus. Opus processes the selected sermon range and hosts generated clips and previews. Timestamped service captions go to OpenAI to locate the sermon boundaries. The app retains source and project identifiers, selected ranges, staff review choices, titles, and processing or publication status. It does not save the full caption transcript in its intake records.

Staff choose which clips to publish. Opus uploads approved clips to the connected YouTube channel; the Dearing server applies the approved title, keeps the description empty, and adds the video to the church playlist. Published videos are public and may be viewed outside the church app. Unpublished reviews are limited to authorized staff.

A channel manager can revoke Dearing's Google access using the link below and can contact the church to request removal of stored integration information. Revoking access stops authorized Google operations; it does not itself remove videos already published on YouTube or copies held in Opus. Those can also be managed through the respective services.

AI-assisted features

When an AI-assisted feature is enabled, the app sends the request and the relevant information needed for that feature to OpenAI. For the church assistant, this can include your message and permitted church context. For sermon detection, it includes the public service's timestamped captions. The app may retain requests, responses, or action history for its assistant workflow; sermon intake retains its selected range and a short explanation.

Sermon detection requests ask OpenAI not to store the response as a retrievable API record. This does not mean the provider keeps no operational or abuse-prevention records. Provider retention and processing are governed by the applicable service terms. The app does not use Google user data to train a general-purpose AI model. AI suggestions can be wrong and should be reviewed where the app asks for approval.

Cookies, device permissions, and outside services

The web app uses cookies and local browser storage for sign-in, security, preferences, and application behavior. The native app stores session information and app settings on your device. You can clear browser or app data, but doing so may sign you out or reset preferences. Camera, photo-library, and notification permissions are used for the features you choose and can be changed in your device settings.

YouTube players and other external services may receive device or network information when you load or interact with them, and may use their own cookies or show advertising. Their privacy policies apply to their services. Giving links take you to an outside payment provider; do not post payment-card information in the church app.

Notifications and the SMS policy

You can manage available email, push, and text-notification preferences in the app. Optional text messages require separate consent. Reply STOP to stop text messages or HELP for assistance. Our SMS Privacy Policy and SMS Terms and Conditions remain applicable; the full app policy does not weaken their restrictions on sharing mobile numbers or SMS consent.

Retention, security, and your choices

We retain information needed for church operations, your account and saved content, support, security, and applicable legal obligations. Retention varies by record type. Opus clip availability and external providers' records follow their own retention settings and terms. Removing information from the app may not immediately remove backup copies or information already shared with others.

We use sign-in, role-based access, and encrypted network connections to help protect information. No online service can guarantee complete security. Protect your credentials and contact the church if you suspect unauthorized access.

You may ask the church to review or correct your information, provide a copy where applicable, remove content or integration data, or close your account. We may verify your identity or authority first. Some records may need to be retained for legitimate church administration or legal obligations; we will explain relevant limits when responding. For a child's information, a parent or guardian can contact the church. Do not send passwords or access tokens with a request.

Policy updates and contact

We will post changes on this page with an updated date and provide notice of significant changes. A policy update does not replace consent required for a new use of your information. Contact the church office using the details below with privacy questions or requests.

Help and contact

Contact the Dearing Christian Church office to ask a privacy question or request access, correction, account closure, or removal of stored integration information.