AI Training_
TRAIN YOUR TEAM WITHOUT LEAKING CONFIDENTIAL INFO_

Simple rules that prevent big mistakes: what not to paste into AI, placeholders, and a plain-English policy.
> simple rules that prevent big mistakes
AI tools are useful.
They're also very good at one thing: remembering what you paste into them (even when you didn't mean to).
If your team is using AI at work, you need clear rules.
Not complicated. Just clear.
---
THE CORE RULE_
If you wouldn't post it publicly, don't paste it into an AI tool.
That includes:
• client info
• addresses, phone numbers, emails
• passwords, codes, links
• internal documents
• financial details
• anything about minors (for churches/ministries)
---
WHAT TO DO INSTEAD_
1) REMOVE IDENTIFIERS_
Replace sensitive details with placeholders:
• "Client Name" → [CLIENT]
• "Invoice #39483" → [INVOICE]
• "Street address" → [ADDRESS]
You can still get help writing, organizing, and improving — without exposing data.
2) SUMMARIZE, DON'T DUMP_
Instead of pasting the whole email thread, write a 3–5 line summary and ask for a reply.
3) USE INTERNAL TOOLS WHEN AVAILABLE_
If you have Microsoft 365 / Google Workspace options that keep data in your org's environment, use those for internal content.
---
WHAT YOUR POLICY SHOULD SAY (IN PLAIN ENGLISH)_
• No passwords or access codes in AI
• No personal info (client/member/student)
• No private financial data
• No internal documents without approval
• Use placeholders by default
• When unsure: ask a supervisor
---
TRAINING THAT ACTUALLY WORKS_
A one-page policy + a 30-minute training beats a 10-page document no one reads.
> BOOK_AI_SAFETY_TRAINING_ → /contact
> GET_AN_AI_POLICY_TEMPLATE_ → /contact
> TRAIN_MY_TEAM_ → /services/consulting-training