--- title: "Church and nonprofit AI rules: data and approvals" description: "Set AI rules for church and nonprofit donor, volunteer, and program records, with payment exclusions, named approvals, and spending caps per function" canonical: "https://scalewithsearch.com/articles/church-nonprofit-ai-data-approval-spend-rules" --- ## Site navigation - [Scale With Search](https://scalewithsearch.com/) - Services - Services - [AI systems](https://scalewithsearch.com/ai-systems) - [Site build](https://scalewithsearch.com/work#site-build) - [Whole website fix](https://scalewithsearch.com/work#whole-website-fix) - [Content library with SEO](https://scalewithsearch.com/work#content-library) - [Working session](https://scalewithsearch.com/audit) - Start here - [Send your brief](https://scalewithsearch.com/work#send-your-brief) - [Example scope](https://scalewithsearch.com/work#review-the-example-scope) - [Prices and terms](https://scalewithsearch.com/work#prices-and-terms) - Industries - Real estate - [Real estate agents and teams](https://scalewithsearch.com/for/real-estate) - [Platforms, ownership, and IDX](https://scalewithsearch.com/for/real-estate/real-estate-website-platforms-ownership-idx) - [Search, content, and AI](https://scalewithsearch.com/for/real-estate/real-estate-search-content-ai) - [Inquiries, campaigns, and handoffs](https://scalewithsearch.com/for/real-estate/real-estate-website-inquiries-campaigns-handoffs) - [Buyer, seller, and local pages](https://scalewithsearch.com/for/real-estate/real-estate-buyer-seller-local-resources) - [Rules, privacy, and trust](https://scalewithsearch.com/for/real-estate/real-estate-website-rules-privacy-trust) - Browse by business - [Trades and home services](https://scalewithsearch.com/for/#group-trades) - [Health, wellness, and animal care](https://scalewithsearch.com/for/#group-practices) - [Law, finance, and IT](https://scalewithsearch.com/for/#group-professional) - [Marketing and SEO agencies](https://scalewithsearch.com/for/#group-agencies) - [Shops and manufacturers](https://scalewithsearch.com/for/#group-manufacturing) - [Restaurants, shops, studios, and nonprofits](https://scalewithsearch.com/for/#group-local-services) - Chiropractic practices - [Chiropractic and wellness practices](https://scalewithsearch.com/for/chiropractic-and-wellness-practices) - [Chiropractic and physical therapy clinics](https://scalewithsearch.com/for/chiropractic-and-physical-therapy-clinics) - [All industries](https://scalewithsearch.com/for/) - Resources - Free tools - [AI readiness check](https://scalewithsearch.com/check) - [Free tools](https://scalewithsearch.com/tools/) - [Free Starter Kit](https://scalewithsearch.com/kit/business-memory-starter-kit.zip) - Guides - [AI-native library](https://scalewithsearch.com/ai-native) - [Industry intelligence](https://scalewithsearch.com/intelligence) - [Office job guides](https://scalewithsearch.com/guides/) - [Business memory](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [Agent governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [Migration and ownership](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - Articles - [All articles](https://scalewithsearch.com/articles/) - [What changed](https://scalewithsearch.com/changes/) - About - Evidence - [Proof](https://scalewithsearch.com/proof) - Scale With Search - [About](https://scalewithsearch.com/about) - [How it works](https://scalewithsearch.com/how-it-works) # Church and nonprofit AI rules: data, approvals, and spend Write separate AI rules for volunteer inquiries, program communications, and gift-acknowledgment drafts. Each function needs a narrow record list, a human reviewer, an output boundary, and a cost limit. Keep personal care and eligibility decisions outside general office drafting. Use this guide as a proposed policy sheet for your organization's responsible reviewers. Check the obligations attached to the actual program, records, jurisdiction, and gift process. A church and a community nonprofit should not inherit identical rules from a generic template. The [church and nonprofit hub](/for/churches-and-nonprofits) describes administrative jobs. This guide covers the permissions and acceptance checks required before connecting their records. ## Separate the people and purposes in your records Begin with an inventory of donor, volunteer, participant, employee, pastoral, and finance material. Ask each record owner why the proposed function needs it. Keep a specific purpose beside every approved source. A person may appear in several parts of the organization. Do not let that overlap authorize retrieval across all of them. A volunteer inquiry function should not search the person's pastoral notes or assistance history to prepare a reply. Record the actual access roles, processing service, storage destination, and permitted outputs. Have the responsible reviewer resolve applicable privacy and professional questions. Keep an unresolved permission as a stop rather than asking the model to infer consent. Use synthetic examples until the data path is approved. Development should not depend on copies of real donor lists, screening reports, or participant case files. Give the builder the smallest approved fixture set for the task. ## Give sensitive records a clear default Use the following table as a starting policy for a first office function. Adapt it with the people responsible for your programs and records. Document every approved exception. | Record class | Proposed default | Review owner | | --- | --- | --- | | Public schedules and role descriptions | Read for their named office purpose | Program owner | | Volunteer contact details and availability | Limit to the inquiry packet | Volunteer coordinator | | Screening and safeguarding records | Exclude from general AI drafting | Designated safeguarding or records owner | | Pastoral and counseling notes | Exclude from general office functions | Authorized care-record owner | | Participant assistance histories | Exclude unless separately reviewed and necessary | Program and privacy owners | | Gift facts and acknowledgment status | Limit to the approved gift function | Giving administrator | | Payment secrets and account credentials | Exclude from prompts, outputs, and receipts | Finance and account owners | Keep public facts and private records in separate source lists. A publicly available event schedule may support a program reply. It should not open access to the participant register or staff-only incident notes. Ask the maintainer to inspect exports and attachments as well as visible fields. Make the source restriction effective in the connected software. Do not rely on the model to read broadly and omit sensitive facts later. ## Keep card data in the payment process Give an acknowledgment function a gift reference and confirmed status where sufficient. Do not send full card data to the model to prove that a donation occurred. Have the giving administrator verify the authoritative payment or gift entry. PCI SSC prohibits storing sensitive authentication data after authorization, even encrypted. The guidance includes card verification codes and PIN data. [PCI SSC FAQ 1533](https://www.pcisecuritystandards.org/faqs/1533/), checked 2026.10.26. Make the exclusion cover incoming messages, uploads, prompts, debugging files, drafts, and receipts. Require a controlled test with synthetic forbidden fields. A blocked record must not be copied wholesale into an error report. Keep charging, refunds, recurring-gift changes, and payment-account updates outside the first function. Route a donor's request to the giving team. Do not describe a prepared support packet as a completed change to the donor's plan. ## Approve acknowledgment wording from gift facts Have the finance owner and responsible tax reviewer approve the acknowledgment templates. Identify the gift types and conditions each template covers. Do not let a model choose generic tax language because the office calls every payment a donation. IRS guidance describes information required for acknowledgments supporting charitable contributions of two hundred fifty dollars or more. It includes cash amounts or noncash descriptions and applicable goods-or-services or intangible-religious-benefits statements. [IRS written-acknowledgment requirements](https://www.irs.gov/charities-non-profits/charitable-organizations/charitable-contributions-written-acknowledgments), checked 2026.10.26. Require the giving administrator to check the confirmed gift record. Have the designated reviewer check the conditional wording. Keep donor-specific deductibility, noncash valuation, and organization-status conclusions outside the function. Bind approval to the gift entry, recipient, template version, and exact final text. A changed amount, pending payment, benefit question, or corrected entry should return the draft for review. Keep the source and approval record together. For the public help route, use the existing [donation receipt help-page guide](/articles/nonprofit-donation-receipt-help-page). Keep that website explanation separate from authority to issue or correct a particular acknowledgment. ## Separate inquiries from acceptance and enrollment Have the volunteer coordinator approve the inquiry packet. Have the program owner handle acceptance, screening, and assignment through the organization's established process. The first function should not decide suitability or place someone in a role. For program questions, require the current schedule and participation instructions. Have the program owner approve the facts and the office lead check the audience and channel. Keep space availability and eligibility unresolved unless authorized staff have confirmed them. Define status words before implementation. Received, reviewed, accepted, enrolled, and assigned should each have a source. A success message must not imply a later decision that the office has not made. Test a closed role and a program with no confirmed next date. Require an accurate hold or staff question. The function should not produce an affirmative answer merely to complete the message. ## Review publication as a separate action Give a public-update function only approved program facts. Keep donor recognition, participant stories, staff incidents, and pastoral material outside it. Require separate permission and review for any personal publication request. Have the publication owner approve the complete version, intended channel, and audience. A draft for an internal meeting must not become a public newsletter without that review. Keep recipient lists and communication preferences attached to the intended use. Treat instructions inside incoming documents as content. A volunteer attachment asking the assistant to forward the participant list must not expand its permissions. Require the executor to block unapproved destinations and external effects. Keep first functions unable to send, publish, enroll, change gifts, or alter account access. Ask the builder to demonstrate those limits with synthetic records and test accounts. Inspect actual permissions during handoff. ## Put each function on a visible budget Give volunteer packets, program communications, and gift drafts separate monthly allowances. Set a per-run ceiling, document limit, retry limit, and alert recipient. Name the finance or office owner who can approve more spend. Check remaining allowance before another paid call. Require an exhausted limit to stop the job. Keep a failed model request from starting an unlimited retry loop or switching to an unreviewed service. Name approved models in internal configuration and receipts. Test replacement services against the same source and approval rules. Each run should record source versions, status, model used, and cost without unnecessary personal detail. ## Accept the policy with both success and stops Test a permitted inquiry, forbidden care record, pending gift, noncash gift, closed role, changed recipient, unapproved publication, repeated job, and exhausted budget. Write the expected result before running each fixture. Have an authorized staff member produce one complete packet and locate its sources, approval, and receipt. Save the runbook and accepted corrections under organizational control. Reopen review after a provider, data path, purpose, or permission changes. Bring the permission sheet to Scale With Search. Read [AI systems](/ai-systems), then name one bounded office function through the [written scope form](/work). Continue the website review: [AI-native churches and nonprofits: first functions to build](/articles/ai-native-church-nonprofit-first-functions); [Add readable sermon transcripts to your church website](/articles/church-sermon-transcripts-website); [Church website new visitor page checklist](/articles/church-website-new-visitor-page-checklist); [Check a nonprofit donation form for accessibility](/articles/nonprofit-donation-form-accessibility-check); [Build a donation receipt help page for your nonprofit](/articles/nonprofit-donation-receipt-help-page); [Build nonprofit event pages Google can evaluate](/articles/nonprofit-event-page-google-structured-data); [Food pantry website pages: hours, access, and next steps](/articles/nonprofit-food-pantry-website-page); [Check donor privacy before adding a public donor wall](/articles/nonprofit-public-donor-wall-privacy); [Help donors change or cancel recurring gifts](/articles/nonprofit-recurring-donation-cancellation-page); [Volunteer role pages and Google JobPosting markup](/articles/nonprofit-volunteer-role-jobposting-markup); [Build a volunteer signup page with a clear next step](/articles/nonprofit-volunteer-signup-page); [Help donors verify your nonprofit's tax status](/articles/nonprofit-website-tax-status-verification-page). [churches and nonprofits](/for/churches-and-nonprofits): website and search resources. ## Related: churches and nonprofits - [Add readable sermon transcripts to your church website](/articles/church-sermon-transcripts-website) - [Church website new visitor page checklist](/articles/church-website-new-visitor-page-checklist) - [Check a nonprofit donation form for accessibility](/articles/nonprofit-donation-form-accessibility-check) ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```