OneBibleVerse — Privacy Policy

Last updated: May 8, 2026 App: OneBibleVerse — Catholic Study Bible reader Publisher: OneBibleVerse Dev (the “app”, “we”, “us”) Contact: doankhanh12@gmail.com

OneBibleVerse is designed to be a private, offline‑first Bible reader. We do not require an account, and the default install runs no crash‑reporting SDK and no analytics SDK — both are strictly opt‑in via Settings → “Help us improve”.

The free tier of the app shows a single banner advertisement above the bottom navigation bar after the first week. To remove that advertisement (and to support our work) you can subscribe via the in‑app purchase. Both the ad and the subscription touch a small amount of additional data, listed below.

This document explains the data the app touches in order to function, and the rights you have over it.

1. What we collect

1.1 Data stored only on your device

All of the following stays on your phone or tablet, in private app storage owned by your operating system. We never copy it off your device unless you explicitly export it via the Backup & restore feature.

Type of data	What it contains	Why we keep it
Reading position	Last book, chapter and verse you opened	So you can resume reading
Highlights	Verse references and color	Personal study
Bookmarks	Verse references and an optional label	Personal study
Notes	Verse references and the note text you write	Personal study
Journal pages	Verse references, your hand‑drawn strokes and stickers	Bible journaling
Reading plans	The plan you started, day completed, streak counter	Habit tracking
Memorize cards	Verses you’re memorizing and your spaced‑repetition history	Habit tracking
Settings	Font, theme, notification time, chosen Bible translation, UI language	App preferences

The app uses an on‑device SQLite database to hold this information. You can wipe it at any time by uninstalling the app or by using Settings → Backup & restore → Reset all user data.

1.2 Data we do not collect

We do not collect any of the following, ever:

Your name, email address, phone number, or any identifier you would recognise as “you”
Your contacts, photos, microphone or camera
Your precise or coarse location
Crash logs, device fingerprints, advertising identifiers, or behavioural analytics
Any “telemetry” of which verses you read or how often you open the app

1.3 Data Google AdMob handles (free‑tier users only)

If you are on the free tier and the 7‑day trial has elapsed, a single banner advertisement is loaded by Google AdMob at the bottom of the in‑app navigation. AdMob is a Google service governed by the Google Privacy Policy.

For each ad request, AdMob receives:

Your device IP address (as any web request does)
A non‑permanent advertising identifier (IDFA on iOS, Advertising ID on Android) only if you grant the App Tracking Transparency prompt on iOS or have not opted out of personalised ads on Android. If you decline, AdMob serves a non‑personalised ad — based only on the screen, language and country, with no identifier shared.
The size of the ad slot and a generic content‑rating signal we pass (we always tag our ads as safe for all audiences).

AdMob may use this data to select an ad and to count impressions and clicks. We never see the underlying advertising identifier.

If you would prefer to see no ads at all:

Subscribe, which removes the banner immediately, or
On Android: open the system Settings → Privacy → Ads → reset or delete your advertising ID, or
On iOS: open Settings → Privacy & Security → Tracking and turn off “Allow apps to request to track”, then decline our ATT prompt.

1.4 Data the in‑app purchase handles

Subscriptions are processed by the App Store (iOS) or Google Play Billing (Android). We never see, store or transmit your payment information — only the platform receives it. The platform returns to us a transaction receipt that confirms the subscription is active and tells us when it next renews; we cache that locally so the app knows whether to show ads.

To detect that the 7‑day free trial has already been spent on this account when the app is uninstalled and reinstalled, we write a single timestamp (the ISO date of first install) into the iOS Keychain or the Android EncryptedSharedPreferences bucket that is auto‑backed up to Google Drive on the same Google account. This timestamp is private to the app and never leaves the keychain / backup.

1.5 Data the opt‑in “Help us improve” toggles handle

Settings → Help us improve exposes two independent switches that default to off. Toggling either on only takes effect for new sessions / new screens after the change.

Crash reports — when on, an unhandled exception triggers a stack‑trace upload to Sentry, our error‑tracking provider (sentry.io). The upload contains: the stack trace, the route the user was on, the app version, the device model + OS version, and a short trail of recent navigations (“breadcrumbs”). It does not contain: your name, email, IP address (Sentry redacts on receipt and we explicitly disable client‑side IP attachment), or the contents of your notes / journal / highlights / bookmarks. Sentry’s data policy is at https://sentry.io/privacy/.

Anonymous analytics — when on, page‑view counts are sent to Plausible Analytics (plausible.io), a cookieless, GDPR‑friendly analytics provider. The Plausible server hashes your IP + user agent against a daily‑rotating salt to derive an anonymous visitor hash — cross‑day visits are not linkable. We see counts per screen, nothing identifying you. Plausible’s data policy is at https://plausible.io/data-policy.

1.6 Data the operating system handles

A few features rely on the operating system, which has its own privacy policy:

Local notifications — the daily verse‑of‑the‑day reminder is scheduled by your OS. The reminder text never leaves your device.
Text‑to‑speech (TTS) — narration is synthesised by your OS voice engine (Apple’s on‑device voices on iOS, Google or Samsung TTS on Android). On some devices, OS TTS may upload the text being spoken to the OS vendor. This is an OS choice, not something we control. To use a fully on‑device voice, install one from your system settings (the app links you there if a network voice is in use).
Sharing — when you tap Share, your OS share sheet decides which apps appear and what is sent. We pass plain text or a PNG to the share sheet and nothing else.
Backup files — when you export a backup, the file is saved to a location you choose. If that location is iCloud Drive, Google Drive or another cloud folder, the cloud provider may sync it.

2. Network requests we make

The app is offline‑first. The Bible text, commentary, hymns, catechism and saint calendar all ship inside the app and work with no internet connection.

The app only makes a network request when one of the following features is used:

Feature	Endpoint	What is sent	What is received
Daily Mass readings (English)	`universalis.com`	The date you are viewing	The day’s readings as HTML
Daily Mass readings (Vietnamese)	`ktcgkpv.org`	The date you are viewing	The day’s readings as HTML
Daily Mass readings (French)	`aelf.org`	The date you are viewing	The day’s readings as JSON
Holy Land map (production builds)	`api.maptiler.com`	The map tiles your viewport needs	Vector / raster tiles
Holy Land map (debug / fallback)	`tile.openstreetmap.org`	The map tiles your viewport needs	Raster tiles
Reader fonts (first launch)	`fonts.googleapis.com`	The font filename	The font file (cached after)

These endpoints will see your IP address (as any web request does) and the date or tile coordinates you requested. They do not receive any other identifier from us. We do not log these requests ourselves.

You can keep the app fully offline by:

Disabling Daily Mass readings in Settings
Disabling the Holy Land map screen (don’t open it)
Choosing Serif (system) or Sans (system) for the reader font, which avoids Google Fonts entirely

3. Children’s privacy

OneBibleVerse is intended for all ages and is safe for children. Because we do not collect any personal information at all, we do not knowingly collect personal information from children under 13 (under 16 in the EEA / UK).

The app contains no advertising, no in‑app social features, no in‑app purchases, and no links to user‑generated content.

4. Your rights

Because we do not store your data on a server, most of the rights that data‑protection laws (GDPR, CCPA, LGPD, PDPA) grant you are already satisfied by the design of the app:

Right of access — every byte of your data is in the app on your device. Backup & restore exports it as a single file.
Right to erasure — uninstalling the app, or Settings → Backup & restore → Reset all user data, deletes everything.
Right to portability — backups are an unencrypted, documented SQLite snapshot you can read, migrate or import into another copy of the app.
Right to object / restrict — you can disable Daily Mass readings, the map, Google Fonts, notifications and TTS individually in Settings.

If you have any other request, write to doankhanh12@gmail.com.

5. App Store / Play Store disclosures

For the Apple App Store privacy nutrition label:

For users on the paid (subscribed) tier, our declaration is “Data Not Collected” in every category — no ads load, no identifiers leave the device.
For users on the free tier after the 7‑day trial, AdMob collects under category “Identifiers — Device ID” linked to Third‑Party Advertising, only when the user grants the ATT prompt. Other categories remain “Data Not Collected”.

For the Google Play Data Safety form:

Data collected — Advertising ID (free tier, after trial, user‑grantable). None for subscribers.
Data shared — Advertising ID with Google AdMob (free tier, after trial, user‑grantable). None for subscribers.
Data is encrypted in transit — yes (HTTPS for every network endpoint listed above)
Users can request data be deleted — yes (data is on‑device or on the platform’s servers; uninstall + reset advertising ID to delete; subscribe to opt out of advertising data entirely)

6. Changes to this policy

If we ever add a feature that changes any of the above (for example, optional cloud sync), we will:

Update this page,
Bump the Last updated date at the top,
Show a one‑time notice inside the app, and
Make the feature opt‑in — never on by default.

7. Contact

Questions, deletion requests or corrections:

OneBibleVerse Dev doankhanh12@gmail.com

Soli Deo gloria.