Back to Blog
Compliance October 30, 2026 8 min read

Donor Data at a Canadian Nonprofit: Small Team, Real Obligations

A shelter, a settlement agency, or a health charity holds information more sensitive than most banks, usually in a spreadsheet, maintained by a volunteer.

By Aparna Netheti

Donor Data at a Canadian Nonprofit: Small Team, Real Obligations

Canadian nonprofits sit in an awkward position. The privacy statutes were written mainly with commercial activity in mind, so the technical question of whether PIPEDA applies to a given charity depends on whether the activity is commercial in character, and the answer varies. Meanwhile the sector holds some of the most sensitive personal information in the country, often with one part-time administrator and a spreadsheet.

My view, offered as a practitioner rather than as legal advice, is that the coverage question is the wrong place to spend your limited attention. Whether or not a statute applies to a particular activity, a shelter that discloses a client list has caused serious harm and will lose the community's trust, and no jurisdictional analysis fixes that afterwards.

What does a nonprofit actually hold?

More categories than a comparable business, and more sensitive ones.

Donor records, including giving history, which reveals affiliations and often religious or political sympathies, plus banking details for recurring gifts, and in planned giving, estate intentions.

Client and service-user records, which in this sector routinely include health conditions, immigration status, family violence circumstances, addiction and recovery, and housing insecurity. This is among the most sensitive data held by any organization of any size.

Volunteer records, including police record check results, which are sensitive in their own right and frequently stored indefinitely in an email folder.

Board and governance material, containing personal information about directors and, in minutes, sometimes about clients or staff matters.

The pairing that creates real risk is a donor database and a client database in the same small organization, because the temptation to cross-reference them exists and the consequences of doing so are severe. A donor who is also a service user should not be identifiable as such to a fundraiser.

Where the risk actually concentrates

Not in a sophisticated attack. In ordinary operations.

The shared spreadsheet. Client or donor lists maintained in a file everyone can open, emailed between people, with copies in several inboxes and no version anyone controls.

Personal accounts and devices. Volunteers and part-time staff using personal email and personal laptops, because that is what exists. When they stop volunteering, the data does not.

Long retention by default. Records kept for a decade because nobody set a rule and storage is cheap. A ten-year archive of service-user records is a substantial liability for an organization with no security team.

Grant and funder reporting. Reports that include more detail than the funder needs, sometimes at individual level where aggregate would do.

Photographs and stories. Consent to use a client's photograph or story in fundraising material is often collected informally, years before the material is used, and rarely revisited.

What should a small organization actually do?

Five things, prioritised for a team with no dedicated staff for this.

Separate client data from donor data properly. Different systems if possible, different access at minimum. Nobody should have both unless their role genuinely requires it, and very few roles do.

Get it out of shared drives and into something with named access. The specific technology matters far less than the fact that access is individual, revocable, and logged.

Set a retention rule and act on it once a year. Even a crude rule applied consistently beats no rule. Service records with no ongoing relationship, donor records for lapsed donors, volunteer checks for people who left. One afternoon annually.

Handle photograph and story consent explicitly. Written, specific about where it will appear, and with a route to withdraw. Then honour withdrawal, including in material already published where that is possible.

Know what to do in the first hour of an incident. One page: who decides, who is told, and the triage questions that determine reporting. Most nonprofits have nothing, and the first hour is when the damage is set.

PriorityActionEffort
1Separate client and donor accessLow to medium
2Named, revocable access to filesLow
3Annual retention cleanupOne afternoon per year
4Explicit photo and story consentLow
5One-page incident procedureHalf a day, once

What about volunteers?

Volunteers create the specific problem that they are not employees, so the usual employment-based controls do not apply, and they often have the most direct contact with the most vulnerable people you serve.

Three things help. Give them accounts rather than shared logins, so access can be removed when they leave. Give them the minimum access their role needs rather than the same access as staff. And include a short data handling conversation in onboarding, focused on specific instructions rather than principles: do not photograph client documents, do not take lists home, ask before sharing anything externally.

For the underlying question of what constitutes personal information here, what counts as PII in Canada covers the categories.

This is general information, not legal advice. Whether a particular statute applies to your organization's activities is a question worth confirming with counsel.

Shielk can scan the spreadsheets, documents, and archives a small organization has accumulated, so you can see what is actually held before deciding what to do about it. See the PII scanner.

Frequently asked questions

Does PIPEDA apply to Canadian nonprofits?+

It depends on whether the activity in question is commercial in character, so the answer varies by organization and activity and is worth confirming with counsel. In practice the coverage question matters less than the harm: disclosing a client list damages people and trust regardless of which statute applies.

What makes nonprofit data especially sensitive?+

Service-user records in this sector routinely include health conditions, immigration status, family violence circumstances, addiction and recovery, and housing insecurity, and donor giving history reveals affiliations. Few commercial organizations hold a comparable concentration.

Why should donor and client data be separated?+

Because a donor who is also a service user should not be identifiable as such to a fundraiser. When both databases sit in one small organization the temptation to cross-reference exists and the consequences of doing so are severe.

How should volunteers be handled?+

Give them individual accounts rather than shared logins so access can be removed, grant the minimum their role requires rather than staff-level access, and cover specific instructions at onboarding: do not photograph client documents, do not take lists home, ask before sharing externally.

What is the highest-value action for a very small team?+

Separating client and donor access, then moving files out of open shared drives into something with named, revocable, logged access. After that, one afternoon a year applying a retention rule removes most of the accumulated liability.

nonprofit privacy Canadadonor data protectioncharity PIPEDAvolunteer records privacynonprofit data breachfundraising data

AI governance and privacy compliance, simplified.

Valdra helps Canadian companies govern AI and meet PIPEDA and Law 25, with records stored in Canada.

Try Valdra

Our own compliance

We run our own compliance programme inside Valdra, the product we sell, aligned to SOC 2 (Security criteria), ISO 27001 and ISO 42001. We do not yet have a SOC 2 report or an ISO certificate, and we do not claim certifications we do not hold.

Our Trust Centre

Measured by Valdra from our own assessments, not audited by a third party. Click the mark to open its verify page and see what it covers.