AI Acceptable Use Policy Generator

Answer nine questions and get a complete AI acceptable use policy for your company. The policy updates as you type. Copy it, or have the PDF emailed to you.

Regulations and frameworks that apply
Data that must never go into an AI tool

Your policy

Acme Health AI Acceptable Use Policy

1. Purpose and scope

This policy sets the rules for using AI systems at Acme Health. It applies to employees, contractors and any third party acting on behalf of Acme Health. It covers chat assistants, coding assistants, AI features inside other software, and AI agents, whether the model is hosted by Acme Health or by a provider.

Acme Health operates in healthcare. This policy supports Acme Health's obligations under HIPAA, SOC 2.

2. Approved AI tools

Only the following AI tools may be used for company work. Use of any other AI tool, including a personal account on an approved product, requires written approval from the Head of Security.

  • ChatGPT Enterprise
  • Microsoft Copilot
  • GitHub Copilot

3. Data that must not be sent to AI systems

The following data must not be entered into any AI tool, prompt, file upload or agent context unless the Head of Security has approved the specific tool for that data type in writing.

  • Protected health information (PHI)
  • Personal data of customers, employees or candidates
  • Passwords, API keys, tokens and other credentials
  • Proprietary source code
  • Customer confidential data and contract terms

4. Human review

A person must review AI output before it is sent to a customer, partner, regulator or the public, and before it is used in a decision about hiring, credit, coverage, care, discipline or any other matter that affects an individual.

The reviewer is accountable for the output. AI-generated content must be checked for accuracy, fabricated citations, and leaked confidential data before use.

5. AI agents and tool access

AI agents that call tools, browse, execute code or act on behalf of a user are permitted only when the agent and every tool or MCP server it can call appear on the approved list kept by the Head of Security.

An agent may hold only the permissions of the person or service it acts for. Write access to production systems, financial systems and customer records requires explicit approval for each agent.

6. Logging and retention

Acme Health records AI usage with the user identity, the tool or model used, the time, and the policy decision taken. These records are retained for 1 year and are available to the Head of Security, internal audit and regulators on request.

7. Incident reporting

Any suspected leak of data into an AI system, unexpected agent behavior, or output that harms a person must be reported to the Head of Security within one business day. Reports are handled under Acme Health's existing incident response process.

8. Enforcement and review

Violations of this policy may result in loss of access to AI tools and disciplinary action under Acme Health's code of conduct. The Head of Security owns this policy and reviews it at least once a year and after any material change to the AI tools in use or to applicable regulation.

Effective date: [insert date]. Approved by: [insert name and title].

This template is provided for general information and is not legal advice.

Get this as a PDF

We email the formatted PDF to you right away.

How the policy is structured

The generated policy has eight sections: scope, approved tools, prohibited data, human review, AI agents and tool access, logging and retention, incident reporting, and enforcement. Each answer in the form changes the matching sections, so a healthcare company that bans PHI in prompts and a SaaS company that allows approved coding agents get different documents.

From written policy to enforced policy

A document tells people what to do. The DeepInspect gateway applies the same rules to HTTP traffic between users, agents, and LLM APIs, by identity and data type, and writes an audit record for each decision. The AI Readiness Check shows where your current AI usage differs from your policy.

Frequently asked questions

What is an AI acceptable use policy?
An AI acceptable use policy is a written rule set for how employees, contractors, and software agents may use AI tools. It names the approved tools, the data that must stay out of prompts, when a person must review AI output, and who owns exceptions.
What should an AI acceptable use policy include?
At minimum: scope, a list of approved AI tools, prohibited data types, human review rules, rules for AI agents and MCP tools, logging and retention, incident reporting, and enforcement. The generator above produces all eight sections.
Which regulations does an AI policy support?
HIPAA, GLBA, SOX, GDPR, and the EU AI Act require documented controls over how personal data and AI systems are used. A written policy is the usual way to document those controls. Frameworks such as SOC 2, ISO 42001, and NIST AI RMF ask for the same evidence from an AI governance program.
How is an AI policy enforced?
A policy sets the rules, and enforcement needs a control on the traffic. The DeepInspect gateway sits inline between users, agents, and LLM APIs, evaluates each HTTP request against policy by identity and data type, and logs the decision. Overhead is under 50 ms.
Is the generated policy legal advice?
The output is a starting draft. Have your legal counsel review it before adoption, and fill in the effective date and approver.
Do I need to give an email address?
The policy on this page is free to read and copy without one. The email is used to send you the formatted PDF.
Free AI Readiness Check