# AI policy of [Company] Version [1.0] of [date] Next review: [date, at most 6 months later] Owner: [name, role] ## 1. Purpose We use AI tools to save time. These rules protect our data and the data of our customers. They apply to everyone who works for [Company]. Company data goes only into approved tools on company devices, never into AI apps on private devices or accounts. ## 2. Approved tools | Tool and plan | Use for | Highest data class | | --- | --- | --- | | [Chat assistant, business plan with data processing agreement, no training on inputs] | [Writing, research, code] | [Yellow] | | [Self-hosted model on our own servers] | [Internal and confidential documents] | [Red, with approval] | Every other tool is not approved for work, including free personal accounts, browser extensions and transcription apps. New tools are requested from [contact]. ## 3. Data classes - **Green**, any approved tool: public website text, published documents, questions without names, customers or figures. - **Yellow**, only tools with a contract: internal documents, meeting notes, non-public code, customer names in normal business context. - **Red**, only after a data protection check and written approval from [role]: health and HR data, unannounced financials, data under NDA. - **Never**, in any tool: passwords, API keys and access tokens. Logs and config files are fine for troubleshooting once secrets are removed and personal data (names, mail addresses, IP addresses) is anonymised; they then count as Yellow. If in doubt, the higher class applies. ## 4. Responsibility AI output is a draft. Whoever sends, publishes, merges or signs it has checked it and owns it like their own work. Decisions about people (hiring, performance, pay) are made by a person. AI that infers the emotions of employees is prohibited (AI Act Art. 5). ## 5. Labelling Realistic AI images, audio and video (deepfakes) are always labelled, also internally. AI text that informs the public on matters of public interest is labelled unless a person reviewed it and holds editorial responsibility. Customer chatbots say that they are an AI. [Communications] decides edge cases. ## 6. Agents and automation Every agent runs with the minimum rights its task needs: its own account or API key, only the scopes and endpoints it uses, read-only where reading is enough. No AI agent gets write access to production systems, mail sending or payments without a named owner and an approval step. Content an agent reads from outside (mails, web pages, tickets) is untrusted. Built-in safety checks (auto mode, permission prompts) stay on; modes that skip every check run only in a sandbox. Changes to systems go through code: the AI writes the change (e.g. an [Ansible playbook]), a person reviews and approves it, then the agent rolls it out. The larger the blast radius, the smaller the steps: [test system], [one production host], [all]. ## 7. Training Before getting access to an approved tool, everyone completes the short training on this policy. Attendance is recorded (EU AI Act, Art. 4). ## 8. Questions and requests [Name or shared mailbox], answer within [two working days]. --- Template as of November 2026, not legal advice. https://rfriedmann.de/ai-policy/