Opens in a new tab

Third-Party Risk in Donor and Event Management Tools

By William A. ClementsDecember 19, 2025

Fundraising and community events are where a lot of nonprofits and schools shine. You bring people together, tell your story, and raise money for real work.

You also rely on a web of outside tools and vendors to make it happen.

Donor databases, online donation forms, ticketing pages, auction tools, email platforms, text messaging, payment processing, volunteer sign-ups, and check-in apps all touch sensitive data and real dollars. Each one adds value. Each one also adds third-party risk.

When we talk with nonprofits, schools, and associations in Chicago and across Chicagoland, we often see the same problem: the mission has outgrown the technology controls. The tools are doing their job, but ownership of security and risk is unclear.

This article explains third party risk in donor and event management tools in plain language. We’ll focus on practical steps you can take, even if you don’t have a large IT team.

What “third-party risk” means for nonprofits, schools, and associations

Third-party risk is the business risk you take on when an outside company stores your data, processes payments, integrates with your systems, or has access to your accounts.

In the donor and event world, third parties show up in two ways:

  • Software vendors that run a platform (donor management, event registration, email marketing, auction bidding, volunteer scheduling)
  • Service vendors that support your operations (web developers, marketing agencies, event production, outsourced bookkeeping, IT providers, payment support)

If a third party has a breach, makes a mistake, or gets compromised, your organization can feel the impact even if you did everything “right” internally.

That impact is often practical, not theoretical:

  • Donor trust gets damaged
  • Payments and payouts get delayed or redirected
  • Events get disrupted at the worst possible moment
  • Staff time gets consumed by cleanup, notifications, and questions
  • Insurance renewals and contract renewals become harder

Security controls can reduce these risks, but they cannot eliminate them completely.

Why donor and event platforms create unique security exposure

Donor and event tools are different from many other business systems because they are public-facing and time-sensitive.

You are collecting high-value data in a high-pressure setting

Most donor and event tools touch at least some of the following:

  • Names, emails, phone numbers, addresses
  • Donation history and donor notes
  • Event attendance and guest lists
  • Payment details (even when handled through a processor)
  • Sponsorship information
  • Student or family information in school settings
  • Internal staff notes about relationships and giving capacity

At the same time, you have deadlines. A fundraiser launches on Monday. The gala is Saturday. A giving campaign runs for two weeks. That pressure leads to rushed permissions, shared logins, and quick integrations.

You have lots of temporary users

Nonprofits and schools often rely on:

  • Volunteers
  • Seasonal staff
  • Board members
  • Committee members
  • Contractors and part-time support

Those users may need access for a short time, then should lose it cleanly. If that offboarding step is missed, old access becomes a long-term risk.

You are integrating many tools that were not designed as one system

A common setup looks like this:

  • Donation form feeds the donor database
  • Ticketing platform feeds event check-in
  • Email platform pulls lists from donor data
  • Accounting system receives exports or reports
  • Marketing tools add tracking scripts or pixels
  • Text messaging platform is connected for reminders
  • Auction tool connects for bidding and receipts

Each connection is a data path. If those paths are not understood and controlled, you can end up with sensitive donor data scattered across multiple systems with unclear ownership.

Common third-party risk scenarios in donor and event management tools

Most incidents are not movie-style hacking. They are routine failures that create real consequences.

Account takeover of an admin user

If a criminal gains access to an admin account for your donor database or event platform, they may be able to:

  • Export donor lists
  • Change payout details
  • Create new admin users
  • Modify donation pages or confirmation emails
  • Add hidden integrations that siphon data

This is why identity controls matter as much as the vendor’s own security.

Payment redirection and refund abuse

Event and donation platforms often have settings for:

  • Bank deposit details
  • Refund rules
  • Gift card or credit handling
  • Payout schedules

Attackers may target these settings through stolen credentials or social engineering. They only need one weak link.

Risky integrations and over-permissioned connections

Many organizations connect tools quickly and never revisit the permissions.

Typical problems include:

  • An integration has access to “all donors” when it only needs “new event registrants”
  • API keys never expire and are stored in shared documents
  • A former vendor still has access to your integrations portal
  • Data exports are emailed or stored in personal cloud accounts

Vendor breach and downstream impact

Even strong vendors can have incidents. If a vendor has a breach, you may face:

  • Donor notifications
  • Questions from sponsors, parents, or board members
  • Increased fraud attempts using leaked lists
  • Pressure from insurers and auditors to prove your controls

The goal is not to assume every vendor is unsafe. The goal is to plan for the reality that incidents happen.

Event-day technology failures

Event day is a special kind of risk.

We see issues like:

  • Check-in tablets are shared and not locked down
  • Staff connect payment devices to open Wi-Fi
  • QR codes posted publicly send guests to look-alike donation pages
  • Volunteers use personal phones to log into admin portals
  • A venue’s network is unstable, forcing staff into unsafe workarounds

Event-day controls should be planned like a checklist, not improvised in the moment.

Build a simple vendor inventory before you try to “secure everything”

You cannot manage third party risk in donor and event management tools if you don’t have a clear list of your tools and vendors.

A practical first step is a one-page inventory that includes:

  • Vendor name and what the tool does
  • Who owns the relationship internally (the person responsible for renewals and access)
  • What data the tool holds (donor PII, payment-related data, student data, etc.)
  • Whether the tool is public-facing
  • Whether the tool integrates with other systems
  • How users log in (email-based logins, SSO, MFA availability)
  • How you would operate if the tool was down for 48 hours

Once you have the list, sort vendors into simple tiers:

  • Tier 1 (critical): donor database, payment-related portals, primary event registration and ticketing, core email system
  • Tier 2 (important): email marketing, auction tools, volunteer management, analytics
  • Tier 3 (helpful): optional add-ons, niche tools, convenience integrations

This helps you focus. Tier 1 tools deserve stronger controls and more frequent review.

Security requirements you should expect from donor and event tool vendors

You do not need to become a security engineer to ask reasonable questions. You just need a baseline.

Here are practical expectations for higher-risk vendors.

Identity and access controls

Look for:

  • MFA support for all users, especially admins
  • Role-based access (so not everyone is an admin)
  • Audit logs (who changed what and when)
  • Support for single sign-on (SSO) if your organization has it
  • The ability to remove users quickly and verify access is gone

If a tool cannot do basic access control, treat it as high risk and limit what you store there.

Data protection and retention

Ask about:

  • Encryption of data in transit and at rest
  • Data retention settings (how long data is kept after a campaign or event)
  • Ability to delete or archive data when it is no longer needed
  • How backups are handled and how recovery works during an outage

You do not need the vendor’s internal blueprint. You need confidence that data is protected and recoverable.

Incident response and notification

Your contracts and vendor terms should be clear on:

  • How quickly the vendor will notify you of an incident
  • What information they will provide (what data was impacted, what was accessed, what is being done)
  • Whether they have a documented incident response process
  • How you will communicate during an outage

Vague incident language creates surprises when you can least afford them.

Integration risk: the hidden part of donor and event platform security

Integrations are where “good tools” become “risky systems.”

Treat integration accounts like privileged accounts

Integrations often run under service accounts or API tokens. Those credentials can be powerful. If they are stolen, a criminal may not need a human login at all.

Good integration hygiene includes:

  • Use separate service accounts, not a staff member’s personal login
  • Grant only the permissions needed for the integration
  • Store API keys in a secure place, not in shared documents
  • Rotate keys when vendors change or staff changes
  • Remove unused integrations promptly

Map your data flows at least once per year

You should be able to answer, at a high level:

  • Where does donor data start?
  • Where does it get copied to?
  • Who can export it?
  • Where is it stored after export?

If you cannot answer these questions, it is a sign the ecosystem has become too complex to manage safely.

Operational controls that reduce fraud and misuse

Some of the best controls are not technical. They are process.

Financial controls for donation and payout changes

Set rules that match your risk:

  • Two-person approval for changes to bank deposit details
  • Verification of payout changes using a known phone number, not an email reply
  • Limits on who can issue refunds and under what conditions
  • Clear separation between event staff and finance staff permissions

These steps prevent a single compromised account from turning into a direct financial loss.

Access reviews and offboarding discipline

For nonprofits and schools, access drift is a major issue. People keep access long after they stop helping.

A simple monthly or quarterly routine helps:

  • Review admin accounts on donor and event platforms
  • Remove access for former staff, volunteers, and vendors
  • Confirm MFA is still enforced and exceptions are minimal
  • Review integrations and disable what you no longer use

This is not busywork. It is basic risk management.

Contract terms and vendor management basics for mission-driven organizations

Many nonprofits and schools sign vendor agreements quickly because they are focused on mission delivery. That is understandable, but it can create long-term exposure.

When possible, your higher-risk vendors should address:

  • Data ownership (your data remains yours)
  • Use of subcontractors (and how they are vetted)
  • Breach notification timelines and responsibilities
  • Support during an incident (what help they provide)
  • Data return and exit process if you switch platforms
  • Minimum security requirements for admin access

You do not need to negotiate like a Fortune 500 company. You do need to avoid signing terms that leave you powerless during a crisis.

How cyber insurance connects to third-party risk

Cyber insurance underwriters often ask about your internal controls. They also care about third-party exposure.

Even when a third party is involved, insurers typically expect you to show:

  • You enforced MFA on critical accounts
  • You limited admin access
  • You had documented processes for access removal
  • You maintained backups and recovery planning where relevant
  • You had vendor management practices appropriate for your size

In other words, third-party incidents do not remove your responsibility. They change the scenario, but you still need reasonable controls and documentation.

A practical checklist for reducing third party risk in donor and event management tools

If you want a short list that drives action, start here:

  • Make a vendor and tool inventory, with Tier 1 and Tier 2 clearly labeled
  • Enforce MFA on email and on all Tier 1 donor and event platforms
  • Reduce the number of admin accounts and separate admin work from daily use when possible
  • Review user access quarterly, including volunteers and outside vendors
  • Review integrations quarterly and remove anything unused
  • Add two-person approval for payout changes and high-dollar refunds
  • Document your incident response contacts, including vendor support paths
  • Decide what data you truly need to store in each platform, and remove what you do not

This is enough to materially reduce risk without turning your organization into a technology shop.

How we support nonprofits, schools, and associations in Chicagoland

We help mission-driven organizations build security-first operations that fit real staffing and budget constraints. That often includes Secure IT Support and Secure IT Management for stable daily operations, plus Advanced Security services to strengthen monitoring, endpoint protection, and identity controls. When leadership needs a structured way to manage vendor risk, document controls, and prepare for insurance or compliance questions, Cyber Assurance Shield can provide an organized framework. For organizations that need clearer security leadership and prioritization, vCSO services can help set direction and keep the program moving.

A low-pressure next step

If you want to reduce third party risk in your donor and event management tools, please reach out to ChicagoTG and we’ll be happy to assist.

The bottom line

Donor and event platforms help you raise money and run programs. They also create real third-party exposure because they sit close to trust, identity, and payments.

You do not need to overhaul everything at once. Start by knowing what you use, tightening access, controlling integrations, and putting simple approval steps around money movement. Those actions reduce risk, improve resilience, and protect the reputation you have worked hard to build.

Share this article

Want help putting this into practice?

Book 15 minutes with our team. Tell us what you're working on and we'll tell you honestly where we'd start.

Book 15 minutesor call (877) 582-4422

Free tool

How does your website score?

Try the Website Grader
Cover of Cybersecurity Checklist for Business Owners by William A. Clements

About the author

William A. Clements

William founded Chicago Technology Group and wrote Cybersecurity Checklist for Business Owners, a plain-English guide to the decisions that protect your company, your clients and your reputation.

Get the book on Amazon