Free template

AI acceptable use policy template

One page your team can read and sign. Fill in the brackets, adjust it to your business, and you have a policy today. Part of our AI governance framework.

Download the template

Plain text (Markdown). Opens in Word, Google Docs or any text editor. Not legal advice.

[Company Name] AI Acceptable Use Policy

Effective date: [date] Owner: [name, title] Review: every 6 months

1. Why we have this policy

We use AI to save time and serve clients better. This policy keeps company and client information safe, keeps a person accountable for everything that goes out, and makes it clear which AI tools are approved.

2. Who it covers

Every employee, contractor and intern who uses AI for [Company Name] work, on any device.

3. Approved AI tools

  • Company AI: [name of the company system, e.g. the AImpact OS]. Use this for any work that involves company or client information.
  • Other approved tools: [list]. Personal AI accounts may be used only for work with no company or client information, unless they are connected to the company system.
  • Anything else: ask [owner] before using it for work.

4. Information you may never put into an unapproved AI tool

  • Client or customer names, contact details, records or files
  • Employee personal information, pay or HR matters
  • Financial statements, pricing, contracts or bank details
  • Passwords, API keys or login codes
  • Health, legal or other regulated information
  • Anything marked confidential

When in doubt, leave it out, or use the company AI.

5. A person stays responsible

  • You own anything AI helps you produce. Read it before you use it.
  • Check facts, numbers, names and dates. AI can be confidently wrong.
  • Anything that goes to a client, the public, a regulator or a bank needs a human review first.
  • AI does not make final decisions about hiring, firing, pay, credit, or anyone's health or legal situation.

6. Actions that need approval

An AI tool or agent may not do these without a named person approving each time:

  • Send email, texts or messages outside the company
  • Spend money, place orders or change prices
  • Delete records or change a client's account
  • Post on social media or the website

7. Records

Company AI keeps a record of what it was asked and what it did. Don't try to get around the record or use a personal account to avoid it.

8. Be honest about AI

Don't present AI work as a client's own or as something it isn't. If a client asks whether AI was used, tell them the truth.

9. Report problems

Tell [owner] right away if you think company or client information went into an unapproved tool, or an AI did something it shouldn't have. Reporting quickly is never held against you.

10. Changes

[Company Name] may update this policy as tools and laws change. We'll tell you when it does.


I have read and will follow this policy.

Name: ______________________ Signature: ______________________ Date: __________

Template provided by AImpact Nexus (aimpactnexus.ai). Adapt it to your business; it is not legal advice.

Questions

What should an AI acceptable use policy include?
Which AI tools are approved, what information may never go into AI, that a person reviews and owns anything AI produces, which actions need approval, how AI use is recorded, and how to report a problem. This template covers all six on one page.
Is this template legal advice?
No. It is a practical starting point written for small businesses. Adapt it to your business and have it reviewed if you are in a regulated industry.
How do we make the policy stick?
Give people an approved AI that is easier than the unapproved ones, and use software that enforces the rules: permissions, approvals and an audit trail. That is what the AImpact OS does.

Support and training

We support you ourselves, and we train your team

AI only pays off when your people use it. So we don't hand you a login and leave. We train your team, answer fast, and keep improving the system with you every month.

  • Support from the people who built it

    No call center and no ticket black hole. Ask right inside your OS and it reaches our team in Fort Wayne, the same people who set up your system.

  • Fixes and changes, often the same day

    One client texts a change and it ships the same day. A plant manager goes from a plain-English request to a live tool the same day. Bug fixes and up to 2 hours a month of small changes are included.

  • Hands-on training included

    Every implementation includes live training sessions for your team, then close support for the first 30 to 90 days after go-live. We can train on site in Indiana, Ohio, Michigan and Illinois.

  • Training that keeps going

    One-minute training videos built into the OS, new features explained as they ship, and an AI Foundations Workshop for your leadership team.

Want the rules enforced, not just written?

The AImpact OS puts permissions, approvals and an audit trail on every AI action. Thirty minutes and we'll show you.