Privacy Policy
Effective date: August 19, 2026
Ministry ("the App") is a church scheduling companion for iPhone and Android. This policy explains what information the App processes, why it is needed, and the choices available to you.
Information stored on your device
The App stores information needed to remember your settings and personalize schedules:
- Member names you choose to follow
- Appearance and schedule-display preferences
- Notification timing preferences
- A random installation identifier used to keep your duties and notification settings separate from other devices
- Your selected calendar provider and the identifier of the Ministry calendar created for you
Information sent to the Ministry backend
The App uses a Supabase backend to operate schedules, duties, notifications, and support:
- Fetch church schedules, schedule types, events, and source-document links
- Register a random installation identifier, push-delivery token, device platform, followed member names, and reminder preferences
- Store personal duties and muted schedule reminders associated with the random installation identifier
- Submit bug reports containing the reporter name and description you choose to provide
- Record structured usage and operational telemetry as described below
The random installation identifier is generated by the App. It is not a hardware identifier and is not used for advertising or cross-app tracking.
Usage analytics and operational telemetry
Ministry uses a first-party telemetry system hosted in its Supabase backend to understand feature adoption and diagnose reliability problems. The App may record:
- A random installation identifier, a random app-session identifier, platform, app version, and build version
- Fixed event names and outcomes for actions such as opening the App, refreshing schedules, changing reminder preferences, syncing a calendar, registering for push notifications, and opening a notification
- Limited counts and measurements, such as schedule count, configured member count, selected calendar provider, operation duration, and standardized error category
- A snapshot of the member names configured on that installation when the list changes, so reports can be associated with the schedule configuration active at the time
If one installation follows multiple members, telemetry can show that the device was configured for those members. It does not identify which person was holding the device or performed an action.
Telemetry events do not include schedule topics, personal-duty titles or descriptions, Google account email addresses, push tokens, OAuth credentials, or raw error messages. Events may be queued briefly on the device while offline and uploaded in batches when a connection is available.
This information is used only to operate and improve Ministry, measure whether features work as intended, investigate failures, and compare reliability between app releases. It is not used for advertising, cross-app tracking, or sale.
Notifications
If you enable notifications, Ministry sends reminder messages through its Supabase backend and the Expo push service, which routes delivery through Apple Push Notification service or Firebase Cloud Messaging. Notification registration includes the push token, followed member names, and reminder preferences needed to determine which reminders to send. Invalid delivery tokens are removed when the push provider reports that the device is no longer registered.
Google Calendar data
Google Calendar connection is optional and starts only when you choose Google Calendar in the App.
Permissions requested
- Create and manage a dedicated Ministry calendar and the events Ministry creates inside it
- Read calendar-list metadata so the App can locate the Ministry calendar it previously created, including across your iPhone and Android devices
How Google data is used
Ministry uses schedule assignments already available in the App to create, update, and remove events in the dedicated Ministry calendar. The App does not read event contents from unrelated calendars and does not modify unrelated calendars. Calendar-list metadata for unrelated calendars is inspected only while locating the marked Ministry calendar and is not retained by the Ministry backend.
The selected Google account identifier and email address, together with the Ministry calendar identifier, are stored locally on your device so the App can reconnect to the correct account. Google OAuth access tokens are handled by the native Google Sign-In SDK and are used by the App to communicate directly with Google Calendar. The Ministry backend does not receive or store Google OAuth access or refresh tokens.
Ministry does not use Google user data for advertising, profiling, or sale, and does not transfer it to third parties except as necessary to provide the calendar-sync feature requested by you.
Ministry's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy , including the Limited Use requirements.
Apple Calendar
On iPhone, you may instead sync to Apple Calendar. Calendar access is used only to create and reconcile a dedicated Ministry calendar and its events. Ministry calendar data accessed through Apple's calendar framework is not sent to the Ministry backend.
Third-party service providers
Ministry uses the following providers only for the functions described in this policy:
- Supabase for backend data and server functions
- Expo for push-notification delivery infrastructure
- Apple Push Notification service and Firebase Cloud Messaging for device delivery
- Google Sign-In and Google Calendar API when you connect Google Calendar
Retention and deletion
- Local settings remain until you reset the App or remove it from your device.
- Deleting the App does not automatically delete an existing Ministry calendar or its events; you can delete that calendar in Apple Calendar or Google Calendar.
- You can revoke Google access at any time from your Google Account's third-party connection settings. Revocation prevents future Google Calendar sync.
- Operational telemetry is retained for up to 30 days. Usage telemetry and its associated member-configuration snapshots are retained for up to 180 days.
- Backend registration, duties, mutes, and bug reports are retained only as needed to operate, secure, and support the App.
To request deletion of backend information associated with your installation, email ministry.shigong@gmail.com. We may ask for limited details needed to identify the relevant records.
Security
Ministry uses encrypted network connections and access controls intended to limit backend data to the functions described above. No method of electronic storage or transmission is completely secure.
Children's privacy
The App is not directed to children under 13 and does not knowingly collect personal information directly from children.
Changes to this policy
This policy may be updated as the App changes. The effective date at the top of this page will be updated when material changes are published.
Contact
For privacy questions or requests, email ministry.shigong@gmail.com.