Your faith. Your space. Your privacy.
This policy explains how The Bible mobile app, Bible service, and public website handle information. The operator is The Bible. Contact us at [email protected] for privacy questions or requests.
[email protected]Effective date: 19 October 202601 / Reading and study on your device
Bible text, downloaded translations, fonts and audio, reading positions and history, notes (including prayer and journal entries), bookmarks, highlights, collections, reading plans, memorization progress, local insights, artwork projects, and appearance or language preferences can be stored on your device.
Signing in does not automatically enable cloud sync. If you enable Cloud sync in Settings, the app sends this account’s bookmarks and exact Scripture references, full notes including prayer and journal entries, folders, tags, note links, collections, and memorization wording identifiers, schedules and reviews to the Bible service. You can separately choose to include existing guest study records from the device. Authorized administrators can access synced records for support; this sync is not end-to-end encrypted.
Your created verse images, selected photos, exports, note attachments, unfinished note drafts and reading history are not uploaded by personal-record sync. Published verse image templates are downloaded for use in your local creations. Your operating system may include app data in device backups according to your settings; those copies are controlled by the backup provider.
Turning sync off stops future synchronization and does not automatically erase copies already on the service. Record deletion uses a marker so other devices can reconcile; sync documents and administrator correction history can remain until account deletion. Deleting your account removes its associated live-service records. Local conflict-recovery copies remain on the device until its app data is cleared.
02 / Optional accounts and staff access
If you choose Google or Apple sign-in, our service processes a verified provider identifier, email address and verification status, display name when supplied, and authentication credentials needed to maintain your session. An optional device name and session creation, expiry, and revocation records may also be stored. We do not receive your Google or Apple password.
We use this information to identify your account, provide sign-in and account management, prevent unauthorized access, and process deletion. The service stores account roles and access levels. Staff access uses server-managed credentials and role checks. Apple credentials needed for authorization revocation are encrypted at rest; session refresh tokens are stored as hashes on the service.
03 / Downloads and network requests
Downloading a translation, checking content revisions, obtaining a font, audio file or verse image template, and checking for app updates require network requests. These can include translation identifiers, installed revisions or content hashes, and the requested resource. They do not require sending your private study notes or reading history.
Our hosting services and external download hosts receive technical request information such as IP address, request path, time, and client information in order to deliver and protect the service. Fonts may be downloaded from the Google Fonts repository hosted on GitHub. App-store update and review features are handled by the relevant store under its own policy.
04 / Reminders and optional push notifications
Local reading, plan, and memorization reminders use your chosen schedule and device time zone. Notification permission is requested where required. Local reminder scheduling does not require uploading your notes or study progress.
On supported devices, optional announcements and content notifications use Firebase Cloud Messaging. When you enable a push category, Firebase processes installation or registration identifiers and technical delivery information; language and category subscriptions determine which messages you receive. We do not include your private notes or prayers in these public notification messages.
When you sign in with push enabled, our service stores your device messaging token and category subscriptions against your sign-in session so administrators can send relevant public updates to your account. Signing out, session expiry, account disabling, and category preferences limit account-targeted sends.
You can disable categories in the app and change notification permission in system settings. Disabling all push categories unregisters messaging in the current implementation. Firebase manages its own identifiers and retention under its privacy information; unregistering messaging is not a promise that every provider record is immediately erased.
05 / Photos, artwork, sharing, and permissions
You may choose a photo as a Scripture-artwork background and allow the app to save an exported image to your photo library. Selected images and artwork composition are processed locally in the current app. When you deliberately export or share a file, the destination app or service receives the content you choose and applies its own policy.
Permissions support selected-photo access, saving images, notifications, network access, reminder rescheduling after restart, and background audio playback where supported. Older Android versions may request legacy storage permission for saving files. The current app does not request location, contacts, microphone, or camera access. You can manage permissions in your device settings; denying an optional permission limits the related feature.
The current build has no configured AI generation provider and does not send prompts, photos, or study content to an AI provider. If a future version changes this, its disclosure and consent flow must be updated before that processing begins.
06 / This website
Public pages can be visited without signing in. The website stores your light or dark appearance preference in browser local storage. The selected language is represented in the page URL. Protected staff sessions use HTTP-only session cookies; secure cookies are used in production over HTTPS.
The current public website and mobile app do not integrate advertising trackers, Firebase Analytics, or Crashlytics. We do not sell personal information or use private study content for advertising. If you email support, we receive your address, message, and any attachments you decide to send.
08 / Retention and security
Local app content remains until you delete it, clear app data, or remove the app, subject to your operating system’s storage and backup behavior. Online account information remains while your account is active; deleting the account removes its associated records from the live service database. Session expiry ends access but is not itself account deletion.
Support correspondence is kept as needed to resolve the request and meet applicable obligations. Operational records, backups, and provider-managed data may have separate retention based on security, recovery, or legal requirements. We do not promise a fixed erasure period for systems we do not control. Contact us to ask about a particular record or request.
The release app requires HTTPS for account API traffic, stores mobile session credentials using operating-system secure storage, and restricts service access by authentication and role. These measures reduce risk; they do not guarantee absolute security. Local study databases are not represented as end-to-end encrypted storage.
09 / Your choices and account deletion
You may read without an account, decline optional permissions, disable push categories or reminders, remove downloaded content, and manage local study content. Subject to applicable law, you can contact us to request access, correction, deletion, or an explanation of personal information associated with your account. We may need to verify account ownership and explain any lawful limits.
To delete an account in the app, open Profile, open your account controls, choose Delete account, and confirm. You may need to sign in again for a recent authenticated session. Apple authorization is revoked as part of the deletion flow. If authorization cannot be revoked, the operation can require retrying before deletion completes.
Account deletion removes the account and its associated service records, including identities, sessions, and any account-linked study, download, or payment records stored there. It does not erase local study files, exported images, copies you shared, or operating-system backups. Remove those separately using the app, device, backup, or destination controls. You can also initiate an account-deletion request by email using the linked instructions below.
10 / Children and family use
The Bible can be read without creating an account or submitting a child’s personal information. Parents and guardians should supervise optional sign-in, permissions, sharing, and support messages as appropriate. If you believe a child has provided personal information that should be removed, contact us so we can investigate and handle the request under applicable law.
11 / Changes and contact
We will update this policy when our information practices change and revise its effective date. Material changes that require notice or consent will be presented through an appropriate app or website notice before the new processing begins.
The Bible is responsible for the practices described here. For questions, privacy rights, or account-deletion assistance, email [email protected]. Do not send passwords, sign-in codes, or sensitive prayer or journal content when making a request.