EU AI Act
Your staff use ChatGPT. What the law asks, and a policy to adopt
No law mentions an AI use policy by name. The AI Act asks for AI literacy measures, prohibits a few uses and requires labels on some published content. The GDPR governs any personal data typed into a tool. A one-page policy, set out below, can cover all four.
By Oscar CobbeCurrent as at 15 minute read13 sources
What the law asks of a business whose staff use AI
Where staff use ChatGPT or another AI tool for the business's work, the business is a deployer under the EU AI Act. Article 3(4) defines a deployer as anybody using an AI system under its authority, other than in a personal non-professional activity. There is no size threshold. The Commission's Article 50 guidelines read authority as responsibility for deciding to use a system and how. They say staff acting on the business's instructions are not separate deployers. They do not deal with a tool used without the business's knowledge, and the policy below settles which tools are used.
| Duty | Where it comes from | Applies from | When it reaches you |
|---|---|---|---|
| Take measures to support AI literacy | AI Act Article 4, as replaced by Regulation (EU) 2026/1744 | 2 February 2025; reworded from 27 July 2026 | Any use of AI for the business's work |
| Do not infer the emotions of staff or job candidates | AI Act Article 5(1)(f) | 2 February 2025 | Where a system reads faces, voices, typing or other biometric data |
| Disclose deep fakes you publish | AI Act Article 50(4) | 2 August 2026 | AI images, audio or video that could pass as real |
| Disclose AI text published on matters of public interest | AI Act Article 50(4) | 2 August 2026 | Unless reviewed by a person, with an editor responsible |
| Protect personal data put into AI tools | GDPR Articles 5, 6, 9, 28 and 32, and Chapter V | 25 May 2018 | Whenever personal data goes into a tool |
| No AI intimate images of an identifiable person without consent | AI Act Article 5(1)(ba) | 2 December 2026 | Only where a tool is used for that purpose |
| Deployer duties for high-risk uses, such as filtering job applications or emotion recognition | AI Act Article 26 and Annex III points 1(c) and 4 | 2 December 2027 | Only for the uses Annex III lists |
AI literacy: measures, not a certificate
Article 4 has applied since 2 February 2025, and Regulation (EU) 2026/1744, the Digital Omnibus on AI, replaced its wording from 27 July 2026. Providers and deployers must take measures to support the AI literacy of their staff and others using AI on their behalf, taking into account their knowledge and experience, the context and the people affected. The duty does not require anybody to guarantee any specific level of AI literacy. A template that asks for a sufficient level, the earlier wording, overstates what is owed.
The Commission's questions and answers say a company whose staff use ChatGPT to write advertising text or to translate must comply, with staff told about specific risks such as hallucination, where a tool states made-up things as fact. They say there is no need for a certificate, that an internal record of trainings can be kept, and that no specific governance structure is mandated. They warn that asking staff to read a tool's instructions might be ineffective. That is why the policy below has staff go through it with a named person, and records the date.
The Regulation of Artificial Intelligence Act 2026, in operation since 31 July 2026 (S.I. No. 403 of 2026), gives Article 4 no notice and no fine of its own. Its contravention notice (section 71) lists Articles 16, 23, 24, 26, 27(3) and 50. Its fines follow Article 99(3) to (5). None of these names Article 4. The Commission says national law could penalise it, so this can change. The Article 4 guide has the detail.
What no tool may be used for at work
Since 2 February 2025, Article 5(1)(f) has prohibited using AI to infer the emotions of a person in the workplace or in education, except for medical or safety reasons. The Commission's guidelines on prohibited practices read the workplace broadly: anywhere work is done, physical or virtual, for employees, contractors, trainees and volunteers, and for job candidates during hiring.
Their examples of prohibited use include webcams and voice recognition tracking call-centre staff's emotions, emotion recognition during recruitment or probation, and supermarket cameras tracking staff's emotions. Assessing wellbeing or motivation is not a medical reason.
The dividing line is biometric data (Article 3(39)). The guidelines give the example of a system reading the tone of an article from its text, which is outside the prohibition. One reading emotion from typing, facial expressions or posture is inside it. Reading customers' emotions from biometric data, such as their voices on calls, is not caught by Article 5(1)(f). Article 50(3) requires the people exposed to it to be told, and Annex III point 1(c) makes such a system high-risk, with the Article 26 deployer duties from 2 December 2027.
S.I. No. 405 of 2026, made on 31 July 2026, designates the Workplace Relations Commission as market surveillance authority for Article 5(1)(f), other than in education institutions, and for the employment uses in Annex III point 4. Under the 2026 Act, also in operation since 31 July 2026, an authorised officer who suspects a breach of Article 5 may serve a prohibition notice (section 72). The officer may instead serve a notice of suspected non-compliance, which can lead to a fine (sections 79 and 105). The fine can be up to €35 million or 7% of worldwide annual turnover, whichever is lower for an SME (Article 99(3) and (6)). The WRC's page says further legislation in the coming months will provide for its supervision and enforcement powers.
From 2 December 2026, Article 5(1)(ba) also prohibits using AI to generate or manipulate realistic images, video or audio of an identifiable person's intimate parts, or of them in sexually explicit activity, without their explicit consent. For a business using a tool, the ban applies where it uses the tool for that purpose (Article 5(1a)(b)).
What you publish: when AI content needs a label
Article 50 has applied since 2 August 2026. Its chatbot and machine-readable marking rules fall on the companies that provide the tools. Paragraph 4 falls on the business using them, in two cases. The Article 50 guide covers the rest.
Deep fakes. If you publish AI-generated or manipulated image, audio or video content that is a deep fake, you must say so. Article 3(60) defines a deep fake as content resembling existing persons, objects, places, entities or events that would falsely appear to a person to be authentic or truthful. The Commission's Article 50 guidelines count consumer goods as objects, and give as an example an AI product image in an advert or on packaging that could mislead about the product. A real product on an AI background is not a deep fake if the advert does not mislead, and nor is a scene nobody would take for real, such as the guidelines' mice arguing over cheese in a cheese maker's advert.
Text. AI-generated or manipulated text published to inform the public on matters of public interest must be disclosed too. The guidelines read public interest widely, from politics and public health to consumer safety and economic or scientific developments. Their example puts advertising copy and product descriptions outside the rule, but not claims on, for example, health, consumer safety or sustainability. Text counts as published when an open-ended, fairly large number of unrelated readers can reach it. Private correspondence and internal texts are not published.
No disclosure is needed where the text has had human review or editorial control and a person or organisation holds editorial responsibility for publishing it. The guidelines say review means somebody with relevant knowledge examining the substance, and at least checking the facts. A spelling check, an editorial policy on paper or a cursory sign-off does not count. A substantive AI edit afterwards cancels the exception. They also say the person or function responsible should be named, with contact details, somewhere easy to find on the website.
Article 50(5) requires a disclosure to be clear and distinguishable, and given no later than the first time a person is exposed to the content.
Personal data in an AI tool is a GDPR question
In the Data Protection Commission's 2025 case studies, a data loss prevention tool at a financial sector organisation flagged that an employee had uploaded 32 CVs, including passport or visa details and photographs, to an external free AI tool. The organisation notified a personal data breach: the data had gone to a third-party site with no data processing agreement and was out of its control. It had no policies on free external tools, including AI, and agreed to review its policies and give its staff direction and training. The DPC's takeaways stress how easily free AI tools are used without an organisation's knowledge, and the importance of usage policies staff know about.
The GDPR does not mention AI tools, but three of its articles apply to them. Article 5(1)(f) requires personal data to be kept secure against unauthorised processing. Article 32(4) requires steps to make sure anybody acting under the business's authority processes personal data only on its instructions. Article 24(2) requires data protection policies where proportionate. A written rule about AI tools is an instruction of that kind.
Where a tool's provider processes personal data on the business's behalf, Article 28 requires sufficient guarantees and a contract with the terms Article 28(3) lists. The organisation in the DPC's case had no such contract. Where the provider's terms let it re-use what is typed in for its own purposes, such as training its models, it is not acting on the business's behalf for that use (Article 4(8)). A data processing agreement does not cover that use. Putting personal data in then needs a lawful basis under Article 6. It also has to fit the purposes people were told about (Articles 5(1)(b), 13 and 14). The DPC's AI guidance says such processing can affect those principles.
Health information is special category data, which also needs one of the conditions in Article 9(2). A clinic's patient notes are data concerning health, and so is a record of a client's allergy (Article 4(15)).
Sending personal data outside the European Economic Area (EEA) also needs a legal basis under Chapter V. For a US provider, that is the EU-US Data Privacy Framework if the provider is on its List. If it is not, the basis is usually Article 46 safeguards such as standard contractual clauses, because Article 49 covers only specific situations. The US transfers guide has the checks.
The DPC's guidance on AI and large language models (18 July 2024) supplies most of the questions in the policy's approved-tools clause. It says that where the business is a controller, a formal risk assessment should be considered. Whether that has to be a data protection impact assessment (DPIA) turns on Article 35 and the DPC's list. It warns that relying on AI output without critical human analysis can bring in automated decision-making risks, which Article 22 limits.
If personal data goes into a tool it should not have, that can be a personal data breach (Article 4(12)). It must be notified to the DPC without undue delay and, where feasible, within 72 hours of the business becoming aware, unless it is unlikely to result in a risk to people's rights and freedoms (Article 33(1)). Every breach must be documented, notified or not (Article 33(5)). The first 72 hours are set out separately.
What does not apply to a ten-person business
None of these is required of a business that only uses general AI tools for ordinary work.
- 1A certificate, an accredited course, a test of what staff know, an AI officer or a governance board. The Commission says no certificate is needed and no specific governance structure is mandated.
- 2The high-risk rules, unless you use AI for a purpose Annex III lists, such as filtering job applications, monitoring performance or emotion recognition. The Article 26 deployer duties start on 2 December 2027. From then, Article 25(1)(c) makes a business the provider of an AI system, including a general-purpose one, if it modifies the system's intended purpose so that it becomes high-risk. Whether sifting CVs with a general chatbot counts is not settled. Keeping general tools out of hiring and staff decisions avoids the question.
- 3The chatbot and machine-readable marking rules in Article 50(1) and (2), which fall on providers. A business that develops or modifies a chatbot and puts it into service under its own name is its provider, the Article 50 guidelines say; the Article 50 guide covers that.
- 4Labels on internal documents and private correspondence drafted with AI, or on advertising copy and product descriptions making no claims on matters such as health, consumer safety or sustainability.
- 5Anything for staff using AI at home for themselves. Article 2(10) takes purely personal non-professional use out of the deployer's obligations.
- 6The official AI register. The AI register in section 43 of the 2026 Act is the AI Office of Ireland's record of prohibited practices, serious incidents and other entries in the State. It is not a list a business keeps.
A short AI use policy to adopt
Copy the clauses as they stand and fill in the names. The brackets say whether each comes from the law or good practice. It is not legal advice, and AI used in decisions about hiring, health or credit needs more.
- 1Scope. This policy covers every AI tool used for the business's work, including AI features in software it already uses, by staff and by contractors working on its behalf. (Law: Article 4 reaches people acting on the business's behalf, contractors among them.)
- 2Approved tools. Use only the AI tools on the register [name] keeps, signed in with an account the business controls. A tool goes on the register once [name] has checked who provides it, whether a data processing agreement is in place, where it processes data, and whether the provider keeps or re-uses what is typed in. Its entry is reviewed when the tool or its terms change. (Good practice. Where personal data goes in: GDPR Article 28 if the provider acts for the business, Article 6 if not, and Chapter V. Most of the questions are the DPC's.)
- 3What never goes in. No personal data about customers, patients, staff or job applicants goes into a tool unless the register says that tool is approved for that data. Health information and other special category data goes into none unless [name] has also confirmed a condition under GDPR Article 9(2). No passwords, bank details or confidential business information go into any tool. (Law for personal data: GDPR Articles 5(1)(f), 6, 9 and 32(4). The rest is good practice.)
- 4Checking output. A person checks anything an AI tool produces before it is relied on or sent: facts, figures, names, dates, quotations, and anything legal, medical or financial. AI output is never the only basis for a decision about a person. (Good practice, serving Article 4, under which the Commission says staff should be told about hallucination. GDPR Article 22 limits solely automated decisions with legal or similarly significant effects.)
- 5Labelling. AI-generated or manipulated images, audio or video that could pass as real people, products, places or events are labelled as AI-made wherever published. AI-drafted text published on a matter of public interest is either labelled, or reviewed in substance and fact-checked by [name], who holds editorial responsibility and is named on the website. (Law: AI Act Article 50(4), since 2 August 2026. Naming the editor on the website follows the Commission's guidelines.)
- 6Never at work. No tool infers the emotions of staff or job candidates from their faces, voices, typing or movements. No tool makes realistic images, audio or video of a real person without their permission. No general AI tool screens job applicants or assesses staff without [name]'s approval. (Law: AI Act Article 5(1)(f), whose narrow medical and safety exception this policy does not use, and Article 5(1)(ba) from 2 December 2026. The permission and hiring rules are good practice.)
- 7Who to ask. [Name] answers questions about this policy. Anybody who has put personal data into a tool not approved for it tells [name] straight away: the business may have to notify the DPC within 72 hours of becoming aware, and must record any breach. (Law: GDPR Article 33(1) and (5). Naming one person is good practice.)
- 8Literacy, dated. Everybody who uses an AI tool for the business goes through this policy with [name] before starting, and again when a tool is added or changes: what the tools are, what they get wrong, what must not go in, and who to ask. [Name] records the date, who took part and what was covered. (Law: Article 4 asks for measures; the Commission says an internal record can be kept.)
- 9Review. This policy is reviewed whenever a tool is added or changes, and at least once a year. (Good practice.)
The register of tools, and the literacy record
Neither has a form set by law. The literacy record can be four entries per session: the date, who took part, what was covered and which tools.
An AI tool that handles personal data also belongs in any record of processing you keep: Article 30(1) asks for the recipients of the data, including any in countries outside the EEA, and for transfers outside the EEA.
| Column | What it holds | Why |
|---|---|---|
| Tool and provider | The product and the company that runs it | Who receives the data |
| Account | Business or personal, and who holds the login | Whose terms the use is on |
| Data processing agreement | Yes or no, and where it is kept | GDPR Article 28(3), where the provider acts for the business |
| Where data is processed | Inside or outside the EEA, and the transfer basis | GDPR Chapter V |
| Personal data allowed | None, or the categories approved, with health data named separately | GDPR Articles 5(1)(f), 9 and 32(4) |
| Kept or re-used by the provider | What the terms say about retaining inputs and training on them | The DPC's AI guidance; GDPR Article 6 |
| Who uses it, and for what | Names or roles, and the tasks | Article 4 measures follow the people and the use |
| AI Act flags | Any emotion recognition, deep fakes or public-interest text | AI Act Articles 5(1)(f) and 50, and Annex III point 1(c) |
Sources
- 1.Regulation (EU) 2024/1689, the AI Act, consolidated text of 27 July 2026: Articles 2, 3, 4, 5, 25, 26, 50, 99 and 113, and Annex III · EUR-Lex, Publications Office of the European Union
- 2.AI literacy: questions and answers (last updated 27 July 2026) · European Commission
- 3.Regulation (EU) 2026/1744, the Digital Omnibus on AI · EUR-Lex, Publications Office of the European Union
- 4.Regulation (EU) 2016/679, the GDPR: Articles 4, 5, 6, 9, 13, 14, 22, 24, 28, 30, 32, 33, 35 and 44 to 49 · EUR-Lex, Publications Office of the European Union
- 5.Regulation of Artificial Intelligence Act 2026, No. 31 of 2026, sections 43, 68, 71, 72, 78, 79 and 105 · Irish Statute Book, Office of the Attorney General
- 6.S.I. No. 403 of 2026, Regulation of Artificial Intelligence Act 2026 (Commencement) Order 2026 · Irish Statute Book, Office of the Attorney General
- 7.S.I. No. 405 of 2026, European Union (Artificial Intelligence) (Designation) (Amendment) Regulations 2026, Schedules 2 and 3 · Irish Statute Book, Office of the Attorney General
- 8.Guidelines on prohibited artificial intelligence practices, C(2025) 5052 final, 29 July 2025 · European Commission
- 9.WRC Role under EU AI Act · Workplace Relations Commission
- 10.Guidelines on the transparency obligations for certain AI systems under Article 50 of the AI Act, content approved by the Commission on 20 July 2026, C(2026) 5054 final, annex · European Commission
- 11.Case Studies 2025, Case Study 28: Employee uploading Curricula Vitae to Artificial Intelligence (AI) tool · Data Protection Commission
- 12.Commission Implementing Decision (EU) 2023/1795 of 10 July 2023, the EU-US Data Privacy Framework · EUR-Lex, Publications Office of the European Union
- 13.AI, Large Language Models and Data Protection, 18 July 2024 · Data Protection Commission
Free, and no account needed
Which AI Act duties reach you
The policy above covers ordinary use of general AI tools. Answer a few questions about what you do with AI and the free checklist returns the duties that follow, the article each comes from, whether it applies today or is dated, and which are not yours. No account needed.
Run the free checkIf you are not sure which tools are already in use
The compliance assessment starts by finding out which AI tools the business already uses, including the ones nobody signed off, classifies them under the AI Act with the article behind each duty, and builds your record of processing in the portal, with the gaps ranked by exposure.
Compliance assessmentWho wrote this
Oscar Cobbe · Founder, FourWinds Digital
Writes and maintains the legal explainers on this site, and does the compliance work behind them. Every date and article number here is checked against the legislation itself before it is published, and updated when the law changes.
More about how we work →Read next
- EU AI ActAI literacy: a real duty, and nothing you have to buy
- EU AI ActDoes the EU AI Act apply to my business?
- EU AI ActDoes your chatbot have to tell people it is AI? Yes, unless that is obvious.
Written on 16 October 2026 and accurate as at that date. This is general information about how the rules work, not legal advice on your situation. Where you need a solicitor, we say so.