Security Matters: ChatGPT for Nonprofits
Like many industries, nonprofits are increasingly turning to ChatGPT to draft grant proposals, brainstorm fundraising campaigns, and save time on everyday communications. While ChatGPT can be a powerful tool for nonprofits, it also introduces new risks that are easy to overlook.
A recent incident revealed just how quickly sensitive data can slip into the open. Shared ChatGPT conversations were indexed by Google, making what users assumed were private exchanges searchable by anyone. For nonprofits, this could mean donor details, beneficiary stories, or internal strategy documents accidentally exposed online.
The lesson is clear: adopting AI without proper safeguards can put your organization’s reputation and the people you serve at risk. Securing ChatGPT use isn’t just a technical step, it’s about protecting trust.
How ChatGPT Conversations Can Become Public
ChatGPT includes a “Share” feature that lets users generate a link to a conversation. The idea was to make collaboration easier. You could send the link to a colleague, and they could see the chat exactly as it appeared in your browser.
The problem arose when those shared links started getting indexed by Google. If a user clicked the “share” option, or if the link was posted somewhere Google could crawl, the entire conversation could end up in search results. That meant prompts, responses, and any data included were now available to anyone running the right search.
What types of information showed up? Reports revealed full resumes with contact details, private personal stories, even names of children. For nonprofits, this raises an obvious concern: using ChatGPT for nonprofits work could expose donor information, financial records, or sensitive beneficiary details if conversations are shared carelessly. Once indexed, that information wasn’t just shared with a colleague, it was exposed to the entire internet.
Wondering if Levacloud can solve your Microsoft Cybersecurity related challenge? Drop us a message!
AI Key Risks for Nonprofits
ChatGPT for nonprofits can be a huge time-saver, but the risks of mishandling it are real. If conversations are shared publicly or used without clear policies, sensitive information can slip out in ways that damage both your mission and your reputation.
Donor and Financial Data
Nonprofits often handle donor names, contact details, and giving histories. If that information makes its way into ChatGPT prompts and is later shared, it could be exposed online. Donor trust is fragile, and even a small leak can make supporters think twice about giving.
Beneficiary and Community Data
Many nonprofits serve vulnerable populations. Accidentally exposing a client’s story, medical details, or location could cause real harm. What might seem like harmless context in a ChatGPT conversation could become dangerous if indexed publicly.
Internal Strategies and Advocacy Plans
Campaign ideas, grant proposals, and advocacy strategies give your organization an edge. If these appear in search results because a staff member used the Share feature, you risk losing that advantage, or giving opponents insight into your playbook.
Reputation and Trust
Above all, nonprofits rely on trust. Using ChatGPT without guardrails can create the perception that your organization doesn’t take privacy seriously. A single incident could undo years of careful relationship-building with donors, clients, and partners.
Broader Security Concerns with ChatGPT for Nonprofits
The Google indexing incident is just one example of how things can go wrong. Even if you never use the “Share” feature, there are other risks nonprofits need to think about when relying on ChatGPT.
- Data Retention
By default, conversations may be stored in your account history. If staff enter sensitive information, like donor contact details or beneficiary case notes, that content could be sitting in ChatGPT indefinitely unless the right settings are applied.
- Untrained Use by Staff or Volunteers
Nonprofits often depend on volunteers or rotating staff who may not be familiar with the rules. Without clear guidelines, someone might use ChatGPT for nonprofits work in ways that put private information at risk.
- Shadow AI
If you don’t provide a secure, sanctioned option, staff may sign up for the free version of ChatGPT on their own. That creates “shadow AI” usage that IT can’t monitor or secure. It’s similar to shadow IT, where employees adopt unapproved tools that bypass data protection controls.
You have a pressing issue, but you’re not sure if Levacloud can help. We get it. Everyone has unique challenges they face in their IT environments. Schedule a free call today and talk us through it.
We’ll let you know how we can best support you.
Best Practices to Secure ChatGPT Use in Nonprofits
You don’t need to stop using ChatGPT for nonprofits work, you just need to put the right safeguards in place. Here are practical steps to reduce risk and keep your data secure:
Build a Responsible AI Use Policy
Set clear boundaries for how ChatGPT can be used. Prohibit entering donor, beneficiary, or financial data into prompts. Define what’s acceptable (e.g., drafting marketing copy) versus what’s off-limits (e.g., case notes or confidential reports).
Train Staff and Volunteers
Make sure everyone understands the risks of sharing conversations and how to use AI safely. Training should include how to recognize sensitive data, how to anonymize examples, and when to escalate questions to leadership.
Control Link Sharing
Discourage or disable use of ChatGPT’s “Share” feature for nonprofit work. Instead, share outputs internally through secure tools like email, Teams, or document platforms. Remind staff that anything posted publicly is potentially permanent.
Audit and Clean Up Existing Shared Links
Ask your team to review any previously shared conversations. Old links can be deleted directly in ChatGPT, and if something was indexed, you can request removal from Google. Doing a one-time cleanup ensures nothing lingers where it shouldn’t.
Use Enterprise-Grade AI Options
When possible, adopt enterprise solutions like Microsoft Azure OpenAI or Copilot. These platforms provide stronger data protections, admin controls, and compliance support, giving nonprofits the same security that larger enterprises rely on.
Monitor and Respond
Include AI tools in your existing incident response planning. If a mistake happens, have a clear process to delete links, notify affected parties, and improve training to avoid repeats. Proactive monitoring with tools like Data Loss Prevention (DLP) can also flag risky usage before it becomes a problem.
Copy-Paste Risks
Even without link sharing, staff might copy ChatGPT content into emails, social media posts, or public documents without realizing sensitive details were still embedded. This creates another pathway for exposure.
In other words, securing ChatGPT isn’t only about preventing search engines from crawling conversations, it’s about building safe habits and systems around every interaction with the tool.
Secure How Your Team Uses ChatGPT
We’ll help your nonprofit put the right guardrails in place, from staff training to data protection policies.
Securing ChatGPT in Practice: Steps You Can Take Now
Here’s how to start securing ChatGPT for nonprofits specifically:
1. Audit Current Usage
- Ask staff and volunteers how they’re currently using ChatGPT. Are they drafting grant proposals? Brainstorming donor outreach? Taking notes from meetings?
- Run a search for site:chatgpt.com/share along with your nonprofit’s name or common project names. This can reveal if any shared conversations are publicly visible.
- Document all the touchpoints where ChatGPT is being used, both official and “shadow” use, so you know where risks exist.
2. Educate Your Team
- Host a short training session to explain the risks of public links and sensitive data entry.
- Provide examples relevant to your nonprofit: “If you paste a donor list into ChatGPT, here’s how it could be exposed.”
- Share a simple rule of thumb: if you wouldn’t put it on your website, don’t put it in ChatGPT.
- Create a one-page guide with safe vs. unsafe use cases (g., safe = drafting event invitations; unsafe = analyzing donor spreadsheets).
3. Review and Delete Shared Links
- In ChatGPT, go to Settings > Data Controls > Shared Links and review past shares. Delete anything not meant for public consumption.
- If you find sensitive conversations indexed by Google, use the Google Remove Outdated Content tool to request deletion after removing the link.
- Assign someone (IT staff or a trusted administrator) to check quarterly for lingering links.
4. Write Down Policies
- Draft an AI use policy tailored to your nonprofit’s work. Keep it short but specific.
- State clearly what data is off-limits: donor names, addresses, case notes, or any financial details.
- Require staff to anonymize examples when asking ChatGPT for help (g., “donor A gave $X” instead of “John Smith donated $10,000”).
- Make policy acknowledgement part of onboarding for staff, interns, and volunteers.
5. Provide Safer Tools
- If budget allows, move staff onto enterprise-grade AI platforms like Microsoft Azure OpenAI or Copilot, which include stronger controls and data protections.
- If you must rely on the free version, configure account settings to disable chat history and training so prompts aren’t stored long-term.
- Encourage sharing outputs internally through secure platforms (email, Teams, OneDrive) rather than ChatGPT’s share links.
6. Monitor and Prepare for Incidents
- Integrate ChatGPT into your incident response plan. If someone shares sensitive data, you’ll know who to notify and what steps to take.
- Consider enabling Data Loss Prevention (DLP) tools if your nonprofit already uses Microsoft 365. These can flag when sensitive data is being copied into unapproved apps.
- Run an annual or semi-annual review of AI usage and update your policies as the tools evolve.
By moving from generic guidelines to concrete actions, your nonprofit can safely adopt ChatGPT without risking donor trust or exposing sensitive beneficiary information.
We’ll keep you up to date on the latest in Microsoft Cybersecurity.
Safe AI Adoption for Nonprofits: Final Thoughts
ChatGPT can be a powerful tool for nonprofits, but only if it’s used responsibly. The indexing issue proved how quickly conversations can slip into the open, and for nonprofits, that could mean donor information, beneficiary details, or internal strategies ending up in search results.
Securing ChatGPT for nonprofits is specifically about putting guardrails in place: auditing current use, educating your team, deleting risky links, writing clear policies, and where possible, moving to enterprise-grade AI tools that include built-in compliance and monitoring.
The takeaway is simple: if you treat ChatGPT like any other system that handles sensitive information, you can benefit from its efficiency without sacrificing trust. Donors, beneficiaries, and partners expect you to safeguard their data, and with the right approach, you can meet that expectation while still embracing new technology.
If you’re ready to strengthen how your nonprofit uses AI, Levacloud can help you set up the right policies, controls, and monitoring so your team can innovate safely.
FAQs About ChatGPT Security for Nonprofits
Does ChatGPT share your data?
By default, ChatGPT doesn’t automatically broadcast your data, but shared conversations can become public if you use the “Share” feature or enable discoverability. That’s how some conversations ended up indexed by Google. Nonprofits should avoid sharing sensitive content through public links and disable chat history where possible.
Is ChatGPT safe for nonprofits?
ChatGPT can be safe if you use it responsibly. It’s important to have an AI use policy, train staff, and keep donor or beneficiary details out of prompts. For stronger protection, enterprise options like Microsoft Azure OpenAI or Copilot provide better data controls.
What should nonprofits not put into ChatGPT?
Never paste donor information, financial data, login credentials, or identifiable beneficiary details. A good rule of thumb: if it would be a problem to see it posted publicly, don’t put it into ChatGPT.
How can a nonprofit monitor ChatGPT use?
You can start by auditing how your team is already using ChatGPT. If you use Microsoft 365, enable Data Loss Prevention (DLP) rules to flag when sensitive data might be shared with AI tools. Regular training and policy reviews are also key to long-term monitoring.
What’s the best way to secure ChatGPT for nonprofits right now?
- Audit your team’s current use.
- Delete any shared links.
- Document clear policies.
- Train staff and volunteers.
- Explore enterprise-grade AI options.
Can ChatGPT be used for grant writing safely?
Yes, as long as you don’t paste sensitive donor information or confidential financial details into prompts. You can safely use ChatGPT to brainstorm ideas, structure proposals, or polish draft language if the data you provide is anonymized.
What happens if a nonprofit’s ChatGPT conversation gets indexed on Google?
First, delete the shared link directly in ChatGPT. Then, use Google’s “Remove Outdated Content” tool to request that the page be removed from search results. Finally, review your team’s practices to prevent the same issue from happening again.
Should nonprofits use free ChatGPT accounts?
Free accounts may be fine for experimenting, but they lack enterprise protections. For nonprofits handling sensitive data, it’s safer to use enterprise options like Azure OpenAI or Microsoft Copilot, which provide stronger compliance, admin controls, and monitoring.
Do shared ChatGPT conversations get stored permanently?
Shared links remain active until they are manually deleted. Deleting a chat from your history does not remove the shared version, you must delete the shared link separately. If left untouched, they can remain visible online indefinitely.
Can ChatGPT help nonprofits without risking data privacy?
Yes. Use it for tasks that don’t involve sensitive data, like drafting newsletters, brainstorming fundraising event ideas, or creating volunteer recruitment posts. The key is to keep private information out of your prompts.
This blog post was reviewed and validated by Gareth Young, a Microsoft Security and Compliance Expert with 15 years of experience in Microsoft solutions. As the founder of Levacloud, Gareth specializes in Security, Modern Work and Security Arcitecture. He holds multiple Microsoft certifications, including: AZ-500, MS-500, SC-400, MS-101, MS-100, MS-900 as well as the CISSP certification.





