IT and cybersecurity for nonprofits
Right-sized IT that protects donor trust, without pretending you have an enterprise budget.
A nonprofit holds the same kind of data a business does: names, addresses, payment cards, and sometimes constituent records as sensitive as anything a clinic keeps. It just does it with a smaller team, more volunteers, and a budget that has to stretch further. The security basics still apply, and so do the rules. If you take card donations, PCI DSS applies to you. Nearly every state has a breach-notification law, and none of them exempt charities.
What changes is the approach. The right setup for a nonprofit isn’t a scaled-down copy of an enterprise security program. It starts with keeping card data off your systems entirely, protects the places donor data actually lives, and produces the documentation your board and funders ask for, at a cost that fits.
What applies to a nonprofit
PCI DSS for card donations. Any organization that accepts card payments falls under the Payment Card Industry Data Security Standard through its merchant agreement. How much of it lands on you depends on how donations come in. A hosted donation page or a processor that tokenizes the card keeps most of the standard with the processor. Card numbers typed into a spreadsheet or saved in an inbox bring it all back to you. You can read more on our PCI DSS page.
State breach and privacy laws. If donor personal information is exposed, state laws require you to notify the people affected, on a deadline. Comprehensive privacy laws are also spreading state by state, and they apply based on where your donors live.
Funders and boards. Grant applications, government grants especially, increasingly ask how you protect data. Board members ask the same question after every headline. A written security program and an incident response plan answer both.
Where donor data hides
Most nonprofit data doesn’t sit in one tidy system. It lives in the donor CRM, the online donation form, email, the spreadsheet exported for the year-end mailing, shared drives, a laptop that goes home with the development director, and paper pledge cards in a filing cabinet. Any security plan that only covers “the network” misses most of it. The first thing we do is trace where donor and payment data actually goes, so the protection covers the real exposure.
What we handle for nonprofits
Day-to-day IT support
Help desk, devices, email, and the shared drives your staff and volunteers live in, run by a team against documented service levels.
Donation and payment flows
We trace how card donations come in and set them up so card numbers stay with the processor, which keeps your PCI scope and your risk small.
Donor and constituent data
Encryption, multi-factor authentication, and access controls on the CRM, email, and the exports that end up on laptops.
Volunteer and seasonal access
Accounts set up cleanly when someone starts and removed just as cleanly when they leave, so former volunteers don’t keep the keys.
Backups and ransomware recovery
Backups tested by actually restoring from them, so a locked server is a bad day instead of a lost year of records.
Documentation for boards and funders
The written security program, incident response plan, and vendor reviews that grant applications and board members increasingly ask to see.
The full set of controls behind this is on our Cybersecurity and Managed IT pages.
10 questions every nonprofit should ask before buying a cybersecurity solution
Plain-English PCI and breach rules, a 10-minute exercise to map your donor data, and the red flags to listen for.
Frequently asked questions
Does PCI DSS really apply to a nonprofit?
Yes, if you accept card donations. PCI DSS applies to any organization that accepts, stores, processes, or transmits payment card data, and there’s no charity exemption. The good news is that how much of it applies depends on how you take payments. With a hosted donation page or a processor that tokenizes the card, most of the standard stays with the processor, and you usually complete a short annual Self-Assessment Questionnaire.
We rely on volunteers. Does that change anything?
It changes how access is handled more than anything else. Volunteers come and go, often use their own devices, and sometimes end up with logins nobody remembers to remove. We set up accounts with only the access each role needs, require multi-factor authentication on systems that hold donor data, and close accounts when people leave.
Can you work within a nonprofit budget?
We price against your actual headcount and systems, and we’ll tell you straight which controls protect donor data and which are enterprise tooling you don’t need. We work the number out on the exploratory call rather than posting a figure that wouldn’t fit your situation.
Where to start
Book a 30-minute exploratory call. Tell us how donations come in, where your donor data lives, and what your board or funders have been asking. We’ll give you a straight read on what matters most and what can wait. No commitment, and if we’re not the right fit, we’ll say so.
Book a call