Data, Systems & Processes (DSP)
Data Team onboarding
Welcome
The Liberty Church
The Liberty Church · Data, Systems & Processes

Handling people’s data with care

Everything you need before you serve on the Data Team, in five steps: GDPR training, cyber security, our Code of Conduct, your confidentiality agreement and a skills profile. About 35 minutes, and your progress saves as you go. If you have done any of these before, we recognise your email and skip them.

~35 min 5 steps Pass to continue
“Know well the condition of your flocks, and give attention to your herds.”
Proverbs 27:23

Before you begin

We record each step you complete so access can be granted. Your details are matched against our records in Planning Center. We also use your email to check what you have already completed.

We use this only to record each step, grant the right access and plan your training. Nothing else.

How we handle this We collect your name, email and location to record each step you complete, to grant access at the right level and, through your skills profile, to plan training. Our lawful basis is our legitimate interest in handling member data safely. Your entry is kept only as long as you serve in a role that needs this access, then removed. It is stored on this device as you go and sent to the church as you finish each step. This is the same standard the training itself asks of you.
Module 1 of 8

Why this matters

Behind every record is a person who trusted us with something personal.

It might be their phone number, or where they live. It might be a prayer request, or the fact that they are walking through something hard and have only told one person at church.

Under the UK GDPR and the Data Protection Act 2018, a church is held to exactly the same standard as any other organisation. Charitable status changes nothing. Get it badly wrong and the regulator can act.

But the deeper reason is pastoral. People hand us their information as an act of trust. Guarding it well is part of how we care for them. Handled carelessly, data becomes a way people get hurt. Handled faithfully, it is quiet, ongoing pastoral care.

What getting it wrong looks like: a home address reaching the abusive ex-partner someone moved to escape. A prayer request shared in confidence, repeated to someone who had no need to hear it: at small group, over coffee, even to a spouse. A spreadsheet of members on a personal laptop that gets stolen. None of these need a hacker. Each one starts with an ordinary person being casual with data.

This module distils, for your role at TLC, the ground covered by hours of professional privacy training. Optional LinkedIn Learning courses for deeper study are linked on your completion screen.

Takeaway

Data is people, not numbers. Guarding it well is part of how we shepherd them.

Module 2 of 8

The seven principles

The whole of the law rests on seven ideas. Here they are in plain English, following one member - call her Grace - from the connect card she fills in on her very first Sunday.

1

Lawfulness, fairness & transparency

We are open about what we collect and why. Grace fills in a connect card and can see it is the church asking, and what for.

2

Purpose limitation

We use data only for what we said. Grace gave her number for a follow-up call, not to be added to an unrelated appeal.

3

Data minimisation

We collect only what we need. To invite Grace to a newcomers’ lunch we need a name and a contact, not her income.

4

Accuracy

We keep records right and current. Grace moves house; we update it promptly and fix mistakes when we spot them.

5

Storage limitation

We do not keep data forever. If Grace drifts away for years, her record is reviewed, not hoarded.

6

Integrity & confidentiality

We keep data secure. Grace’s details stay inside approved systems, seen only by people who need them.

7

Accountability

We can show we do all of this. Every action under your login is logged, so the church can prove it handled Grace’s data well.

Takeaway

Collect little, keep it right, hold it safe, and be able to show it.

Module 3 of 8

What counts as sensitive

All of it is personal data: name, phone, email, address, attendance, serving history. It all deserves care.

Some of it is special-category data, which the law protects far more tightly because mishandling it can cause real harm. On this team, that means:

Pastoral care notes Safeguarding information DBS checks (Disclosure and Barring Service) Health needs
Children & young people

Anything about an under-18 - a child in kids’ church, a teenager in youth - carries extra weight. Handle it with special care and never share it beyond the people directly responsible for their care.

In your ordinary week this is not abstract. A first-timer card, a check-in list, a small group register, a photo consent form, a note that Grace asked for prayer about her health: every one is personal data, and the last one is special-category. If Grace mentioned her diagnosis on her connect card, that detail now carries the heaviest duty of care in this module, even though it arrived on a small piece of card on a Sunday morning.

What these mean in practice

Safeguarding information is anything about the protection of children or vulnerable adults: a concern raised, an incident record, or a restriction on someone’s serving. DBS information is a person’s Disclosure and Barring Service record, the UK criminal-records check required for roles with children or vulnerable people. Both are held on a restricted list that this team never touches: if one ever reaches you by mistake, do not read on, do not forward it, and tell the Data Lead the same day.

Takeaway

Pastoral, safeguarding, DBS and health data carry the heaviest duty of care. Handle them as you would want yours handled.

Module 4 of 8

What you see, you hold

The biggest risk in a church is not a hacker. It is a loose word at small group.

Serving on this team, you will see things. That a couple is in counselling. That someone has fallen behind on giving. That a name sits on a safeguarding list. You see it because a task needs you to, not because it is yours to carry into the rest of your week.

So the rule is simple and it is sacred: what you see in service, you hold in confidence. You do not mention it to a friend, a fellow volunteer, or your spouse. Not as gossip, not as a prayer point, not as “you won’t believe what I saw.”

How it happens in real life: you were updating records and saw that Grace has stepped back from serving and is receiving pastoral care. On Sunday a mutual friend asks, “Is Grace okay? I have not seen her around.” The kind, correct answer gives nothing away: “I am not sure, why not drop her a message? I am sure she would love to hear from you.” Grace’s story is hers to tell, not yours. That one sentence is this whole module in practice.

Discretion is pastoral care

Holding someone’s story in confidence is not secrecy. It is how you honour the trust that let them tell it in the first place.

Takeaway

What you see while serving stays with you. Discretion is part of the ministry, not a limit on it.

Module 5 of 8

The golden rules

These are not suggestions. They exist so member data never leaves the church’s control. The Volunteer Confidentiality Agreement you sign repeats these same rules.

Your approved device only. Whether church-issued or your own personal device, it must be password-locked, auto-locking, and kept up to date.

Nothing comes off the system. No downloads, no screenshots, no photos, no printing of member data.

View-only means view-only. If you have view access, copying or reproducing it is not allowed.

Work lives in Planning Center (PCO) and SharePoint. Not in your email, not in your camera roll, not in a personal cloud drive. Paper counts too: a first-timer card or printed list is personal data, so hand it in or destroy it once entered, never take it home.

One source of truth. No shadow spreadsheets, no private copies, no unofficial databases.

Your login is yours alone. Never share it, never use someone else’s, never leave a logged-in device open to others. Everything done under your login is recorded as you.

A real example

A volunteer borrows a colleague’s laptop that is still logged in to Planning Center, just to “quickly check something.” That is a breach. The action is now recorded against someone else, and the data has been seen on an unapproved session. Log in as yourself, on your own device, every time.

Takeaway

If data stays in Planning Center and SharePoint, on your device, under your login, you are doing this right.

Module 6 of 8

Only what your role needs

Access is scoped to your role and your location. You get exactly what you need to serve, and no more. There are three levels.

Level 1

Data Volunteers

Can: view member records for assigned tasks, update attendance, update approved profile fields, view serving information.
Cannot: financial or giving records, safeguarding, DBS or staff records; no unrestricted exports; no managing permissions.

In practice: you are updating attendance after a Sunday service and notice the profile also shows a giving tab. Your task is attendance, so the giving tab is not for you, even though the system may let you click it. Access being possible is not the same as access being yours.

Level 2

Data Lead

Can: view and update records, run reports, review and oversee data quality, manage volunteer assignments.
Cannot: safeguarding, HR or confidential staff records, unless specifically authorised.
Level 3

Data Owner · Staff

Owns: permissions, audits, authorised exports, and breach and compliance management.
Takeaway

If a task needs data your level cannot see, you do not work around it. You ask. That is the system working.

Module 7 of 8

Spotting and reporting a breach

A breach is any time data is lost, seen, or sent where it should not be. Most are honest mistakes. What matters is what you do next.

What a breach can look like

Sending information to the wrong person
A lost or stolen phone or laptop
Someone accessing data they should not
Accidental disclosure in person or writing
A phishing email or malware
CC instead of BCC on a group email, exposing every address
Data downloaded, copied or shared without authority
24h
Report it immediately, and no later than 24 hours after you become aware.

Who to tell

Either one. This is what the confidentiality agreement you sign says.

Your team lead
The Data Lead
Early reporting over blame

We would always rather hear it straight away than have it hidden. Trying to conceal a breach is the serious failure, not the breach itself.

Takeaway

Noticed something? Report it within 24 hours to your team lead or the Data Lead. Speed and honesty, every time.

Module 8 of 8

Consent and communications

We only email and message people who have agreed to hear from us. Consent must be freely given and clearly recorded. Someone giving their number for a prayer request has not signed up to a weekly newsletter. In practice: before any send, the list is checked for consent and for compliance flags, and anyone who has opted out is excluded automatically, never re-added by hand.

People can change their mind at any time. An unsubscribe or a request to stop must be honoured promptly, and it is your job to keep mailing lists clean and current.

The law allows six lawful bases for using personal data: consent, contract, legal obligation, vital interests, public task, and legitimate interests. Your role touches two. The church relies on legitimate interest to hold and administer member records, including the record that you completed this training, and on consent for messages and marketing-style communications, which is why consent must be recorded and respected without exception. When Grace unsubscribes from the newsletter, that choice is permanent unless she opts back in herself: she is suppressed from future sends automatically and is never re-added by hand, however good the reason feels.

Compliance flags

Some locations or cohorts carry a compliance flag from time to time and are excluded from communications while it is worked through case by case (Lagos is one current example). Never add flagged contacts to a mailout, and never clear a flag yourself. If you are unsure whether a contact is covered, ask before you send.

Takeaway

Message only those who agreed, honour every opt-out, and keep compliance-flagged contacts out until cleared.

Before the check

Your declaration

This is your personal commitment for completing this training. It stands on its own. It is separate from the Volunteer Confidentiality & Data Handling Agreement, which you sign after the training.

This is the heart of it. Not a form - a promise you make to the people whose data you will hold. Tap each one you commit to.

I will treat every record as a person who trusted us, not a number.

What I see in service, I will hold in confidence - I will not discuss a member’s situation with anyone outside my task.

I will work only on my approved device, inside Planning Center and SharePoint, and take nothing off the system.

I will use my own login and access only what my role needs.

If I see a breach or a mistake - mine or anyone’s - I will report it within 24 hours, without hiding it.

When I am unsure, I will ask before I act.

Made in the name of …
Knowledge check

Let’s make it stick

Sixteen quick questions drawn from what you have just read. You need 13 out of 16 to pass. When you pass, your completion screen also links optional LinkedIn Learning courses for deeper study. You will see the right answer as you go, and you can retake it straight away if you need to.

16
QUESTIONS · 13 CORRECT TO PASS
0/10

Almost there

You need 13 out of 16. Have a quick look at the ones below, then go again - you have got this.

Worth another look

Declaration made · Check passed

GDPR training complete

Your completion code
TLC-GDPR-...
Recording your completion...

Your completion is recorded automatically the moment this screen appears. The code is your personal receipt: keep it, and quote it if your Data Lead asks.

Go further · optional

This module is the required training and your completion here is what counts. If you want to go deeper, these LinkedIn Learning courses are a good next step (LinkedIn Learning licence required; they are optional and not tracked):

GDPR Compliance: Essential Training - Mandy Huth, 1h 24m. The closest match to this module; recommended for Data Leads and anyone handling data weekly.
Understanding and Prioritizing Data Privacy - Michelle Dennedy, 1h 17m. A broader foundation on why privacy matters.
Full path: Advance Your Data Privacy Skills - the complete four-course LinkedIn Learning path.

Your onboarding

Your steps

In this module
    After this module, with the Data Team
    1. 6
      Data Team inductionYour Data Lead books this with you once steps 1 to 5 are done.
      Later
    2. 7
      Systems onboardingYour church accounts and multi-factor authentication, set up with you after your induction.
      Later
    Step 3 of 5

    Code of Conduct

    How we behave as a team. Read it, then accept it at the bottom.

    THE LIBERTY CHURCH

    Data Team Code of Conduct

    Version 0.9 (draft)

    This code applies to every member of the Data Team whenever you serve, in person or online. It adapts the church’s staff code of conduct for volunteers. It sits alongside the Volunteer Confidentiality & Data Handling Agreement, which covers how you handle personal data.

    • Values. Know The Liberty Church’s vision, mission and core values, and show them in how you serve.

    • Decorum. Be professional, warm and courteous with members, guests, staff and each other, including by email and in team chats.

    • Integrity. Conduct yourself so that your reputation and the church’s are enhanced. Never use your role or your access for personal interest.

    • Honesty. Never knowingly or recklessly record, report or share false or misleading information or data. If you make a mistake, say so and help put it right.

    • Confidentiality. Do not disclose confidential information about the church, its members or partners without approval. What you learn while serving stays with the role.

    • Respect. Treat every person in the data with dignity. Do not discuss, joke about or comment on anyone’s details, including in team chats.

    • Care and process. Follow the agreed process for each task. Enter data carefully, and ask before you change anything you are unsure of.

    • Commitment. Serve when you say you will. Tell your team lead early if you cannot.

    • Representing the church. Do not speak for the church, or share church information on social media or in public, without approval.

    • Speak up. Raise concerns about conduct, data or systems with your team lead or the Data Lead. Safeguarding concerns follow the church’s safeguarding procedure.

    If this code is not followed

    Your team lead will normally talk with you first. Serious or repeated breaches may lead to removal from the Data Team, in line with the church’s policies.

    Step 5 of 5

    Your skills profile

    So we can match you to the right work and plan training. About 5 minutes. There are no wrong answers.

    How we use this Your answers go to the Data Team to plan roles and training. We keep them while you serve on the team, then remove them.
    Cyber security · Module 1 of 4

    Why churches get targeted

    Attackers go after trust. A church runs on it.

    Churches hold names, addresses, prayer requests, giving records and safeguarding notes. Most of the people who handle that data are volunteers on their own phones and laptops. Attackers know this.

    They rarely break in with clever code. They send a message that looks as if it came from someone you trust, then wait for one person to act on it.

    The scam you are most likely to see

    A message from a new number or an unfamiliar email: “Hi, it’s your pastor. I’m in a meeting and can’t talk. Can you do something for me quickly?” It ends with a request for gift cards, a payment or a login code. Pastors and staff will never ask you for these by message. Do not reply. Contact the person on the number or address you already have.

    Takeaway

    Unexpected plus urgent is the warning sign. Slow down and check through a channel you already trust.

    Cyber security · Module 2 of 4

    Spot the phish

    Phishing is a message built to make you click, open, pay or log in. It comes by email, text, WhatsApp or phone call.

    The tells

    Pressure. “Today”, “immediately”, “your account will close”.

    A sender that does not match. The name says Planning Center or Microsoft. The address says something else.

    A link that goes somewhere odd. On a computer, hover over it. On a phone, press and hold to preview it before you tap.

    A login page you reached from a message. Go to the site yourself instead: type the address or use your bookmark.

    An attachment you did not expect, even from someone you know.

    Any request for a password, a code, a payment or gift cards.

    What they look like

    “Your Microsoft 365 password expires today. Keep it here.”
    “New form submission in Planning Center: view now” from an address that is not planningcenteronline.com
    A WhatsApp from an unknown number, with a pastor’s photo, asking an urgent favour
    An invoice or “shared document” you never asked for
    Takeaway

    If a message asks you to click, pay or log in, take the long way round: check first.

    Cyber security · Module 3 of 4

    Lock the front door

    Most stolen accounts start with a weak or reused password. A leak from a shopping site can open your church account if the password is the same.

    Use three random words as a passphrase. Long beats clever.

    A different password for every account. A password manager, including the one built into your phone, remembers them for you.

    Never share a password or log in for someone else. Your account is yours alone.

    Do not save church passwords in a browser on a shared or public computer.

    Never share a code

    No one from the church, Planning Center or Microsoft will ever ask you for a login code. If a code or sign-in prompt arrives that you did not ask for, someone may have your password. Deny it, change your password and report it the same day.

    Takeaway

    Long, unique, never shared. And nobody ever needs your code.

    Cyber security · Module 4 of 4

    Look after your devices

    The phone in your pocket can open member records. Treat it that way.

    Keep your phone, laptop and browser up to date. Updates close the holes attackers use.

    Lock your screen with a PIN, password or fingerprint, and lock it whenever you step away.

    Use your own device or a church device for church systems. Never a shared or public computer.

    On public Wi-Fi, switch to mobile data or a personal hotspot before you open church systems.

    Install only the apps and browser extensions you need, from the official store.

    Log out when you finish, especially on any device someone else uses.

    24h
    Tell your team lead or the Data Lead within 24 hours if something goes wrong.

    Report it if you

    Clicked a link you now doubt
    Typed your password on a page you are now unsure of
    Opened an attachment you did not expect
    Lost a phone or laptop with church access
    See odd activity, such as emails you did not send
    Get a login code or prompt you did not ask for

    Keep the message or take a screenshot. Reporting fast is what we want, and nobody is in trouble for reporting.

    Takeaway

    Reporting fast turns a mistake into a near miss.

    Cyber security · Knowledge check

    Would you spot it?

    Ten quick questions. You need 8 out of 10 to pass. You see the right answer as you go, and you can retake straight away.

    10
    QUESTIONS · 8 CORRECT TO PASS
    Check passed

    Cyber security complete

    Your completion code
    TLC-CYB-...
    Recording your completion...
    Step 4 of 5

    Sign your agreement

    Read it in full, then sign at the bottom. The agreement sits alongside the training: you need both before access is granted. When you sign, the Data Team gets a copy for its records and we email one to you.

    THE LIBERTY CHURCH

    Volunteer Confidentiality & Data Handling Agreement

    Version 1.1 - applies to any volunteer in any Liberty Church team whose role may involve access to member personal data.

    1. Who This Agreement Applies to

    This agreement applies to all volunteers (team members) serving within The Liberty Church Global whose role may involve access to personal information relating to members, guests, visitors, volunteers, contractors, or any other individual connected with the church.

    It applies regardless of:

    • the ministry or team in which the volunteer serves;
    • the church location;
    • whether access to member information is regular or occasional;
    • whether information is accessed, viewed, recorded, stored, or shared in digital or paper format; and
    • whether access is direct or indirect in the course of service.

    Access to member personal data is granted solely for the purpose of carrying out authorised church responsibilities and is subject to the commitments set out in this agreement.

    2. What we mean by personal data

    Personal data is any information about an identifiable living person: names, contact details, addresses, dates of birth, attendance, serving history, photographs, and notes about a person. Some information carries special protection under UK GDPR and the Data Protection Act 2018, including anything about a person's health, their religious belief (which membership itself reveals), pastoral care they receive, safeguarding matters, and Disclosure and Barring Service (DBS) information. The stricter the category, the greater your duty of care.

    3. Your commitments

    By signing this agreement, the volunteer agrees to the following commitments during their time serving with The Liberty Church Global and after their service ends:

    • Purpose. Member information must only be accessed and used for the purpose of carrying out the responsibilities assigned by the church. Information must not be accessed out of curiosity or used for personal reasons.

    • Confidentiality. Never share member information with anyone who does not need it for their role - inside or outside the church, including family, friends, and other church members. What you see or hear while serving stays with the role.

    • Approved Systems: Work only in the church's approved systems. Do not copy member information into personal email, notes, photos, cloud drives, spreadsheets, or messaging apps. Paper carrying member information is handed in or securely destroyed once entered, never taken home.

      Church information, including personal data, confidential documents, reports, or internal communications, must not be entered into publicly available artificial intelligence (AI) tools or services (such as ChatGPT, Gemini, Copilot, or similar platforms) unless expressly authorised by the church and appropriate safeguards have been applied, including the removal or anonymisation of personal and confidential information where required.

    • Accounts and Security: Volunteers must use only their authorised church account and must not share login credentials or allow another individual to access church systems using their account. Where applicable, security measures such as multi-factor authentication must be maintained. Activity within church systems may be monitored and audited.

    • Care When Handling Information: Reasonable care must be taken when handling member data. This includes locking devices when unattended, avoiding displaying confidential information in public or shared spaces, and ensuring documents are stored and disposed of securely.

    • Breaches. Report any loss, mistaken disclosure, or suspected misuse of member data to your team lead or the Data Lead within 24 hours of realising, preserving rather than deleting the evidence. The church holds separate legal duties to the regulator that depend on your prompt report.

    • Rights requests: Requests from individuals to access, correct, erase, restrict, transfer, or object to the use of their personal information must not be actioned directly by the volunteer. All such requests must be referred to the Data Lead immediately upon receipt.

    • Leaving. When you stop serving in a role with data access, you will securely delete any church information you hold, return any materials, and your confidentiality commitments continue without end date.

    4. What this agreement is not

    This agreement does not make you an employee, and does not transfer the church's own legal responsibilities to you. The church remains the data controller. Your training (the GDPR & Data Handling module) is a separate requirement and completing it does not replace this agreement, nor does this agreement replace the training.

    5. If this agreement is broken

    If this agreement is not followed, the church may need to take appropriate action depending on the nature and seriousness of the breach when assessed. This may include but is not limited to the following:

    • Immediate suspension of access
    • Review of volunteer role
    • Removal from serving
    • Escalation to church leadership
    • Where a breach is intentional, repeated, or involves serious misuse of personal information, the church reserves the right to remove the individual from any role involving access to personal data and, where necessary, take further action in accordance with applicable law

    6. Your declaration

    Sign with your finger, stylus or mouse. Prefer not to draw? Choose Type.

    Your signed record How this is stored: acceptance is captured digitally with your name, email, team, the agreement version, and a timestamp, and held by the Data, Systems & Processes function as the record your access depends on. When you tap Sign and send, a PDF of this agreement with your signature is sent to the Data Team (). You can download your own copy straight after, and we email one to you too.