Nonprofits trust MonkeyPod with their books, the personal details of their donors, members and volunteers, and more. This page explains how we protect that information. Questions, or a security concern to report? Email security@monkeypod.io.

Where your data lives

MonkeyPod runs on Amazon Web Services (AWS) in the United States, with backup copies in a second US region.

  • Your organization's data is kept separate from every other organization's. Every request to MonkeyPod is limited to the organization it belongs to.

  • Encryption in transit: every connection to MonkeyPod uses HTTPS with TLS 1.2 or later, and connections between our servers and our database are encrypted too.

  • Encryption at rest: our database, file storage and backups are encrypted with AES-256. Sensitive fields, such as tax identification numbers, get a second layer of encryption with a key unique to your organization.

  • Payments are processed by Stripe. Card numbers go straight to Stripe and never touch MonkeyPod's servers.

  • Bank connections use Plaid. MonkeyPod never sees or stores your online banking password.

Backups

  • The database is backed up continuously and can be restored to any point in the last 35 days.

  • Copies of the database are kept in a second region: a daily copy for two weeks and a monthly copy for a year. These copies are locked, so no one, including our own administrators, can delete them early.

  • Uploaded files are versioned and copied to the second region as they're saved. A deleted or replaced file can be recovered for 90 days.

  • In the event that data or documents belonging to your organization are lost due to user error (as opposed to a bug or other error by MonkeyPod), they can usually be recovered within the above constraints. Additional charges for engineering time may apply.

Who at MonkeyPod can see your data

We use the contents of your organization's records only to provide MonkeyPod to you.

  • The contents of your records. MonkeyPod staff may access your organization's records, especially including your relationships' personal information, only to help you (for example, when you ask support for help with an import), to fix a problem that affects you, to investigate security or abuse, or when the law requires it.

  • Usage information. We look at how organizations use MonkeyPod, such as which features and apps they use, how many records of each kind they have, and when their users sign in, to improve the product, support customers, and run our business. This never involves reading the contents of your records. When we study or publish statistics across all organizations, we use combined, de-identified information, and we never identify an organization or its data without its consent.

  • Your data stays in production. We don't copy customer data into test or development systems. Files you send us for onboarding or support are kept only as long as that work needs them.

  • Our team signs in to our core systems with multi-factor authentication, and access to our production systems is limited to the people who need it. Engineers' direct access to the production database is read-only and every query is recorded.

AI features

Some MonkeyPod features use AI, for example to read bank statements or receipts, suggest categories, or explain possible duplicate records. To provide them, we send the relevant information to Anthropic or OpenAI, which may include your organization's records and personal information. Under our agreements with them, neither uses your data to train its models.

Service providers

These companies process customer data on MonkeyPod's behalf:

  • Amazon Web Services: hosting, database, file storage, backups, and sending email

  • Stripe: payments and subscriptions

  • Plaid: bank connections

  • Anthropic and OpenAI: AI features

  • Meilisearch Cloud: search, including contacts, relationships and interactions

  • Laravel (Nightwatch): application monitoring and error reports

  • Cloudflare: generating PDF documents such as receipts

  • Google: address lookup, spam protection on forms, and sign-in with Google

  • Help Scout: customer support conversations

  • LocationIQ: address geocoding

  • Unlayer: the email design editor

  • Dots: payouts through MonkeyPod Pay, when you use it

  • PassKit: digital membership cards, when you use them

  • Vonage: text messages, when you use them

Other services you choose to connect, such as Gusto or Jotform, receive data only when you turn on that integration. We update this list when a provider is added or removed.

Your data after you leave

Your data belongs to you. If you close your account, our standard practice is to keep your organization's data indefinitely so you can come back, unless you ask us to delete it. When you ask, we delete it from MonkeyPod, and it ages out of our backups within a year. We reserve the right to delete a closed account's data beginning 30 days after it closes.

Your organization controls the information it keeps about its donors, members and other contacts. If one of them asks MonkeyPod to delete their information, we pass the request to your organization and help you act on it.

If something goes wrong

We monitor our systems for threats and unusual activity, and we have a written plan for responding to security incidents. If an incident affects your organization's data, we will tell your account administrators without undue delay, and share what we know about what happened, what data was involved, what we have done, and what you should do, updating you as we learn more.

Reporting a vulnerability

If you believe you've found a security problem in MonkeyPod, email security@monkeypod.io with enough detail for us to reproduce it. We read every report and fix real issues promptly. Please don't access other people's data or disrupt the service while testing.

MonkeyPod does not run a bug bounty program and does not pay for unsolicited reports.

Our security program

MonkeyPod's security program follows the SOC 2 framework, covering security, availability and confidentiality. We are preparing for a SOC 2 Type I audit.