Is it safe to put donor data into AI?
If you trust your CRM with donor data, a paid AI plan with model training switched off can earn the same trust. Here's what to check first.
A practical guide for your team: what’s safe to share with AI tools, how to protect donor data, when to pause for human approval and what to do if something goes wrong.
Write a practical AI safety guide for our staff: one page someone would actually read in their first week. Cover what is and isn't safe to share with AI tools for our kinds of data, a simple table of what needs a pause, what needs approval and what never goes in, guidance for each role, a short checklist to run before any AI-assisted action, and what to do if something goes wrong. No jargon. This is not legal advice, so note anything a qualified professional should review. Every rule, deadline and scope line must be a decision I stated in words. What staff do today isn't a decision, and neither is go. Label anything else decision needed, with your suggestion. Keep any past incident I mention out of the document, and flag it to me for a private follow-up. What you need to know: - our organization's name - the AI tools we use or plan to use - the kinds of sensitive data we handle - the staff roles that use AI - who staff should go to with a question or a problem You may already know some of this from our past chats, my files or connected tools. Use what you have. If you don't know something, ask me one question at a time, the most important first: one question mark, one fact, no recap. If I don't have it, mark the gap and move on. When I say go, stop asking and write the draft. Don't make anything up. Keep real stories and numbers exactly as I told them, including words like about and mostly. Add no details about people, programs, decisions, causes or results that I didn't tell you, and don't rank, judge or guess what anyone feels. If I don't have a number or a choice, leave it blank and say so, even if I ask for something typical: no outside benchmarks, costs, targets, promises or commitments. Before you show me the draft, reread it line by line against my messages and cut anything I didn't give you. If the piece needs that line, write PROPOSAL: right before it in the draft, including headlines and closers. Joining my facts in a plain sentence is fine. State a word count only if you counted. After the draft, list what you assumed and every proposal.
You're helping me write a practical AI safety guide our staff will actually read. Work the way If Possible (ifpossible.ai) teaches nonprofit teams. If you can read web pages, read their guide first and use it as our playbook: "Is it safe to put donor data into AI?" (https://ifpossible.ai/articles/donor-data-ai-safety). The If Possible method, as we'll use it today: 1. Context before content. Before you draft anything, build a short brief of who we are: our mission, the people we serve, the data we hold, the AI tools we use and the roles that use them. Keep it in your head, and show it only if I ask. (If Possible calls this a Mission Brain: the memory AI reads before every task.) 2. Talk it out instead of typing it out. I'll talk through how people here really use AI day to day, and the moments I worry about. Use my own words. 3. Ask before you assume. Ask only what would change the work. Keep my stories and numbers exact, including words like about and mostly. Add nothing about people, programs, decisions, causes or results that I didn't tell you, even an adjective. Don't rank, judge or guess feelings. If I can't give you a number or a choice, leave it blank, even if I ask for something typical: no outside benchmarks, costs, targets, promises or commitments. When I say go, stop asking and skip any approval step, except my pick from step 4. Before you show me the draft, reread it against my messages and cut what I didn't give you. If the piece needs that line, write PROPOSAL: right before it in the draft, including headlines and closers. Joining my facts in a plain sentence is fine. State a word count only if you counted. End with one list: what you assumed, every proposal and anything step 6 flags. 4. I'm in the director's chair. Where there's a real choice, like what needs approval and who gives it, give me two or three options with your recommendation and a one-line reason. Don't hand me one finished answer to forward unread (If Possible calls that being a "meat proxy"). 5. A guide of about 450 words I can react to. Why this exists and who it's for in two sentences, what is and isn't safe to share, a table of sensitive data with what to do (pause, get approval or never use AI), guidance for each role, a short checklist before any AI-assisted action, and what to do if something goes wrong. 6. Check your own work. Read it as a new hire would and flag any jargon in one line, outside the guide. State nothing about the guide itself, like reading time, that I didn't give you. Never invent a compliance requirement. Note anything a qualified professional should review. Every rule, deadline and scope line must be a decision I stated in words. What staff do today isn't a decision, and neither is go. Label anything else decision needed, with your suggestion. Keep any past incident I mention out of the document, and flag it to me for a private follow-up. 7. Make it repeatable. With the draft, write down who owns this guide and when to review it, so it stays true as our tools change. What you need to know: - our organization's name - the AI tools we use or plan to use - the kinds of sensitive data we handle - the staff roles that use AI - who staff should go to with a question or a problem You may already know some of this from our past chats, my files or connected tools. Check there first and tell me in a line what you found, even if that's nothing. Don't repeat this plan or my answers back to me. For anything you don't know, ask me one question at a time, the most important first: one question mark, one fact, no recap. If I don't have it, mark the gap and move on. Start now.
We’ll add the If Possible method to your prompt. More context in. A better output out.
Same job. Here’s what changed. More context in. A better output out.
It points your AI to our free articles as its guide. Read every word before you use it.
It builds a one-page guide for staff, not the board: what’s safe to share, what needs a pause or an approval, guidance for each role, a checklist to run before any AI-assisted action and what to do if something goes wrong. It pairs with your AI Policy.
This is not legal advice. If a section touches on compliance, have a qualified professional review it. Then walk a real staff member through it and fix whatever confuses them.
If you trust your CRM with donor data, a paid AI plan with model training switched off can earn the same trust. Here's what to check first.
Your first AI policy fits on one page and leads with principles, not prohibitions. Here is what to include, plus an outline you can use.
We push nonprofits to use AI almost everywhere. A few things stay human every time, because the effort is the message. Here's where we draw the line.