FREE

Course certificates are free until March 31, 2027.

PT738E Privacy and Confidentiality in Ministry

Lecture 4-4: Volunteers, Borrowed Devices and Handing Over Access

Contents 31
PT738E Privacy and Confidentiality in Ministry
Chapter 0 · Introduction: Held in Trust
  1. Introduction: Held in Trust
Chapter 1 · Week 1: Entrusted Words
  1. Lecture 1-1: Secrets, Shame, Gossip and Trust in Scripture
  2. Lecture 1-2: Confidence in the Traditions, and Where It Stops
  3. Lecture 1-3: What a Church Holds, and What Can Hurt
  4. Lecture 1-4: When the Community Must Know, and When It Must Not
  5. Lecture 1-5: Practice Lab, Map What Your Community Holds
Chapter 2 · Week 2: Collecting, Keeping, Using, Letting Go
  1. Lecture 2-1: Collect Less, and Say Why
  2. Lecture 2-2: Consent When the Asker Holds Authority
  3. Lecture 2-3: Keeping It: Places, Keys and Who Needs to See
  4. Lecture 2-4: Using, Sharing, Letting Go
  5. Lecture 2-5: Practice Lab, Fix One Form
Chapter 3 · Week 3: Notes, Prayer Requests and People at Risk
  1. Lecture 3-1: Writing Notes About People, and Not Writing Them
  2. Lecture 3-2: Prayer Requests and the Circle Around a Person
  3. Lecture 3-3: Children, Young People and Vulnerable Adults
  4. Lecture 3-4: When Exposure Can Endanger
  5. Lecture 3-5: Practice Lab, Rewrite the Note and the Request
Chapter 4 · Week 4: Digital Safety
  1. Lecture 4-1: Accounts, Passwords and Devices
  2. Lecture 4-2: Group Chats, Social Media, Livestreams, Cameras and Photographs
  3. Lecture 4-3: Choosing Tools and Vendors, the Questions to Ask
  4. Lecture 4-4: Volunteers, Borrowed Devices and Handing Over Access
  5. Lecture 4-5: Practice Lab, Audit One Day of Access
Chapter 5 · Week 5: When It Goes Wrong, and When Hands Change
  1. Lecture 5-1: When Something Goes Wrong: The First Hours
  2. Lecture 5-2: Speaking to the People Who Were Hurt
  3. Lecture 5-3: Hands Changing: Pastors, Leaders, Splits and Closures
  4. Lecture 5-4: Leaving, Moving, Dying, Asking: Requests About a Person's Record
  5. Lecture 5-5: Practice Lab, The First Hour and the Handover List
Chapter 6 · Week 6: Policy and Culture
  1. Lecture 6-1: Writing a Plain Policy
  2. Lecture 6-2: Teaching and Culture: Making It Ordinary
  3. Lecture 6-3: Different Places, Different Rules: How to Ask
  4. Lecture 6-4: Known and Kept: A Theology of Being Held
  5. Lecture 6-5: Practice Lab, My Rule and Our One Page

Jump to the key points ↓

26 min

Churches run on volunteers, and volunteers run on what they own. The sound desk is managed from a retired teacher's tablet. The newsletter is made on a laptop that belongs to a student. The first email account of the church was opened by a man who has since moved to another country, and it is still the account that every other account resets through. The register of the youth club lives in a phone that has also been used for games by three children. Nothing in this is shameful. It is how churches work, and it is a large part of why they work. But every one of these devices and accounts is a place where the people's information lives, and it is a place that the church does not fully control.

This lecture asks how to make simple rules for such a situation without suspicion, and how to hand access over, and take it back, with grace. The central claim of this course is that what people entrust to a church is theirs, and the church is its keeper. A keeper does not insist that everyone use church-owned equipment, which most churches cannot afford. A keeper knows which devices and accounts hold the information, who has them, and what happens to them when the person's service ends.

The lecture is about practice. It is not legal advice, and rules about employment, volunteers and personal devices differ from place to place. It is also not a security audit; a qualified person should look at anything that holds sensitive records. And it keeps to defence: it describes how to give and withdraw access carefully, never how to get into what is not ours.

What these 26 minutes give you

  • Write a short understanding for a volunteer who uses their own device or account for church work.
  • Keep church work and personal use apart where it is possible, and say what to do where it is not.
  • Carry out the steps when a volunteer leaves, so that access ends in the same week.
  • Decide what a board, an elder or a deacon needs to see, and what it does not.
  • Describe how to take care when sharing a screen, using an office in a shared building, or handling a minister's own devices.
  • Create a way for people to ask questions and report a slip without fear.

So let a man think of us as Christ’s servants, and stewards of God’s mysteries. — 1 Corinthians 4:1

World English Bible

Here, moreover, it is required of stewards, that they be found faithful. — 1 Corinthians 4:2

WEB

Shepherd the flock of God which is among you, exercising the oversight, not under compulsion, but voluntarily, not for dishonest gain, but willingly; — 1 Peter 5:2

WEB

neither as lording it over those entrusted to you, but making yourselves examples to the flock. — 1 Peter 5:3

WEB

He who is faithful in a very little is faithful also in much. He who is dishonest in a very little is also dishonest in much. — Luke 16:10

WEB

Paul is speaking of himself and his fellow workers, and the "mysteries" are the things of the gospel, not the contents of a database. But the structure of the thought carries over: those who hold what belongs to another are measured by faithfulness, not by cleverness or rank. A volunteer who holds a list is a steward in this ordinary sense.

Peter speaks to elders. The words "those entrusted to you" fit this chapter: a leader who sets rules for volunteers does so as one who serves, and gives the example himself. A rule that the leaders do not keep is only a way of lording it over.

A closed account, a changed password, a returned key are very little things, and they are the places where faithfulness is seen.

1. Start from gratitude, not from suspicion

The tone matters before any rule does. A person who is told, "we need to check you are not misusing our information", hears an accusation. A person who is told, "we are asking everyone who helps with the youth records to do the same four things, and we are doing them too, because the families trust us", hears a shared task. Almost all the volunteers who hold a church's information are trustworthy. The rules are not for them against the few who are not. The rules are for the people whose information is held, against the ordinary things that go wrong: a device is lost, a person leaves, a password is shared in a hurry, a job is passed from hand to hand and the information with it.

This is also why the rules must apply to leaders first. When the minister's own phone is the least protected device in the church, no volunteer will believe that the rules are about care.

2. A short written understanding

For each person who will see information about people, write a short understanding. Half a page is enough, and it should be in plain words that a person with little schooling and little technical background could follow. It can be a spoken promise in some traditions; some prefer a signed paper. Chapter 6 returns to that difference. Whatever its form, it says:

  • What you will be able to see, in categories: for example, the names and contact details of the youth group's families.
  • What you may use it for: the work you were asked to do, and nothing else.
  • What you must not do: pass it on, copy it to places the church does not know about, or keep it after you leave.
  • How we will keep it safe together: who else has access, where it is kept, and what we will do if something is lost.
  • Whom to tell if something goes wrong, and a promise that you will be thanked for telling, not blamed.

The last line is the most important and the one most often left out. A volunteer who knows she will be thanked will report a slip within the hour. A volunteer who suspects she will be blamed will wait.

3. Work and personal, kept apart where possible

Where a volunteer uses a personal phone or laptop, church information and private life share one device. Some separation is cheap and valuable.

Separate accounts. Use a church email address for church work instead of the volunteer's private one, and a separate sign-in on a shared computer for each person. If the volunteer leaves, the church email can be closed and the private one is untouched.

Separate places. Keep the church's files in the church's storage, and not scattered in a phone's photographs or the downloads folder. A person should be able to say, "all of it is in that one place".

Separate habits. Do not forward church messages to a private address because it is easier. Do not export a list to a spreadsheet on the desktop and forget it. Do not let children play on the phone that has the register on it.

Where separation is not possible (and in a poor or small church it often is not), say so, and compensate: the device is locked, updated, and not shared; church information on it is limited to what the task needs; the volunteer knows what to do if the device is lost; and the leaving checklist includes deleting what is on it. A church that insists on rules it cannot pay for will only drive the practice out of sight.

4. Handing out access: start small

Access is easiest to give and hardest to take back. So give it by task, and no more than the task needs. A volunteer who sends the weekly notice does not need to see the giving records. The person who looks after the rota does not need the pastoral notes. The word for this principle in Chapter 2 was need to know, by task and not by title or by curiosity.

A helpful habit is to give access for a season. If someone helps with a camp, they receive access for the camp, and it ends when the camp ends unless it is renewed. Renewal is a small, plain conversation, not a ceremony. It prevents the slow accumulation of people who can see things because they once helped with something.

Keep a short list of who has access to what, in categories, held by the person responsible and checked each season. It does not need to be a technical document. A sheet of paper with the accounts down one side and names across the top, in a locked place, is a record that works.

5. When a volunteer leaves

This is the moment in which most real failures happen, because it is the moment at which no one is paying attention. The volunteer is leaving, the church is busy, and the access remains for months. Treat it like locking the building at night: a task that is done on the day, by a named person, from a list.

The steps are those of the first lecture in this chapter, with some added.

Access ends the same week. Remove the person from the shared storage, the membership program, the accounts and the groups that carry sensitive material. Remove or reduce their permissions rather than waiting for them to say they have stopped.

Passwords are changed. Any password the person knew is changed, including shared ones. Recovery details that pointed to the person's phone or address are changed to a role the church controls.

Shared drives and groups are checked. Look at who has been given access to what the person created. A folder that the volunteer shared with her own private account, or with a friend, should be checked and closed if it should not remain open.

Files are returned or deleted. Ask the volunteer to hand back the church's files, and to delete church information from their own devices and accounts. Ask kindly, and ask them to tell you when it is done. You cannot check everything, and you should not search their devices; what you can do is ask, and trust a person who has served.

Keys, devices and papers come back. Physical things too: the key to the office, the notebook of contacts, the borrowed laptop.

Say thank you, and write down the date. The record shows when the access ended, and the thanks shows what kind of community it is.

What if the volunteer leaves in anger? Then the list is more urgent, not less, and it is still not an accusation. Do the steps promptly, plainly and without comment, and keep the manner of it calm. Do not use the person's access, or the files, as leverage in a quarrel, and do not discuss the disagreement with the people whose information is concerned. A later chapter returns to files in a conflict.

6. The minister's own devices

The minister is a volunteer in this sense too, and often the largest holder of sensitive information: the phone with years of messages from people in distress, the laptop with sermon files and notes, the personal email in which a family wrote about a death. A minister's devices should follow the same rules as everyone's, and a few more.

A lock and updates. A phone that opens without a code, in a bag on a train, holds the confidences of everyone who has ever written to the minister.

Messages from people in trouble. Decide what you will do with them: a short habit of moving what needs to be kept to the church's proper place, and deleting the rest, is better than an archive in a phone that no one can reach.

Where the minister's papers go when the minister goes. A later chapter takes up what happens to a minister's private notes when they leave or die; the point here is only that a minister should know where the information is, and that someone else should know the minister has it.

7. Screens, shared rooms and the office computer

Some risks are not about the internet.

Sharing a screen in a meeting. When you share your whole screen in an online meeting, everyone sees everything on it: an open message, a list in another window, a notification. Share a single window, not the whole screen, where the tool allows; close other things first; turn off notifications for the meeting. The aim is not to be afraid of the meeting but to know what the others can see.

Public places. Do not work on a list of members in a café where a stranger can read the screen, and do not leave a laptop open in a car.

The church office computer in a shared building. Many churches share a building with other groups, or rent a hall. A computer in a room that others have keys to is a computer that others might touch. Lock the screen when you step away, keep the machine in a locked room or a locked cupboard when no one is there, and keep paper records in a cabinet that other groups cannot open. Ask who else holds keys to the building, and whether that includes someone you do not know.

Printouts. A printed list left in a copier or taken to a meeting is a list in the open. Collect printouts, and collect them at the end of the meeting too. Where a list has been handed out in a meeting, ask for the copies back or say how to destroy them.

8. What a board or elder needs to see

Members of a board, council or elders' meeting are often given more than they need, because it is simpler to give everything. But an is a steward, not an owner, and access by rank turns into curiosity. Ask of each item: what decision is this person being asked to make, and what do they need to know to make it?

A board deciding on the budget needs totals of giving, not who gave. A board deciding on a building does not need the pastoral notes. A board hearing a complaint about a leader needs the facts of the complaint, but not necessarily everything the leader's family has confided. The principle is not secrecy from leadership, which would make the church unaccountable. It is that each person sees what the task needs, and that what is seen is shown in a way that does the work with the least exposure: totals instead of names, a summary instead of a file, a description instead of the person's own words.

In some traditions the whole congregation, meeting as one body, is the highest authority, and the people have a right to know a great deal about their church's life. In others, a small body such as a council of elders, a parish council or a bishop's office carries the responsibility. Chapter 1 set out this difference. Whatever the structure, the rule is the same: the circle that sees a sensitive matter should be no larger than the task requires, and should know that it holds the matter in trust.

9. The culture side: asking and reporting without shame

All of these steps rely on one thing that cannot be written into a form: people have to feel free to ask, and to say, "I think I made a mistake." A church where mistakes are punished teaches people to hide them, and a hidden mistake about people's information is the worst kind, because it cannot be put right.

A few small practices help. Have a one-line way to report a slip: a name and a number, or a short phrase, "If anything with the lists goes wrong, tell Ana first, any time, and you will be thanked." Say it aloud at the start of every season. Thank the first person who reports one; people notice. Let leaders report their own slips first. Ask questions in the open: "Is it all right if I keep this list on my phone?" should be an ordinary sentence, and the ordinary answer is a calm one.

And do not shame. Many readers of this course have already made a mistake with someone's information. The point of the course, and of this chapter, is what to do next time and how to put things right now.

10. A worked example

An invented case. (An invented case.) Joseph helped for three years with the children's ministry of a small church. He ran the sign-in sheet, which he typed up each week on his own laptop, and he had the group chat for the parents. This autumn he took a job in another city. At the farewell, someone said, "We'll miss you, send us a message when you are settled." Nobody said anything about the laptop, the chat or the files.

Six months later a parent asks to be removed from the chat; no one can do it, because Joseph is the only administrator and he is busy. Three months after that, someone realises that Joseph's laptop holds a list of every child's name, allergy and the telephone numbers of their parents, and nobody has asked whether it is still there.

What should have happened is plain. The leader who accepted Joseph's resignation would have taken out the short checklist: made a second person the administrator of the chat before he left; asked Joseph to move the files to the church's storage and delete his own copies; changed the shared password; written the date. And she would have done it at the farewell, as a way of saying thank you: "Before you go, let us do what we do for everyone." The late discovery is not a disgrace for anyone. What the church does after it is: ask Joseph kindly to move and delete the files and to tell them when it is done, make a second administrator, and write the checklist so that the next farewell is not like this one.

Diagram 1. Access by task and season, and the leaving week

Giving access and taking it back By task, for a season, ended in the same week While someone serves A short written understanding Access by task, not by title Church work and private use apart A list of who has access to what Renewed each season, in a short chat Leaders keep the rules first. When someone leaves Access ends the same week Passwords and recovery changed Shared drives and groups checked Files returned or deleted, asked kindly Keys, devices, papers back Date written down; thanks said. A slip happens. What makes it come to light quickly? A named person and one line: tell Ana first, any time, and you will be thanked. Blame hides mistakes, and a hidden mistake cannot be put right.

In short

  • Churches rely on volunteers' own phones, laptops and accounts. The aim is simple rules, applied first to leaders and without suspicion, for devices and accounts the church does not fully control.
  • Write a short plain understanding: what you may see, what you may use it for, what you must not do, and whom to tell, with a promise of thanks.
  • Keep church work and private use apart where possible; where it is not, lock the device and limit what is on it.
  • Give access by task and for a season, keep a list of who has what, and end access in the same week a person leaves.
  • Share a single window, not a screen. Show a board only what its task needs. Make reporting a slip easy.
Front Back
Topic Volunteers, borrowed devices and handing over access: simple rules, given and taken back without suspicion.
Remember A short understanding, access by task and season, a list of who holds what, and the leaving steps done the same week, with thanks.
Caution A volunteer who fears blame will hide a slip, and a leader who does not keep the rules teaches that they are only for others.
One line to carry into ministry Make it easy to say "I made a mistake", and make ending access a way of saying thank you.
Review every summary in this course →

Check yourself

Not "did you read it" but "can you explain it". Ticks are kept on this device only.

Reflection and discussion

  • List the devices and accounts in your community that belong to a volunteer or a former volunteer and yet hold information about people. Which of them does the church know about?
  • What would you put in a half-page understanding for a volunteer in your setting? What would be the hardest sentence to say kindly?
  • Why is "access for a season" a gentler way of ending access than waiting for someone to resign? What would the renewal conversation sound like?
  • A volunteer leaves angry and still has the group chat. What do you do first, and what do you carefully not do?
  • What does a board or elder in your tradition really need to see to do its work, and what is it given only because that is simpler?
  • What one-line way of reporting a slip could your community adopt, and who should be the first to use it?

Sign in to write and keep your answers

What next

The lecture ends here. What follows was written by its readers.