IN SHORT
- If your association has a religious, philosophical or political aim, its member and donor lists are usually special-category data, even when they hold only names and addresses.
- Article 9(2)(d) lets you keep those lists for your own activities, but not share them outside the association without the consent of the people on them.
- Security must match the real risk to your members: need-to-know access, multi-factor authentication, encryption and a breach plan made before anything goes wrong.
A membership list looks harmless: names, addresses, a phone number, the date someone paid their fee. But the name of the association often says more than the list itself. If the association has a religious, philosophical or political aim, being on its list can reveal what a person believes. That changes how the data protection rules apply, and how carefully the list must be kept.
This guide is for associations (ASBL/VZW), foundations, schools and weekend schools, cultural and faith-based organisations, youth groups and parents’ associations. Most are run by volunteers with little time. The aim here is to show what the law expects, and what a proportionate set-up looks like.
When a list becomes sensitive data
The GDPR gives extra protection to “special categories” of personal data. Article 9(1) names, among others, data revealing political opinions, religious or philosophical beliefs and trade union membership, and data concerning health. Processing these is prohibited unless one of the exceptions in Article 9(2) applies.
The data does not have to state a belief outright. In 2022 the Court of Justice held that data which can reveal a sensitive characteristic indirectly, by deduction or by cross-referencing, also falls within Article 9 (OT, C-184/20). For an association, that means:
- a member or donor list of a religious, philosophical or political organisation is usually special-category data, even if it holds only names and contact details;
- a pupil list of a school or weekend school with a religious or philosophical profile can be too;
- notes on the people you help (health, family situation, residence status) often are, whatever your aim.
For many associations, the most sensitive thing about a list is simply the name at the top of it.
The exception for not-for-profit bodies
Article 9(2)(d) gives associations a specific route. A foundation, association or other not-for-profit body with a political, philosophical, religious or trade union aim may process special-category data in the course of its legitimate activities, with appropriate safeguards, on three conditions:
- the processing relates only to members, former members, or people in regular contact with the body in connection with its purposes;
- it stays within the body’s legitimate activities;
- the data is not disclosed outside the body without the consent of the people concerned.
This covers most day-to-day work: keeping a member register, collecting fees, inviting members to activities. It does not cover everything.
Where you rely on consent for special-category data, it must be explicit, given for specified purposes, and as easy to withdraw as to give. Keep a record of who agreed to what.
Responsibility is not limited to the board. The Court of Justice has held that a religious community which organises and encourages its members to collect personal data during their activities can be a controller jointly with those members (Jehovan todistajat, C-25/17). What volunteers do in the association’s name is the association’s concern too.
Records and paperwork
Article 30 requires a record of processing activities. Organisations with fewer than 250 people are exempt only if the processing is occasional, unlikely to pose a risk and does not include special-category data. An association that keeps a member register with sensitive data on a regular basis therefore needs a record, however small it is.
The record does not need to be long. For each activity (members, donors, pupils, volunteers, people you help) it lists the purpose, the categories of data and people, who receives the data, how long you keep it and the security measures. It doubles as the map you need when something goes wrong.
Larger associations should also check whether they must appoint a data protection officer. Article 37(1)(c) requires one where the core activities consist of large-scale processing of special-category data.
Volunteers, phones and messaging groups
In practice, data rarely leaks from the register. It leaks from a spreadsheet emailed to a volunteer, a printed list left in a meeting room, or a messaging group in which every member can see every other member’s phone number.
Give volunteers a one-page set of rules: what they may keep, where, and for how long; no member data on shared family devices; screen lock and two-step verification on accounts used for the association; and whom to call if a phone is lost. A short session once a year does more than a long policy nobody reads.
Photos of children and events
Recital 38 of the GDPR says children merit specific protection. Photos from a school party, a camp or a religious celebration combine both concerns: the image of a child and, sometimes, the community the child belongs to.
- Ask parents for consent before publishing recognisable photos of children, separately for each use (website, social media, printed newsletter), and make it easy to withdraw.
- Once children are old enough to understand what publication means, ask them too.
- Prefer group shots from behind or at a distance for public channels. Keep identifiable photos in a closed space for families where that serves the purpose.
- Think about what a photo reveals about the place and the people in it, not only about the child.
Sharing with partners and authorities
Before you pass on any list, ask three questions. Do we have a basis to share it outside the association? Does the recipient need names, or would numbers do? Is the recipient a processor working for us, in which case a processor agreement under Article 28 is required, or a separate controller?
Requests from public bodies deserve the same care. Ask for the legal basis in writing, check that it covers the data requested, and share no more than it requires. If a request comes from outside the European Economic Area, separate rules on international transfers apply.
Security that matches the risk
Article 32 asks for measures appropriate to the risk. For an association whose members could face pressure, discrimination or worse if their membership became known, the risk is high, and the measures should follow:
- access on a need-to-know basis, reviewed when volunteers leave;
- multi-factor authentication on email, cloud storage and membership software;
- encryption of laptops, phones and exported files;
- care with where data is hosted and who can reach it, including the provider’s staff;
- a plan for suspicious contacts: approaches asking who your members are, phishing aimed at board members, or unexplained login attempts.
Where processing is large-scale, involves vulnerable people, or the risk is otherwise high, a data protection impact assessment (DPIA) under Article 35 is required before you start. The European data protection authorities’ guidelines treat sensitive data and vulnerable data subjects as risk criteria; when two or more apply, a DPIA is usually needed. Even when it is not strictly required, working through one is the clearest way to decide which measures are proportionate.
If a list leaks
A lost laptop, a list sent to the wrong group or a hacked mailbox is a personal data breach. Under Article 33 you must notify the Belgian Data Protection Authority (APD/GBA) without undue delay and, where feasible, within 72 hours of becoming aware of it, unless the breach is unlikely to result in a risk. When the risk to the people concerned is high, Article 34 also requires you to inform them, in plain language, with advice on how to protect themselves.
For a sensitive member list, high risk is the likely outcome. Decide in advance who leads, who contacts the authority and who writes to members, and keep a breach register even for incidents you do not notify.
Where to start
- Map your lists. Write down every list you keep (members, donors, pupils, volunteers, people you help), where it lives and who can see it.
- Check your basis for each. Decide whether Article 9(2)(d) covers it, or whether you need explicit consent or another ground, especially for anything you share.
- Close the easy gaps. Multi-factor authentication, encrypted devices, one register with named access, and rules for messaging groups.
- Assess the real risk. If your members could be targeted, run a structured review of threats and measures, and prepare your breach response before you need it.
Sources
- Regulation (EU) 2016/679 (GDPR), Articles 9, 30, 32, 33, 34, 35, 37 and recital 38
- Court of Justice, judgment of 1 August 2022, OT, C-184/20, data that indirectly reveals special categories
- Court of Justice, judgment of 10 July 2018, Jehovan todistajat, C-25/17, a religious community as joint controller with its members
- Article 29 Working Party, Guidelines on data protection impact assessment (WP248 rev.01), endorsed by the EDPB
- EDPB Guidelines 9/2022 on personal data breach notification
- Belgian Data Protection Authority (APD/GBA), breach notification and guidance
- Droits Quotidiens, photos of children by schools and crèches, parental consent in Belgian practice
General information, checked on 2 November 2026. Rules and decisions change, and every situation is different: this is not advice on your own case.
The information in this article is current as of 16/11/2026.
