Lecture 4-3: Choosing Tools and Vendors, the Questions to Ask
Contents 31
- Lecture 1-1: Secrets, Shame, Gossip and Trust in Scripture
- Lecture 1-2: Confidence in the Traditions, and Where It Stops
- Lecture 1-3: What a Church Holds, and What Can Hurt
- Lecture 1-4: When the Community Must Know, and When It Must Not
- Lecture 1-5: Practice Lab, Map What Your Community Holds
- Lecture 2-1: Collect Less, and Say Why
- Lecture 2-2: Consent When the Asker Holds Authority
- Lecture 2-3: Keeping It: Places, Keys and Who Needs to See
- Lecture 2-4: Using, Sharing, Letting Go
- Lecture 2-5: Practice Lab, Fix One Form
- Lecture 3-1: Writing Notes About People, and Not Writing Them
- Lecture 3-2: Prayer Requests and the Circle Around a Person
- Lecture 3-3: Children, Young People and Vulnerable Adults
- Lecture 3-4: When Exposure Can Endanger
- Lecture 3-5: Practice Lab, Rewrite the Note and the Request
- Lecture 4-1: Accounts, Passwords and Devices
- Lecture 4-2: Group Chats, Social Media, Livestreams, Cameras and Photographs
- Lecture 4-3: Choosing Tools and Vendors, the Questions to Ask
- Lecture 4-4: Volunteers, Borrowed Devices and Handing Over Access
- Lecture 4-5: Practice Lab, Audit One Day of Access
- Lecture 5-1: When Something Goes Wrong: The First Hours
- Lecture 5-2: Speaking to the People Who Were Hurt
- Lecture 5-3: Hands Changing: Pastors, Leaders, Splits and Closures
- Lecture 5-4: Leaving, Moving, Dying, Asking: Requests About a Person's Record
- Lecture 5-5: Practice Lab, The First Hour and the Handover List
Most churches do not choose their tools. They find them. A volunteer likes a certain form tool and builds the registration with it. The treasurer has been using a payment service for years because a friend recommended it. The youth leader starts a shared folder in a cloud storage service because it is free. A denominational office asks every parish to use a particular church-management program. By the time anyone asks whether these tools are safe for the people whose information is inside, the information is already inside.
This lecture does not review any product; products change and any list would be out of date soon. Instead it teaches a set of questions that can be asked of any tool at any time: a cloud storage service, a church-management program, a giving or payment service, a survey or form tool, a messaging platform. A person does not need a technical background to ask them. A person does need the courage to ask a question that a cheerful volunteer may not have thought of, and the patience to read an answer.
The central claim of the course is that what people entrust to a church is theirs and the church is its keeper. When a church puts that information in a company's hands, the church is still the keeper. It cannot hand the duty over with the data. So the church needs to know, in plain words, what it has done. This lecture is not legal advice and not a security audit. Anything that will hold sensitive information should be looked at by someone qualified, and the rules about outside services, and about telling people when data is lost, differ from place to place.
The last section is short and plain, and concerns tools that write and translate: what not to type into them.
What these 23 minutes give you
- Ask, of any outside tool, where the data will be kept and under whose rules, and who at the vendor can see it.
- Check whether a church can export and delete everything, and what happens to its data when it stops paying.
- Explain why a record of who has seen or changed information matters, and why a promise to tell the church about a breach matters.
- Read the terms of a service for what the vendor may do with the data, and decide who in the community owns the choice.
- State what should never be typed into an AI, translation or document tool, and what to do instead.
A simple man believes everything, but the prudent man carefully considers his ways. — Proverbs 14:15
World English Bible
For which of you, desiring to build a tower, doesn’t first sit down and count the cost, to see if he has enough to complete it? — Luke 14:28
WEB
Or perhaps, when he has laid a foundation, and is not able to finish, everyone who sees begins to mock him, — Luke 14:29
WEB
saying, ‘This man began to build, and wasn’t able to finish.’ — Luke 14:30
WEB
Test all things, and hold firmly that which is good. — 1 Thessalonians 5:21
WEB
The verse is about a habit of the mind. Believing everything is the mark of the simple person. A cheerful claim that a tool is "secure" or "free" or "used by thousands of churches" is a thing to be considered, not swallowed whole. This is not suspicion of people; it is carefulness over what is not ours.
Jesus is speaking about the cost of , and the passage should not be bent into advice about software. But the everyday wisdom he uses is that a builder counts the cost before starting, including the cost of finishing. For a tool, "finishing" includes leaving: what it costs to get everything out and to stop.
The verse speaks of testing what is taught in the church, and the same temper suits a tool: test, and keep what proves good. It does not forbid tools. It asks that a tool be tried, with eyes open, before it is trusted with what is not ours.
1. Why this is a question of love and not just of caution
A church often adopts a tool because a generous volunteer likes it. That generosity should be welcomed. The question this lecture raises is not about the volunteer's character. It is about what happens to the people whose information is now in the tool, who did not choose it and may not know that it is there.
A church has duties to those people that do not move to the vendor. If the vendor keeps their information for years after the church has stopped using the tool, the church is still the one who told them it would be careful. If the vendor is affected by something that exposes the information, the member will not blame the vendor; the member will remember that the church had it. So the questions below are a form of the same question that Chapter 2 asked about forms: what will we do with this, and who will see it?, now turned toward the company that stands behind the tool.
Ask the questions before the tool is adopted, when the answers can still change the decision. A church that has already put everything in can ask them too, and should; but the sooner, the cheaper.
2. The questions
Each of the following can be asked of any outside tool. They are written to be asked in plain words, of a vendor, a denominational office or a knowledgeable friend. Keep the answers in writing.
Where will the data be kept, and under whose rules? Data does not float in the air. It sits on machines in some country, and the rules of that country, and the vendor's own terms, decide what can be done with it. A church should know in general terms where its data will live, and whether that matters for the people in it. Some places are comfortable to store data in; in others, a government may have wide power to demand it. For a church whose members may be at risk (Chapter 3 spoke of such communities), this is not a minor question.
Who at the vendor can see it? Some services are built so that the vendor's staff cannot read what is stored; others are built so that staff can, under some conditions. The difference matters most for the most sensitive material. Ask: Can your staff read what we store? Under what conditions? Is that written down?
Can we export everything and delete everything? A church should be able to take all of its data out, in a form that another tool or a person can read, without being held hostage. And it should be able to have the vendor delete what is held, and have that confirmed. Ask this before you start, because a tool that keeps your information after you leave is one that keeps the people's information after the church's reason for holding it has ended.
What happens when we stop paying? Free tools end. Paid tools lapse when the treasurer changes or the budget is cut. Some services delete the data soon after payment stops; some keep it, and may use it. Find out which, and what warning you will get. A church that loses its register because a card expired has been careless with the people in it.
Can we limit who sees what, and is there a record of who did? A tool that shows every record to every user, with no way to restrict it, cannot hold sensitive material, however pleasant it is. Look for ways to give each person access only to what their task needs, and for a log that records who looked at or changed a record. The log is not for suspicion. It is how a church can answer a member who asks, "who has seen my record?".
What happens in a breach, and will we be told? Any service can be affected by a failure. The question is what the vendor does then. Will it tell the church promptly? What will it tell? Many places also have rules about telling people when their data is lost; those rules differ, and this course names none. Ask whether the vendor has a plain description of what it does.
What may the vendor do with our data? Read the terms, or have someone who reads such things read them with you, looking for plain-word answers. May the vendor use the content for its own purposes? May it share it with other companies? May it use members' details to advertise to them? May it use what you type to improve its own tools? If you cannot find out, or the answer is "yes" to a use that the members would not expect, that is a reason to look elsewhere or to put only harmless information in.
What does it cost to leave? Add up the money, the time, and the work of moving. A tool that is easy to enter and hard to leave is one to treat carefully.
Do the members need to be told? If the church begins holding members' information in a new outside service, the people concerned may be entitled to know, and in some places must be told. Even where no rule demands it, telling them is honest. A short sentence in the registration form saying that the information is kept in an outside service is enough in many cases.
Who in our community owns the decision? The tool should not be adopted by the enthusiasm of one volunteer, and it should not be adopted by an enthusiasm of the board that does not know where the data goes. Name a person or a small group who decides, who writes down what was asked and what was answered, and who will see to it that the tool is reviewed. This lecture's questions are ones that a leader can ask even if she does not understand how the tool works. She does not need to understand. She needs to hear a clear answer, and to be unsatisfied by a vague one.
Ask someone qualified to look. For any tool that will hold sensitive material (counselling or safeguarding records, health information, the details of vulnerable people), the questions here are only the beginning. Someone qualified should look, and the church should accept their advice even when it is inconvenient. This is no weakness. A church does not build its own wiring.
3. A worked example
An invented case. (An invented case.) A congregation of about a hundred wishes to move its giving records and its member list out of a paper ledger. Pedro, the volunteer who proposes it, has found a church-management program that is free for small churches. It looks friendly and does what is needed.
The leaders, instead of saying yes at once, put the questions to him. He had not asked where the data would be kept. They write to the company and ask; the reply is vague. They ask whether the company's staff can read the records, and whether everything can be exported and deleted. The answers are not clear. Pedro reads the terms and finds a clause that allows the company to use the information "to improve its services". Nobody can say what that includes. The leaders decide not to put the counselling or prayer notes in it, since it has no way to limit who sees what, and to put in only names, a contact detail and giving totals. They ask a friend who works in this field to look at it. And they write one sentence on the registration form: "Your name and contact details are kept in an outside service chosen by the church."
Notice that the leaders did not say no to a good tool, and that they did not let enthusiasm decide. They learned what the tool could safely hold, and held the rest elsewhere. That is the whole of the method.
4. Paying for things: a note on giving and payment services
A giving or payment service holds what is among the most sensitive records a church has: who gave, how much, and when. In some places, a gift to a church is itself a thing a member would prefer to keep private; in some, it is a thing a hostile person could use. The questions above apply with extra weight. Add two: Does the service keep card or bank details itself, or does it pass them to a specialist? Who in the church can see the giving of named individuals, and does that need to be more than one or two people? A rule that the treasurer sees the totals but the elders do not see the names often serves everyone, and a church's treasurers are happier for the rule when it is written down.
5. AI, translation and document tools: what not to type in
Many ministers now use programs that write, summarise, translate or tidy documents. These can save hours. This course does not teach how they work; a course on AI for ministers does that. The one thing it teaches here is what not to put into them.
Do not type in names, health details, family trouble, counselling content, or anything that could identify a person. That includes a story with the name taken out if the story is distinctive enough to identify someone.
Why, in plain words?
You cannot see where your words go. When you type into such a tool, the words travel to machines you do not control. You often cannot tell who can read them, how long they are kept, or whether they are used to improve the tool.
Terms and practices change. What a service promised last year may not be what it does now. A church that relies on a promise it read once is relying on something that can move.
A story without a name can still identify someone. In a small community, "a woman in the choir whose husband lost his job and who has been unwell" is enough for those who know. Removing a name does not remove the person.
What you type is a record you did not mean to make. It may be stored somewhere you cannot reach, beyond your power to delete.
What to do instead is easy and costs little. Describe the task using an invented case. If you want help phrasing a letter of condolence, write: "Help me write a short, plain letter to a family who has lost an elderly father; keep it warm and not too long." Add no real name, no real illness, no real family detail; add your own real details afterwards, by hand, in your own document. If you want to translate a notice, translate the parts that are general, such as the time and place, and handle the sensitive parts by a person you trust. If a tool is wanted for something that must include personal details, then it is not a task for such a tool, and the course on AI for ministers explains why and what else there is.
The rule is simple enough for a volunteer to remember: if you would not put it on a noticeboard in the street, do not type it into a tool you cannot see inside.
Diagram 1. The questions to put to any outside tool
In short
- A church often adopts a tool because a volunteer likes it. The church stays the keeper of the information and cannot hand that duty to the vendor.
- Ask where the data is kept, who at the vendor can see it, and what the vendor may do with it, in plain words and in writing.
- Check that you can export and delete everything, what happens when payment stops, whether access can be limited and logged, and whether you will be told of a breach.
- Name a person or small group to own the decision, tell members where their information is kept, and ask someone qualified to look at any tool that will hold sensitive material.
- Do not type names, health, family trouble or counselling content into AI, translation or document tools. Describe the task with an invented case.
| Front | Back |
|---|---|
| Topic | The questions to put to any outside tool or vendor before it holds information about people. |
| Remember | Where is the data, who can see it, can we export and delete it all, can we limit and log access, will we be told of a breach, and who owns the decision. |
| Caution | A free or cheerful tool may hold what it should not, and a story without a name can still identify a person. Never type sensitive content into an AI or translation tool. |
| One line to carry into ministry | Count the cost of leaving before you enter, and keep the people's information as theirs. |
Check yourself
Not "did you read it" but "can you explain it". Ticks are kept on this device only.
Reflection and discussion
- Which tools does your community already use that nobody ever decided to adopt? For one of them, which of the questions in this lecture could you answer today?
- Why does a church remain the keeper of members' information after it is placed in a vendor's hands? What would a member say if asked who was responsible?
- What is the difference between a tool that is "free" and a tool that is safe to leave? How would you find out what happens to your data when you stop using it?
- In the worked example, the leaders kept counselling notes out of the new program. What rule would you use to decide what goes into an outside tool and what stays elsewhere?
- Why does removing a name from a story not make it safe to type into a tool you cannot see inside? Give an example from a small community you know.
- Who in your community should own the decision about adopting a tool, and what should that person write down?