GDPR for churches made simple: what data you hold, special category data, photo consent, the ICO fee, processors, deleting data and breaches. With a checklist.
Data protection sounds like a job for lawyers. In a small church it's mostly about trust. People hand you their address, their birthday, their children's names, sometimes a prayer request nobody else knows about. They expect you to look after it.
The good news is that for a church of 30 or 150 people, GDPR is not a huge project. A few clear decisions and a bit of tidying up go a long way. There's a checklist at the end.
Note: this is practical guidance, not legal advice.
Which law applies to you?
UK churches fall under the UK GDPR and the Data Protection Act 2018. The regulator is the Information Commissioner's Office (ICO).
Irish churches fall under the EU GDPR and Ireland's Data Protection Act 2018. The regulator is the Data Protection Commission (DPC).
Churches elsewhere in the EU fall under the EU GDPR directly, plus national rules.
UK GDPR and EU GDPR are almost identical on the points below. If your church belongs to a denomination or diocese, check for its own guidance and templates.
Step 1: Write down what you hold
Most churches end up with something like this:
Members and regular attenders: names, addresses, phone numbers, email, birthdays, family links
Children and young people: names, ages, parents' contacts, allergies, who may collect them
Giving: amounts, bank details, Gift Aid declarations
Volunteers: rotas, groups, safeguarding and DBS check records
Photos and video from services, holiday clubs and events
For each one, note where it lives and who can see it. Often the honest answer is "a spreadsheet on someone's laptop". Our post on moving your member list off Excel and WhatsApp covers how to fix that.
Step 2: Faith is special category data
Simply being on your church list says something about a person's religious belief. Under Article 9 that is special category data, just like the health details that often turn up in prayer requests.
Churches have a specific condition for this: Article 9(2)(d). A not-for-profit body with a religious aim may process this data in the course of its legitimate activities, with appropriate safeguards, as long as it relates to with it. The data must .
members, former members, or people in regular contact
not be shared outside the church without consent
What this means in practice:
For your membership list you usually don't need separate consent.
For a one-off visitor it doesn't apply automatically. Ask before you store their details.
Prayer requests and pastoral notes belong with very few people.
Step 3: Know your lawful basis
Every use of personal data needs a lawful basis under Article 6. In a church the usual ones are:
What
Typical lawful basis
Managing membership
Legitimate interests (or your membership terms), plus Art. 9(2)(d)
Giving records and Gift Aid
Legal obligation (tax and accounting rules)
Newsletter, WhatsApp group
Consent
Photos on the website or social media
Consent
Birthday list in the notice sheet
Consent
Consent must be freely given, clear, recorded and easy to withdraw. A plainly worded tick box on your welcome card is fine, if you keep the card.
Step 4: Write a privacy notice
People have a right to know what you do with their data (Article 13). One page is enough:
Who you are and how to contact you
What you collect, why, and on what basis
Who you share it with (for example your software provider or denomination)
How long you keep it
Their rights: access, correction, deletion, and complaining to the ICO or DPC
Hand it out when people join, pin a copy on the noticeboard and link it from your website. For what else belongs there, see our small church website checklist.
Step 5: Photos, newsletters and WhatsApp
Photos. For church photo consent, the rule of thumb is simple: the more public the use, the clearer the consent. For the website, Facebook or a printed magazine, get written consent. For children, a parent or guardian signs, and it's good practice to ask older children too. A sign at the door ("Photos are being taken today") helps, but doesn't replace consent for publishing. Offer a camera-free seating area.
Newsletters. Consent only, and every email needs a way to unsubscribe. Electronic marketing also falls under PECR in the UK.
WhatsApp groups. In a group, everyone can see everyone's number. So never add someone without asking. For announcements, a channel or a community with an announcement group is often a better fit. And remember: the WhatsApp group is not your member list.
Step 6: Decide who sees what
Not everyone needs everything. A simple set of roles:
Minister or church leadership: people and pastoral care
Church secretary or administrator: addresses and contacts
Treasurer: giving and bank details, nothing more
Group leaders: their own group only
Add a few habits: no member lists on personal laptops or USB sticks, no exports in private cloud folders, strong passwords, and when someone steps down, their access goes too. Ask volunteers with access to sign a short confidentiality agreement.
Step 7: Keep a record of processing
A record of processing activities (Article 30) is just a table. The small-organisation exemption usually doesn't help churches, because the processing is regular and includes religious data. For each line: purpose, people involved, types of data, who receives it, how long you keep it, and how you protect it. Your list from Step 1 is half the work. The ICO offers templates.
Step 8: Contracts with software providers
If you use church software, cloud storage or an email service, that provider is a processor acting on your behalf. You need a written contract with the terms set out in Article 28. Also check where the data is stored. More in choosing church management software.
Step 9: The ICO fee and a DPO
ICO data protection fee. UK organisations that process personal data must pay an annual fee to the ICO unless they are exempt. There is an exemption for not-for-profit organisations, but it is narrow: broadly, it covers processing only for membership, supporting the organisation and its activities. Things like CCTV can take you outside it. Check with the ICO's online self-assessment. Irish organisations don't have an equivalent fee.
Data Protection Officer. A DPO is mandatory for public authorities and for organisations whose core activity involves large-scale processing of special category data or systematic monitoring. A small local church is usually not in that position.
Step 10: Delete what you no longer need
Put a date in the diary once a year:
People who have moved away or left: delete their contact details, unless you must keep something
Prayer requests and event sign-up lists: delete them soon after
Step 11: Breaches and access requests
Data breaches. A laptop is stolen, a list goes to the wrong group? Time matters. Reportable breaches must be reported to the ICO or DPC within 72 hours of becoming aware (Article 33). If the risk to people is high, tell them too. Agree in advance who handles this, and log every breach.
Subject access requests. Anyone can ask what data you hold about them (Article 15). You normally have one month to respond, free of charge.
Checklist
Confirmed which law applies (UK GDPR or EU GDPR) and checked denomination guidance
Listed all data you hold and where it lives
Noted the lawful basis for each use
Privacy notice written, handed out and on the website
Consent recorded for photos, newsletters and birthday lists
Nobody added to WhatsApp groups without asking
Roles and access agreed, no lists on personal devices
Record of processing activities set up
Article 28 contracts in place with every software provider
ICO fee self-assessment done (UK)
Yearly clean-up date in the diary
Plan for breaches (72 hours) and access requests (one month)
Where Churchtable fits
Churchtable won't make these decisions for you, but it makes them easier to live by. Your data is hosted in the EU, belongs to your church and can be fully exported at any time. Religious data sits in separate, access-restricted tables, and on Pro your secretary, treasurer and group leaders get their own logins with the right roles. The free plan for up to 30 people and all pricing are on the home page.