Skip to main content

    Free AI use policy generator

    You get
    Formats
    Cost
    Privacy

    Your answers

    Your policy updates as you answer. Everything stays in this browser tab: nothing you type is sent to Sonomos or anyone else.

    Your organization

    Adds the rule for your sector, such as HIPAA, FERPA or client confidentiality.

    Decides who approves exceptions, handles incidents and keeps records.

    AI tools
    Approved AI tools

    Business plans only. Every tool not on this list is unapproved for company information.

    Separate them with commas, e.g. Otter.ai, Notion AI.

    Personal AI accounts
    Data
    Never enter into an AI tool

    Each one becomes a specific line in the policy. Vague rules are hard to follow.

    Controls
    Data-masking tool

    Software on each computer that replaces sensitive values before a prompt is sent.

    Ownership and review

    The person who maintains the policy and the approved tool list.

    An email address or a chat channel.

    Your policy

    1,478 words in seven sections, plus a sign-off sheet

    Shaded text comes from your answers. Dashed text is still blank.

    [Organization Name] AI Acceptable Use Policy

    Effective date
    [Effective date]
    Policy owner
    Head of IT
    Applies to
    All employees, contractors and third parties
    Review cycle
    Every year
    Next review
    [Next review date]
    Version
    1.0

    Purpose

    This policy sets out how personnel at [Organization Name] may use AI tools for work: which tools are approved, what information must never be entered into them, how they must be configured, and what to do when something goes wrong. It is not a ban on AI. It is how [Organization Name] uses AI with confidence.

    1. Scope

    1.1

    This policy applies to all employees, contractors, and third parties ("personnel") who use generative AI tools, large language model interfaces, AI coding assistants, AI search tools, or AI content generation tools (collectively, "AI tools") in connection with their work for [Organization Name], whether on company-owned or personal devices.

    1.2

    It applies to all AI tools, including but not limited to ChatGPT, Claude, Gemini, Microsoft Copilot, GitHub Copilot, Cursor, Perplexity, Grok, and similar services, regardless of whether accessed through a browser, desktop application, API, or embedded in another product. That includes AI features built into other software, such as meeting transcription, writing assistants and the AI features of email, CRM and document tools.

    1.3

    In this policy, "company information" means any information [Organization Name] creates, receives or holds that is not public, including information about clients, customers and personnel, as classified in [Organization Name]'s information classification policy where one exists.

    2. Approved tools

    2.1

    [Organization Name] has approved the following AI tools for use with company information, subject to the conditions in this policy:

    ChatGPTApproved plan or account: ChatGPT Enterprise, company workspaceRequired settings: Sign in with the company workspace account. Business data is excluded from model training by default; keep it that way. Apps and connectors only with approval.
    Microsoft 365 CopilotApproved plan or account: Microsoft 365 Copilot licenseRequired settings: Signed in with a work (Microsoft Entra ID) account, so enterprise data protection applies. Never a personal Microsoft account.
    2.2

    All other AI tools are unapproved for use with company information. Using an unapproved AI tool with company information is a violation of this policy.

    2.3

    To ask for a new tool, or for an exception to this policy, contact the policy owner. Exceptions are granted in writing only.

    2.4

    Work with AI tools happens in the approved accounts above. Personal AI accounts, free or paid, must not be used for [Organization Name] work, and company information must never be entered into them. Using AI tools for personal tasks on a company device is permitted, provided no company information is included in any prompt or attachment.

    2.5

    Approved tools may be used with public and internal information. Confidential information may be used only where [Organization Name]'s information classification allows it for that tool. The information listed in Section 3 is not permitted in any AI tool, approved or not, unless an exception is documented under Section 3.

    2.6

    Personnel are responsible for the work they produce with AI tools. Check facts, figures, citations and code before relying on AI output or sharing it, and do not use AI output as the only basis for a decision about a person, such as hiring or performance.

    3. Prohibited data

    3.1

    The following must not be entered into any AI tool, including approved tools, whether by typing, pasting, uploading a file or connecting an integration, unless a specific exception is documented and approved in writing by the policy owner:

    Regulated data
    • Protected health information (PHI) as defined by HIPAA: patient names, diagnoses, medical record numbers, dates of service, and any other individually identifiable health information
    • Personally identifiable information (PII) of customers, employees, or other individuals: names combined with government IDs, financial account numbers, biometrics, or other identifying information
    • Payment card data: primary account numbers (PANs), CVVs, track data and PINs
    Confidential business information
    • Client and customer records, including customer contracts, pricing schedules and contract terms marked confidential
    • Unpublished financial results, projections or forecasts
    • Trade secrets, M&A targets, deal terms and due diligence materials
    • Proprietary source code and internal tooling, including algorithms and model weights
    • Attorney-client privileged communications
    • Personnel records, compensation data and HR investigation materials
    Authentication material
    • Passwords, API keys, tokens, certificates, private keys, or any other credential, including credentials inside code, logs or configuration files
    3.2

    When in doubt whether information falls into a prohibited category, treat it as prohibited and ask the policy owner before proceeding.

    4. Required settings and technical controls

    4.1

    Personnel using approved AI tools must keep the following settings in place:

    • Training opt-out. Turn off any setting that lets the AI provider use your prompts to improve its models. Business plans usually exclude business data from training by default; confirm it for each tool with the policy owner.
    • Chat history. Turn off saved conversation history for any session that involves confidential information. Where history cannot be turned off, do not enter confidential information.
    • Memory and personalization. Turn off AI memory features that store information across sessions when using AI tools for work, and delete any sensitive content already stored in memory.
    • Connected apps and integrations. Do not connect AI tools to company systems (email, CRM, code repositories, cloud storage) without prior review and approval by the policy owner.
    4.2

    The policy owner checks these settings when a tool is approved and at each review of this policy.

    Technical controls
    4.3

    Where an approved tool supports single sign-on, personnel sign in through [Organization Name]'s identity provider, so access can be reviewed and removed when someone leaves.

    4.4

    Personnel are encouraged to use a data-masking tool, which detects sensitive values, such as names, contact details, account numbers and credentials, on the device and replaces them before a prompt or file is sent. Masking reduces risk; it does not make the information in Section 3 permitted. Use an on-device masking tool, such as Locke, to keep sensitive values out of prompts.

    5. Incident response

    5.1

    If you believe you have sent prohibited data to an AI tool, whether by typing, pasting, uploading a file or through an integration, take these steps immediately:

    1. Stop the session. Do not continue the conversation or add more context.
    2. Delete the conversation. Use the tool's delete feature to remove it from your history. This may not immediately delete it from the provider's servers.
    3. Report it within 24 hours. Tell the policy owner at [email address or chat channel]. Include the AI tool used, the kind of data involved, the date and time, and your best estimate of how much was shared.
    4. Do not try to fix it alone. Leave contact with the AI provider to the policy owner.
    5.2

    Failure to report a suspected incident is treated the same as the underlying policy violation.

    5.3

    Violations of this policy are handled under [Organization Name]'s disciplinary process, from coaching to a written warning to termination, applied consistently. Prompt, voluntary reporting is taken into account. For contractors and other third parties, a violation may end their access or their engagement.

    6. Training and acknowledgment

    6.1

    All personnel must complete AI acceptable use training before first using an AI tool for work, and every year after that. Training can be a walkthrough of this policy with the policy owner. It covers:

    • This policy and the prohibited data categories
    • How to recognize confidential information in your own work
    • The required settings for approved tools
    • How to report an incident
    6.2

    Personnel must acknowledge this policy in writing (electronic acknowledgment is acceptable) when they first receive it and every year after that. The policy owner keeps acknowledgment records for the duration of employment plus three years.

    7. Review and updates

    7.1

    This policy is reviewed and updated at least every year, and also when any of the following occur:

    • A new AI tool is approved or removed from the approved list
    • A significant change occurs in an approved tool's privacy terms or data handling
    • A regulatory change introduces new requirements applicable to AI tool use
    • An incident occurs that reveals a gap in the policy
    7.2

    The approved tool list in Section 2 is a living list. The policy owner reviews it every quarter and decides requests for new tools within 30 days.

    7.3

    Policy owner: Head of IT. The policy owner maintains this policy and the approved tool list. Questions about this policy go to [email address or chat channel].

    Acknowledgment

    I have read [Organization Name]'s AI Acceptable Use Policy, I understand it, and I agree to follow it.

    Name:
    Signature:
    Date:

    About this draft

    Drafted with the free AI use policy generator at sonomos.ai/tools/ai-use-policy-generator. It is a starting point, not legal advice. Before you adopt it, fill in anything in [brackets], check it against your other policies, contracts and the laws that apply to you, and have it reviewed by counsel. Then delete this note.

    A template, not legal advice. Laws, contracts and your other policies may require more. Have counsel review it before you adopt it.

    What the policy covers

    1. 1

      Scope

      Who the policy covers and which tools, including AI built into other software.

    2. 2

      Approved tools

      The tools people may use, the plan and settings for each, and the rule for personal accounts.

    3. 3

      Prohibited data

      The specific information that never goes into an AI tool, plus the rule for your sector.

    4. 4

      Required settings

      Training opt-out, history, memory and integrations, and technical controls such as data masking.

    5. 5

      Incident response

      Four steps for when someone pastes the wrong thing, and how violations are handled.

    6. 6

      Training and acknowledgment

      Training before first use, and a written sign-off every year.

    7. 7

      Review

      How often the policy and the tool list are revisited, and who owns them.

    Before you roll it out

    • Fill the blanks and check the settings

      Confirm each tool's plan and settings with whoever administers it, and replace anything left in brackets.

    • Fit it to the policies you have

      Point it at your information classification and disciplinary policies, or fold it into your existing acceptable use policy.

    • Launch it as permission, not a ban

      A note from leadership saying why it exists and which tools people can use, with an example for each role.

    • Collect sign-offs and book the review

      Use the acknowledgment form, keep the records, and put the next review date in the owner's calendar.

    Questions about AI use policies

    What is an AI use policy?

    An AI use policy, often called an AI acceptable use policy, is the document that tells employees which AI tools they may use for work, what information must never be entered into them, how those tools must be configured, and what to do when something goes wrong. Without one, each person makes their own call about what is safe to paste into ChatGPT, Claude or Copilot.

    What should an AI acceptable use policy include?

    Seven parts: the scope (who and which tools it covers), a list of approved tools, the data that must never be entered, the required settings and technical controls, incident response, training and acknowledgment, and a review schedule. This generator writes all seven, plus an acknowledgment form for employees to sign.

    Is this AI use policy generator free?

    Yes. There is no sign-up and no email gate. Answer the questions, then copy the policy or download it as a Word document.

    Is what I type sent anywhere?

    No. The policy is assembled by code running in your browser, and the Word file is built on your device. Nothing you type is sent to Sonomos or anyone else, and nothing is saved: closing the tab clears your answers.

    Is the generated policy legal advice?

    No. It is a structured starting point based on common practice, not advice about your situation. Sector rules such as HIPAA, GLBA, FERPA and the rules of professional conduct, client contracts and employment law can all require more or different wording. Have counsel review it before you adopt it.

    Can I edit the policy after I download it?

    Yes. The .docx file opens in Microsoft Word, Google Docs, Apple Pages and LibreOffice, with real headings and lists. Any blank you left empty is highlighted in yellow so you can find it. The Markdown copy pastes cleanly into Notion, GitHub or most wikis.

    How often should an AI use policy be reviewed?

    At least once a year, and whenever an AI tool is added or removed, a provider changes its data terms, a new regulation applies, or an incident shows a gap. Many organizations also review the approved tool list every quarter, because AI products change faster than policies do.

    Do employees need to sign an AI use policy?

    They should acknowledge it in writing when they first receive it and every year after that; electronic acknowledgment is fine. Auditors commonly ask for these records. The generated policy ends with a one-page acknowledgment form.