[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$ftZzWA6a-WpcMZhkteGXACVJ84ZMou1b-ayS8fdvORfI":3,"$fDuOfbrGklFg9DNstLQj01v77JKgm8YTNP3W1V3nd5U4":78,"faq-section-":233,"white_papers":234},{"tableOfContents":4,"markDownContent":5,"htmlContent":6,"metaTitle":7,"metaDescription":8,"wordCount":9,"readTime":10,"title":11,"nbDownloads":12,"excerpt":13,"lang":14,"url":15,"intro":16,"featured":4,"state":17,"author":18,"authorId":19,"datePublication":23,"dateCreation":24,"dateUpdate":25,"mainCategory":26,"categories":42,"metaDatas":67,"imageUrl":68,"imageThumbUrls":69,"id":77},false,"The “AI Omnibus” agreement, formally adopted by the [Council on 29 June](https://www.consilium.europa.eu/en/press/press-releases/2026/06/29/artificial-intelligence-council-gives-final-green-light-to-simplify-and-streamline-rules/), has pushed back several milestones under the Regulation. For many organisations, this news has been welcomed as a broad relief: more time, less pressure.\n\nHowever, that impression is only partly accurate. Several legally binding obligations have applied since February 2025, including one in particular that the AI Omnibus did not postpone.\n\nSince 2 February 2025, the [European Regulation on Artificial Intelligence (AI Act)](https://www.dastra.eu/fr/blog/ai-act-lessentiel-du-reglement-en-bref/59534) has imposed an obligation that is still not widely known, but which is cross-cutting: **AI literacy**, as provided for in **Article 4 of the AI Act**. In practical terms, any organisation that develops or uses artificial intelligence must take measures to support the development of an appropriate level of **AI literacy** among its staff. This is often the first concrete obligation that companies encounter under the AI Act.\n\n## **What is AI literacy?**\n\n**AI literacy**, also referred to as **artificial intelligence literacy** or **AI literacy**, refers to the set of skills needed to understand, use and supervise **AI systems** in an informed manner.\n\nThis is not about turning everyone into a data scientist capable of designing **AI models** or mastering **machine learning**, but about giving each employee the reference points needed to work with these **new technologies** knowingly, rather than treating them as a “black box”.\n\nThis literacy should in particular make it possible to understand the capabilities and limitations of an **AI tool**, identify the risks linked to an **AI application**, and know under what conditions AI can contribute to **decision-making**.\n\n## **What Article 4 requires, as amended by the AI Omnibus**\n\n### **An obligation already in force**\n\n[Article 4 of the AI Act](https://artificialintelligenceact.eu/article/4/) requires providers and deployers of **AI systems** to take measures to support the development of AI literacy among their staff and any other persons dealing, on their behalf, with the operation and use of AI systems.\n\nThis obligation therefore concerns in particular **operators and deployers of AI systems** and applies regardless of the risk level of the system concerned. It has been in force since 2 February 2025.\n\n> *What is too often overlooked is that this Article has already entered into force and was not postponed by the AI Omnibus. As a result, many organisations are delaying their compliance work on AI literacy and acculturation, even though it has already been in force since February 2025.*\n\n> *Moreover, from 2 August 2026, the national market surveillance authorities began monitoring organisations’ compliance with this Article, among others.*\n\n### **AI literacy after the AI Omnibus**\n\nThe original text required organisations to “ensure a sufficient level” of AI literacy, which amounted to a result obligation.\n\nThe text as amended by the AI Omnibus, which entered into force at the end of July 2026, now requires them to “take measures to support the development” of that literacy, which amounts to an obligation of means.\n\nThe obligation has not been removed and the February 2025 application date has not changed, but its legal nature has shifted from a guarantee to a demonstrable effort.\n\n> *It is easy to read this as an obligation quietly fading away. That is not the case. What changes is the standard against which an organisation’s efforts will be assessed, not the very existence of the obligation to make an effort.*\n\n## **Who is affected, and since when?**\n\nThe obligation has applied since 2 February 2025 to all providers and deployers of **AI systems**, regardless of size or sector.\n\nUnlike other obligations under the AI Act, it is not limited to high-risk systems: once an organisation uses AI, it must take appropriate measures to develop the AI literacy of the people who handle it.\n\nThis applies both to employees who use **generative AI** on a daily basis and to those involved in more technical AI projects involving **AI models**, **machine learning**, or specialised systems.\n\n## **A risk linked to insufficient AI literacy: Shadow AI**\n\nInsufficient AI literacy generally produces a well-known side effect: *Shadow AI*, meaning the use of AI tools by employees without oversight from IT, legal or compliance teams.\n\nThis phenomenon is reminiscent of the older problem of *Shadow IT*, while also carrying risks specific to AI: leakage of sensitive data through unsecured external **AI tools**, unauthorised data transfers, increased exposure to data breaches, litigation and reputational damage.\n\nShadow AI should above all be read as an early warning signal: a sign that the pace of AI adoption within an organisation has outstripped the pace of its governance.\n\n### **Two illustrative cases**\n\n- An internal security incident at a major electronics manufacturer, where engineers shared proprietary source code with a public AI conversational agent, exposing that code outside the company.\n- A legal risk area identified within an international law firm, which had to issue internal guidelines on the use of AI after some lawyers proved unable to justify the sources underlying AI-assisted legal research.\n\n## **A practical approach, grounded in the Commission’s guidance**\n\nThe good news is that the level of requirement is genuinely proportionate, and organisations do not have to guess what regulators expect. The European Commission has published a [permanent FAQ on AI literacy](https://digital-strategy.ec.europa.eu/en/faqs/ai-literacy-questions-answers), which sets out a minimum approach without imposing a rigid model. It can be summarised in four steps.\n\n1. First, develop within the organisation a general understanding of what AI is, how it works, and the ways in which it is actually used. Many organisations are still unable today to answer this precisely.\n2. Second, identify the organisation’s role: does it develop AI systems, or does it merely use systems developed by third parties? AI literacy needs differ between a provider and a deployer.\n3. Third, assess the risk level of the AI systems concerned, since staff using a system in the context of HR decisions need a different level of understanding from those using a simple general-purpose writing assistant.\n4. Fourth, build concrete measures on the basis of that analysis, tailored to the technical knowledge, experience and usage context of each group. In practice, this usually translates into a short list of manageable actions: a documented training session for staff exposed to AI systems, differentiated between technical and non-technical audiences; a written internal policy describing acceptable uses, etc.\n\n### **AI literacy according to risk level**\n\nThe risk level should also guide the content of the training, not just its intensity.\n\n> *The Commission’s guidance gives a telling example: employees using a general-purpose tool such as ChatGPT to draft marketing copy or translate content must still understand specific risks such as hallucination, even though the tool is not high-risk.*\n\nDeployers of high-risk systems also have an additional, related obligation under Article 26, namely to ensure that staff are trained to exercise human oversight. This obligation should be integrated into the same programme rather than treated separately.\n\n## **How do you become compliant? A 5-step approach**\n\n- **Assess existing levels**: map who uses AI and how well, by profile.\n- **Segment needs**: executives, technical teams, support functions and business users do not need the same skills.\n- **Build training programmes** covering the fundamentals: how AI and **AI models** work, capabilities and limitations, bias, prompt engineering, the regulatory framework (AI Act, GDPR) and ethical considerations.\n- **Embed through practice**: test real **use cases** — drafting, data analysis, automation of repetitive tasks — to understand AI’s strengths and limits. This approach also helps better understand how to **support the development of AI** literacy within teams.\n- **Document and maintain**: keep a record of actions taken (content, participants, dates) as evidence of compliance, and ensure regular updates in light of fast-evolving **AI projects**.\n\n> *The Commission has clarified that no certificate is required, that no dedicated AI officer or governance committee is imposed, and that simply reproducing an already published training programme does not, by itself, guarantee compliance. What matters is that the measures are real, proportionate to the organisation’s actual use of AI, and sufficiently documented to be produced if requested by a regulator.*\n\n## **AI literacy and governance: a common foundation**\n\nLiteracy is not limited to one-off training: it underpins the entire AI governance framework. Teams that are aware of the issues are better at identifying risky systems, feeding the [AI systems register](https://www.dastra.eu/fr/blog/ai-act-les-questions-cles-pour-votre-registre-ia/59552) and applying the other obligations more easily (transparency, human oversight, impact assessments). They also foster better decision-making and responsible day-to-day use of AI. [Dastra’s AI governance solution](https://www.dastra.eu/fr/product-features/ai-governance) helps structure this approach across the organisation.\n\n## **AI Literacy FAQ**\n\n### **What is AI literacy?**\n\nIt is the set of skills that make it possible to understand, use and supervise artificial intelligence (artificial intelligence / AI) in an informed way: how models work, capabilities, limitations, bias, prompt engineering and ethical considerations. Article 4 of the AI Act makes it an obligation.\n\n### **Since when has the AI literacy obligation applied?**\n\nSince 2 February 2025, at the same time as the prohibitions under Article 5.\n\n### **Who is covered by Article 4 of the AI Act?**\n\nAll providers and deployers of **AI systems**, regardless of size or sector, and not only high-risk systems.\n\n### **How can compliance with the literacy obligation be demonstrated?**\n\nBy documenting the training programmes implemented: content, participants, dates, and regular updates.\n\n### **Does AI literacy concern only technical teams?**\n\nNo. It concerns everyone who uses AI or supervises its use, at a level adapted to each role (executives, lawyers, support functions, business users).","\u003Cp>The “AI Omnibus” agreement, formally adopted by the \u003Ca href=\"https://www.consilium.europa.eu/en/press/press-releases/2026/06/29/artificial-intelligence-council-gives-final-green-light-to-simplify-and-streamline-rules/\" rel=\"nofollow\">Council on 29 June\u003C/a>, has pushed back several milestones under the Regulation. For many organisations, this news has been welcomed as a broad relief: more time, less pressure.\u003C/p>\n\u003Cp>However, that impression is only partly accurate. Several legally binding obligations have applied since February 2025, including one in particular that the AI Omnibus did not postpone.\u003C/p>\n\u003Cp>Since 2 February 2025, the \u003Ca href=\"https://www.dastra.eu/fr/blog/ai-act-lessentiel-du-reglement-en-bref/59534\">European Regulation on Artificial Intelligence (AI Act)\u003C/a> has imposed an obligation that is still not widely known, but which is cross-cutting: \u003Cstrong>AI literacy\u003C/strong>, as provided for in \u003Cstrong>Article 4 of the AI Act\u003C/strong>. In practical terms, any organisation that develops or uses artificial intelligence must take measures to support the development of an appropriate level of \u003Cstrong>AI literacy\u003C/strong> among its staff. This is often the first concrete obligation that companies encounter under the AI Act.\u003C/p>\n\u003Ch2 id=\"what-is-ai-literacy\">\u003Cstrong>What is AI literacy?\u003C/strong>\u003C/h2>\n\u003Cp>\u003Cstrong>AI literacy\u003C/strong>, also referred to as \u003Cstrong>artificial intelligence literacy\u003C/strong> or \u003Cstrong>AI literacy\u003C/strong>, refers to the set of skills needed to understand, use and supervise \u003Cstrong>AI systems\u003C/strong> in an informed manner.\u003C/p>\n\u003Cp>This is not about turning everyone into a data scientist capable of designing \u003Cstrong>AI models\u003C/strong> or mastering \u003Cstrong>machine learning\u003C/strong>, but about giving each employee the reference points needed to work with these \u003Cstrong>new technologies\u003C/strong> knowingly, rather than treating them as a “black box”.\u003C/p>\n\u003Cp>This literacy should in particular make it possible to understand the capabilities and limitations of an \u003Cstrong>AI tool\u003C/strong>, identify the risks linked to an \u003Cstrong>AI application\u003C/strong>, and know under what conditions AI can contribute to \u003Cstrong>decision-making\u003C/strong>.\u003C/p>\n\u003Ch2 id=\"what-article-4-requires-as-amended-by-the-ai-omnibus\">\u003Cstrong>What Article 4 requires, as amended by the AI Omnibus\u003C/strong>\u003C/h2>\n\u003Ch3 id=\"an-obligation-already-in-force\">\u003Cstrong>An obligation already in force\u003C/strong>\u003C/h3>\n\u003Cp>\u003Ca href=\"https://artificialintelligenceact.eu/article/4/\" rel=\"nofollow\">Article 4 of the AI Act\u003C/a> requires providers and deployers of \u003Cstrong>AI systems\u003C/strong> to take measures to support the development of AI literacy among their staff and any other persons dealing, on their behalf, with the operation and use of AI systems.\u003C/p>\n\u003Cp>This obligation therefore concerns in particular \u003Cstrong>operators and deployers of AI systems\u003C/strong> and applies regardless of the risk level of the system concerned. It has been in force since 2 February 2025.\u003C/p>\n\u003Cblockquote>\n\u003Cp>\u003Cem>What is too often overlooked is that this Article has already entered into force and was not postponed by the AI Omnibus. As a result, many organisations are delaying their compliance work on AI literacy and acculturation, even though it has already been in force since February 2025.\u003C/em>\u003C/p>\n\u003C/blockquote>\n\u003Cblockquote>\n\u003Cp>\u003Cem>Moreover, from 2 August 2026, the national market surveillance authorities began monitoring organisations’ compliance with this Article, among others.\u003C/em>\u003C/p>\n\u003C/blockquote>\n\u003Ch3 id=\"ai-literacy-after-the-ai-omnibus\">\u003Cstrong>AI literacy after the AI Omnibus\u003C/strong>\u003C/h3>\n\u003Cp>The original text required organisations to “ensure a sufficient level” of AI literacy, which amounted to a result obligation.\u003C/p>\n\u003Cp>The text as amended by the AI Omnibus, which entered into force at the end of July 2026, now requires them to “take measures to support the development” of that literacy, which amounts to an obligation of means.\u003C/p>\n\u003Cp>The obligation has not been removed and the February 2025 application date has not changed, but its legal nature has shifted from a guarantee to a demonstrable effort.\u003C/p>\n\u003Cblockquote>\n\u003Cp>\u003Cem>It is easy to read this as an obligation quietly fading away. That is not the case. What changes is the standard against which an organisation’s efforts will be assessed, not the very existence of the obligation to make an effort.\u003C/em>\u003C/p>\n\u003C/blockquote>\n\u003Ch2 id=\"who-is-affected-and-since-when\">\u003Cstrong>Who is affected, and since when?\u003C/strong>\u003C/h2>\n\u003Cp>The obligation has applied since 2 February 2025 to all providers and deployers of \u003Cstrong>AI systems\u003C/strong>, regardless of size or sector.\u003C/p>\n\u003Cp>Unlike other obligations under the AI Act, it is not limited to high-risk systems: once an organisation uses AI, it must take appropriate measures to develop the AI literacy of the people who handle it.\u003C/p>\n\u003Cp>This applies both to employees who use \u003Cstrong>generative AI\u003C/strong> on a daily basis and to those involved in more technical AI projects involving \u003Cstrong>AI models\u003C/strong>, \u003Cstrong>machine learning\u003C/strong>, or specialised systems.\u003C/p>\n\u003Ch2 id=\"a-risk-linked-to-insufficient-ai-literacy-shadow-ai\">\u003Cstrong>A risk linked to insufficient AI literacy: Shadow AI\u003C/strong>\u003C/h2>\n\u003Cp>Insufficient AI literacy generally produces a well-known side effect: \u003Cem>Shadow AI\u003C/em>, meaning the use of AI tools by employees without oversight from IT, legal or compliance teams.\u003C/p>\n\u003Cp>This phenomenon is reminiscent of the older problem of \u003Cem>Shadow IT\u003C/em>, while also carrying risks specific to AI: leakage of sensitive data through unsecured external \u003Cstrong>AI tools\u003C/strong>, unauthorised data transfers, increased exposure to data breaches, litigation and reputational damage.\u003C/p>\n\u003Cp>Shadow AI should above all be read as an early warning signal: a sign that the pace of AI adoption within an organisation has outstripped the pace of its governance.\u003C/p>\n\u003Ch3 id=\"two-illustrative-cases\">\u003Cstrong>Two illustrative cases\u003C/strong>\u003C/h3>\n\u003Cul>\n\u003Cli>An internal security incident at a major electronics manufacturer, where engineers shared proprietary source code with a public AI conversational agent, exposing that code outside the company.\u003C/li>\n\u003Cli>A legal risk area identified within an international law firm, which had to issue internal guidelines on the use of AI after some lawyers proved unable to justify the sources underlying AI-assisted legal research.\u003C/li>\n\u003C/ul>\n\u003Ch2 id=\"a-practical-approach-grounded-in-the-commissions-guidance\">\u003Cstrong>A practical approach, grounded in the Commission’s guidance\u003C/strong>\u003C/h2>\n\u003Cp>The good news is that the level of requirement is genuinely proportionate, and organisations do not have to guess what regulators expect. The European Commission has published a \u003Ca href=\"https://digital-strategy.ec.europa.eu/en/faqs/ai-literacy-questions-answers\" rel=\"nofollow\">permanent FAQ on AI literacy\u003C/a>, which sets out a minimum approach without imposing a rigid model. It can be summarised in four steps.\u003C/p>\n\u003Col>\n\u003Cli>First, develop within the organisation a general understanding of what AI is, how it works, and the ways in which it is actually used. Many organisations are still unable today to answer this precisely.\u003C/li>\n\u003Cli>Second, identify the organisation’s role: does it develop AI systems, or does it merely use systems developed by third parties? AI literacy needs differ between a provider and a deployer.\u003C/li>\n\u003Cli>Third, assess the risk level of the AI systems concerned, since staff using a system in the context of HR decisions need a different level of understanding from those using a simple general-purpose writing assistant.\u003C/li>\n\u003Cli>Fourth, build concrete measures on the basis of that analysis, tailored to the technical knowledge, experience and usage context of each group. In practice, this usually translates into a short list of manageable actions: a documented training session for staff exposed to AI systems, differentiated between technical and non-technical audiences; a written internal policy describing acceptable uses, etc.\u003C/li>\n\u003C/ol>\n\u003Ch3 id=\"ai-literacy-according-to-risk-level\">\u003Cstrong>AI literacy according to risk level\u003C/strong>\u003C/h3>\n\u003Cp>The risk level should also guide the content of the training, not just its intensity.\u003C/p>\n\u003Cblockquote>\n\u003Cp>\u003Cem>The Commission’s guidance gives a telling example: employees using a general-purpose tool such as ChatGPT to draft marketing copy or translate content must still understand specific risks such as hallucination, even though the tool is not high-risk.\u003C/em>\u003C/p>\n\u003C/blockquote>\n\u003Cp>Deployers of high-risk systems also have an additional, related obligation under Article 26, namely to ensure that staff are trained to exercise human oversight. This obligation should be integrated into the same programme rather than treated separately.\u003C/p>\n\u003Ch2 id=\"how-do-you-become-compliant-a-5-step-approach\">\u003Cstrong>How do you become compliant? A 5-step approach\u003C/strong>\u003C/h2>\n\u003Cul>\n\u003Cli>\u003Cstrong>Assess existing levels\u003C/strong>: map who uses AI and how well, by profile.\u003C/li>\n\u003Cli>\u003Cstrong>Segment needs\u003C/strong>: executives, technical teams, support functions and business users do not need the same skills.\u003C/li>\n\u003Cli>\u003Cstrong>Build training programmes\u003C/strong> covering the fundamentals: how AI and \u003Cstrong>AI models\u003C/strong> work, capabilities and limitations, bias, prompt engineering, the regulatory framework (AI Act, GDPR) and ethical considerations.\u003C/li>\n\u003Cli>\u003Cstrong>Embed through practice\u003C/strong>: test real \u003Cstrong>use cases\u003C/strong> — drafting, data analysis, automation of repetitive tasks — to understand AI’s strengths and limits. This approach also helps better understand how to \u003Cstrong>support the development of AI\u003C/strong> literacy within teams.\u003C/li>\n\u003Cli>\u003Cstrong>Document and maintain\u003C/strong>: keep a record of actions taken (content, participants, dates) as evidence of compliance, and ensure regular updates in light of fast-evolving \u003Cstrong>AI projects\u003C/strong>.\u003C/li>\n\u003C/ul>\n\u003Cblockquote>\n\u003Cp>\u003Cem>The Commission has clarified that no certificate is required, that no dedicated AI officer or governance committee is imposed, and that simply reproducing an already published training programme does not, by itself, guarantee compliance. What matters is that the measures are real, proportionate to the organisation’s actual use of AI, and sufficiently documented to be produced if requested by a regulator.\u003C/em>\u003C/p>\n\u003C/blockquote>\n\u003Ch2 id=\"ai-literacy-and-governance-a-common-foundation\">\u003Cstrong>AI literacy and governance: a common foundation\u003C/strong>\u003C/h2>\n\u003Cp>Literacy is not limited to one-off training: it underpins the entire AI governance framework. Teams that are aware of the issues are better at identifying risky systems, feeding the \u003Ca href=\"https://www.dastra.eu/fr/blog/ai-act-les-questions-cles-pour-votre-registre-ia/59552\">AI systems register\u003C/a> and applying the other obligations more easily (transparency, human oversight, impact assessments). They also foster better decision-making and responsible day-to-day use of AI. \u003Ca href=\"https://www.dastra.eu/fr/product-features/ai-governance\">Dastra’s AI governance solution\u003C/a> helps structure this approach across the organisation.\u003C/p>\n\u003Ch2 id=\"ai-literacy-faq\">\u003Cstrong>AI Literacy FAQ\u003C/strong>\u003C/h2>\n\u003Ch3 id=\"what-is-ai-literacy-1\">\u003Cstrong>What is AI literacy?\u003C/strong>\u003C/h3>\n\u003Cp>It is the set of skills that make it possible to understand, use and supervise artificial intelligence (artificial intelligence / AI) in an informed way: how models work, capabilities, limitations, bias, prompt engineering and ethical considerations. Article 4 of the AI Act makes it an obligation.\u003C/p>\n\u003Ch3 id=\"since-when-has-the-ai-literacy-obligation-applied\">\u003Cstrong>Since when has the AI literacy obligation applied?\u003C/strong>\u003C/h3>\n\u003Cp>Since 2 February 2025, at the same time as the prohibitions under Article 5.\u003C/p>\n\u003Ch3 id=\"who-is-covered-by-article-4-of-the-ai-act\">\u003Cstrong>Who is covered by Article 4 of the AI Act?\u003C/strong>\u003C/h3>\n\u003Cp>All providers and deployers of \u003Cstrong>AI systems\u003C/strong>, regardless of size or sector, and not only high-risk systems.\u003C/p>\n\u003Ch3 id=\"how-can-compliance-with-the-literacy-obligation-be-demonstrated\">\u003Cstrong>How can compliance with the literacy obligation be demonstrated?\u003C/strong>\u003C/h3>\n\u003Cp>By documenting the training programmes implemented: content, participants, dates, and regular updates.\u003C/p>\n\u003Ch3 id=\"does-ai-literacy-concern-only-technical-teams\">\u003Cstrong>Does AI literacy concern only technical teams?\u003C/strong>\u003C/h3>\n\u003Cp>No. It concerns everyone who uses AI or supervises its use, at a level adapted to each role (executives, lawyers, support functions, business users).\u003C/p>\n","AI literacy: the obligation under Article 4","Article 4 of the AI Act requires AI acculturation (AI literacy): training your teams on the capabilities, limitations, and risks of AI. Who is affected, since w",1594,9,"AI literacy: why Omnibus changed the rules without changing the date",0,null,"en","ai-literacy-why-the-omnibus-changed-the-rules-of-the-game-without-changing-the","The “AI Omnibus” agreement, formally adopted by the Council on 29 June, has pushed back several milestones under the regulation. For many organizations, this news was welcomed as a general relief: more time, less pressure.","Published",{"id":19,"displayName":20,"avatarUrl":13,"bio":13,"blogUrl":13,"color":13,"userId":21,"creationDate":22},25699,"Zelie Aderic",28682,"2026-08-06T20:46:39.3043599","2026-09-07T13:02:00","2026-09-07T13:02:47.0068987","2026-09-07T13:45:55.6294856",{"id":27,"name":28,"description":29,"url":30,"color":31,"parentId":13,"count":13,"imageUrl":13,"parent":13,"order":12,"translations":32},2,"Blog","A list of curated articles provided by the community","blog","#28449a",[33,36,39],{"lang":34,"name":28,"description":35},"fr","Une liste d'articles rédigés par la communauté",{"lang":37,"name":28,"description":38},"es","Una lista de artículos escritos por la comunidad",{"lang":40,"name":28,"description":41},"de","Eine Liste von Artikeln, die von der Community verfasst wurden",[43,48],{"id":27,"name":28,"description":29,"url":30,"color":31,"parentId":13,"count":13,"imageUrl":13,"parent":13,"order":12,"translations":44},[45,46,47],{"lang":34,"name":28,"description":35},{"lang":37,"name":28,"description":38},{"lang":40,"name":28,"description":41},{"id":49,"name":50,"description":51,"url":52,"color":53,"parentId":27,"count":13,"imageUrl":13,"parent":54,"order":59,"translations":60},221,"AI Governance","Best practices, regulatory frameworks and real-world insights to manage AI responsibly and in compliance with the AI Act.","ai-governance","#000000",{"id":27,"name":28,"description":29,"url":30,"color":31,"parentId":13,"count":13,"imageUrl":13,"parent":13,"order":12,"translations":55},[56,57,58],{"lang":34,"name":28,"description":35},{"lang":37,"name":28,"description":38},{"lang":40,"name":28,"description":41},3,[61,64],{"lang":34,"name":62,"description":63},"Gouvernance de l'IA","Bonnes pratiques, cadres réglementaires et retours d'expérience pour piloter l'IA de façon responsable et conforme à l'AI Act.",{"lang":40,"name":65,"description":66},"KI-Governance","Best Practices, regulatorische Rahmenbedingungen und Praxiserfahrungen für einen verantwortungsvollen KI-Einsatz im Einklang mit dem AI Act.",[],"https://static.dastra.eu/content/1de66c9d-6ba5-49f0-8b86-1a55f317299c/visuel-article-original.jpg",[70,71,72,73,74,75,76],"https://static.dastra.eu/content/1de66c9d-6ba5-49f0-8b86-1a55f317299c/visuel-article-1000.webp","https://static.dastra.eu/content/1de66c9d-6ba5-49f0-8b86-1a55f317299c/visuel-article.webp","https://static.dastra.eu/content/1de66c9d-6ba5-49f0-8b86-1a55f317299c/visuel-article-1500.webp","https://static.dastra.eu/content/1de66c9d-6ba5-49f0-8b86-1a55f317299c/visuel-article-800.webp","https://static.dastra.eu/content/1de66c9d-6ba5-49f0-8b86-1a55f317299c/visuel-article-600.webp","https://static.dastra.eu/content/1de66c9d-6ba5-49f0-8b86-1a55f317299c/visuel-article-300.webp","https://static.dastra.eu/content/1de66c9d-6ba5-49f0-8b86-1a55f317299c/visuel-article-100.webp",60562,{"total":79,"items":80,"parent":228},8,[81,102,122,144,166,186,195,211],{"id":82,"name":83,"description":84,"url":85,"color":86,"parentId":27,"count":13,"imageUrl":13,"parent":87,"order":79,"translations":92},20,"Inside Dastra","Go behind the scenes at Dastra: company news, culture, events, team highlights, and the people driving our GDPR solution.","dastra-life","#e3cf68",{"id":27,"name":28,"description":29,"url":30,"color":31,"parentId":13,"count":13,"imageUrl":13,"parent":13,"order":12,"translations":88},[89,90,91],{"lang":34,"name":28,"description":35},{"lang":37,"name":28,"description":38},{"lang":40,"name":28,"description":41},[93,96,99],{"lang":34,"name":94,"description":95},"Vie de Dastra","Plongez dans les coulisses de Dastra : actualités internes, culture d’entreprise, événements, équipes et engagements. Découvrez qui se cache derrière notre solution RGPD.",{"lang":40,"name":97,"description":98},"Innerhalb von Dastra","Eintauchen in das Unternehmen",{"lang":37,"name":100,"description":101},"Dentro de Dastra","Sumérjase en la empresa",{"id":103,"name":104,"description":105,"url":106,"color":53,"parentId":27,"count":13,"imageUrl":13,"parent":107,"order":112,"translations":113},69,"Expertise","Gain insights from our experts on GDPR compliance, data protection, and privacy challenges. In-depth articles, professional analysis, and real-world best practices.","indepth",{"id":27,"name":28,"description":29,"url":30,"color":31,"parentId":13,"count":13,"imageUrl":13,"parent":13,"order":12,"translations":108},[109,110,111],{"lang":34,"name":28,"description":35},{"lang":37,"name":28,"description":38},{"lang":40,"name":28,"description":41},7,[114,116,119],{"lang":34,"name":104,"description":115},"Bénéficiez des conseils de nos experts sur la conformité RGPD, la protection des données et les enjeux privacy. Articles de fond, analyses et retours d’expérience métier.",{"lang":40,"name":117,"description":118},"Fachwissen","Entdecken Sie die Artikel unserer DSGVO-Experten",{"lang":37,"name":120,"description":121},"Experiencia","Descubre los artículos de nuestros expertos en Privacy",{"id":123,"name":124,"description":125,"url":126,"color":127,"parentId":27,"count":13,"imageUrl":13,"parent":128,"order":133,"translations":134},4,"Use cases","Discover how companies use Dastra to manage their GDPR compliance. Testimonials, use cases, and real-world integrations of our privacy management solution.","case-studies","#b61b9c",{"id":27,"name":28,"description":29,"url":30,"color":31,"parentId":13,"count":13,"imageUrl":13,"parent":13,"order":12,"translations":129},[130,131,132],{"lang":34,"name":28,"description":35},{"lang":37,"name":28,"description":38},{"lang":40,"name":28,"description":41},6,[135,138,141],{"lang":34,"name":136,"description":137},"Retours d'expérience","Découvrez comment les entreprises utilisent Dastra pour piloter leur conformité RGPD. Témoignages, cas d’usage et intégrations concrètes de notre solution de privacy management.",{"lang":40,"name":139,"description":140},"Case Studies","Entdecken Sie die Erfahrungsberichte unserer Kunden",{"lang":37,"name":142,"description":143},"Casos prácticos","Descubra los testimonios de nuestros clientes",{"id":145,"name":146,"description":147,"url":148,"color":149,"parentId":27,"count":13,"imageUrl":13,"parent":150,"order":155,"translations":156},10,"Release notes","Keep up with the latest features of Dastra: product updates, new functionalities, and improvements to our GDPR compliance and data management platform.","release","#8c316a",{"id":27,"name":28,"description":29,"url":30,"color":31,"parentId":13,"count":13,"imageUrl":13,"parent":13,"order":12,"translations":151},[152,153,154],{"lang":34,"name":28,"description":35},{"lang":37,"name":28,"description":38},{"lang":40,"name":28,"description":41},5,[157,160,163],{"lang":34,"name":158,"description":159},"Notes de version","Restez informé(e) des dernières fonctionnalités de Dastra : mises à jour, évolutions produit et améliorations de notre solution de conformité RGPD et de gestion des données personnelles.",{"lang":40,"name":161,"description":162},"Veröffentlichungen","Alle Versionshinweise und Funktionen von Dastra",{"lang":37,"name":164,"description":165},"Lanzamientos","Todas las notas de la versión e información sobre las funciones de Dastra",{"id":10,"name":167,"description":168,"url":169,"color":170,"parentId":27,"count":13,"imageUrl":13,"parent":171,"order":123,"translations":176},"News","Stay up to date with the latest news from data protection authorities: decisions, fines, guidelines, and regulatory trends in GDPR and privacy.","news","#1676ca",{"id":27,"name":28,"description":29,"url":30,"color":31,"parentId":13,"count":13,"imageUrl":13,"parent":13,"order":12,"translations":172},[173,174,175],{"lang":34,"name":28,"description":35},{"lang":37,"name":28,"description":38},{"lang":40,"name":28,"description":41},[177,180,183],{"lang":34,"name":178,"description":179},"Actualités","Suivez les dernières actualités des autorités de protection des données (CNIL, EDPS, etc.) : décisions, sanctions, lignes directrices et tendances réglementaires en matière de RGPD et de privacy.",{"lang":37,"name":181,"description":182},"Actualidad","Todos los artículos relativos a las autoridades de protección de datos",{"lang":40,"name":184,"description":185},"Nachrichten","Alle Artikel mit Bezug zu Datenschutzbehörden",{"id":49,"name":50,"description":51,"url":52,"color":53,"parentId":27,"count":13,"imageUrl":13,"parent":187,"order":59,"translations":192},{"id":27,"name":28,"description":29,"url":30,"color":31,"parentId":13,"count":13,"imageUrl":13,"parent":13,"order":12,"translations":188},[189,190,191],{"lang":34,"name":28,"description":35},{"lang":37,"name":28,"description":38},{"lang":40,"name":28,"description":41},[193,194],{"lang":34,"name":62,"description":63},{"lang":40,"name":65,"description":66},{"id":196,"name":197,"description":198,"url":199,"color":53,"parentId":27,"count":13,"imageUrl":13,"parent":200,"order":27,"translations":205},220,"Compliance","Regulatory news, practical guides and analysis to keep your organization compliant with the GDPR and beyond.","compliance",{"id":27,"name":28,"description":29,"url":30,"color":31,"parentId":13,"count":13,"imageUrl":13,"parent":13,"order":12,"translations":201},[202,203,204],{"lang":34,"name":28,"description":35},{"lang":37,"name":28,"description":38},{"lang":40,"name":28,"description":41},[206,209],{"lang":34,"name":207,"description":208},"Conformité","Actualités réglementaires, guides pratiques et analyses pour maintenir votre organisation en conformité RGPD et au-delà.",{"lang":40,"name":197,"description":210},"Regulatorische Neuigkeiten, Praxisleitfäden und Analysen, um Ihre Organisation DSGVO-konform und darüber hinaus aufzustellen.",{"id":212,"name":213,"description":214,"url":215,"color":53,"parentId":27,"count":13,"imageUrl":13,"parent":216,"order":221,"translations":222},219,"Privacy","Principles, techniques and trends in personal data protection — from privacy by design to data subject rights.","privacy",{"id":27,"name":28,"description":29,"url":30,"color":31,"parentId":13,"count":13,"imageUrl":13,"parent":13,"order":12,"translations":217},[218,219,220],{"lang":34,"name":28,"description":35},{"lang":37,"name":28,"description":38},{"lang":40,"name":28,"description":41},1,[223,225],{"lang":34,"name":213,"description":224},"Principes, techniques et tendances autour de la protection des données personnelles — de la privacy by design aux droits des personnes.",{"lang":40,"name":226,"description":227},"Datenschutz","Grundsätze, Methoden und Trends zum Schutz personenbezogener Daten — von Privacy by Design bis zu Betroffenenrechten.",{"id":27,"name":28,"description":29,"url":30,"color":31,"parentId":13,"count":13,"imageUrl":13,"parent":13,"order":12,"translations":229},[230,231,232],{"lang":34,"name":28,"description":35},{"lang":37,"name":28,"description":38},{"lang":40,"name":28,"description":41},[],{"items":235,"total":302,"size":221,"page":221},[236],{"title":237,"nbDownloads":123,"excerpt":238,"lang":14,"url":239,"intro":240,"featured":4,"state":17,"author":241,"authorId":242,"datePublication":246,"dateCreation":247,"dateUpdate":248,"mainCategory":249,"categories":255,"metaDatas":288,"imageUrl":292,"imageThumbUrls":293,"id":301},"AI Act Transparency Notice Template (Word Format) Compliant with Article 50","Download a Microsoft Word template for AI transparency notices compliant with Article 50 of the EU AI Act, including four ready-to-use notice variants for AI providers and deployers.","ai-act-transparency-notice-template-word-format-compliant-with-article-50","Since 2 August 2026, Article 50 of the European Artificial Intelligence Act (AI Act) has introduced transparency obligations for several categories of AI systems. AI providers and deployers must inform individuals when they interact with AI, are exposed to AI-generated content, are subject to emotion recognition or biometric categorisation, or encounter AI-generated deepfakes. To help organisations comply with these requirements, Dastra provides a free Microsoft Word template that can be adapted and integrated into your documentation, websites and user interfaces.",{"id":242,"displayName":243,"avatarUrl":244,"bio":13,"blogUrl":13,"color":13,"userId":242,"creationDate":245},38,"Paul-Emmanuel Bidault","https://static.dastra.eu/tenant-27/avatar/38/paul-emmanuel-bidault-150.jpg","2019-12-03T19:09:28","2026-08-06T12:40:00","2026-08-06T12:40:04.9054724","2026-09-14T13:50:25.0328281",{"id":250,"name":251,"description":13,"url":252,"color":253,"parentId":13,"count":13,"imageUrl":13,"parent":13,"order":59,"translations":254},70,"Livre blanc","white-papers","#1795d3",[],[256,261,266,268,276,284],{"id":27,"name":28,"description":29,"url":30,"color":31,"parentId":13,"count":13,"imageUrl":13,"parent":13,"order":12,"translations":257},[258,259,260],{"lang":34,"name":28,"description":35},{"lang":37,"name":28,"description":38},{"lang":40,"name":28,"description":41},{"id":262,"name":263,"description":13,"url":264,"color":53,"parentId":13,"count":13,"imageUrl":13,"parent":13,"order":133,"translations":265},48,"Ressources","resources",[],{"id":250,"name":251,"description":13,"url":252,"color":253,"parentId":13,"count":13,"imageUrl":13,"parent":13,"order":59,"translations":267},[],{"id":269,"name":270,"description":271,"url":272,"color":273,"parentId":262,"count":13,"imageUrl":274,"parent":13,"order":12,"translations":275},83,"IA","Toutes les ressources sur l'IA","intelligence-artificielle","#342d9f","https://static.dastra.eu/tag/9bce43f2-c750-4e6c-9b31-18ea1409a5ba/dalle-2024-11-25-225448-a-modern-and-sleek-square-logo-for-artificial-intellige-original.webp",[],{"id":277,"name":278,"description":279,"url":280,"color":281,"parentId":262,"count":13,"imageUrl":282,"parent":13,"order":12,"translations":283},92,"Artificial intelligence","Key ressources for AI","ai-ressources","#0f1cd7","https://static.dastra.eu/tag/3cf3f039-04ed-4b3a-b386-a99b43cb4e64/ai-act-bis-original.png",[],{"id":49,"name":50,"description":51,"url":52,"color":53,"parentId":27,"count":13,"imageUrl":13,"parent":13,"order":59,"translations":285},[286,287],{"lang":34,"name":62,"description":63},{"lang":40,"name":65,"description":66},[289],{"typeMetaDataId":123,"value":290,"id":291},"https://static.dastra.eu/backofficefilescontainer/875e1e54-f479-43ff-9572-c4add516b85c/Dastra-AI-transparency-notice-template-art50-EN.docx",117744,"https://static.dastra.eu/content/34bf6ba9-1e42-45b0-b292-63b6a01a0c70/ai-transparency-notice-1600x900-en-original.png",[294,295,296,297,298,299,300],"https://static.dastra.eu/content/34bf6ba9-1e42-45b0-b292-63b6a01a0c70/ai-transparency-notice-1600x900-en-1000.webp","https://static.dastra.eu/content/34bf6ba9-1e42-45b0-b292-63b6a01a0c70/ai-transparency-notice-1600x900-en.webp","https://static.dastra.eu/content/34bf6ba9-1e42-45b0-b292-63b6a01a0c70/ai-transparency-notice-1600x900-en-1500.webp","https://static.dastra.eu/content/34bf6ba9-1e42-45b0-b292-63b6a01a0c70/ai-transparency-notice-1600x900-en-800.webp","https://static.dastra.eu/content/34bf6ba9-1e42-45b0-b292-63b6a01a0c70/ai-transparency-notice-1600x900-en-600.webp","https://static.dastra.eu/content/34bf6ba9-1e42-45b0-b292-63b6a01a0c70/ai-transparency-notice-1600x900-en-300.webp","https://static.dastra.eu/content/34bf6ba9-1e42-45b0-b292-63b6a01a0c70/ai-transparency-notice-1600x900-en-100.webp",60275,14]