About us / Our mission

Help people read Scripture
with understanding.

We’re building Ask Why Bible so a question can become a reason to stay with the Bible and explore it more deeply.

A passage can be hard to follow. A familiar verse can raise a new question. We want people to be able to pause, explore the words and their context, and return to Scripture with more to consider.

This is for someone opening the Bible for the first time, someone returning after time away, and someone who has studied it for years. Reading, listening, and asking questions should fit together in the same experience.

Why we’re building it

Made for a life with Scripture.

More room for curiosity, reflection, and faith in everyday life.

A question can be a beginning

Understanding grows one question at a time.

Ask Why Bible began with a familiar experience: reading a passage and wanting to understand it more deeply. Some words invite a closer look. Some questions stay with us long after we close the book.

We believe there should be room for those questions. A place to read, listen, explore the context, and consider what Scripture means for the choices and challenges of everyday life.

Our purpose is to make that rhythm easier to return to. Whether you are opening the Bible for the first time or continuing a lifelong study, curiosity can become a way to keep growing.

A rhythm to return to

Read deeply. Ask freely. Keep growing.

Scripture at the center.
Space for your questions.

Churches & Christian communities

Who contributes, and how

We are building partnerships with churches from different denominations and theological perspectives. Their input will be critical to shaping the curated knowledge base: identifying resources, examining interpretations, and helping us understand where Christian traditions agree and where they differ.

These relationships are still developing. Our aim is to make each church’s contribution clear and to record who has reviewed a resource, what was reviewed, and why it was included. We want those conversations to help us represent different views fairly, with the project’s theological framework clearly stated.

Input into source curation does not mean a church reviews or endorses every answer from the Ask Why Bible assistant. Current answers are generated automatically without individual human review before delivery, but they are governed by our theological constitution through the instructions used for written and spoken responses. We continually review and improve that constitution and its application.

What the project does

Read. Listen. Pause for a question.

Ask Why Bible connects Scripture reading, recorded Bible audio, and written or spoken conversation with the Ask Why Bible assistant. Available editions and recordings depend on the source and its permitted use.

  1. Begin with Scripture

    Read a passage or listen to a Bible recording. Keep the text and the place you are exploring at the center.

  2. Ask what you’re wondering

    Pause to speak or type a question about a word, the setting, or how the passage relates to another part of the Bible.

  3. Explore, then continue

    Consider the explanation, look at the referenced passages, and ask a follow-up. Return to reading or listening when you’re ready.

Where the assistant fits

The Ask Why Bible assistant generates the conversation and helps explore questions in context. It can make mistakes or miss an important perspective. Personal study, pastors, teachers, and Christian community remain essential places to weigh an answer and work through what it means for your life.

How the project is funded

What’s free, and what subscriptions support.

The Bible experience is free and will always remain free. The primary purpose of subscriptions is to cover the operating and infrastructure costs of conversations with the Ask Why Bible assistant, helping us sustain the experience of reading, listening, and exploring Scripture.

Free Bible access

Read Scripture, listen to available Bible recordings, use basic search, keep bookmarks and a Journal, and return to saved answers without a subscription. An account is required; available editions and recordings depend on source permissions.

Subscriptions for conversation

Paid plans provide written questions and live voice conversations with the Ask Why Bible assistant. Subscriptions help pay for the computing, speech services, hosting, and ongoing operation needed to make those conversations possible.

An introductory trial provides limited conversation access. Bible reading, your Journal, and saved answers remain available when a trial or subscription ends.

How we organize information

Four kinds of information.

Our framework separates Scripture, human-curated resources, Resources curated with the Ask Why Bible assistant, and public knowledge. Their source identity and review status help you weigh what each can support.

Scripture

Implemented

The biblical text, identified by translation, edition, and passage. Retrieved Scripture and its references provide the foundation for study.

A generated explanation is distinct from the text it explains.

Human-curated resources

In development

Resources selected and explicitly reviewed by people. The planned record identifies who reviewed a particular edition or portion, when, and why it was approved.

Human review adds editorial judgment; it does not turn an interpretation into Scripture or establish universal agreement.

Resources curated with the Ask Why Bible assistant

26 source summaries implemented

The current source selection includes 26 original summaries of specific official church sources, checked through an automated process. They cover selected questions about authority, the biblical canon, baptism and Communion. Each summary names the church, source section and edition it represents; these are not full documents or quotations of their original wording.

Automated review must carry its own label. Human approval requires a separate, recorded human decision.

Public knowledge

Implemented

Attributed public research, including historical discussion, archaeology, and current findings. Public research has separate guidance for attribution and evidence limits.

Appearing in search results does not mean a resource has been admitted to a curated collection.

Source identity, review status, interpretation, and permission to use a work are separate questions. The limited summaries have automated source checks, not human approval or church endorsement. The fuller source library and review-history presentation are still being developed. Model training knowledge does not automatically count as a verified source.

Human responsibility

Built with people who can question it.

People building Ask Why Bible remain responsible for its choices: the guidance given to the Ask Why Bible assistant, the sources it may use, the problems investigated, and the changes made.

Answers are delivered automatically.

Current answers are generated under instructions drawn from our theological constitution, which we continually review and improve. They are not individually reviewed by a human before they are shown or spoken. This guidance, citations, and automated checks do not guarantee an accurate or theologically sound answer.

Review, challenge, and correction

Internal tools let authorized operators inspect dialogue shared under users’ privacy choices, flag concerns, and compare experimental answers. People decide whether to change the application’s guidance; offline analysis does not automatically update it.

We are developing relationships with churches to help shape critical review and correction. Formal reviewer roles, review schedules, and a source correction process are still being developed. This draft does not claim church endorsement or a staffed theological review board.

Transparency in practice

A closer look, if you’d like one.

These details describe the current implementation and its limits. They are an overview, not a claim that every planned capability is available in a public release.

How Scripture and sources reach an answer

For written passage study, the server retrieves the passage from the configured Scripture source using its canonical reference. It checks the requested source and its permitted use, and builds the Scripture citations separately from the generated explanation. Words supplied by a client are not accepted as authoritative Scripture.

The edition used for reading and the edition permitted for study with the Ask Why Bible assistant can differ. Where the study flow uses a separate reference edition, its citations identify that edition. Access to read a translation does not, by itself, permit sending it to an assistant provider.

These source and permission checks do not independently verify every claim in an answer. Live spoken conversation is not a separately verified written study answer. A proposed resource catalog is also not evidence of a licensed or fully reviewed library.

The theological framework guiding the project

A shared Nicene Christian foundation guides the project. Your selected tradition now determines the church sources used and the perspective explained in written and spoken answers. Catholic and Orthodox explanations follow the represented tradition’s canon and church authority. This replaces the earlier fixed Protestant-only canon policy. The Ask Why Bible assistant still distinguishes Scripture from interpretation and acknowledges uncertainty and disagreement.

We continually review and improve the constitution and the instructions that put it into practice. This work shapes how answers are generated; it is separate from reviewing an individual answer before delivery.

Asking about another tradition or comparing views changes that answer’s perspective without changing your saved preference. Unspecified preferences stay unspecified. Bible translation is chosen separately: if an approved edition lacks a passage, that is an availability limit, not a judgment about your tradition’s canon. A public shared conversation does not load its owner’s private denomination preference.

Current coverage includes selected Catholic Catechism sections, Orthodox Church in America teaching, one regional Coptic baptism resource, and sources from the Church of England, Southern Baptist Convention, Lutheran Church—Missouri Synod, United Methodist Church, Assemblies of God USA and Orthodox Presbyterian Church. These named bodies do not speak for every church in their broader families. Many topics and jurisdictions are not yet covered; the assistant should explain those limits rather than substitute another tradition’s teaching.

The assistant should not claim divine revelation or replace the life and care of a church. Source selection and automated checks are not human approval or proof that every answer is correct.

Questions, personal Journal thoughts, and privacy

Questions and conversation dialogue are processed to answer you. Ask Why Bible and its configured answer and speech providers may process dialogue and available transcripts to answer questions and create conversation summaries. Saved study preferences and eligible study memories can also provide context. This processing is not entirely on your device.

Personal Journal thoughts have a separate boundary. They are excluded from Ask Why Bible assistant prompts, summaries, study memory, retrieval, provider tools, and product analytics. If you accept the device’s sync disclosure and enable their sync category, they may be stored in your authenticated account for synchronization. Permission to store them never grants permission to use them with the Ask Why Bible assistant.

Sync and improvement sharing have separate controls. The initial privacy screen preselects sync categories, but transfers wait until choices are saved. Conversation sharing permits authorized review and offline analysis of retained dialogue; those records are kept for 30 days, and opting out deletes them and linked results. Study-memory sharing is a separate human-review choice and starts on for new accounts. Personal thoughts are excluded from both forms of review.

Storage has limits and deletion controls. Account storage is encrypted in transit and at rest, but is not end-to-end encrypted. Turning sync off stops future uploads without deleting existing account copies. Saved account data can be deleted separately; synced deletions reach other devices when they reconnect, and encrypted server backups expire after 14 days. Providers’ own processing and retention are separate from these account-storage rules.

The app’s Privacy settings contain the fuller disclosure and controls. This page is a short implementation overview. Read our Privacy Policy for the full details.

Bible text, recorded audio, and licensing

Bible text and recorded Bible audio have separate permissions. We need to establish the permitted use of each edition and recording, including attribution, playback, storage, and any use with an assistant or speech provider. A recording’s presence in a provider catalog is not blanket permission to use it.

The app retains source identities and copyright notices. Its available reading and listening catalog is broader than the sources permitted for study with the Ask Why Bible assistant. Development access and internal source settings do not establish a public-release license.

Text and audio choices for public release still require their relevant permissions to be documented. This page does not announce a new license, publisher endorsement, or approval of automatic answers from the Ask Why Bible assistant. The requested NIV dramatized recording remains an access and licensing question, not an enabled feature.

Questions about the project?

For a question about this page or a concern you’d like us to consider.

care@askwhy.bible