Manna Bible Privacy Policy

Last updated: August 25, 2026

Manna Bible is a Bible reading, devotional, study, plan, mood, reminder, and sync application. This policy explains what information we collect, how we use and share it, which third-party services help us operate and promote the app, and how you can contact us.

Services Currently Integrated

The app uses Firebase Analytics, Firebase Crashlytics, Firebase Remote Config, Firebase Cloud Messaging, and Google Sign-In. These services are provided by Google and Firebase and help us understand app usage, diagnose errors, deliver configuration, send notifications when enabled, and support account sign-in.

The Android app also includes TopOn/TU advertising mediation, Meta Audience Network, TopOn ADX, Google AdMob, and related advertising diagnostics and fraud-prevention components. These services help request and display ads, measure ad delivery and interactions, prevent invalid activity, and diagnose advertising errors. The network that fills an ad request depends on the active mediation configuration and region.

Manna Bible also sends first-party advertising telemetry to our encrypted backend so we can operate and audit placements. This telemetry can include an app-generated advertising installation identifier, app/build and operating-system versions, session/request/event identifiers, placement and screen categories, ad-network and waterfall identifiers, request, bid, load, impression, click, close, refresh and error outcomes, estimated eCPM, publisher revenue, currency, and revenue precision. It does not include your Manna Bible account ID, Bible passages, searches, prayers, notes, mood values, or other saved content.

Separately, after consent, Firebase Analytics may receive privacy-bounded aggregate advertising lifecycle and revenue events, including advertising SDK initialization, request, load, display, click, close, automatic refresh, and revenue stages. These Firebase advertising events may include the lifecycle stage, ad format, a fixed placement or screen category, ad source, estimated eCPM, publisher revenue, currency, and revenue precision. Manna Bible does not attach an ad request ID, show ID, its first-party advertising installation identifier or another app-generated device identifier, account identifiers, Bible or devotional content, searches, prayers, notes, mood data, or other user content to these events. The Firebase SDK may still process its own app-instance or installation identifiers and standard app, device, and network context as otherwise described in this policy.

Unexpected advertising SDK initialization, callback, or telemetry-integration exceptions may be reported to Firebase Crashlytics as non-fatal diagnostic reports. Normal no-fill or other expected ad-delivery outcomes are recorded as lifecycle analytics rather than app crashes. Manna Bible does not attach ad request or show IDs, its first-party advertising installation identifier, account identifiers, or user content to these non-fatal reports. Crashlytics may process its own crash-grouping or app-instance identifiers and the standard technical context described below.

Separately, the app includes Meta App Events for limited measurement and attribution of advertisements that promote Manna Bible. The Meta acquisition-measurement integration is distinct from Meta Audience Network, which may supply ads shown inside the app.

Information We Collect

• If you choose to sign in with Google and give consent through the Google Sign-In flow, we may receive basic profile information from your Google account, such as your Google account identifier, email address, display name, and profile photo URL. We do not receive or store your Google password.
• App and device information, such as app version, package name, language, device model, operating system version, country or region derived from technical signals, Firebase installation ID or app instance identifier, notification permission status, and last active time.
• Usage and analytics information through Firebase Analytics, such as app launches, screen views, feature usage, session activity, in-app events, privacy-bounded aggregate advertising lifecycle and revenue events, approximate region, and device and app information.
• Crash and diagnostic information through Firebase Crashlytics, such as crash stack traces, non-fatal advertising-integration exception reports, error logs, crash timestamps, device state, app version, operating system version, and identifiers used to group crashes and diagnose reliability issues.
• Remote configuration information through Firebase Remote Config, such as installation or app instance identifiers, app version, language, and configuration fetch or assignment data needed to deliver app settings and experiments.
• Advertising information processed by TopOn and an enabled ad network, such as an ad request, impression, click or other ad interaction, app and SDK version, device and operating-system information, network context, IP-derived approximate location, and SDK diagnostic or fraud-prevention signals.
• First-party advertising operations data sent to our backend, including an app-generated advertising installation identifier, session/request/event identifiers, placement and screen categories, network and waterfall identifiers, request, bid, load, display, click, close and refresh outcomes, bounded error details, estimated eCPM, publisher revenue, currency, and precision.
• Limited Meta attribution information after you agree to the in-app privacy notice, including a Meta install-attribution ping and, for a permitted App Event, the event name and time together with standard app and device context needed by the Meta SDK. The only App Events we permit are app activation and, where our backend confirms a genuinely new account registration, completion of that registration.
• User content and activity that you choose to save, submit, or sync, such as bookmarks, notes, highlights, reading position, plan progress, quiz progress, mood choices and history, prayers, Amen or other reactions, achievements, reminders, and settings.
• Push notification information if notifications are enabled, such as Firebase Cloud Messaging tokens used to deliver reminders or app messages to a specific app installation.

Some user-created content, such as prayers, notes, highlights, mood history, or devotional activity, may reflect personal or religious interests. We use this information only to provide app features selected by the user, such as sync, history, reminders, and account recovery.

Sensitive Content Is Not Sent To Meta

We do not send Meta the text or identity of Bible verses or passages you read, prayers, notes, highlights, bookmarks, search terms, mood entries, devotional or reading-plan details, or a field that describes or classifies your religion or religious preference. We also do not add your Manna Bible account ID, backend user ID, Firebase UID, Google account identifier, email address, display name, or other account identifier to Meta App Events.

Meta receives the identity of Manna Bible and standard technical context needed to process an allowed attribution event. We do not attach content-level, account-level, or religious-profile parameters to that event.

Emotional Well-Being And Faith-Related Information

Your mood choices and mood history may reflect your emotional state or well-being and may be treated as sensitive or health-related information in some places. Manna Bible uses a selected mood only to provide the mood-based Bible verse experience you request, maintain your optional mood history, and support optional sync through our first-party backend. The mood feature does not diagnose, monitor, prevent, or treat a medical or mental-health condition and is not a substitute for professional care.

Prayer records, Amen or other faith-related reactions, devotional activity, and Bible reading or plan progress may reveal or allow someone to infer religious beliefs or practices. These items are stored locally to provide the features you choose. When you sign in and use sync, selected account-linked records may be sent to our first-party backend so they can be restored across your devices. When you use an online reaction or engagement feature, the related first-party event may also be sent to our backend to operate the feature and maintain aggregate counts.

We never provide an underlying mood choice or history, prayer or note text, Bible passage or search term, Amen target or content, or religious-belief classification to Meta App Events, TopOn, Meta Audience Network, TopOn ADX, Google AdMob, or another advertising SDK or network. Firebase Analytics may receive generic fixed product events and privacy-bounded aggregate advertising lifecycle or revenue events, but not the underlying mood value, prayer text, Bible reference, search term, account ID, or other sensitive content.

How We Use Information

• To operate the app and provide local Bible reading, devotionals, plans, quizzes, reminders, and sync.
• To provide a mood-based verse experience and optional mood history or sync at your request, not to diagnose, monitor, or treat a health condition.
• To authenticate your account through Google Sign-In and associate your devices with your account so synced data can be available across devices.
• To send app notifications when enabled on your device and to manage notification delivery.
• To measure app performance, understand aggregate usage trends, identify bugs, and improve app reliability.
• To deliver app settings, feature flags, and content configuration through Firebase Remote Config.
• To display and measure non-personalized advertising, prevent advertising fraud, and diagnose advertising delivery problems.
• To attribute an app activation or a confirmed new registration to an advertisement for Manna Bible and evaluate aggregate campaign performance.
• To protect accounts, detect service issues, prevent abuse, and maintain security.

Meta App Events And Advertising Attribution

• Meta initialization, the install-attribution ping, and manual App Event reporting occur only after you tap Agree in the app's privacy notice. If you choose Not Now, the app closes and these SDKs are not initialized during that session.
• Automatic Meta app-event logging is disabled. Manna Bible manually allows only an app-activation event and a completed-registration event after the backend confirms a genuinely new account was created. A normal login by a returning user is not reported as a registration.
• Meta Advertiser ID collection is disabled by default. The production Android manifest removes the Android Advertising ID permission and all Android AdServices permissions, while retaining the signature-level Play Install Referrer binding solely to help match an installation to its acquisition source after privacy consent.
• These restrictions do not mean Meta receives no technical data. Meta may still process install-referrer information, event time, app identity, app and SDK version, device or operating-system context, IP address or IP-derived approximate location, and its own SDK diagnostic or app-scoped signals under its terms.

Push Notification Tokens

Firebase Cloud Messaging tokens identify an app installation for message delivery. They are not treated as a user identity. If you later sign in with Google, the current device can be linked to your account so notifications and sync work correctly. Different phones have different tokens, even when signed in to the same Google account.

Third-Party Services

We use Google, Firebase, TopOn, Meta, and related service providers to operate, measure, monetize, and promote the app. These providers may process app, device, network, account, analytics, advertising, diagnostic, and configuration data as described in their own privacy and data-processing materials and subject to the restrictions described in this policy.

• Firebase Analytics helps us understand aggregate app usage, feature performance, and privacy-bounded advertising lifecycle and revenue trends.
• Firebase Crashlytics helps us collect crash reports and unexpected non-fatal integration exceptions and diagnose reliability issues.
• Firebase Remote Config helps us deliver app configuration, feature flags, and experiments.
• Firebase Cloud Messaging helps us deliver push notifications to app installations when notifications are enabled.
• Google Sign-In helps users sign in with a Google account and share basic profile information with the app after consent.
• TopOn/TU mediates MREC and interstitial ads, and may use Meta Audience Network, TopOn ADX, or Google AdMob Partner Bidding to fill an ad request. Related components support delivery diagnostics and fraud prevention.
• Meta App Events helps measure and attribute advertisements promoting Manna Bible using the limited event configuration described above.

Advertising

The Android app includes third-party advertising SDKs and may show MREC and interstitial ads supplied through TopOn mediation, including Meta Audience Network, TopOn ADX, or Google AdMob when enabled for a region. Advertising SDKs are initialized only after the in-app privacy agreement. The current production configuration requests non-personalized advertising; agreeing to the app privacy notice is not treated as consent to personalized advertising.

The production app does not request the Android Advertising ID permission, does not enumerate or upload the list of apps installed on your device, and does not include TopOn's optional Tramini material-collection plugin. Advertising providers may nevertheless process app, device, network, IP-derived approximate location, ad-delivery, ad-interaction, diagnostic, and fraud-prevention information. We do not pass them the Bible passages, prayers, notes, search terms, mood values, account profile data, or other first-party religious-content fields described above.

After consent, Firebase Analytics receives the aggregate advertising lifecycle and revenue fields described above, and Firebase Crashlytics may receive unexpected advertising-integration exceptions as non-fatal diagnostic reports. Manna Bible does not attach per-request or per-show identifiers, its first-party advertising installation identifier, account identifiers, or user content to those Firebase advertising events or reports.

Sharing

We do not sell personal information. We use service providers such as Google, Firebase, our backend hosting providers, TopOn, Meta, AdMob, and the advertising networks enabled in the mediation configuration to operate authentication, notifications, analytics, crash reporting, remote configuration, storage, advertising, campaign attribution, fraud prevention, and app services. These providers process data as needed to provide their services. We may also disclose information when required by law, to protect users or the service, or as part of a business transaction subject to appropriate safeguards.

Your Choices

• You may use many app features without signing in. If you sign in with Google, you can sign out in the app at any time.
• You can manage notification permission in your device settings.
• The production advertising configuration requests non-personalized ads and does not request the Android Advertising ID permission. The app currently does not offer a separate personalized-ad toggle because personalized advertising is not enabled.
• You can choose Not Now in the initial privacy notice; the app closes, Firebase Analytics transmission and app-owned event collection remain disabled, and the advertising and attribution SDKs are not initialized during that session. While Crashlytics transmission is disabled, Firebase may keep crash information only on your device. Before collection is enabled after you later tap Agree, the app keeps Crashlytics collection disabled, checks for pending reports, and queues reports cached before consent for deletion rather than opting them into transmission. Clearing the app's storage or uninstalling it stops future app-side collection from that installation.
• You can request account and synced data deletion as described below.

Security

We use reasonable technical and organizational measures to protect information, including encrypted transmission where supported. However, no method of transmission or storage is completely secure.

Data Retention

We keep account and sync data while your account is active or as needed to operate the app. Push tokens may be replaced or removed when they become stale, when you sign out, or when you delete your account. Unsent first-party advertising telemetry is kept on the device for no more than 30 days and is removed sooner when queue limits apply; received advertising telemetry is retained for a limited operational reporting period. Analytics, crash, diagnostic, remote-configuration, advertising, fraud-prevention, and attribution data may be retained by Firebase, TopOn, Meta, AdMob, and enabled advertising providers according to their configured retention periods and service requirements.

Account Deletion

You can request deletion in the app through Me > Settings > Delete Account and Data. If you cannot access the app, contact us at sd.wang.qq@gmail.com. Account deletion removes or de-identifies account-linked data on our backend as described on the account deletion page. It does not automatically erase local data left on your device or de-identified, aggregate, diagnostic, advertising, or attribution records retained by independent service providers under their own policies.

International Processing

Our service providers may process information in countries or regions outside where you live. We rely on these providers to protect information according to their security, privacy, and data processing commitments.

Children

The app is intended for a general audience and is not directed to children under 13. If you believe a child provided personal information, contact us so we can review and delete it where required.

Changes to This Policy

We may update this policy when the app, third-party services, advertising status, or legal requirements change. The updated version will show a new last updated date.

Contact

For privacy questions, contact sd.wang.qq@gmail.com.