September 24, 2026

What Happens to Your Members When a Church Database Is Hacked

If you pastor a church, you hold information about people. Names. Phone numbers. Who is new. Who asked for prayer. It may live in a notebook, a spreadsheet on your laptop, or an app on your phone. Wherever it lives, it can be taken. That is the uncomfortable beginning of any honest conversation about a church data breach: the question is not whether your church keeps records, but what happens to the people in those records if the records are ever opened by someone who should not have them.

Many pastors tell me some version of the same thing. I am not a technical person. This is not my world. I understand that. So let me try to make it as plain as I can, because the consequences land on your members, not on your computer servers.

Writing things down is not the problem

Before anything else, let me say clearly: keeping notes about your people is not a failure of trust. It is part of caring well.

Paul wrote letters full of particulars. He named people. He addressed quarrels between two women in Philippi by name. He remembered Timothy’s mother and grandmother, and he remembered Timothy’s stomach. He knew who was sick, who had wandered, who had been a help to him. “Besides those things that are outside, there is that which presses on me daily: anxiety for all the assemblies” (2 Corinthians 11:28). You cannot carry anxiety for people you cannot remember.

So the instinct to write things down is a shepherd’s instinct, two thousand years old. What has changed is not the instinct. What has changed is where the writing goes.

Where your member list actually lives

Here is the part nobody explains to pastors.

When you type a member’s name into an app or an online spreadsheet, that information does not stay on your phone. It travels to a computer owned by the company that makes the app, or more often to a computer that company rents from a hosting provider. A hosting company rents out computers the way a storage firm rents out units. Thousands of unrelated businesses keep their data in the same building, so to speak.

This matters for one reason. Your church might have excellent habits, strong passwords, a careful team. And your members’ data can still be exposed because a company you have never heard of, several steps removed from your Sunday morning, was broken into. Every door can be forced, given enough time and a determined enough person. That is simply the nature of doors.

This is not theoretical. In 2023, security researchers found that a Brazilian church software provider had left a database exposed online; the files contained personal data belonging to roughly 932,000 church members, and researchers warned the information could be used for targeted phishing, identity theft and doxxing. In 2022, The Church of Jesus Christ of Latter-day Saints disclosed that attackers had reached systems holding members’ usernames, full names, email addresses, birthdates, mailing addresses and phone numbers. Small congregations are affected too: a Presbyterian church in the United States notified around 1,000 people after an external breach of its systems in early 2026.

None of those churches were careless about their people. They simply trusted a system, as we all must.

Why a leaked church list is not like a leaked shop list

If my own name and email leaked tomorrow, I would shrug. I am an engineer with a public profile; I am already findable. But a church list is not a customer list, and this is the heart of the matter.

A church list tells the reader what you believe.

European law recognises this explicitly. Under Article 9 of the GDPR, personal data revealing religious or philosophical beliefs is a special category whose processing is prohibited by default, permitted only under specific conditions such as explicit consent. The law treats a name attached to a church the way it treats medical records, because both can be used to hurt the person they describe. (I am a software engineer, not a lawyer, and this is general information rather than legal advice.)

Think about who sits in your pews.

The convert from a hostile country. Someone who came to faith from a Muslim family, who still travels home to see relatives. A leaked list places her name, her phone number and her church in searchable form. Open Doors’ 2026 World Watch List reports 388 million Christians facing high levels of persecution and discrimination, more than one in seven believers worldwide. For that sister, a breach is not an inconvenience. It is a risk to her freedom and possibly her safety.

The couple who asked you to pray over their relationship. They came forward together one Sunday. The prayer request was recorded, with two names attached. A year later the relationship ended. Neither of them would choose to have that moment published, and neither of them ever imagined it could be.

The man who wrote one honest sentence about his depression in the space you provided for prayer requests, because he trusted that it would go no further than you.

A retail breach costs people money. A church data breach costs people their privacy about the most tender things in their lives: faith, marriage, addiction, grief, fear.

The damage that lasts longest is the silence

Money can be replaced. Trust cannot, or not quickly.

What I fear most is what happens the week after. Members stop writing anything down. They give a nickname only. They stop bringing prayer requests. They carry the same burdens into the same building and hand none of them over. And they carry that caution into the next church, and the one after that.

Paul’s picture of the church is a body. “If one member suffers, all the members suffer with it” (1 Corinthians 12:26). A body works because the parts report to each other. When a toe goes numb, the injury does not stop; the knowledge of it stops. The damage continues quietly and unnoticed.

That is why a breach is not only a technical event. It is a pastoral one.

The paper notebook is not the safe alternative

Some pastors react by going backwards: no software, just a book. I understand, but a book has its own failure modes. It can be left on a train. It can go missing during a move to a new building. It can be handed to a leader working on a family situation and never come back. And unlike a digital record, you rarely find out that it has been read.

The goal is not to avoid technology. The goal is to make sure that if the worst happens, there is nothing readable to take.

What encryption changes

This is the one technical idea worth a pastor’s time, and it is simpler than it sounds.

Encryption turns readable information into something meaningless. A name, a phone number, a prayer request becomes a jumble that no one can interpret without the right key. In a zero-knowledge system, that key belongs to your church and to the people you choose, and not to the company providing the software.

That is how Velyora is built. Your members’ names, contacts, birthdays and prayer requests are locked on their own device before they ever reach us. I cannot read them. If someone broke into the systems where that information sits, they would find nothing they could turn back into a human being. No name to match to a church. No relationship to expose. No prayer request to publish or ransom.

I would rather no attack ever came. But I would rather also that, if one did, the honest answer to your congregation could be: they took a locked box and no key exists that opens it.

You do not need to understand cryptography to give your people that. You only need to choose tools that were built with them in mind. And if you are wondering about gentle follow-up more generally, the same care applies to noticing the teenager who quietly stops showing up: knowing matters, and protecting what you know matters just as much.

Frequently asked questions

Is my small church really a target for a data breach?

Attackers rarely pick churches by name. They find weak systems, and they take whatever is inside. A congregation of eighty can be exposed through the same provider as a congregation of eight thousand, and the church in the example above notified about 1,000 people after an external breach. Size offers no protection.

Does GDPR apply to a church?

Generally yes, if you are in the EU/EEA or handle data of people who are. Article 9 treats information revealing religious beliefs as a special category, prohibited from processing unless a specific condition such as explicit consent applies. A membership list attached to a church usually reveals belief by its very existence. This is general information, not legal advice; for your own situation, speak to a qualified adviser in your country.

What should we do if our church data is breached?

Contain it, find out what was taken, and tell your members honestly and quickly rather than hoping it passes. Depending on where you are, you may have a legal duty to notify your data protection authority within a short deadline. Get proper legal guidance early. Pastorally, reach out first to the members most at risk, such as converts from hostile contexts.

Does encryption mean we can stop being careful?

No. Encryption protects the information you store. It does not decide what you collect, who you give access to, or how long you keep it. Collect only what serves your care of people, give each helper access only to the people they actually serve, and review it once a year.

Can I still keep prayer requests at all?

Yes, and I think you should. Prayer requests are one of the clearest signs that a church is a family and not an audience. Keep them because you will pray over them, tell people plainly how they are protected, and make sure they are unreadable to anyone outside the circle of care you have defined.

The name Velyora comes from velad y orad, watch and pray. Watching over a flock means knowing your people. Protecting them means making sure that knowledge stays where it belongs. If you would like to see what private, encrypted check-in looks like for your congregation, you can try Velyora free and have your QR code ready before Sunday.