Effective date: 11 October 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.
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.
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 Android the key is encrypted with a key held in the Android Keystore, which never leaves the phone, and the encrypted copy is stored in a location Android excludes from backups. Because that Keystore key cannot be transferred, an Android key does not travel to a new phone: after restoring a backup you will need to enter it again. On a directly downloaded Mac build, and on Windows and Linux, 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 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), openbible.info (cross-reference data),
and API.Bible, at 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,
which is the only host contacted for playback. The recordings originate with
openbible.com (Berean Standard Bible narration),
David Williams's public-domain narration distributed by
audiotreasure.com (World English Bible), and
eBible.org (a public-domain synthetic narration
of the World English Bible Catholic edition's Greek books); those are recording credits, and
BibleText does not contact them. The read-aloud option instead hands the chapter text to your
device's own speech-synthesis engine, and BibleText makes no network request to do so. On
Apple devices that synthesis happens on the device. On Android, whether the engine you have
set as your system default synthesises on the device or through its own online service is
determined by that engine, not by BibleText. These are
ordinary network requests for the text, study data, and audio themselves; no personal
information about you is attached to them.
BibleText's AI features — Find, Explain, context or translation analysis, Compare perspectives, and Ask a question — 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, including the question text when you use Ask a question, 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.
The developer operates no application server, accounts, or analytics and does not receive your AI requests. The provider you choose receives those requests directly under your own key. If you tap Report under an AI answer, your email app opens a message to our support address naming the passage and the study action, with your question and the answer; it reaches us only if you choose to send it. Providers can retain content and usage records associated with your provider account or API key. Its retention and use of your requests depend on the provider's policies and your account settings. In particular, Google's Gemini API terms permit product and model improvement and human review for unpaid services; paid-service handling and regional exceptions differ. BibleText does not enforce which service tier your key uses.
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.
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 Keystore-encrypted copy on Android; 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.
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.
If this policy changes, the updated version will be posted at this address with a new effective date.
Questions about this policy can be sent to support@bibletext.co.uk.