Private beta · Features are being tested

Your information

Privacy, in plain language.

Your reading data stays separate from your account. An account is optional, and the app can be used without one.

Updated November 16, 2026 · Contact: ndowling970@gmail.com

What stays on your device

The app stores bookmarks, saved passages, topic choices, hidden topics, shown-card history, reading-based recommendation preferences, study-path progress and local feedback in its own device storage. That reading data does not sync to your account or go to a developer analytics service in the current build.

The World English Bible and King James Version are bundled for offline reading. Switching between them does not request their text from a server. NIV and NLT links open an outside online reader; those editions are not stored in the app.

Reading narration uses an installed Apple device voice. Illustrations and prepared study notes are separate from Scripture. The current app does not send your private reading activity, notes or feedback to an AI model for generation.

iOS may include local app data in device backups according to your settings. The app does not operate a separate reading-data cloud backup.

Friendships and shared plans

When friendships are enabled in your beta build, a chosen username and display name are visible to connection-request participants, accepted friends and shared-plan participants. Joining a shared plan reveals membership; progress starts private. A manual sharing control can publish only a completed-step count for that plan.

When personal invitation links are available, anyone holding a link or QR code can preview its sender’s display name and the offered plan. Links expire after seven days, work once and can be revoked by the sender. Accepting friendship and joining a plan are separate choices. Group comments and profile posts remain gated for testing. Profile photos, media uploads, contacts discovery and social push alerts are not enabled.

Text posts and moderation

When community features are enabled, choosing to submit a profile post or shared-plan comment sends that text, your account ID and its intended audience to Supabase. Text has a 2,000-character limit after normalization; some visible characters, such as combined emoji, count as more than one. Published profile posts are visible to you and your current accepted friends; shared-plan comments are visible to current participants in that plan. Pending or rejected text is not shown to those other readers.

Before publication, our server sends submitted text to Amazon Web Services (AWS) Comprehend in the U.S. East (N. Virginia) region for automated toxicity checks. Additional server rules and authorized human moderators review content. Initial publication requires human approval even when automated checks pass. Private reading notes, prayers, saved verses and reading history are not automatically submitted or sent for these checks. A Scripture quotation is not an exemption from review.

Authorized moderators can inspect held, rejected and reported posts, limited recent submission history, report counts and posting restrictions. If you report a post, Supabase stores the selected reason, reporter account ID and time for review; the reporter’s identity is not shown to the author. Reports do not automatically ban an account. Blocks and posting restrictions also affect community access.

You can hide or report a post, block its author, and delete your own post. Post bodies remain until you delete the post or account, or a moderator removes the post. Author deletion or moderator removal clears the stored body and stops any active publication attempt. Limited moderation and security records, such as action reasons, account identifiers, timestamps and spending reservations, can remain separately. We do not copy post bodies into app analytics, application logs or notification previews. No photo/video uploads or direct messages are enabled. Email ndowling970@gmail.com to request review of a moderation decision or ask about these records.

Optional accounts and sign-in email

When account access is enabled in your build, requesting a sign-in code sends your email address to Supabase, our account and database provider. Supabase creates and verifies the one-time code. Resend delivers the sign-in message and processes information about its delivery. Sign-in emails are transactional; no newsletter signup is included.

Your cloud profile contains an account ID, an optional display name, and creation/update timestamps. A chosen social username and connection records are stored when you use friendships. Your email is held with the authentication account and is not shown to friends. Profile editing is limited to its owner; social display-name and username visibility is described above. There is no public profile directory.

Supabase and Resend also process connection, operational and security information as part of providing their services. Resend open/click tracking is not enabled for this sending-domain setup. App sign-in details are stored in device-only Keychain storage rather than ordinary app preferences.

Usage streaks and reminders

In beta builds with streaks enabled, app-opening dates and streak progress stay on this device. A usage day is earned when the app opens in the foreground, once per local date. This includes opening the app from a notification. A usage streak does not mean a passage was read or completed, does not measure spiritual growth, and does not require reminders or an account.

Reminders start off. You can choose a time and enable the primary study-path plan, with up to three reminders per week, or choose Not now, before the app requests iPhone notification permission. An additional-reminders screen suggests daily Scripture and streak reminders with visible selections that you can uncheck. They only become enabled when you choose Save selected reminders; you can also choose Skip extras. A reminder already chosen as the primary one is not repeated in the extras form. Every category can be turned off in Your space → Reminders or through iPhone notification settings.

Reminder preferences, local activity dates, and a short scheduling history are used on this device to avoid duplicate or excessive alerts. Usage streaks and this scheduling information are not uploaded to a developer analytics service or synchronized to your cloud profile. The local plan shares one quiet reminder slot per day, with at least 24 hours between planned alerts; study-path reminders use up to three selected weekdays per week. Pauses and quiet hours are available. Opening the app can suppress that day's streak reminder, and meaningful reading can suppress today's other pending reminder. iOS controls actual delivery.

Clear local data removes local streak progress and reminder settings and stops the app's pending local reminders. Device backups may include local data according to your iOS settings.

Choices you can make

  • Use the app as a guest. Reading and local saved data do not require an account.
  • Adjust local recommendations. Turn reading-based personalization off or reset recommendations in the app. A temporary study focus lasts only for the current session.
  • Clear local data. This removes the app’s local preferences, reading history, saved items, feedback and progress. It does not delete an account or remove files you already exported or shared.
  • Manage an account when enabled. Open Your space → Account to edit the display name, sign out, or request permanent deletion of the sign-in account and cloud profile. Account deletion removes its friendships and community posts; this device’s reading data remains until you clear it separately.

Cloud account/profile data remains until you delete the account or request help with removal. Operational logs and provider backups may remain under the providers’ retention settings. We do not promise immediate deletion of every service log or backup, and no fixed retention period is stated for those separate records.

For access, correction, deletion or other privacy questions, email ndowling970@gmail.com. We may need to confirm account ownership before acting on an account request.

Feedback and outside links

Feedback entered in the app stays local unless you choose to export and share it. Review an exported file before sending it. A locally saved content concern is not automatically sent as a moderation report.

If you email support, we receive what you include in that message so we can respond. Opening publisher links, an online Bible reader, an email app, or a destination in the share sheet uses that service under its own policies.

Apple support payments

Live support payments and payouts are not ready. Some beta builds may offer optional support choices for testing. TestFlight purchases use Apple’s sandbox and do not charge real money. The app requests available products and localized prices through Apple; Apple handles purchase confirmation and provides verification to the app. Bible Trailhead does not collect your card or bank details.

Monthly support is also not enabled. Any monthly option, if activated, renews under the terms shown by Apple until canceled. Deleting an app account or clearing local data does not cancel an Apple subscription or remove Apple’s purchase records. Apple explains how to manage or cancel a subscription.

Advertising, telemetry and this website

No advertising or app analytics is enabled in this beta. Google/Apple sign-in and optional telemetry are not active in the app. We will update this policy and explain the choices before enabling materially different processing.

This static website has no lead form, analytics script, cookie-setting code, embedded media, remote fonts or advertising. The website host may process connection information to serve pages and protect the service.

Service information

Providers have their own service information: Supabase privacy information, Resend privacy information and AWS privacy information. AWS processes submitted community text only when that feature is enabled and you choose to submit it. Apple manages device backups, app distribution and purchase records under its own services.

We will revise this page when enabled features or providers materially change. This policy describes the private beta and conditional features explained above; it does not claim a legal or regulatory certification.