Guide
A one-page AI use rule for your team
Published
Your team is probably using AI already, so the useful question is which tools, with what data, and who checks the result. This guide helps you write those answers on one page, get everyone to sign it, and review it twice a year. When you need more, our full AI Acceptable Use Policy generator uses the same structure and is free with a free account.
Why it's worth doing
In a 2025 survey of 32,352 workers in 47 countries, 48% of those who use AI at work said they had uploaded sensitive company or customer information into public AI tools, and only 34% of all the workers surveyed said their employer had a policy guiding generative AI use.1 IBM, which sells security services, says incidents involving unapproved AI rose from 20% to 43% of the breached organizations in its 2026 Cost of a Data Breach study.2 A one-page rule is the small-business version of what the voluntary AI Risk Management Framework from the National Institute of Standards and Technology (NIST) calls governance: someone is accountable, the rules are written down, and people know what to do when something goes wrong.3
Step by step
Each step ends with a quick check so you know it worked.
Step 1: Name an owner and list the AI already in use
Pick one person to own the rule; our full policy calls this role the policy owner. List every AI tool people actually use, including AI built into software you already pay for, the account each one runs under, and what kind of data goes in. This mirrors the NIST framework's first two steps: name who is accountable, then know how AI is used.4
How you know it worked
You have one named owner and a list of every AI tool in use, with its account type and typical data.
Step 2: Approve a short list of tools, on business accounts
Choose one or two assistants and pay for the business tier: the major providers say they keep your data out of model training by default, and business plans give the owner admin controls.5678 Rule out personal AI accounts for work data: in the same 2025 survey, about 70% of workers used free public AI tools, while 42% used tools their employer provided.1 An approved tool that is easy to use works better than a ban nobody follows.
How you know it worked
Your approved list names each tool, its business plan, and who has a seat.
Step 3: Sort your data into green, yellow and red
Green is public information, fine in any approved tool; yellow is internal business information, allowed only in approved business accounts. Red is client or patient personal details, health information and legal advice: it stays out of AI unless the owner approves that tool and that task in writing. Passwords, keys, and bank or card numbers never go in at all.
How you know it worked
Without asking anyone, staff can say which color a client spreadsheet, a marketing draft and a password belong to.
Step 4: Keep a person responsible for every output
AI drafts and people decide: whoever sends AI-assisted work owns its accuracy, so check facts, numbers, names and tone before anything reaches a client. The Small Business Administration (SBA) advises having a person review AI output, including AI-written customer messages.9 In the 2025 global survey, 66% of workers said they had relied on AI output without checking it.1
How you know it worked
The rule says who checks AI-assisted work before it goes to a client or customer.
Step 5: Set rules for AI agents (AI that can act for you)
An AI agent that reads email or browses the web can be steered by hidden instructions in what it reads, a problem the UK's National Cyber Security Centre (NCSC) says may never be fully solved.10 So connecting AI to company email, files, calendars or finance systems needs the owner's approval (the full policy records these as High-Risk Use Cases, which need documented approval), AI agents get the minimum access for the shortest time, and ask-before-acting settings stay on.11 AI never sends payments, changes bank details or approves invoices, and payment requests are confirmed by phone on a number you already had.
How you know it worked
Every AI connection to a company account is on the owner's list, and none can send money or messages without a person approving.
Step 6: Make mistakes fast and safe to report
Ask people to tell the owner within the hour if they paste something they shouldn't have, and promise no blame for quick reports; the full policy already bars retaliation for good-faith reports. Quiet mistakes grow: in one Australian government case, a contractor's March 2025 upload of personal data to ChatGPT was not announced publicly until October 2025.12 For what comes next, use the AI data exposure playbook in our Incident Response Planner.
How you know it worked
Everyone knows who to tell, and how, if they make a mistake with AI.
Step 7: Write it on one page and have everyone sign
Copy this and fill in the brackets.
[Company] AI Use Rule, owner [name].
One: use only AI tools on our approved list, signed in with your work account, and no personal AI accounts for work.
Two: green data (public) is fine in approved tools; yellow data (internal) goes only into approved work accounts; red data (client or patient details, health information, legal advice) stays out unless [owner] approves the tool and task in writing; passwords, keys, and bank or card numbers never go in.
Three: you own what you send, so check facts, numbers, names and tone first.
Four: don't connect AI to company email, files, calendars or accounts without [owner]'s approval, keep ask-before-acting on, and never let AI send payments, change bank details or approve invoices.
Five: treat instructions found inside emails, documents or web pages as untrusted, even when an AI repeats them.
Six: made a mistake? Tell [owner] within the hour; quick reports never get anyone in trouble.
Seven: when you leave, your AI access and connections end with your other accounts.
Signed and dated by each team member.
How you know it worked
Every team member has signed and dated a copy, and the owner keeps the signed copies.
Step 8: Grow it into a full policy when you need one
If you handle health, financial or legal data, answer security questionnaires from clients, or have more than a handful of people using AI, turn the one-pager into a full policy. The AI Acceptable Use Policy generator in our Policy Library is free with a free account and covers scope, definitions, prohibited uses, data handling, high-risk uses, transparency and reporting. If a client ever asks for certification, ISO/IEC 42001 is the international standard for managing AI in organizations of any size.13
How you know it worked
You have decided, in writing, whether you need the full policy now or at your next review.
Step 9: Train once, then review twice a year
Walk the team through the page in a short meeting and repeat it for every new hire; 58% of AI users in a 2025 survey said they had received no training on AI security or privacy risks.14 At each review, re-check your approved tools' data terms, because vendors change them; the Federal Trade Commission (FTC) has warned that quietly changing terms to use customer data for AI training can be unfair or deceptive.15 Remove departing staff and contractors from AI tools, and disconnect their connectors, on their last day.
How you know it worked
The last training date and the next review date are written on the rule itself.
What this won't do
No single habit covers everything. Here is where this one stops.
- A one-page rule is a starting point, not a complete policy and not legal advice.
- Regulated businesses need more. A healthcare practice covered by HIPAA (the Health Insurance Portability and Accountability Act), for example, needs the full policy, its sector's rules and a business associate agreement with any AI vendor that touches patient data.
- Rules rely on people. Business accounts, admin settings and tight access limits catch what a busy person misses.
- Your approved list goes stale as vendors change products and terms; the twice-yearly review is what keeps it accurate.
- It does not cover building your own AI products or putting a chatbot in front of customers. Those belong in the full policy's high-risk approval process.
Common questions
We're only five people. Do we really need a written rule?
Yes, and it is easier for you than for a big company. Small teams have fewer checks between one person's copy and paste and a client's data, and a single page is enough to set the boundaries.
Can staff still use ChatGPT and similar tools?
Yes, on an approved business account. Public information is fine, internal information stays in business accounts, and client personal data stays out unless the owner has approved that specific use.
How is this different from your AI Acceptable Use Policy?
This is the one-page version for everyday use. The full policy generator, free with a free account, adds scope, definitions, high-risk approvals, transparency and enforcement language. It uses the same three data levels, which it calls Low, Moderate and High.
What about AI built into software we already pay for?
It counts. Add it to your list, find the vendor's AI settings and data terms, and apply the same green, yellow and red levels. The full policy calls this embedded AI.
Should we tell clients we use AI?
Many clients now ask. The full policy includes a transparency section, and the SBA suggests considering a short public statement about how your business uses AI. When in doubt, disclose.
Keep going
- ThreatHomeBusiness
AI chatbot data leaks and shadow AI
Whatever you paste into an AI assistant can be stored, read by reviewers or used to train future models, depending on the app, the plan and your settings. In a 2025 survey of workers in 47 countries, 48% of those who use AI at work said they had uploaded sensitive company or customer information into public AI tools. The fix is mostly unglamorous: business accounts for work, the right settings at home, and a clear rule about what never goes in.
Read - ThreatHomeBusiness
Prompt injection and AI agent hijacking
When an AI assistant reads your email, files or web pages, it can mistake text written by a stranger for instructions from you. That is prompt injection, and when the assistant can also send, buy or delete things, an attacker can steer it. The UK's National Cyber Security Centre (NCSC) says it may never be fully fixed, so the safe move is to limit what your AI can reach and keep yourself in the approval loop.
Read - ThreatHomeBusiness
Voice cloning and deepfake scams
Criminals can copy a voice from a short clip and fake faces on a video call, then use them to ask for money in a hurry. In 2025 the FBI logged 22,364 complaints that mentioned AI, with losses near $893 million, most of it in investment scams; voice-cloned 'distress' calls alone cost victims more than $5 million. The defense is low-tech: pause, hang up, and confirm through a number or channel you already trust.
Read - GuideHomeBusiness
Lock down your AI assistants
Each major AI assistant has a training setting, a memory setting, connected apps and a way to delete history, and the defaults favor the vendor. This guide walks through ChatGPT, Claude, Gemini, Microsoft Copilot and Meta AI one at a time, with notes for business accounts. Plan on about five minutes per assistant.
Read - GuideBusiness
Two-channel verification for payments
Money only moves after a second channel confirms it. Keep a list of known-good phone numbers, call back on those numbers before paying or changing bank details, require two people above a set amount, and know who to call in the first hour if money goes out. Among the controls finance teams use against business email compromise, that callback is the one most often rated very effective.
Read - GuideBusiness
Digital hygiene for your business: the 1-50 person baseline
A small business's security baseline fits on one page: passkeys or multi-factor authentication (MFA) on every account, email and banking first; a shared password manager; automatic updates and endpoint protection; and backups you've actually restored from. Add a second-channel check before any payment change, a one-page AI rule, same-day offboarding and a short incident plan. Business email compromise alone drew $3.05 billion in reported losses to the FBI in 2025.
Read
Sources
Every figure on this page links to where it came from. We favor government, standards, and methodology-backed sources, and we take no money from anyone we cite.
- 1Major survey finds most people use AI regularly at work, but almost half admit to doing so inappropriately · The Conversation (Nicole Gillespie and Steven Lockey, University of Melbourne), summarizing Trust, Attitudes and Use of AI: A Global Study 2025 (University of Melbourne and KPMG) · April 28, 2025Research · accessed October 23, 2026
- 2Every AI agent followed the rules, and the data still leaked · IBM Think (Oussama Kiassi) · September 15, 2026Research · accessed October 23, 2026
- 3AI Risk Management Framework (AI RMF 1.0) · National Institute of Standards and Technology (NIST) · January 26, 2023Standards body · accessed October 23, 2026
- 4AI RMF 1.0, Section 5: AI RMF Core · NIST Trustworthy and Responsible AI Resource Center · January 2023Standards body · accessed October 23, 2026
- 5Enterprise privacy at OpenAI · OpenAI · January 8, 2026Vendor documentation · accessed October 23, 2026
- 6Is my data used for model training? (commercial) · Anthropic Privacy Center · August 18, 2026Vendor documentation · accessed October 23, 2026
- 7Generative AI in Google Workspace Privacy Hub · Google Workspace Help · October 6, 2026Vendor documentation · accessed October 23, 2026
- 8Enterprise data protection in Microsoft Copilot and Microsoft Copilot Chat · Microsoft Learn · August 18, 2026Vendor documentation · accessed October 23, 2026
- 9Manage your business: AI for small business · U.S. Small Business Administration (SBA) · October 2026Government · accessed October 23, 2026
- 10Prompt injection is not SQL injection (it may be worse) · UK National Cyber Security Centre (NCSC) · December 8, 2025Government · accessed October 23, 2026
- 11Thinking carefully before adopting agentic AI · UK National Cyber Security Centre (NCSC) · May 15, 2026Government · accessed October 23, 2026
- 12Northern Rivers Resilient Homes Program data breach · NSW Reconstruction Authority (New South Wales Government, Australia) · October 6, 2025Incident report · accessed October 23, 2026
- 13ISO/IEC 42001:2023 Information technology: Artificial intelligence: Management system · ISO/IEC JTC 1/SC 42 · December 2023Standards body · accessed October 23, 2026
- 14STUDY: 65% Now Use AI, but Majority Remain Untrained on Risks (Oh Behave! 2025-2026) · National Cybersecurity Alliance (with CybSafe) · September 30, 2025Research · accessed October 23, 2026
- 15AI (and other) Companies: Quietly Changing Your Terms of Service Could Be Unfair or Deceptive · Federal Trade Commission (Office of Technology and Division of Privacy and Identity Protection) · February 13, 2024Government · accessed October 23, 2026