Swiss churches’ AI guidelines draw a firm boundary around pastoral confidences

Five bodies, one church-facing statement

Five Swiss Christian bodies announced joint AI guidelines on October 12: the Protestant Church in Switzerland, the Swiss Bishops’ Conference, the Christian Catholic Church of Switzerland, the Freikirchen.ch umbrella and the Swiss Evangelical Alliance. The announcement presents ten ethical principles for church institutions, congregations and ministries, with human dignity as their measure. An October 20 conference is scheduled to discuss them; it has not yet taken place. Source: bischoefe.ch

For a church office, the immediate question is less whether AI belongs on an agenda than what happens when an ordinary task includes somebody else’s private life. Preparing a notice, translating an email and summarizing a pastoral conversation can look similar on a screen. They do not carry the same responsibilities. This report examines a few concrete provisions and offers an original example of how a team could distinguish those tasks.

The joint website lists German and French versions as available and English and Italian as working translations that are not final. The linked German PDF retains a September 3 working-version footer. That version marker should remain visible when churches circulate or translate its recommendations. Source: menschlichkeit-digital.ch

The boundary is sharper than a privacy slogan

Principle seven of the linked German text excludes material covered by pastoral confidentiality from any AI system. It also rejects AI profiling of people seeking help, employees or volunteers, and automated decisions in sensitive areas. For other personal or sensitive information, it requires clarity and contractual arrangements concerning storage, reuse and deletion. Principle five calls for checked outputs, appropriate disclosure and a named responsible person. These are the document’s directions, not evidence that every participating institution has implemented them. Source: menschlichkeit-digital.ch

The distinction matters because a procurement question and a pastoral boundary are different decisions. A team may be able to explain how a service handles information while still deciding that a particular kind of conversation must remain outside it. In our reading, the document asks church leaders to address both questions rather than treating a satisfactory vendor answer as universal permission.

A useful comparison appears in section seven of the British Methodist Church’s 2026 conference agenda report. That working group’s proposed guidance says personal or confidential data should not enter systems whose storage or use cannot be clearly understood. It also retains responsibility for ministry and final content with people. This comparison concerns the published texts; the agenda alone does not establish the subsequent conference vote or implementation. Source: media.methodist.org.uk

The Swiss text’s pastoral-confidentiality exclusion is more categorical than that particular Methodist data-handling clause. This is not a ranking of the two churches’ entire privacy regimes. It is a specific difference that matters when someone copies a short AI policy from another institution and assumes the permissions are interchangeable.

A hypothetical church-office test

Imagine a congregation wants help turning a week’s correspondence into a staff briefing. The inbox contains a public event announcement, a routine room-booking question and a message requesting a private pastoral conversation. A single instruction to summarize everything would hide the differences between the materials. The team should decide what may enter the workflow before asking whether the summary is accurate.

Our proposed exercise starts with a deliberately fictional sample, so nobody’s real confidence is used to test the tool. Staff mark which items are public, which involve personal information, and which should go directly to a designated human contact. They then identify where the proposed system would send or retain each category. An unanswered question is recorded as an unanswered question, rather than silently converted into permission.

Next, the team assigns someone who can stop the process and someone who can explain it to the congregation. Those may be the same person in a small church, but the responsibility should be understandable to anyone using the service. A volunteer covering an absence should not need to reconstruct the decision from a colleague’s memory.

Finally, the team tests its exception route. What happens when a private request arrives in the wrong mailbox, or when an apparently routine message turns out to contain a confidence? The exercise should show how a person takes over. It should not rely on a chatbot correctly detecting every sensitive situation before any information has left the church’s control. These are our suggested implementation questions, not a procedure reported as adopted by the Swiss signatories.

What adoption would need to make visible

A published commitment becomes useful to a congregation when people can understand its practical consequences. Follow-up reporting should therefore look for local instructions, staff preparation, an accountable contact, and a route for raising a concern. Evidence of those arrangements would still not prove that every use is safe, but it would show what the institution has actually done beyond endorsing a principle.

Church leaders can also explain a decision without exposing the very information they are protecting. A public account could describe the category of work allowed, the category excluded and who reviews the arrangement. It need not reveal private pastoral cases to demonstrate that the boundary exists.

For Christian readers, 1 Corinthians 12:12–27 describes a community whose members need one another and give particular honor to those who might otherwise be regarded as weaker. Its subject is the body of Christ, not information-security design. A practical application is to ask whose interests shape a technology decision, especially when the person whose story is being processed has the least influence over it. 1 Corinthians 12:12-27 (NIV)

The October announcement creates a shared reference point. The next evidence to seek is how churches translate that reference into decisions that people can recognize, question and trust.