Ministry privacy policy ↗

Privacy Policy & Browser Storage

Igniting Hope App · Updated November 7, 2026

Igniting Hope Ministries operates the Igniting Hope App and ignitinghope.app. This notice explains how information is used in the app and this website. Contact support@ignitinghope.app with privacy questions or requests. The ministry’s separate website has its own privacy policy.

Information you provide and use

Account information includes your app account identifier, email address, display name, and the sign-in information provided by your chosen Apple, Google, or email sign-in method. Apple may provide a private relay email address. We use this information to sign you in, maintain your account, and associate your app data and purchases with that account.

The app stores declarations, counts, progress, settings, reminders, and other features you choose to use. Some data stays in your browser or device. Optional cloud sync, backup, Circles, challenges, and community features send relevant data to our backend. Information shared in community features, including your display name and progress, may be visible to other participants. Avoid putting sensitive personal information into public or shared features.

Support requests collect the name, reply email, topic, platform, optional device details, and message you submit. Netlify processes the form and stores submissions; notifications are sent to our support mailbox. Do not submit passwords, card details, or private declaration content.

Cookies, local storage & your choices

Browser storage includes cookies, local storage, IndexedDB, and session storage. We use storage to keep you signed in, save app data for local use, remember settings, and support security and purchases. Blocking or clearing it can sign you out, reset preferences, and remove locally saved data that has not been synced or exported.

How browser storage is used
PurposeWhat it doesYour control
Sign-in & securityFirebase maintains your sign-in session. Firebase App Check uses Google reCAPTCHA to help protect backend requests from abuse.Sign out to end your app session. Browser settings control stored site data.
Saved app dataLocal declarations, progress, settings, cached content, and browser media support the app’s features.Use the app’s sync, export, and reset tools as appropriate. Export or sync important local data before clearing it.
Session preferencesRemember that you closed the download banner or this site’s privacy information.These dismissal preferences last for the current tab session.
Optional browser remindersOneSignal uses a browser subscription identifier and related storage to deliver reminders you enable.Enable or disable browser notifications in Settings → Notifications. Browser and operating system permissions also control delivery.
PurchasesRevenueCat and the payment provider support plan selection, checkout, purchase verification, and subscription management.Purchases require sign-in. Manage billing through the provider that billed you.

This notice is information about necessary app features, not a request to accept advertising cookies. Optional browser reminders remain off until you enable them. We do not include Google Analytics or advertising pixels in this app website. If optional analytics or advertising is introduced, this notice and the relevant consent controls must be updated before it runs.

Optional browser notifications

When you enable browser notifications, you allow the app to use OneSignal and share your app account identifier, browser subscription identifier, reminder schedule, and time zone to deliver your reminders. OneSignal also processes technical browser and network information needed for its service. We delay loading the notification SDK until reminders are enabled. A notification choice previously enabled in this browser is remembered for future visits.

You can withdraw this permission by turning off browser notifications in the app. This opts the browser subscription out, clears its active server reminder schedule, and withdraws SDK consent for further collection. Data already held by a service provider is not automatically deleted by disabling notifications; contact support for a deletion request. Revoking permission in your browser or operating system also stops delivery.

Native apps, diagnostics & recordings

On iPhone, iPad, Mac, and Android, Firebase Crashlytics collects crash reports, error logs, app and operating-system versions, device and installation identifiers, and technical diagnostic information to diagnose failures and improve reliability. When signed in, we associate crash reports with your Firebase account identifier; these reports are not treated as anonymous. Native diagnostic collection is enabled in production builds. Crashlytics keeps crash reports and associated identifiers for 90 days before beginning removal from live and backup systems, as described in Firebase’s privacy information.

Native OneSignal initializes to support notification services and collects installation and push identifiers, device/OS information, session activity, notification interactions, permission status, language, time zone, and network information. For signed-in native users, the app sends OneSignal the account ID, email, and display name. This differs from the website, where loading the OneSignal SDK waits until browser reminders are enabled. Disabling native notification delivery or denying operating-system permission does not itself delete a provider profile or disable all SDK diagnostics.

Service providers may derive a country or approximate location from an IP address. The app does not request GPS/location permission or collect precise GPS coordinates. We use technical and usage information for service operation, account management, reliability, notification delivery, security, and service analytics; this is separate from advertising tracking.

The microphone is used only when you choose to record an audio declaration. Your microphone recordings remain on your device or browser; the app does not automatically upload them to our servers or use them to train a voice model. A backup or export that you choose to share can contain recordings and other app data, and its destination is under your control. Device voices and Apple Personal Voice use the device’s supported speech features. Premium readback is a separate cloud service: selected text is sent by our backend to Fish Audio and generated audio may be cached on our backend and your device.

Personal declarations and NFPF journal/reflection text can reveal religious or philosophical beliefs or other sensitive information you choose to write. These features do not require you to disclose sensitive details. Cloud synchronization of private declarations/reflections is optional; when enabled, the content is associated with your account and protected as private synced data. Shared Circle/challenge content and progress have a different audience, as explained above.

Service providers & payments

We use Google Firebase for account sign-in, app data, backend services, and security; Netlify for website hosting and support forms; RevenueCat for purchase access and subscription information; and OneSignal for optional notifications. Web checkout uses Stripe through RevenueCat. Apple and Google handle purchases made through their stores. Payment card details are handled by the payment provider rather than stored in app profile records. Optional premium voice generation sends the text you select to our backend and Fish Audio to create the requested audio. RevenueCat receives purchase history and app account identifiers; native account linking can also provide your email, display name, and OneSignal identifier. Purchase and notification dashboards provide service analytics. We do not use these data for cross-app targeted advertising or sell personal information to data brokers.

Providers process information under their applicable service and privacy terms, including in the United States and other countries. Fish Audio may retain submitted text and use it to improve its services or models under its terms. We do not promise that Zero Data Retention or a model-training opt-out is enabled. Choose Device voice to avoid sending text to the premium voice provider, and avoid including private personal details in premium readback text. Read the relevant provider notices: Firebase, Netlify, RevenueCat, Stripe, and OneSignal, Fish Audio.

Why information is processed

We process information to provide the features you request, maintain accounts and purchase access, respond to support requests, protect the service, and meet applicable legal obligations. Where consent is required for an optional feature, we rely on your choice to enable it and provide a way to withdraw that choice. Depending on the circumstances and applicable law, other processing is necessary to perform our agreement with you or for legitimate interests such as security and service administration.

Security

App/backend connections use HTTPS and encrypted transport. Firebase Authentication identifies signed-in users, and backend authorization and Firestore security rules restrict private synced content to its owner. Purchase entitlements and protected voice requests are validated by backend services. Administrative access is limited to authorized operators and service providers. Community profile names and progress are visible as needed for leaderboards and group features. No storage or transmission system can be guaranteed completely secure; protect your device, account credentials, and exported backups.

Retention, deletion & privacy requests

Local data remains in your browser or device until changed, removed, or cleared. Account and synced data is retained while needed to provide the service, resolve support or billing issues, and meet applicable legal requirements. We do not currently apply a fixed automatic expiry to support requests or billing/security records. Support requests are retained to resolve and follow up on issues, and can be included in a verified deletion request. Transaction records are retained by billing providers and, where necessary, by us to administer purchases, resolve disputes, prevent fraud, and comply with applicable legal obligations. We assess those retention needs when responding to a deletion request rather than promising an unimplemented deletion deadline.

You can request account deletion through Settings → Advanced → Danger Zone → Delete Account. Deleting your account removes account-linked app data through our deletion process; provider-held data is reviewed separately as part of the deletion process, and legally required records may remain. We retain a minimal account-ID deletion marker to prevent stale signed-in devices from recreating deleted synced data and to track completion of provider deletion requests. Account deletion does not cancel a store or web subscription. Cancel billing with the provider that billed you.

Depending on your location, you may have rights to access, correct, delete, restrict, or obtain a copy of your personal information, object to certain processing, withdraw consent, or complain to a privacy regulator. Email support@ignitinghope.app or use our support form. We may need to verify your identity before acting. Parents and guardians can contact us about a child’s information or request its removal. To request deletion without reinstalling the app, follow the account and data deletion instructions. We do not charge for submitting a deletion request.

Changes & contact

We will update this notice when our app practices change and show the revision date above. Material changes that require a new choice will be presented before the affected optional feature is used. For questions, contact support@ignitinghope.app.