The confidence comes before the software
A person who asks a church to pray has entrusted it with something. That request may include far more than a topic for Sunday intercessions. It can disclose a fear, a relationship or an event involving someone who never spoke to the church at all. Before asking what AI could do with the information, Christian leaders should ask what they have actually been entrusted to do.
This is already a concrete institutional concern. The Methodist Church in Britain’s Artificial Intelligence Report in its 2026 Conference Agenda expressly identifies prayer requests and pastoral conversations among material requiring care. It recommends against entering confidential information into systems whose storage or use cannot be clearly understood. The document is evidence of the working group’s guidance, not proof of a particular breach or, by itself, the final conference vote. Source: media.methodist.org.uk
Our position is that permission to receive a prayer request should never be silently expanded into permission to experiment with it. That remains true when the experiment is intended to make the church more attentive, and when the technology comes with a reassuring ministry name.
A request has a purpose and an audience
Consider a hypothetical member who asks a small prayer group to remember a difficult family situation. The group can pray without turning the account into a reusable example for a writing tool. If a volunteer wants AI help composing a general prayer about family tension, the task rarely requires the member’s distinctive story.
The difference concerns the member’s agency. They chose a particular circle of people for a particular purpose. A software provider, an administrator with access to exports and a future audience for a generated summary are not automatically included in that choice. A compassionate intention does not erase the change in audience.
Removing a name is also an incomplete moral test. In a small congregation, details about an occupation, recent event or relationship may make a story recognizable. The safer question is whether the task needs a real person’s circumstances at all. A wholly invented example can test a workflow without conscripting someone else’s vulnerability.
These are proposed boundaries for responsible church practice, not a claim that every processing arrangement is identical. A carefully assessed service used with clear, appropriate permission differs from an unexamined upload. The burden is on the institution to understand and explain the difference.
Scripture gives reasons for restraint
Matthew 6 places Jesus’ teaching about prayer alongside giving and fasting. Across these practices he challenges righteousness performed for an audience’s admiration. The instruction to pray privately belongs to that argument; it is not a prediction of cloud computing or a ban on all communal prayer. Read the chapter in the NIV: Matthew 6 (NIV)
Its application here is a challenge to the appetite for visibility. A church does not need to make every expression of dependence on God into measurable activity, shareable content or institutional evidence of engagement. Some things can be received and answered faithfully without being made productive in another way.
Proverbs 11:12–13 places restraint in speech and the keeping of confidences within wise treatment of a neighbor. The passage concerns human character, not a technical security guarantee. It asks whether the person receiving information can be trusted with it. That question reaches the volunteer choosing a prompt and the leader approving a system, even when neither intends to gossip. Proverbs 11 (NIV)
The Christian application is not that information must never move. It is that another person’s disclosure creates an obligation of care, rather than an opportunity to use every available feature.
Shared prayer does not make a person public property
James 5:13–20 describes prayer within the life of a community, including calling its elders, mutual confession and concern for people who wander. This setting challenges the idea that faith is merely a private transaction. It also names relationships and responsibilities; it does not authorize indiscriminate circulation of intimate material. James 5 (NIV)
Catholic and Protestant communities have different structures for confession and pastoral responsibility. Ordinary prayer-request handling should not be casually equated with every tradition’s sacramental practice. The narrower point is that a community can receive people deeply without treating everything it learns as information for unlimited organizational use.
A Catholic contribution helps explain the stakes. In paragraphs 90–93 of the January 28, 2025 note Antiqua et Nova, the Vatican connects privacy with conscience, relationships and religious freedom. That is a theological and ethical argument, not a technical audit of religious apps. It gives privacy a positive purpose: protecting the freedom to have an inner life and to form relationships without undue control. Source: vatican.va
Training is only one question
The title’s warning should not imply that every AI provider trains on every submitted prayer. Services and agreements differ. A promise not to use input for model training addresses one use of information; a church still needs to understand processing, storage, access and deletion. Its explanation to members should match the specific arrangement it has verified.
The UK National Cyber Security Centre’s 2023 discussion of language models distinguished concerns about model learning from questions about who can see submitted queries. Its advice to examine terms and access arrangements remains a useful question to bring to a current contract. The older article should not be treated as a description of every provider’s September 2026 settings. Source: ncsc.gov.uk
There is also a legal context, although this argument does not depend on one jurisdiction. The UK Information Commissioner’s Office identifies data revealing religious belief and data concerning health as specially protected categories. Its page currently carries a notice that guidance is under review following legislative change. That is a reason to check applicable requirements carefully, not to turn this article into a universal compliance checklist. Source: ico.org.uk
Better administration can be a form of care
The strongest objection comes from overstretched churches. A missed request can leave someone feeling abandoned. Tools that help organize work, translate public information or remind a responsible person to follow up could support attentive ministry. Paper notebooks and informal email chains can also be handled carelessly. Refusing AI does not certify an institution’s trustworthiness.
That objection should push churches toward better design. A reminder that a designated person needs to make a call may require less information than the entire history behind the request. An administrative tool can sometimes support care without receiving the most intimate content. Where sensitive processing is genuinely necessary, the church should explain the purpose, limit access and establish who is responsible for the arrangement.
Members should also have a workable way to request prayer without accepting an optional experiment. Consent becomes difficult to call free when a person must choose between disclosing to an unfamiliar system and being excluded from ordinary care. The church should not make technical enthusiasm a test of belonging.
A small discipline with a large meaning
A sensible church practice begins at the point of receiving a request. Ask what may be shared and with whom. Keep private details out of public intercessions unless the person has agreed. Before adding AI, examine whether the additional processing serves the agreed purpose and whether the same task could be done with less information.
This responsibility includes honesty about limits. Confidentiality should not be invoked to conceal abuse or prevent appropriate safeguarding action. Those situations require the church’s established procedures and relevant professional advice. An indiscriminate promise that nothing will ever be shared would itself mislead the person seeking help.
The larger Christian discipline is learning to receive without possessing. Someone’s fear is not raw material simply because it has arrived in an inbox. A church can make good use of technology while refusing to turn entrusted speech into something available for every new purpose. Its members should be able to know that asking for prayer will not require surrendering control of their story.