Divine Word

Privacy Policy

Last updated: September 11, 2026

Divine Word is a Bible reading app for iPhone and Android, developed by Moodlr. This policy explains what the app collects, which services receive it, why, and when each of them is switched on or off.

In short

There is no account. Your notes, favourite verses, highlights and reading progress stay on your device.
On iPhone, if you choose “Ask App Not to Track”, nothing the app collects is used to track you. Session analytics, Firebase Analytics and Meta app events are not started, ads are not personalised, and the app does not ask you about data use again.
Divine Word does not set or read cookies, and it has no WebView or in-app browser.
The app shows ads from Google AdMob. That is how it stays free.

What stays on your device

Divine Word has no accounts and no sign-in. What you create or change in the app is stored only on your device: notes, favourite verses, highlights, reading progress and your last position, the app’s language and settings, the Bible translations you download, and your privacy choices. We do not receive a copy of any of it. Deleting the app deletes it.

Tracking and your choices

On iPhone

The first time you open Divine Word, Apple’s App Tracking Transparency prompt asks whether the app may track you. That answer comes first and decides everything below.

If you choose “Ask App Not to Track” — or tracking is restricted on your device, or the prompt could not be shown — the app records your choice as “essential only” and shows no further privacy question. Microsoft Clarity, Firebase Analytics and the Meta SDK are not started, no advertising identifier is collected, and every ad request asks Google for non-personalised ads.
If you choose “Allow”, the app then shows its privacy sheet, where you can accept everything, turn analytics or personalised ads off separately, or choose “Essential only”. The sheet can only narrow what you allowed, never widen it.
If you turn tracking off later in Settings › Privacy & Security › Tracking, the app switches Clarity, Firebase Analytics, Meta app events and ad personalisation off the next time it starts or comes back to the screen. If you turn tracking back on, your stored choices apply again — and if you had first chosen “Ask App Not to Track”, the stored choice is “essential only”.

On Android

Android has no tracking prompt. The privacy sheet shown on first launch decides whether analytics and personalised ads are used. Choosing “Essential only” keeps Clarity and the Meta SDK from starting, switches Firebase Analytics off, and limits ads to non-personalised ones.

The app has no screen for changing these answers afterwards. Deleting and reinstalling the app, or clearing its data, brings the questions back.

Services the app uses

Google AdMob — ads

What it receives: Ad requests from your device, which reach Google with your IP address and information about the device and the app. On iPhone the advertising identifier is available only if you chose “Allow” at the tracking prompt.
Why: To choose, show and measure the ads that keep Divine Word free. Ads are limited to content rated for general audiences.
When it is on: Always, because the app shows ads. Requests ask for non-personalised ads unless personalised ads are allowed: on iPhone that takes “Allow” at the tracking prompt and personalised ads accepted in the sheet; on Android, personalised ads accepted in the sheet. Some ad placements always ask for non-personalised ads.
Provider’s policy: How Google uses information from apps that use its services

Google Firebase Analytics — usage statistics

What it receives: Events about how the app is used: the app and its home screen being opened, the button that starts or continues reading, ads being shown, tapped, closed, failing to load or granting a reward, and interactions with the card that suggests our other apps. The Firebase SDK also records some events by itself, such as the first time the app is opened and the start of each session, and adds information about the device and the app to every event.
Why: To understand which parts of the app are used and whether its ads work.
When it is on: On iPhone, only if you chose “Allow” at the tracking prompt and accepted analytics in the sheet; otherwise collection stays switched off. On Android, it follows your analytics choice in the sheet. The consent signals that let Google use this data for advertising are sent as granted only when personalised ads are allowed as well.
Provider’s policy: Privacy and security in Firebase

Meta (Facebook SDK) — app events

What it receives: The same app events listed for Firebase Analytics, and the app events the Meta SDK records by itself, such as the app being opened. The advertising identifier is included only when personalised ads are allowed — on iPhone, that also takes “Allow” at the tracking prompt.
Why: To measure how the app is used and, where you allowed it, to measure advertising on Meta’s platforms.
When it is on: The SDK is built into the app with automatic event logging and advertising-identifier collection switched off, and it is only started after your answers: on iPhone, “Allow” at the tracking prompt and analytics accepted in the sheet; on Android, analytics accepted in the sheet. Otherwise it is never started.
Provider’s policy: Meta Privacy Policy

Microsoft Clarity — session analytics

What it receives: A record of how the app is used during a session — screens viewed, taps and scrolls, and what was shown on screen — with information about the device and the app’s version, language and platform.
Why: To find screens that are confusing or broken.
When it is on: On iPhone, only if you chose “Allow” at the tracking prompt and accepted analytics in the sheet. On Android, only if you accepted analytics in the sheet. Otherwise it is never started, and if you turn tracking off later, recording is paused.
Provider’s policy: Microsoft Privacy Statement

Google Firebase Remote Config — app settings

What it receives: A request from your device to download the app’s settings, which reaches Google with your IP address and an identifier Firebase uses to deliver the settings to this installation.
Why: To adjust the app without an update — for example, which of our other apps it may suggest, and how often.
When it is on: At every launch, whatever you chose, because the app needs its settings. The app does not use it to analyse what you do or to target ads.
Provider’s policy: Privacy and security in Firebase

Google Firebase (Cloud Firestore and Cloud Storage) — Bible text

What it receives: Requests for the Bible translations and chapters you open that are not yet on your device, which reach Google with your IP address.
Why: To deliver the Bible text.
When it is on: Only when text has to be downloaded. The app only reads from these services: your notes, your reading and your settings are never stored on them.
Provider’s policy: Privacy and security in Firebase

Apple App Tracking Transparency

What it receives: Nothing. The app uses Apple’s framework to show the tracking prompt on iPhone and to read your answer.
Why: So that your answer decides whether anything above may be used for tracking.

Cookies and web content

Divine Word does not set or read cookies, and it does not use cookies to track you. It has no WebView and no in-app browser: links in the app, including the link to this policy, open in your device’s browser. The only web-based content displayed inside the app is ads, which Google’s SDK draws under Google’s policies.

This page sets no cookies and loads no scripts, fonts or other resources.

Your data and requests

What is stored on your device is removed when you delete the app. What the services above receive is handled by those companies under their own policies, linked above. For any question or request about your data, write to moodlrinc@gmail.com.

Changes to this policy

When the app changes what it collects or how it uses it, this page is updated and the date at the top changes.