Security & trust
Your ministry partners trust you with their information. We take that seriously.
Koala stores sensitive donor records and financial activity. Here is how organization boundaries, permissions, operational access and change history are designed to protect that trust—and where we are still building.
Three commitments, enforced in the code
Your organization's data stays separate
Access follows responsibility
Important changes leave a trail
Your organization's data stays separate
Every query in Koala is bound to a single organization before it runs. That is not a convention people are asked to remember — the unscoped database handle is blocked in the codebase, so reaching for it fails automatically rather than failing in review.
The separation is tested from the outside too: the suite includes checks that one organization’s administrator, querying as hard as they can, cannot produce another’s records.
Access follows each person's responsibilities
A support raiser sees their own partners and their own numbers. A coach sees the people they coach — not the whole roster — and the donors belonging to those people. Finance sees the money. Administrators see everything, and the differences are enforced in the queries rather than by hiding buttons.
Administrators and coaches can view the product as somebody they oversee, which is useful for support and training. Anything changed while doing so is recorded against the real person, not the one whose screen they borrowed.
Important changes leave a trail
Gifts, pledges, goals, member roles and settings each write an entry naming who changed what and when, in language meant to be read rather than parsed. It is visible to your administrators without asking us for anything.
Our own access is accountable
Being straightforward about this: Koala’s operators can reach customer records. Any vendor who can restore your backup can do the same, whatever their marketing page says. What matters is the constraints around it.
- Operator access is a separate identity from any account inside an organization. No role a customer can grant, including their own administrator, reaches across organizations.
- It requires two independent things: a grant in the database, and the address being on a list that lives in the server’s configuration and takes a deployment to change. Neither alone is enough.
- Reads are recorded, not only changes — including which organization, what kind of records, and how many. Opening a donor list leaves a durable trail.
- Access is revoked rather than deleted, so the record of who could see what, and until when, survives.
What Koala does not do
- We do not sell or share donor data. There is no second use for it.
- We do not take a percentage of donations, so we have no reason to be in the middle of them.
- We do not email your donors on our own behalf. Newsletters go out as your organization, when somebody there sends them.
Honest about our stage
Koala is early. There is no SOC 2 report, because claiming one that does not exist would be worse than saying so. We also do not currently publish commitments on encryption standards, hosting regions, backup schedules or retention periods — not because they do not matter, but because we would rather answer a specific question accurately than make a general claim we have not verified.
If your organization needs particular assurances — a data processing agreement, a hosting region, a retention commitment — ask before you commit and you will get a straight answer about what exists today and what does not.
Questions boards ask
- Can one organization see another's donors?
- No. Every query carries its organization before it runs, and the test suite includes an attempt to break that from the outside.
- Can our missionaries see each other's partners?
- No. A missionary's donors are their own; coaches see the staff they are assigned, and administrators and finance see the organization.
- Do you have SOC 2?
- No. We would rather say so than imply otherwise.
- Can Koala staff see our data?
- Yes, under the constraints described above — a separate identity, two independent requirements, and every read recorded.
- Can we get our data out if we leave?
- Yes, as CSV, any time, without asking us.
- Do you train anything on our donor data?
- No. There is no machine learning on customer data in the product today.