Key takeaways
- A small business AI policy can fit on one page. It needs approved tools, banned data, account rules, review rules and a contact person.
- Only allow AI tools on business accounts that the company controls, not personal logins.
- Name the data that never goes into an AI tool, such as customer payment details, passwords and health records.
- A person must check AI output before it reaches a customer. This guide is general information and not legal advice.
A small business AI use policy is a short document that tells your team which AI tools they may use, what information must stay out of them, and who checks the results. One page is enough. The goal is to let people use AI with clear limits instead of guessing or hiding it.
This guide gives you the five parts to cover and example wording you can adapt. It is general information and not legal advice. Laws about privacy, employment and industry rules differ by place, so have a lawyer review your final policy.
Why a short policy helps
Staff are probably already using AI tools. Without a rule, they pick their own tools and paste in whatever is handy. A policy sets the boundaries before a mistake happens.
You do not need to write it from scratch in a legal style. NIST describes its AI Risk Management Framework as a voluntary framework to help organizations build trustworthiness into how AI is designed, used and evaluated. You can borrow its spirit by keeping your policy honest and easy to follow.
The five parts of the policy
| Part | What it answers | Example rule |
|---|---|---|
| Approved tools | Which AI tools may be used for work | Only the tools on our approved list, signed in with a company account |
| Data that never goes in | What must stay out | No passwords, payment card numbers, health records or private customer files |
| Accounts and admin | Who controls access | The owner holds the admin role and removes access when someone leaves |
| Review of output | Who checks AI work | A person reads and approves anything before it goes to a customer |
| Who to ask | Where questions go | Ask the named policy owner before trying a new tool |
Approved tools and banned data
Part 1: Approved tools
List the tools your business allows and say what each is for. If you have not picked one yet, read how to choose an AI assistant for your team.
Here is what vendors say about their business products, which is a reason to approve business plans over free ones.
- ChatGPT: OpenAI’s business page says your data is never used for training its models.
- Claude: Anthropic says commercial inputs and outputs are not used for training by default.
- Gemini: Google says Workspace does not use customer data for training models without prior permission.
- Microsoft 365 Copilot: Microsoft says prompts, responses and data accessed through Microsoft Graph are not used to train foundation models.
These promises are tied to the business products. They do not cover free personal accounts, so your policy should say “company accounts only.” Add a line that new tools need approval, and keep a simple list of what is approved.
Part 2: Data that never goes in
This part does the most to prevent harm. Write a plain list of banned data, then explain it in one sentence each. A sensible starting list follows.
- Passwords, security codes and API keys.
- Payment card and bank account numbers.
- Government ID numbers such as Social Security numbers.
- Health or medical records about customers or staff.
- Private employee files, such as reviews and pay records.
- Contracts and documents marked confidential.
- Anything a client told you in confidence.
The FTC’s guide for business is built on five principles: take stock of what personal information you hold, scale down to what you need, lock it, dispose of what you do not need, and plan ahead. They are a useful check for your list. If you do not need to give an AI tool a person’s details, leave them out.
Teach people to remove names and numbers before pasting text. For example, replace a customer’s name with “Customer A.” The AI can still help with the wording.
Accounts and review
Part 3: Accounts and admin control
Say that AI tools must be used with company-owned accounts. This lets the owner see who has access and remove people when they leave. It also keeps business data out of personal accounts that the company cannot manage.
Include these rules.
- The owner or a named admin creates and manages the accounts.
- Staff do not share logins.
- When someone leaves, the admin removes their access the same day.
- Turn on multi-factor sign-in where the tool offers it.
- The admin reviews which apps and integrations are connected to each tool.
If you use Microsoft 365 Copilot, remember that it only shows files a person already has permission to open, according to Microsoft’s privacy article. Fix your file sharing before you roll it out. Microsoft’s admin guide also suggests adding a link to your organization’s AI usage policy in the welcome email to users.
For Gemini, Google says admins can turn the Gemini app off, so the policy can state who decides that. For setup of a ChatGPT workspace, see how to set up ChatGPT for your business.
Part 4: Review of AI output
AI can sound confident and still be wrong. Microsoft’s own article says responses are not guaranteed to be fully factual and that people should use judgment before sharing them. Your policy should turn that advice into a rule.
- A person reads everything before it goes to a customer, vendor or the public.
- Check names, numbers, dates and legal or medical claims against a real source.
- Do not present AI work as a finished expert opinion.
- Keep a human in the loop on any automation. For example, the workflow in how to draft email replies with Zapier and AI creates drafts for a person to send.
- If your team records calls with AI, follow the consent steps in how to record and summarize meetings with AI.
Who to ask and what happens next
Name one person who answers questions, approves new tools and handles mistakes. In a small company this is often the owner or office manager.
Add a short mistake rule: if someone pastes banned data into a tool, they tell the policy owner right away. Make it clear that reporting early is better than hiding it. Then review the policy every six months or when you add a new tool, since vendor features change.
Roll it out
- Write the one-page draft using the five parts above.
- Have a lawyer review it, especially if you handle regulated data.
- Share it in a short team meeting and answer questions.
- Ask each person to confirm they read it.
- Put the policy where people can find it, and review it twice a year.
Tools in this guide
ChatGPT
by OpenAI
A general AI assistant for writing, research and everyday office tasks.
Best for Teams that want one general assistant for many tasks
Free plan, paid plans from Business Standard seat: $20 per user per month, billed yearly
Claude
by Anthropic
An AI assistant for writing, analysis and working through long documents.
Best for Teams that work with long documents and written content
Free plan, paid plans from Pro: $17 per month, billed yearly
Gemini
by Google
Google's AI assistant, built into Gmail, Docs and Meet for Workspace teams.
Best for Teams already paying for Google Workspace
Paid plans from Business Starter: $7 per user per month with a 1-year commitment
Microsoft 365 Copilot
by Microsoft
Microsoft's AI assistant that works inside Word, Excel, Outlook and Teams.
Best for Teams already paying for Microsoft 365
Paid plans from Copilot Business add-on: $18.00 per user per month, paid yearly (promotional through December 31, 2026)
Frequently asked questions
What should an AI use policy for a small business include?
Include the approved AI tools, the data that must never be entered, rules for accounts and admin control, a requirement to review AI output, and a named person to ask. One page is enough for most small teams.
Is an AI use policy required by law for small businesses?
This guide is not legal advice, so ask a lawyer about your situation. NIST's AI Risk Management Framework is a voluntary guide, and it is a useful reference when you write your own rules.
Can employees paste customer information into ChatGPT, Claude, Gemini or Copilot?
Set a clear rule. A safe default is no sensitive customer data in any AI tool unless the owner has approved that tool for that purpose. The FTC advises businesses to collect and keep only the personal data they need.
Sources
- AI Risk Management Framework (NIST)
- Protecting Personal Information: A Guide for Business (FTC)
- ChatGPT Business (OpenAI)
- Is my data used for model training? (Anthropic Privacy Center)
- Generative AI in Google Workspace privacy hub
- Data, Privacy, and Security for Microsoft Copilot (Microsoft Learn)
- Microsoft Copilot adoption and onboarding guide for IT admins (Microsoft Learn)
About the author
Andy Kang, AI Partner Team. Andy Kang writes the AI directory for AI Partner Team, which sets up and builds AI tools for small businesses alongside managed IT. Each page is written from the vendor’s own pricing, help and trust pages, and shows the day those pages were checked.
- Facts come from the vendor’s own website and help docs, linked on every page.
- Each page shows the date we last read those sources.
- We do not score or rank tools. We say who each one suits and who it does not.
- If a vendor does not publish a price, we say so instead of guessing.