Before you paste customer information into an AI tool, or connect one to your inbox or documents, know what data you hold, keep the most sensitive data out, and read the vendor's data terms for your exact plan. Then name who may use the tool, have a person approve its output, and write a one-page policy.
This is general information, not legal advice. Terms change, so check each vendor's current pages yourself.
Start by classifying the data you hold
The FTC's guide for business, Protecting Personal Information, lists five principles: take stock, scale down, lock it, pitch it, and plan ahead. The first one applies directly to AI. It tells you to identify the sensitive personal information you hold and everywhere it is stored, including vendor systems. An AI tool is now one of those places.
A simple three-tier sort is enough for a small team:
- Public: your website copy, price list, published reviews, and product descriptions.
- Internal: schedules, draft proposals, process notes, and vendor quotes with no customer details.
- Sensitive: anything that identifies a customer or employee, plus payment, health, financial, legal, or login information.
Write the tiers down. The rest of this checklist depends on them.
What never goes into an AI tool
Unless you have checked the vendor's terms for your plan and decided the risk is acceptable, keep these out:
- Payment card numbers, bank account numbers, and Social Security numbers.
- Passwords, API keys, and one-time codes.
- Health, medical, or insurance details.
- Full customer lists, or a spreadsheet export with names, emails, and phone numbers.
- Signed contracts, legal correspondence, and anything under a confidentiality agreement.
- Employee records, including performance notes and anything used to decide who is hired, promoted, or let go.
The FTC's second principle, scale down, helps here. If you do not need to share a detail to get the task done, remove it. Example (hypothetical): replace "Maria Lopez, 14 Elm St." with "Customer A" before you paste a complaint into a drafting tool.
What to ask a vendor
Vendor terms differ, and they differ between a free consumer plan and a business plan from the same company. Do not assume one vendor's answer applies to another. As an example of how much they vary, here is what four pages said when we read them on November 18, 2026:
- Anthropic's privacy policy, effective September 10, 2026, says it may use inputs and outputs to train and improve its models "unless you opt out through your account settings," and that some uses continue even after an opt-out, such as safety reviews. A separate commercial-products page, dated August 18, 2026, says that by default it will not use inputs or outputs from its commercial products to train its models, though training can happen if you opt in, for example by reporting feedback.
- Google's Gemini Apps Privacy Hub says human reviewers review some data, and advises: "Please don't enter confidential information that you wouldn't want a reviewer to see." It says chat history is deleted after 18 months by default, and that reviewed chats are kept for up to three years.
- Microsoft's Copilot privacy page says prompts, responses, and data accessed through Microsoft Graph are not used to train its foundation models, and that Copilot only surfaces organizational data a user already has at least view permission to see.
These pages will change, and plans have separate terms. Re-read the page for your plan before you rely on any of this. The FTC has also said, in a February 2024 staff post, that it may be unfair or deceptive to quietly and retroactively loosen data practices. That is a reason to check again later, not a reason to stop checking.
| Question to ask | What a good answer sounds like |
|---|---|
| Is our content used to train your models? | A plain yes or no for our plan, in writing, with the settings page that controls it. |
| Do people at your company or your vendors read our chats? | A clear description of when human review happens and how to turn it off or avoid it. |
| How long do you keep our data, and can we delete it? | A stated retention period and a way to delete, with the deletion timeline. |
| Who owns what we put in and what comes out? | Your inputs stay yours. Output rights are stated in the terms. |
| Who can see our data inside the tool? | Access follows the permissions you already set, with admin controls and logs. |
| What happens if you have a security incident? | A commitment to notify you, in the contract. The FTC's guide says to require providers to report incidents. |
| Will you tell us before the terms change? | A notice process, not a quiet edit. |
Accounts and settings
Use a business or team account if one exists, owned by the company and not by one employee's personal email. Then check the settings:
- Turn off training or "improve the model" options where they exist.
- Turn off or limit chat history if you do not need it.
- Turn on two-step sign-in for every user.
- Review connections to your inbox, calendar, and shared drive. Connect only the folders the tool needs, not the whole drive.
- Remember that a connected tool can reach whatever the connected account can reach. Clean up old shared folders first.
Who may use which tool
Pick the tools your team may use and say so. Allow the approved tool for public and internal data. Allow sensitive data only in a tool you have reviewed, and only for people who need it. Ban personal accounts for company data. If someone wants a new tool, they ask first.
A person approves what goes out
AI tools make mistakes, and they can invent details. Nothing should reach a customer, a contract, or a payroll decision without a named person reading it first. The NIST AI Risk Management Framework is voluntary, but it backs the idea. It says documentation "can enhance transparency, improve human review processes, and bolster accountability," and one of its subcategories (MAP 3.5) calls for processes for human oversight to be defined, assessed, and documented. For a small team, that means a short written rule on who reviews what.
A one-page policy outline
Keep it to one page. Cover these points:
- Purpose: why the business uses AI tools.
- Approved tools: the list, the plan for each, and the owner of each account.
- Data tiers: what is public, internal, and sensitive, and which tier each tool may touch.
- Never paste: your list from above.
- Review: who approves outputs before they go to a customer or affect a person.
- Connections: who may connect a tool to email or documents, and to which folders.
- Incidents: who to tell, and how fast.
- Review date: when you will re-check vendor terms. Put a recurring reminder on the calendar.
If something is pasted by mistake
The FTC's last principle is plan ahead, and its breach response guide is a useful model. Act in this order:
- Stop using that chat and tell the person in charge.
- Write down what was pasted, which tool, which account, and when.
- Delete the chat or use the vendor's deletion tools, and read the vendor's terms to see how deleted data is handled.
- Change any password or key that was pasted.
- Decide whether customers or others must be told. Many states have breach notice rules, so for sensitive data ask a lawyer.
- Update the policy so it does not happen again.
A note for Illinois employers
If you employ people in Illinois, the Illinois Human Rights Act now has a section on AI. Public Act 103-0804 took effect January 1, 2026. It makes it a civil rights violation for an employer to use AI for recruitment, hiring, promotion, discharge, discipline, and similar decisions if it has the effect of discriminating against protected classes, or to use zip codes as a proxy for protected classes. It is also a violation to fail to give an employee notice that AI is used for those purposes. The law tells the Illinois Department of Human Rights to write rules on when, how, and in what time period notice is given. Check the current Department rules and ask a lawyer before you use AI in any employment decision.
Where we fit
We build and run AI workflows for small businesses, and our AI and automation plans are priced publicly: Monitor is $149 a month with setup from $349. You own your accounts and data. If you are also curious how AI tools describe your business, see how to check what ChatGPT, Gemini and Perplexity say about you. Prices are on our pricing page.
