Every tool we build is designed around one rule: your donor, client, and program data stays under your control, in your systems, and out of anyone's training set. Here is how we hold that line, and the questions boards ask most.
We build on zero-retention, enterprise AI tiers — never the consumer chatbots. Your data isn't used to train models, and we'll show your board the exact vendor terms in writing.
Each tool touches only the data it needs, read-only wherever possible. Scoped access, no blanket admin keys — so a single tool can never reach further than its job.
Nothing sends externally or writes to a system of record without a person signing off. Our tools draft; your team decides. The AI never acts on its own.
We identify which rules apply — HIPAA, FERPA, and the like — before we build, and design to them from the start. Sometimes the honest answer is that data shouldn't go through a model at all.
Every tool runs in your accounts, in standard code. You can revoke access or turn a tool off at any moment — there's no proprietary black box holding your data hostage.
Every tool ships with one page any board member can read: what it touches, where data goes, who can access it, what the AI vendor does with it, and how to switch it off.
No. We build on enterprise AI tiers with zero-retention, no-training terms — never the consumer chatbots. We'll point you to the exact vendor terms so your board can read them for themselves.
In your own systems — your Google Workspace, your database, your accounts. Our tools read and write in place. We don't copy your records into infrastructure we control.
Each build ships with documentation and a support window, and it's written in standard, maintainable code — not a proprietary black box. You're never one person's departure away from losing it.
Carefully, and sometimes the honest answer is “this shouldn't go through a model at all.” We identify which rules apply — HIPAA, FERPA, and the like — before we build, and design to them from the start rather than bolting on compliance after.
No. The tools are built for the people who do the work — a development director, a program manager — not for engineers. If it needs a manual, we built it wrong.
The first tool is typically live in a few weeks, because we deliberately scope it small. You feel the time savings before you commit to anything larger.
We take on new clients by referral only — but if we share someone in common, we're always glad to talk through how a tool would handle your data.
Ask for an introduction