How Nonprofits Can Protect Donor Information From Cybersecurity Threats
Donor information is among the most sensitive data a nonprofit organization manages. Names, contact details, donation histories, and confidential fundraising records support donor relationships and future campaigns. They also require protection against unauthorized access, accidental disclosure, and cyberattacks.
Nonprofit donor data security involves protecting this information wherever it is stored, accessed, or shared. That includes donor management software, employee computers, email, cloud storage, and third-party fundraising platforms.
For nonprofit leaders, the starting point is understanding where donor information resides, who can access it, and what safeguards are in place. These questions are particularly important for organizations that rely on a small administrative team or outside technology providers.
Organizations that need help evaluating their technology environment can work with a provider experienced in IT services for nonprofits to identify security weaknesses and establish appropriate safeguards.
What Donor Information Do Nonprofits Need to Protect?
A nonprofit's donor database may contain considerably more information than names and email addresses.
Depending on the organization's fundraising activities, records can include:
- Personal information: Names, mailing addresses, phone numbers, and email addresses.
- Donation history: Contribution amounts, donation dates, recurring gifts, and fundraising campaign participation.
- Financial information: Transaction references, billing details, and limited payment information provided by payment processors.
- Donor communications:Correspondence, meeting notes, giving preferences, and relationship-management records.
- Organizational information: Corporate sponsorship contacts, employer details, and matching-gift information.
- Restricted or confidential records: Anonymous giving preferences, planned-giving discussions, or information about major donors.
Not every nonprofit collects all these details. The information held depends on the fundraising platforms, donor management practices, and services the organization provides.
An important first step is identifying which information is necessary to retain. Keeping unnecessary personal or financial details increases the amount of information that must be protected.
For example, a development team may need access to a donor's giving history to prepare a fundraising campaign. It generally does not need to retain complete payment card information in a spreadsheet or shared folder.
Donor confidentiality preferences also deserve attention. If a supporter requests anonymity, that preference should be reflected in reporting and information-sharing procedures so identifying details are not unnecessarily disclosed.
The goal is to maintain useful fundraising records while limiting unnecessary exposure.
Where Is Donor Information Stored and Shared?
Donor data rarely remains inside one application.
A nonprofit may maintain its primary records in a customer relationship management (CRM) system, but employees often use the same information in other applications.
Common locations include:
| System or location | How donor information is used | Potential security concern |
|---|---|---|
| Donor management or CRM software | Maintains donor profiles, giving history, and fundraising activity | Excessive user permissions or compromised accounts |
| Microsoft 365 or Google Workspace | Stores reports, spreadsheets, and shared documents | Files shared with unintended recipients |
| Email systems | Sends donor communications and internal fundraising reports | Sensitive attachments or phishing attacks |
| Online donation platforms | Processes contributions and provides transaction records | Weak account security or unclear vendor responsibilities |
| Event registration systems | Manages attendees, sponsors, and ticket purchases | Data exported or retained unnecessarily |
| Accounting software | Reconciles donations and financial transactions | Broader access to financial records than required |
| Employee computers | Downloads and processes fundraising reports | Unprotected devices or locally stored files |
The challenge is maintaining appropriate protection after information leaves its original system.
Consider a development director who exports a donor report from the CRM to prepare an annual fundraising campaign. The file is saved to a laptop, uploaded to a shared folder, and emailed to an outside mailing vendor.
Each copy creates another location where donor information may be accessible.
A secure donor database cannot protect every copy of information exported from it.
Nonprofits should review their fundraising workflows and establish approved methods for storing, sharing, and deleting donor records.
Who Should Have Access to Donor Records?
Access to donor information should reflect each person's responsibilities.
A development director may need detailed donor histories and reporting capabilities. An event coordinator might need attendee names and contact information for a specific event. A volunteer checking in guests may only need access to an attendance list.
Providing all three users with the same level of access creates unnecessary exposure.
Assign Permissions Based on Job Responsibilities
Most established donor management systems provide some form of user permissions.
Depending on the platform, administrators may be able to control who can:
- View individual donor profiles.
- Access donation histories and financial reports.
- Export complete donor lists.
- Edit or delete donor records.
- Manage user accounts and permissions.
- Access confidential donor notes.
Nonprofits should configure these permissions around actual responsibilities rather than giving every user broad access for convenience.
The ability to export donor records deserves particular attention. A user who can download an entire database may be able to move thousands of records outside the organization's normal security controls.
Avoid Shared Accounts
When several employees use the same CRM login, it becomes difficult to determine who accessed or modified donor information.
Individual accounts improve accountability and allow administrators to remove one person's access without affecting everyone else.
Shared passwords also increase the risk of former employees or volunteers retaining access after their involvement ends.
Review Access Regularly
Permissions should be reviewed when responsibilities change and periodically throughout the year.
Development directors and operations managers should be able to answer three questions:
Who currently has access to the donor database?
Which users can export or delete donor information?
Are any accounts assigned to people who no longer work with the organization?
A short review can reveal unnecessary permissions that have accumulated over time.
Essential Donor Data Security Measures for Nonprofits
A donor management platform may include strong security features, but those protections depend on how the organization configures and uses the system.
The following safeguards should form the foundation of nonprofit donor data security.
Require Multifactor Authentication
Multifactor authentication (MFA) requires an additional verification step when someone signs in.
For example, after entering a password, a user may need to approve the login through an authenticator application.
This reduces the likelihood that a stolen password alone will allow someone to access donor records.
MFA should be enabled for donor management platforms, email accounts, administrative accounts, and other systems containing sensitive information whenever supported.
Protect the Computers Used to Access Donor Records
A secure cloud application can still be accessed from an infected or poorly maintained computer.
Employees who work with donor information should use devices with:
- Current operating system and application updates.
- Endpoint security protection against malicious software.
- Screen locks and appropriate sign-in controls.
- Encryption to protect locally stored information if a device is lost.
- Approved methods for accessing and storing organizational files.
These protections are especially important when employees work remotely or use laptops outside the office.
Secure Networks ITC provides cybersecurity services to help organizations protect employee devices, email systems, networks, and sensitive information from unauthorized access.
Secure Administrator Accounts
Administrator accounts can often change permissions, configure integrations, or access large amounts of data.
These accounts should be assigned only to authorized personnel, protected with MFA, and used for administrative tasks rather than routine fundraising activities where the platform supports separate roles.
Organizations should also understand who holds administrative access on behalf of an outside consultant or technology provider.
Review Security Features and Vendor Responsibilities
Before adopting a donor management system, nonprofit leaders should understand what security protections the vendor provides.
Useful questions include:
- Does the platform support MFA and role-based permissions?
- Can administrators review account activity or data exports?
- How does the vendor protect stored information?
- What happens if the vendor experiences a security incident?
- How can the organization retrieve its information if it changes platforms?
- Which security settings must the nonprofit configure itself?
Vendor-provided security does not eliminate the organization's responsibility for managing users, permissions, and day-to-day handling of donor information.
SECURE NETWORKS ITCYour Nonprofit Deserves Reliable IT Support
20 years of experience supporting San Diego organizations. Get unlimited IT support, proactive cybersecurity, and predictable monthly pricing from a Microsoft Certified Partner.
IT Support for San Diego Nonprofits
Local expertise. Long-term partnership.
Protecting Donor Information During Fundraising Activities
Some of the most significant opportunities for accidental data exposure arise during routine fundraising work.
Development teams regularly prepare mailing lists, organize events, share reports with board members, and coordinate with external partners.
Fundraising data security also depends on how employees handle donor lists after exporting them from the organization's primary database.
Common Fundraising Activities That Require Safeguards
| Fundraising activity | Potential exposure | Recommended safeguard |
|---|---|---|
| Exporting donor lists | Complete records saved outside the CRM | Limit exports and use approved storage locations |
| Sharing fundraising reports | Confidential details sent to unintended recipients | Use controlled file sharing and verify recipients |
| Organizing fundraising events | Volunteers receive unnecessary donor information | Provide task-specific access or limited lists |
| Working with mailing vendors | External companies retain donor files | Review data handling, retention, and deletion procedures |
| Preparing board reports | Detailed donor records distributed too broadly | Share summarized information when individual records are unnecessary |
| Coordinating campaigns | Multiple copies of donor spreadsheets circulate | Maintain an approved source and remove outdated copies |
Use Secure File Sharing Instead of Uncontrolled Attachments
Email attachments can be difficult to manage after they are sent.
If a donor spreadsheet is emailed to several people, the organization may lose visibility into where those copies are stored and who can access them.
When appropriate, a secure cloud-sharing system can provide greater control through individual permissions, restricted links, and access removal.
For nonprofits using Microsoft 365, properly configured SharePoint and OneDrive permissions can help manage access to fundraising documents.
However, employees still need clear instructions about which information may be shared and with whom.
Limit Information Provided to Outside Partners
Mailing companies, event organizers, fundraising consultants, and other vendors may need certain donor details to complete their work.
They should receive only the information necessary for the agreed activity.
For example, a mailing vendor may need names and postal addresses but not donation histories, confidential notes, or other financial details.
Before transferring donor records, establish how the information will be transmitted, who may access it, how long it will be retained, and when it should be deleted.
These decisions should be documented rather than left to informal email arrangements.
Establish Rules for Donor Data Exports
A practical donor information policy should explain:
- Who may export donor records.
- When an export is appropriate.
- Where downloaded files may be saved.
- How files can be shared externally.
- When temporary copies must be deleted.
How to Protect Online Donations and Payment Information
Online donations introduce additional responsibilities because supporters may provide payment information through a website, fundraising platform, or event registration service.
Most nonprofits should avoid collecting or storing complete payment card details themselves unless there is a legitimate operational need and appropriate security controls.
Using a reputable payment processor can reduce the amount of sensitive card information handled directly by the organization.
However, using a third-party payment processor does not automatically remove all payment security responsibilities.
The PCI Security Standards Council explains that organizations outsourcing payment processing still have responsibilities related to service-provider oversight and applicable payment card security requirements.
What Nonprofit Leaders Should Verify
When reviewing online donation systems, confirm that:
- Payment information is handled through an appropriately secured payment service.
- Employees do not request or retain complete card details through ordinary email.
- Access to donation platform administration is restricted.
- MFA is enabled for accounts that support it.
- Website integrations and payment-related software are maintained.
- The organization understands its responsibilities and those of its payment provider.
Nonprofits should also examine how their donation forms connect with their website and CRM.
A secure payment processor does not necessarily protect a compromised website administrator account or an incorrectly configured integration.
Payment card compliance requirements depend on the organization's payment environment and should be confirmed with its payment provider or qualified compliance adviser.
What Should a Nonprofit Do If Donor Information Is Exposed?
A suspected donor data exposure requires a coordinated response.
Examples include an employee sending a donor spreadsheet to the wrong recipient, an unauthorized login to a fundraising account, or a lost laptop containing downloaded donor records.
Not every incident constitutes a legally reportable data breach. However, organizations should investigate promptly rather than assume that an accidental disclosure has no consequences.
1. Stop Further Exposure
Take appropriate immediate action, such as disabling a compromised account, removing a public sharing link, or revoking access to an affected file.
If a security incident is suspected, coordinate containment with the IT team so that important evidence is preserved.
2. Determine What Information Was Affected
Identify the systems, files, and accounts involved.
Establish what types of donor information may have been accessed, whether information was disclosed or downloaded, and which individuals may be affected.
Avoid making assumptions before the available evidence has been reviewed.
3. Contact Relevant Technology Providers
Notify the appropriate CRM provider, payment processor, cloud service provider, or IT support team when their systems may be involved.
Different providers may control different parts of the affected environment. A nonprofit should know whom to contact before an incident occurs.
4. Evaluate Notification Requirements
Depending on the information involved and the applicable laws, an organization may need to notify affected individuals, regulators, payment providers, or other parties.
California nonprofits should consider applicable California data breach notification requirements, as well as any other laws relevant to their operations and donors.
Legal counsel or an appropriate privacy adviser should help determine notification obligations and deadlines.
5. Address the Cause
Once the incident is understood, correct the underlying problem.
This might involve changing permissions, securing accounts, improving file-sharing practices, or updating technology configurations.
The organization should document what happened and how similar incidents can be reduced in the future.
A written incident response procedure makes these decisions easier to coordinate when staff members are under pressure.
Questions Nonprofit Leaders Should Ask About Donor Data Security
Executive directors and development managers do not need to manage every technical security setting personally.
They should, however, expect clear answers about how donor information is protected.
Use the following questions during an internal review or meeting with your IT provider.
If the answers are unclear, the organization has a practical starting point for improving its donor information security.
Donor Data Security Requires Ongoing Attention
Donor information moves through many parts of a nonprofit's operations. Fundraising databases, employee devices, shared files, donation platforms, and outside vendors all play a role in how that information is handled.
Protecting these records requires appropriate technology settings, clear organizational procedures, and regular reviews.
For nonprofit leaders, the most useful priorities are knowing where donor information resides, limiting access to people who need it, controlling exports and external sharing, and ensuring that security responsibilities are clearly assigned.
These practices also need ongoing maintenance. New employees, fundraising campaigns, software integrations, and vendor relationships can change how donor information is accessed.
A nonprofit that lacks dedicated technical staff may benefit from managed IT services for nonprofits to maintain device security, manage accounts, support cloud systems, and address technology issues before they interfere with daily operations.
Protect the Donor Information Your Organization Depends On
Secure Networks ITC helps nonprofits throughout San Diego County improve the security and reliability of the technology used in their daily operations.
With 20 years of experience as a Microsoft Certified Partner, our team supports account security, employee devices, email protection, cloud environments, and ongoing IT management.
If your organization is unsure who can access sensitive information or how securely donor-related files are shared, Secure Networks ITC can help review your account security, device protection, and cloud file-sharing configurations to identify practical improvements.
