BibleText — Privacy Policy

Effective date: 18 August 2026

BibleText is a Bible reading and study app, built to respect your privacy. This policy explains what information the app does and does not handle.

The short version

BibleText has no user accounts, shows no ads, and does not track or sell your data. The developer runs no server that receives it. If you enable an optional AI feature, the app sends only the request described below directly to the provider account you selected.

Information stored on your device

Your reading position, history, display settings, and any shared notes you have received or sent are stored only on your device. On iPhone and iPad, any AI provider key you choose to add is stored in the system Keychain, encrypted at rest and included in your own encrypted device backups, so it survives a restore or a move to a new device; an existing key saved by an older BibleText release is moved there automatically. The Mac App Store edition keeps the key in the macOS Keychain in the same way. On a directly downloaded Mac build, and on Windows, Linux, and Android, the key is held in the app's own local settings store on that device rather than a system keychain. These values are not transmitted to the developer.

Bible text, study data, and audio

Bible translations and study data are downloaded from public, free services so the app can display scripture: bible.helloao.org (the primary source for the World English Bible — including the Catholic edition — and the Berean Standard Bible), bible-api.com (a fallback text source), and openbible.info (cross-reference data), and rest.api.bible (the New King James Version). The API.Bible request carries the passage being fetched and an API key — the project fallback included with release builds, or your own replacement added in Settings. BibleText does not attach your notes, reading history, AI-provider keys, or an app account. API.Bible receives ordinary network metadata and may associate a reader-supplied key with that reader's API.Bible account; it handles the request under its own terms. If you play a chapter's audio, the public-domain recordings are streamed from the project's own public mirror hosted on GitHub (originally recorded for openbible.com — Berean Standard Bible narration — for the World English Bible, David Williams's public-domain narration via audiotreasure.com, and for the World English Bible Catholic edition's Greek books a public-domain synthetic narration from eBible.org); the on-device read-aloud option uses your device's speech synthesis and makes no network request. These are ordinary network requests for the text, study data, and audio themselves; no personal information about you is attached to them.

Optional AI study features (bring your own key)

BibleText's AI features — Find, Explain, and context or translation analysis — are optional and active only if you add your own API key for a third-party AI provider (Google Gemini, OpenAI, Anthropic, or SpaceXAI/Grok). When you use one of these features, your Find search or the passage and study action you selected are sent directly from your device to the provider you chose, using your own key, so it can generate a response. The provider may associate that request with your provider account and retain it under its own privacy policy and terms. BibleText does not route the request through any server of ours, does not use it for tracking, and does not retain your prompts after the app closes.

For App Store privacy disclosure, BibleText is listed as Data Not Collected: the developer operates no server, no accounts, and no analytics, and never receives any of this data. Text you choose to send to your own AI provider goes directly to that provider under your own key and their policies — it is your disclosure to your own vendor, not collection by this app's developer.

Shared verse links and notes

When you share a verse as a link — with or without a note attached — everything travels inside the link itself, through whatever messaging app you choose to send it with. BibleText operates no server and never sees or stores what you share. A note someone sends you is kept only on your device once opened, and the app's settings can delete every stored note at once. If a shared link is opened on the BibleText website instead of in the app, the note is read and displayed entirely within the browser: it rides in the part of the web address that browsers do not send to web servers, so it is never transmitted to the site either.

Your choices, retention, and deletion

You can use every core reading feature without AI. Choose Assistant → None to stop AI features, and use Clear beside a provider key to remove that key from wherever it is stored on that device (the Keychain on iPhone, iPad, and the Mac App Store edition; the app's local settings elsewhere). Removing the app clears its ordinary reading preferences and cached data; clear provider keys in the app first if you also want those credentials removed.

BibleText keeps AI results only in memory until the app closes. An AI provider may retain requests under your account terms. Use that provider's account controls or contact the provider for access or deletion; the BibleText developer cannot view or delete data held in your provider account.

Children's privacy

The developer does not knowingly collect personal information from anyone, including children. AI cannot be used unless the user supplies a provider account key, and that provider's age requirements and terms apply.

Changes to this policy

If this policy changes, the updated version will be posted at this address with a new effective date.

Contact

Questions about this policy can be sent to support@bibletext.co.uk.