Personal data protection in the church: what it means to safeguard it

Every member record you fill out in your church holds more than just a name and a phone number. It holds a religious affiliation. And in Argentina, that has a precise legal name: sensitive data.

Personal data protection in the church is a topic that is almost never discussed in evangelical circles. People talk about discipleship, small groups, finances. Almost never about what happens to the spreadsheet where you note who attended last Sunday, who needs a visit, and who stopped coming.

It’s worth taking a closer look, because the law already does.

Why are a church’s data considered sensitive information?

Law 25.326 on Personal Data Protection defines “sensitive data” as information that reveals ethnic origin, political opinions, health, or religious, philosophical, or moral beliefs. Any spreadsheet that identifies someone as part of your congregation falls into that category. It doesn’t matter whether your church has fifteen members or 1,500: what defines the sensitivity of the data is its nature, not the size of the database.

This is not some unusual feature of Argentine law. It follows the same logic behind why an electoral roll cannot be freely cross-referenced with a list of members of a religious group: the mere fact of appearing there already says something intimate about a person.

What the law says about your congregation’s data

The rule starts from a strict principle: no one can be forced to provide sensitive data, and in general its collection is restricted. But it includes a specific exception worth knowing: religious associations are explicitly authorized to keep a record of their members. The law is not asking a church to stop noting who belongs to it. It is asking it to do so carefully.

That care is overseen at the national level by the Public Information Access Agency, which monitors compliance with the law. If your church stores data in a system shared with third parties, it’s a good idea to check with a legal or accounting advisor whether some type of formal registration is required. A private list in a notebook is not the same as a database shared with external providers.

What information from your church falls into this category

It doesn’t have to say “evangelical” in any field for the data to be sensitive. It is enough that the existence of the record reveals a religious belief. Among what a congregation usually handles:

• Full name and contact information for each member
• Address, when used to coordinate pastoral visits
• Attendance history for meetings and activities
• Pastoral follow-up notes, which sometimes include health or family situations
• Participation in small groups, ministries, or discipleship processes
• Records of contributions or offerings, when they are linked to a name

Follow-up notes deserve special mention. That is where even more sensitive information often slips in: an illness, a family crisis, a financial situation. That kind of data requires greater care than the rest of the spreadsheet.

Good practices for protecting that data today

You don’t need a complex system to get started. Here are some practical steps you can apply as early as this month:

1. Ask only for what you need. If a field won’t be used for anything, don’t add it to the registration form.
2. Limit who can see the full spreadsheet. Not every small-group leader needs access to the entire congregation’s data, only to the data for their own group.
3. Be careful where the information lives. A shared spreadsheet without a password, accessible to anyone with the link, is not a good place for sensitive data.
4. Tell people what their data will be used for. When someone signs up, a simple sentence explaining how that information will be used already aligns with the spirit of informed consent required by law.
5. Have a clear process for deleting data. If someone leaves the congregation and asks for their information to be removed, it helps to know exactly what steps to follow.
6. Separate administrative and pastoral information when possible. One thing is the form with name and phone number; another is the follow-up notes with personal details. They do not always need to live in the same place or be seen by the same people.

What to ask any tool that will handle your church’s data

More and more churches are moving away from notebooks and loose spreadsheets to a digital tool. Before choosing one, it’s worth asking a few questions:

• Where is the data stored, and who on that team can access it?
• What happens to the information if the church stops using the tool?
• Is it possible to correct or delete a piece of data when a member asks?
• Is there any consent step when adding a person?

These are the same questions we ask at INPERIA as we build the platform: first think about how to protect each congregation’s information, before thinking about how to display it. If you’re evaluating moving your church’s follow-up process to a digital system, you’re invited to join the waitlist, at no cost in this initial stage.

Frequently asked questions

Do I need each member’s consent to keep their data?

Yes. The law requires informed consent, although it doesn’t have to be a complicated process: it is enough to explain to the person, when they sign up, what their data will be used for.

Does an Excel spreadsheet also count as a sensitive database?

Yes. The law does not distinguish by system type, but by content. A notebook, a spreadsheet, or a cloud system are treated the same way if they store information that reveals religious affiliation.

What happens if a member asks for their data to be deleted?

Argentine regulations recognize a person’s right to request the correction or deletion of their personal data. It’s a good idea to have a simple process in place to respond to that request within a reasonable time.

Does this apply only to large churches?

No. The legal criterion is the type of data being stored, not the number of members. A congregation of twenty people is covered just the same as one of two thousand.