GDPR applies to any organisation processing personal data of EU and UK residents, regardless of sector. Nonprofit organisations face a specific configuration of obligations shaped by the personal data they collect, the regulatory environment they operate in, and the systems they use to do it.
This page covers the GDPR obligations specific to Nonprofit, the lawful bases that apply, and the implementation approach that survives supervisory authority scrutiny.
Regulatory context
Supervisory authority: National supervisory authorities + charity regulators
Key personal data categories: donor records, beneficiary records, volunteer data, donation history, Gift Aid declarations
Special category data present: Yes — requires Article 9 lawful basis in addition to Article 6
Primary lawful bases: Consent (donor marketing), Legitimate Interests (donor stewardship), Legal Obligation (Gift Aid), Contract (employment/volunteering)
Nonprofits serving vulnerable populations often process special category data about beneficiaries — health conditions, ethnicity, religion, political opinions. The lawful basis for processing beneficiary data is typically legal obligation or vital interests (Article 9(2)(b) or (c)), not consent — because consent from a beneficiary in a dependent relationship may not be freely given.
The hard part
Legacy databases frequently contain donor data with no documented lawful basis from before May 2018. A remediation programme is required before that data can legally be used for marketing — and the channels available to seek reconsent are limited to those for which valid consent already exists.
This is the implementation decision that most Nonprofit GDPR programmes get wrong. It is also the issue most likely to appear in a supervisory authority audit or a data subject complaint.
Required controls
- Separate consent models for donors, volunteers, and beneficiaries
- Legacy data audit with documented remediation programme
- Special category data (beneficiary health/circumstance records) under explicit consent or legal obligation
- Gift Aid records retained per HMRC schedule (6 years)
- DSAR workflow spanning CRM, grants management, and finance systems
GDPR gap assessment framework for Nonprofit
A gap assessment for a Nonprofit organisation covers five areas:
1. Data inventory and ROPA
Map every system that holds personal data specific to Nonprofit operations: donor records, beneficiary records, volunteer data, donation history, Gift Aid declarations. Document the purpose, lawful basis, retention period, and third-party recipients for each. The ROPA must be current — a snapshot taken at implementation and not updated is not compliant.
2. Lawful basis audit
For each processing activity, confirm the lawful basis is documented and appropriate. Nonprofit organisations frequently find that processing that was assumed to be covered by legitimate interests has not had a Legitimate Interests Assessment completed. Where special category data is present, Article 9 requires a separate documented basis.
3. Consent management
Where consent is the lawful basis, verify that consent records meet GDPR Article 7 requirements: freely given, specific, informed, unambiguous, and withdrawable. Legacy consent from before the current privacy notice version should be assessed for adequacy.
4. DSAR readiness
Test the DSAR workflow with a synthetic request. The test should cover: intake, identity verification, data discovery across all systems identified in the data inventory, response assembly, and delivery within the 30-day deadline. Most Nonprofit DSAR gaps are discovered at the data discovery stage — systems that hold personal data but are not connected to the DSAR workflow.
5. Breach preparedness
Verify the incident log, the severity classification matrix, and the 72-hour notification workflow. The Nonprofit-specific question is: which data categories, if breached, trigger notification to individuals (not just to the supervisory authority)? Notification to individuals is required where the breach is likely to result in high risk to their rights and freedoms.
Implementation priority order
For Nonprofit organisations starting a GDPR programme:
- Data inventory — identify all systems holding personal data before configuring any controls
- Lawful basis documentation — stop processing for which there is no documented basis
- DSAR workflow — rights requests can arrive at any time; the workflow must be operational before launch
- Consent remediation — address legacy consent before running any marketing to the affected population
- ROPA — live, connected to source systems, reviewed quarterly
- Breach procedure — tested annually; DPO and legal team both trained on the 72-hour obligation