FeaturesCompareDownload

AI and your data

An AI assistant for your church — on your terms

You can connect Claude or another AI assistant so it can answer questions about songs, service plans and the serving schedule. Here we explain in plain words what the assistant sees, what it does not see and how to cut off its access at any time.

In short

Read-only

The assistant can read, but it cannot change, add or delete anything.

Your admin decides

Access is off by default. Only someone who manages the church's settings can turn it on.

No training

WorshipPro does not train AI models on your church's data and does not sell it.

Data in the EU

We store church data on a server in Poland. The assistant only gets what it asks for at that moment.

What the assistant sees

The assistant uses a few tools. Each one only reads and returns data of one church — the one chosen when connecting. Below is the full list, the same as in our code.

Always

  • Basic information

    The church name, time zone, today's date and the list of data the assistant may read.

    Tool name: get_church_context

Songs

  • Song search

    A list of songs in the church's library: title, author, keys, tempo, tags, status, CCLI number and songbook.

    Tool name: search_songs

  • Song

    Lyrics with chords (ChordPro) and without chords, keys, tempo, arrangements (section order) and copyright information. No sheet music files or recordings.

    Tool name: get_song

Service plans

  • Plan list

    Service plans in the chosen dates — drafts included: title, date, service type, times and place, number of items.

    Tool name: list_plans

  • Service plan

    The order of service: songs with key and section order, scripture readings, sermon, announcements, times and notes for the team. No private leader notes.

    Tool name: get_plan

Teams and roster

  • Who serves

    The plan's roster: team, position, the person's first and last name and their response (invited, accepted, declined, confirmed). No contact details; invitations not yet sent are not shown.

    Tool name: get_plan_roster

  • Team list

    Serving teams and their positions, e.g. worship: vocals, guitar, keys.

    Tool name: list_teams

  • Team

    Positions, leaders and members of a team — first and last names only, no contact details.

    Tool name: get_team

Events

  • Events

    The church calendar in the chosen dates: title, description, place, rooms, time and whether the event repeats.

    Tool name: list_events

When connecting, the admin ticks which kinds of data the assistant may read. The assistant never sees more than the person who connected it — and when you turn off a module in your church (e.g. the calendar), its tools disappear too.

What the assistant does not see

No tool returns this data — the assistant has no way to reach it, even if it asks.

  • The people directory: email addresses, phone numbers, addresses, birth dates and households. Of people, it only sees first and last names in teams and rosters.
  • Sensitive data (Art. 9 GDPR), e.g. about health, allergies and baptism.
  • Children: Sunday school and check-in.
  • Finances: donations, donors, accounting and budget.
  • Forms and their responses.
  • Pastoral notes about people and private leader notes in plans.
  • User accounts, passwords, church settings and files (PDF sheet music, recordings, photos, attachments).

Who decides

  • AI access is off by default — every church has to turn it on deliberately.
  • Only an owner or admin who manages the church's settings can use the “AI has access” switch, create AI tokens and approve a connection.
  • When connecting, the admin sees who is asking for access and where they will return to, chooses the church and the kinds of data, and then approves.
  • Every change of the switch and every approval is recorded in the church's activity log.

How to turn it off

  • Turn off the “AI has access” switch in Settings → Integrations. It works immediately: no assistant can read anything any more, even with a valid token.
  • Revoke a single connection under “Connected apps” or revoke an AI token in the token list — also immediately.
  • When you turn the switch back on, earlier connections work again. To end them for good, revoke them.
  • A connection expires by itself after 30 days without use and after a year at the latest. Access granted at any moment is valid for an hour and is renewed only while the connection exists.

Call log

We record every use of a tool, so you can see who read the church's data and when.

We record

  • the date and time, the tool name and the result (whether it worked);
  • only the names of the parameters used, e.g. “query” — not their content;
  • the token or connection the request came from, and the IP address.

We do not record

  • the questions asked to the assistant or the conversation;
  • the assistant's answers or the data it read;
  • parameter values, e.g. which song was searched for.

Entries are deleted after 90 days. You can see an AI token's log in Settings → Integrations.

Where the data is

We store church data — including what the assistant reads — on a server in Poland, in the European Union. When the assistant reads something, that answer goes into the conversation with the AI provider chosen by the church (e.g. Anthropic for Claude) and follows that provider's rules, including where it is processed.

Where we store data and the list of subprocessors

Model training

  • WorshipPro does not use church data to train AI models or for marketing, and does not sell it — we commit to this in the data processing agreement.
  • The church chooses and connects the assistant. Whether conversations with it may be used to train models depends on the AI provider, the plan and the account's privacy settings — check them before connecting.
  • The church, as the data controller, decides whether to use an assistant and which one. The safest choice is to connect it to an account whose settings you control yourself.

How to connect

First an admin turns on “AI has access” in Settings → Integrations (AI assistant). Then:

Claude (claude.ai and the Claude apps)

  1. In Claude, open Settings → Connectors → Add custom connector.
  2. Enter the name WorshipPro and the server address:
    https://worshippro.net/api/mcp
  3. Click Connect, sign in to WorshipPro, choose the church and the data, then Allow.

Claude Code (in the terminal) — then type /mcp in Claude Code and sign in:

claude mcp add --transport http worshippro https://worshippro.net/api/mcp

Other MCP-compatible apps connect with the same address and an AI token from Settings → Integrations. Tokens and request limits are described in the API documentation.

API documentation

AI suggestions in WorshipPro

Apart from an assistant your church connects, WorshipPro can make suggestions itself in two places. This is a completely different switch from “AI has access”: nobody outside reads your data — WorshipPro sends the AI provider a small, chosen slice and shows the answer only to the person who asked.

Announcement draft

You type a few points (and optionally pick a calendar event), and the AI proposes a title and text in the language and tone of your announcements. The draft goes into the editor marked “check before publishing” — it is never sent by itself.

Plan proposal from history

In an empty plan WorshipPro proposes the order of items and songs based on recent services of the same type, without repeats from recent weeks. Songs come only from your church's library; only what you tick and accept goes into the plan.

What we send

  • For an announcement draft: the points and topic you type, the time and place of the chosen event and a few recent announcements to the whole church as a style example.
  • For a plan proposal: service type and date, theme and reading, the order of items with their lengths, and titles, keys and tags of songs from the library.
  • E-mails and phone numbers in the text you type are replaced with placeholders and put back only in the finished draft.

What we never send

  • Names, e-mail addresses or phone numbers of people, or the name of your church.
  • The roster, notes (including private notes in plans), event descriptions and plan item titles, which may contain names.
  • The directory, sensitive data, children, finance or forms.

Rules

  • Off by default. A person who manages church settings switches it on and off (Settings → Integrations); every change goes into the audit log.
  • Limit: 30 suggestions a day and 300 a month per church.
  • We keep a log without content — who, when, which suggestion and how many tokens — for 400 days.
  • Provider: Claude (Anthropic), the same as for sermon translation. When no AI is connected or it does not answer, a simple heuristic over your church's history makes the suggestion and nothing leaves WorshipPro. The demo church always works this way.
  • Text from users and from the database is treated as material, not instructions: we check and trim the AI's answer and drop anything that is not in your church's library or in the text you typed (such as foreign links).

Documents: Privacy policy · Data processing agreement · Subprocessors

Questions about AI and church data: contact@worshippro.net

    AI and your data — WorshipPro