{"id":4577,"date":"2026-08-21T09:00:00","date_gmt":"2026-08-21T07:00:00","guid":{"rendered":"https:\/\/www.lablogic.pl\/?p=4577"},"modified":"2026-11-05T23:18:17","modified_gmt":"2026-11-05T22:18:17","slug":"who-is-responsible-for-ai-act-transparency-obligations","status":"publish","type":"post","link":"https:\/\/www.lablogic.pl\/en\/who-is-responsible-for-ai-act-transparency-obligations\/","title":{"rendered":"Who is responsible for AI Act transparency obligations?"},"content":{"rendered":"\n<p class=\"ll-art-meta wp-block-paragraph\"><a href=\"https:\/\/www.lablogic.pl\/en\/michal-rutkowski\/\"><strong>Micha\u0142 Rutkowski<\/strong><\/a> \u2022 for boards, compliance teams and DPOs \u2022 published August 21, 2026 \u2022 updated October 20, 2026 \u2022 8 min read<\/p>\n\n\n\n<div class=\"wp-block-columns ll-art-shell is-layout-flex wp-container-core-columns-is-layout-7387b849 wp-block-columns-is-layout-flex\">\n<div class=\"wp-block-column ll-art-rail is-layout-flow wp-block-column-is-layout-flow\">\n<div class=\"wp-block-group ll-art-railinner is-layout-constrained wp-block-group-is-layout-constrained\">\n\n\n\n<\/div>\n<\/div>\n\n\n\n<div class=\"wp-block-column ll-art-main is-layout-flow wp-block-column-is-layout-flow\">\n<div class=\"wp-block-group ll-art-answer is-layout-constrained wp-block-group-is-layout-constrained\">\n<h2 id=\"krotka-odpowiedz\" class=\"wp-block-heading\">Short answer<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Responsibility follows the role held towards a specific system, not the level of its risk. The provider is responsible for making the system disclose that a person is interacting with AI and for marking synthetic content in a machine-readable format. An organisation that itself develops an AI system or has it developed and puts it into service under its own name is also a provider, including for its own use. The deployer has two obligations of its own. It informs people about emotion recognition and biometric categorisation. It also discloses deep fakes and text published with the purpose of informing the public on matters of public interest. The obligation concerning text does not apply where the content has undergone human review or editorial control and a natural or legal person holds editorial responsibility for the publication. The obligations have applied since 2 August 2026. Providers of systems generating synthetic content that were placed on the market before that date have until 2 December 2026 for marking.<\/p>\n<\/div>\n\n\n\n<h2 id=\"dlaczego\" class=\"wp-block-heading\">Why this question arises at all<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">In the summer of 2026 the market settled on one message. The AI Act has been postponed. The postponement, however, covered the requirements and obligations concerning high-risk systems. The transparency provisions became applicable on the original schedule. The exception is a transitional period until 2 December 2026 for providers of systems generating synthetic content that were placed on the market before 2 August 2026. It concerns only the marking and detectability of outputs under Article 50(2).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For an organisation that only uses AI, the difference is fundamental. High-risk requirements apply to a narrow group of use cases. They apply from 2 December 2027 to high-risk AI systems under Annex III and from 2 August 2028 to high-risk AI systems under Annex I. Transparency obligations do not ask about the risk category. They ask what the system does and who uses it in a given arrangement.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The second source of confusion is commercial. The vendor of a tool usually declares compliance with the AI Act, and the organisation reads that as the end of the subject. Yet two of the four transparency obligations are addressed directly to the deployer. The provider cannot take them over from the client, because it does not decide towards whom and for what purpose the client uses the system.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The third source is terminological. \u201cTransparency\u201d in the AI Act does not mean documentation or a policy. It means specific information given to a specific person at a specific moment.<\/p>\n\n\n\n<h2 id=\"co-ustalic\" class=\"wp-block-heading\">What to establish before deciding<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Four obligations and two roles<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Article 50 of the Regulation contains four separate obligations. The first two are designed into the product; the other two are performed inside the organisation.<\/p>\n\n\n\n<figure class=\"wp-block-table ll-art-table\"><table><thead><tr><th>Obligation<\/th><th>Who holds it<\/th><th>What it covers<\/th><th>Exceptions and limits<\/th><\/tr><\/thead><tbody><tr><td>Informing people that they interact with an AI system (para. 1) \u2014 from 2 August 2026<\/td><td>provider<\/td><td>systems intended to interact directly with natural persons<\/td><td>no notice is required where the AI interaction is obvious to a reasonably well-informed, observant and circumspect person in the circumstances and context of use; a separate law-enforcement exception applies, except for systems available to the public to report a criminal offence<\/td><\/tr><tr><td>Marking synthetic content in a machine-readable format (para. 2) \u2014 from 2 August 2026<\/td><td>provider<\/td><td>audio, image, video and text that is generated or manipulated<\/td><td>excluded for assistive standard editing or where the system does not substantially alter the input data or its semantics; a separate law-enforcement exception applies; providers of systems placed on the market before 2 August 2026 have until 2 December 2026 to comply (Article 111(4))<\/td><\/tr><tr><td>Informing people about emotion recognition and biometric categorisation (para. 3) \u2014 from 2 August 2026<\/td><td>deployer<\/td><td>the persons the system is applied to<\/td><td>law-enforcement exception, subject to safeguards for the rights and freedoms of third parties<\/td><\/tr><tr><td>Disclosing deep fakes and published text (para. 4) \u2014 from 2 August 2026<\/td><td>deployer<\/td><td>image, audio and video content constituting a deep fake; text published with the purpose of informing the public on matters of public interest<\/td><td>deep fake in an evidently artistic, creative, satirical or fictional work or in an analogous one \u2014 the duty is limited to disclosure in a way that does not hamper the display or enjoyment of the work; text \u2014 no obligation after human review or editorial control where a natural or legal person holds editorial responsibility for the publication; a separate law-enforcement exception applies<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">The split has a practical consequence for procurement. The provider\u2019s obligations can be moved into contractual terms and verified before deployment. The deployer\u2019s obligations cannot be moved anywhere. They depend on how the organisation uses the system\u2019s output, and the provider does not control that.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The role follows from the definition, not from who sold the tool. A provider is an organisation that develops an AI system or has it developed and places it on the market or puts it into service under its own name or trademark (Article 3(3)). This also covers a system built on another company\u2019s model and used only within the organisation (Article 3(11) and (68)). In its guidelines on Article 50 the European Commission gives the example of a chatbot developed in-house. Such an organisation is responsible for the obligation under paragraph 1 and, where it generates content, also under paragraph 2. According to the Commission, a company commissioning an advertisement without deciding on the agency\u2019s use of AI is not a deployer.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What the deployer has to disclose<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The first obligation covers two kinds of systems. The organisation informs people that an emotion recognition system or a biometric categorisation system is being applied to them. The provision also requires personal data to be processed in line with the GDPR, so both layers run in parallel.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In the workplace, however, the question usually comes earlier. The Regulation prohibits the use of AI systems to infer emotions of individuals in the workplace and in education institutions. The exception covers medical and safety reasons only. Before the organisation designs information for its staff, it therefore has to settle whether it may run such a tool at all. For biometric categorisation a separate prohibition under Article 5(1)(g) applies regardless of the setting. With narrow exceptions it covers inferring race, political opinions or sexual orientation from biometric data, among other things.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The second obligation covers content. The Regulation defines a deep fake as AI-generated or manipulated image, audio or video content. Such content resembles existing persons or objects, places, entities or events. A person could falsely take such content to be authentic or truthful. The European Commission\u2019s guidelines on Article 50 read the word \u201cexisting\u201d broadly. According to the Commission, a realistic synthetic avatar of a person who could plausibly exist can also be a deep fake. The assessment of whether content could appear authentic is objective in the Commission\u2019s view. It does not require any intention to deceive. For such content the deployer discloses that it has been artificially generated or manipulated.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The same paragraph covers text. The obligation for text is narrower, however, and concerns text published in order to inform the public on matters of public interest. Ordinary marketing communication and internal correspondence fall outside its scope. The line gets thin in the communication of public institutions and in materials on safety, health and the environment.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">When the editorial exemption applies<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">For text the provision sets out an exemption that is easy to apply too broadly. The duty to disclose falls away where the content has undergone human review or editorial control and a natural or legal person holds editorial responsibility for the publication.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The condition has two limbs. Review alone is not enough \u2014 there has to be someone bearing editorial responsibility. In its guidelines on Article 50 the European Commission states that the review must concern the substance, with fact-checking as a minimum. According to the Commission, neither spell-checking nor cursory approval nor the mere existence of an editorial policy meets that condition. The Commission also considers that a substantive AI change to the text after approval voids the exemption. It recommends making the details of the person or function with editorial responsibility publicly available, for example in the website\u2019s legal notice. An organisation relying on the exemption would therefore do well to document who reviews the text before publication and how.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A separate relaxation applies to deep fakes forming part of an evidently artistic, creative, satirical or fictional work or of an analogous one. The obligation is then limited to disclosing the existence of such content in a way that does not hamper the display or enjoyment of the work.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How and when to give the information<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The Regulation settles both the form and the moment. The information is given in a clear and distinguishable manner, at the latest at the time of the first interaction or exposure. For content, the Commission takes this to mean the moment a person is first exposed to the system\u2019s output. The information must also meet the applicable accessibility requirements.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Three practical design decisions follow from that. The information cannot be hidden in terms of service or in a privacy policy, because it does not reach the person at the moment of first contact. It must also be accessible to persons with disabilities, because the Commission treats this as a condition of clear information. And it cannot be delivered after the fact.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The provision also states that paragraphs 1 to 4 are without prejudice to other transparency obligations of deployers under Union or national law. Information under Article 50 therefore does not replace the information duty under the GDPR. They are two parallel messages with different subject matter.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What changes on 2 December 2026<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The July 2026 omnibus added one date that concerns older tools. Providers of systems generating synthetic content that were placed on the market before 2 August 2026 have until 2 December 2026 to align with the marking obligation.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For the deploying organisation the conclusion runs the other way than it first seems. A tool generating content that was placed on the market before 2 August 2026 may not mark its output in a machine-readable way until December. What counts is the date on which the provider placed it on the market, not the date of purchase. The disclosure obligations under paragraph 4, however, already rest with the deployer and apply regardless of what the tool does. In that period the disclosure has to be delivered by a process, not by a product feature.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What you can rely on<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">On 20 July 2026 the European Commission published guidelines on Article 50. It approved their content at that time and announced formal adoption once all language versions are available. The guidelines explain the division of responsibility between the provider and the deployer, the scope of the exemptions and the meaning of a deep fake, among other things. They are not binding, but they show how the Commission reads the provision.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The second document is the Code of Practice on Transparency of AI-Generated Content. Article 50(7) provides that the Commission assesses whether adherence to such a code is sufficient to ensure compliance with paragraphs 2 and 4. In doing so the Commission takes utmost account of the opinion of the Board. The second section of the code is addressed directly to deployers and describes the labelling of deep fakes and of text under paragraph 4 as well as internal processes. According to the Commission\u2019s guidelines, adhering to a code assessed as adequate makes it possible to demonstrate compliance with those paragraphs. Signing up to the code is therefore a way of demonstrating compliance, not compliance itself.<\/p>\n\n\n\n<h2 id=\"bledy\" class=\"wp-block-heading\">Most common mistakes<\/h2>\n\n\n\n<ul class=\"wp-block-list ll-art-errors\">\n<li><strong>Assuming the postponement covered the whole Regulation.<\/strong> What moved were the requirements for high-risk systems. Transparency has applied since 2 August 2026. The transitional period until 2 December 2026 covers only the marking of outputs of older systems generating synthetic content.<\/li>\n\n\n\n<li><strong>Assigning all four obligations to the provider.<\/strong> Paragraphs 3 and 4 of Article 50 are addressed to the deployer and cannot be shifted by contract.<\/li>\n\n\n\n<li><strong>Treating machine-readable marking as disclosure to the recipient.<\/strong> The marking under paragraph 2 serves technical detectability. The disclosure under paragraph 4 is a message for a human being.<\/li>\n\n\n\n<li><strong>Invoking the editorial exemption with no one holding editorial responsibility.<\/strong> The provision requires both elements at once, and the organisation has to be able to show both.<\/li>\n\n\n\n<li><strong>Putting the information in the terms of service instead of at the moment of first contact.<\/strong> The provision fixes a moment, not a place in the documentation.<\/li>\n\n\n\n<li><strong>Overlooking the prohibition on emotion recognition in the workplace.<\/strong> Informing staff does not cure a practice that is prohibited.<\/li>\n<\/ul>\n\n\n\n<h2 id=\"wnioski\" class=\"wp-block-heading\">Conclusions and next steps<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Transparency, alongside AI literacy and prohibited practices, already concerns an organisation using off-the-shelf tools.<\/p>\n\n\n\n<div class=\"wp-block-group ll-art-zdanie is-layout-constrained wp-block-group-is-layout-constrained\">\n\n<p class=\"wp-block-paragraph\">Remember<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Responsibility for transparency is decided by the role held towards a specific use case, not by the risk category and not by the provider\u2019s declaration.<\/p>\n\n<\/div>\n\n\n\n<p class=\"wp-block-paragraph\">The organisation itself is responsible for two obligations, so it needs a process rather than just a clause in a contract.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A sequence that works when putting this area in order.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Collect the use cases in which AI interacts with people or produces synthetic content. Add the emotion recognition and biometric categorisation systems applied to people.<\/li>\n\n\n\n<li>For each use case establish the organisation\u2019s role and assign the obligations from the relevant paragraph of Article 50.<\/li>\n\n\n\n<li>Check whether tools placed on the market before 2 August 2026 mark their output in a machine-readable way. Plan a solution for the period until December.<\/li>\n\n\n\n<li>Design the wording and the moment of the information, and for text covered by Article 50(4) settle who holds editorial responsibility.<\/li>\n\n\n\n<li>Keep a trace of those decisions, because that is what answers the question of a client, an auditor or an authority.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">A trace of the decisions is easy to skip. Transparency obligations are performed towards people, but they are demonstrated towards an authority \u2014 and that calls for different material than a notice on a website.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Related materials<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong><a href=\"https:\/\/www.lablogic.pl\/en\/when-does-an-organization-become-an-ai-provider\/\">When does an organisation using AI become the provider of a system?<\/a><\/strong> \u2014 when an organisation is a provider by definition and bears the obligations under Article 50(1) and (2), and when it takes over the role of provider of a high-risk AI system under Article 25.<\/li>\n\n\n\n<li><strong><a href=\"https:\/\/www.lablogic.pl\/en\/what-should-an-ai-use-register-contain\/\">What should an AI use register contain?<\/a><\/strong> \u2014 the list in which the Article 50 answers are recorded for each use case.<\/li>\n\n\n\n<li><strong><a href=\"https:\/\/www.lablogic.pl\/en\/high-risk-ai-system\/\">Is the AI tool we use a high-risk system?<\/a><\/strong> \u2014 the classification that decides the postponed obligations.<\/li>\n\n\n\n<li><strong><a href=\"https:\/\/www.lablogic.pl\/en\/new-ai-act-prohibitions\/\">What new prohibitions does the AI Act introduce from 2 December 2026 and whom do they cover?<\/a><\/strong> \u2014 new Article 5 prohibitions that labelling deep fake content does not lift.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\">Sources<\/h2>\n\n\n\n<ul class=\"wp-block-list ll-art-sources\">\n<li>Regulation (EU) 2024\/1689 of the European Parliament and of the Council (Artificial Intelligence Act), consolidated version of 27 July 2026, Article 3(3), (11), (60) and (68), Article 5(1)(f) and (g), Article 25, Article 50, Article 111 and Article 113 \u2014 <a href=\"https:\/\/eur-lex.europa.eu\/legal-content\/EN\/TXT\/?uri=CELEX:02024R1689-20260727\" target=\"_blank\" rel=\"noreferrer noopener\">eur-lex.europa.eu<\/a>.<\/li>\n\n\n\n<li>Regulation (EU) 2026\/1744 of the European Parliament and of the Council of 8 July 2026, Article 1(39) and (40) (amendments to Articles 111 and 113) \u2014 <a href=\"https:\/\/eur-lex.europa.eu\/legal-content\/EN\/TXT\/?uri=CELEX:32026R1744\" target=\"_blank\" rel=\"noreferrer noopener\">eur-lex.europa.eu<\/a>.<\/li>\n\n\n\n<li>European Commission, guidelines on the implementation of the transparency obligations for certain AI systems under Article 50 of Regulation (EU) 2024\/1689 \u2014 content approved by Communication C(2026) 5054 final of 20 July 2026, formal adoption announced once all language versions are available \u2014 <a href=\"https:\/\/digital-strategy.ec.europa.eu\/en\/library\/guidelines-transparency-obligations-providers-and-deployers-ai-systems\" target=\"_blank\" rel=\"noreferrer noopener\">digital-strategy.ec.europa.eu<\/a>.<\/li>\n\n\n\n<li>Code of Practice on Transparency of AI-Generated Content, together with the Commission\u2019s opinion on its assessment, European Commission \u2014 <a href=\"https:\/\/digital-strategy.ec.europa.eu\/en\/policies\/code-practice-ai-generated-content\" target=\"_blank\" rel=\"noreferrer noopener\">digital-strategy.ec.europa.eu<\/a>.<\/li>\n<\/ul>\n\n\n\n<div class=\"wp-block-group ll-art-cta is-layout-constrained wp-block-group-is-layout-constrained\">\n<h2 class=\"wp-block-heading ll-nietoc\">See where AI already speaks for your organisation<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Transparency obligations concern use cases that usually appeared without a board decision. The review starts with a list of them and ends by assigning the obligations under Article 50 to specific people in the organisation.<\/p>\n\n\n\n<div class=\"wp-block-buttons is-layout-flex wp-block-buttons-is-layout-flex\">\n<div class=\"wp-block-button\"><a class=\"wp-block-button__link wp-element-button\" href=\"https:\/\/www.lablogic.pl\/en\/ai-act\/\">A review of AI use cases<\/a><\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>Article 50 of the AI Act splits the obligations by role towards the system, not by risk level. Two of the four are addressed directly to the organisation that only deploys AI \u2014 and the provider will not perform them for it.<\/p>\n","protected":false},"author":2,"featured_media":5561,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ll_stan_prawny":"November 2026","footnotes":""},"categories":[83],"tags":[],"class_list":["post-4577","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-eu-ai-act"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.5.1 - aioseo.com -->\n\t<meta name=\"description\" content=\"Article 50 of the AI Act splits obligations by role, not by risk level. Two of the four fall on the deployer. See what the provider will not do for you.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Micha\u0142 Rutkowski\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/www.lablogic.pl\/en\/who-is-responsible-for-ai-act-transparency-obligations\/\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.5.1\" \/>\n\t\t<meta property=\"og:locale\" content=\"en_US\" \/>\n\t\t<meta property=\"og:site_name\" content=\"LabLogic - Micha\u0142 Rutkowski | DPO, GDPR, NIS2 and cybersecurity in practice\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"AI Act transparency \u2014 the obligations follow the role\" \/>\n\t\t<meta property=\"og:description\" content=\"Two of the four transparency obligations fall on the organisation that only deploys AI.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/www.lablogic.pl\/en\/who-is-responsible-for-ai-act-transparency-obligations\/\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/09\/ll-og-obowiazki-przejrzystosci-ai-act-en.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/09\/ll-og-obowiazki-przejrzystosci-ai-act-en.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"1200\" \/>\n\t\t<meta property=\"og:image:height\" content=\"630\" \/>\n\t\t<meta property=\"article:section\" content=\"AI Act\" \/>\n\t\t<meta property=\"article:tag\" content=\"ai act\" \/>\n\t\t<meta property=\"article:tag\" content=\"transparency\" \/>\n\t\t<meta property=\"article:tag\" content=\"deepfake\" \/>\n\t\t<meta property=\"article:tag\" content=\"compliance\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2026-08-21T07:00:00+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2026-11-05T22:18:17+00:00\" \/>\n\t\t<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n\t\t<meta name=\"twitter:title\" content=\"AI Act transparency \u2014 the obligations follow the role\" \/>\n\t\t<meta name=\"twitter:description\" content=\"Two of the four transparency obligations fall on the organisation that only deploys AI.\" \/>\n\t\t<meta name=\"twitter:image\" content=\"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/09\/ll-og-obowiazki-przejrzystosci-ai-act-en.jpg\" \/>\n\t\t<script type=\"application\/ld+json\" class=\"aioseo-schema\">\n\t\t\t{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/who-is-responsible-for-ai-act-transparency-obligations\\\/#article\",\"name\":\"AI Act transparency obligations \\u2014 who is responsible\",\"headline\":\"Who is responsible for AI Act transparency obligations?\",\"author\":{\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/#michal-rutkowski\"},\"publisher\":{\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/#organization\"},\"image\":{\"@type\":\"ImageObject\",\"url\":\"https:\\\/\\\/www.lablogic.pl\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/ll-og-obowiazki-przejrzystosci-ai-act-en.jpg\",\"width\":1200,\"height\":630,\"caption\":\"Four obligations, two roles \\u2014 LabLogic article graphic by Micha\\u0142 Rutkowski\"},\"datePublished\":\"2026-08-21T09:00:00+02:00\",\"dateModified\":\"2026-11-05T23:18:17+01:00\",\"inLanguage\":\"en-US\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/who-is-responsible-for-ai-act-transparency-obligations\\\/#webpage\"},\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/who-is-responsible-for-ai-act-transparency-obligations\\\/#webpage\"},\"articleSection\":\"AI Act\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/who-is-responsible-for-ai-act-transparency-obligations\\\/#breadcrumblist\",\"itemListElement\":[{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/#listItem\",\"position\":1,\"name\":\"LabLogic\",\"item\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/baza-wiedzy\\\/eu-ai-act\\\/#listItem\",\"name\":\"AI Act\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/baza-wiedzy\\\/eu-ai-act\\\/#listItem\",\"position\":2,\"name\":\"AI Act\",\"item\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/baza-wiedzy\\\/eu-ai-act\\\/\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/who-is-responsible-for-ai-act-transparency-obligations\\\/#listItem\",\"name\":\"Who is responsible for AI Act transparency obligations?\"},\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/#listItem\",\"name\":\"LabLogic\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/who-is-responsible-for-ai-act-transparency-obligations\\\/#listItem\",\"position\":3,\"name\":\"Who is responsible for AI Act transparency obligations?\",\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/baza-wiedzy\\\/eu-ai-act\\\/#listItem\",\"name\":\"AI Act\"}}]},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/#organization\",\"name\":\"LabLogic\",\"description\":\"LabLogic is the advisory practice of Micha\\u0142 Rutkowski, based in Gdynia, Poland. It acts as an external data protection officer and supports NIS2 and Polish KSC Act implementation, incident and breach response, and AI Act readiness for medium and large organisations, on site in the Tricity area and remotely across Poland.\",\"url\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/\",\"email\":\"m.rutkowski@lablogic.pl\",\"foundingDate\":\"2004\",\"logo\":{\"@type\":\"ImageObject\",\"url\":\"https:\\\/\\\/www.lablogic.pl\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/cropped-lablogic-site-icon-512.png\",\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/who-is-responsible-for-ai-act-transparency-obligations\\\/#organizationLogo\",\"width\":512,\"height\":512},\"image\":{\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/who-is-responsible-for-ai-act-transparency-obligations\\\/#organizationLogo\"},\"sameAs\":[\"https:\\\/\\\/www.linkedin.com\\\/in\\\/michal-rutkowski-iod\"],\"additionalType\":\"https:\\\/\\\/schema.org\\\/ProfessionalService\",\"legalName\":\"LabLogic Consulting Micha\\u0142 Rutkowski\",\"address\":{\"@type\":\"PostalAddress\",\"streetAddress\":\"ul. Wolno\\u015bci 15\",\"postalCode\":\"81-327\",\"addressLocality\":\"Gdynia\",\"addressRegion\":\"pomorskie\",\"addressCountry\":\"PL\"},\"vatID\":\"PL9580972114\",\"taxID\":\"9580972114\",\"areaServed\":{\"@type\":\"Country\",\"name\":\"Poland\"},\"knowsAbout\":[\"GDPR\",\"Data Protection Officer (DPO)\",\"NIS2 Directive\",\"Polish National Cybersecurity System Act (KSC)\",\"Cybersecurity incident and data breach response\",\"EU AI Act\",\"ISO\\\/IEC 27001\",\"Information security management\"],\"founder\":{\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/#michal-rutkowski\"},\"hasOfferCatalog\":{\"@type\":\"OfferCatalog\",\"name\":\"Services\",\"itemListElement\":[{\"@type\":\"Offer\",\"itemOffered\":{\"@type\":\"Service\",\"name\":\"External Data Protection Officer (DPO)\",\"url\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/external-dpo\\\/\"}},{\"@type\":\"Offer\",\"itemOffered\":{\"@type\":\"Service\",\"name\":\"NIS2 and KSC implementation support\",\"url\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/nis2-ksc\\\/\"}},{\"@type\":\"Offer\",\"itemOffered\":{\"@type\":\"Service\",\"name\":\"Incident and data breach response\",\"url\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/incident-response\\\/\"}},{\"@type\":\"Offer\",\"itemOffered\":{\"@type\":\"Service\",\"name\":\"GDPR and NIS2 training\",\"url\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/training\\\/\"}},{\"@type\":\"Offer\",\"itemOffered\":{\"@type\":\"Service\",\"name\":\"AI Act: roles, obligations and preparation\",\"url\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/ai-act\\\/\"}}]}},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/#michal-rutkowski\",\"url\":\"https:\\\/\\\/www.lablogic.pl\\\/michal-rutkowski\\\/\",\"name\":\"Micha\\u0142 Rutkowski\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/#michal-rutkowski-portret\",\"url\":\"https:\\\/\\\/www.lablogic.pl\\\/wp-content\\\/uploads\\\/2026\\\/08\\\/michal-rutkowski-iod-dpo-rodo-nis2-lablogic.webp\",\"width\":864,\"height\":1080,\"caption\":\"Micha\\u0142 Rutkowski\"},\"sameAs\":[\"https:\\\/\\\/www.linkedin.com\\\/in\\\/michal-rutkowski-iod\"],\"jobTitle\":\"Data Protection Officer (DPO), NIS2\\\/KSC and cybersecurity advisor\",\"description\":\"Data protection and cybersecurity practitioner, owner of LabLogic. Since 2004 he has supported medium and large organisations: audits, implementations, incidents and training.\",\"email\":\"m.rutkowski@lablogic.pl\",\"knowsAbout\":[\"GDPR\",\"Data Protection Officer (DPO)\",\"NIS2 Directive\",\"Polish National Cybersecurity System Act (KSC)\",\"Cybersecurity incident and data breach response\",\"EU AI Act\",\"ISO\\\/IEC 27001\",\"Information security management\"],\"worksFor\":{\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/#organization\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/who-is-responsible-for-ai-act-transparency-obligations\\\/#webpage\",\"url\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/who-is-responsible-for-ai-act-transparency-obligations\\\/\",\"name\":\"AI Act transparency obligations \\u2014 who is responsible\",\"description\":\"Article 50 of the AI Act splits obligations by role, not by risk level. Two of the four fall on the deployer. See what the provider will not do for you.\",\"inLanguage\":\"en-US\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/#website\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/who-is-responsible-for-ai-act-transparency-obligations\\\/#breadcrumblist\"},\"author\":{\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/#michal-rutkowski\"},\"creator\":{\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/#michal-rutkowski\"},\"image\":{\"@type\":\"ImageObject\",\"url\":\"https:\\\/\\\/www.lablogic.pl\\\/wp-content\\\/uploads\\\/2026\\\/09\\\/ll-og-obowiazki-przejrzystosci-ai-act-en.jpg\",\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/who-is-responsible-for-ai-act-transparency-obligations\\\/#mainImage\",\"width\":1200,\"height\":630,\"caption\":\"Four obligations, two roles \\u2014 LabLogic article graphic by Micha\\u0142 Rutkowski\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/who-is-responsible-for-ai-act-transparency-obligations\\\/#mainImage\"},\"datePublished\":\"2026-08-21T09:00:00+02:00\",\"dateModified\":\"2026-11-05T23:18:17+01:00\"},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/#website\",\"url\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/\",\"name\":\"Micha\\u0142 Rutkowski - LabLogic\",\"alternateName\":\"LabLogic\",\"description\":\"DPO, GDPR, NIS2 and cybersecurity in practice\",\"inLanguage\":\"en-US\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/#organization\"}}]}\n\t\t<\/script>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"AI Act transparency obligations \u2014 who is responsible","description":"Article 50 of the AI Act splits obligations by role, not by risk level. Two of the four fall on the deployer. See what the provider will not do for you.","canonical_url":"https:\/\/www.lablogic.pl\/en\/who-is-responsible-for-ai-act-transparency-obligations\/","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.lablogic.pl\/en\/who-is-responsible-for-ai-act-transparency-obligations\/#article","name":"AI Act transparency obligations \u2014 who is responsible","headline":"Who is responsible for AI Act transparency obligations?","author":{"@id":"https:\/\/www.lablogic.pl\/#michal-rutkowski"},"publisher":{"@id":"https:\/\/www.lablogic.pl\/#organization"},"image":{"@type":"ImageObject","url":"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/09\/ll-og-obowiazki-przejrzystosci-ai-act-en.jpg","width":1200,"height":630,"caption":"Four obligations, two roles \u2014 LabLogic article graphic by Micha\u0142 Rutkowski"},"datePublished":"2026-08-21T09:00:00+02:00","dateModified":"2026-11-05T23:18:17+01:00","inLanguage":"en-US","mainEntityOfPage":{"@id":"https:\/\/www.lablogic.pl\/en\/who-is-responsible-for-ai-act-transparency-obligations\/#webpage"},"isPartOf":{"@id":"https:\/\/www.lablogic.pl\/en\/who-is-responsible-for-ai-act-transparency-obligations\/#webpage"},"articleSection":"AI Act"},{"@type":"BreadcrumbList","@id":"https:\/\/www.lablogic.pl\/en\/who-is-responsible-for-ai-act-transparency-obligations\/#breadcrumblist","itemListElement":[{"@type":"ListItem","@id":"https:\/\/www.lablogic.pl\/en\/#listItem","position":1,"name":"LabLogic","item":"https:\/\/www.lablogic.pl\/en\/","nextItem":{"@type":"ListItem","@id":"https:\/\/www.lablogic.pl\/en\/baza-wiedzy\/eu-ai-act\/#listItem","name":"AI Act"}},{"@type":"ListItem","@id":"https:\/\/www.lablogic.pl\/en\/baza-wiedzy\/eu-ai-act\/#listItem","position":2,"name":"AI Act","item":"https:\/\/www.lablogic.pl\/en\/baza-wiedzy\/eu-ai-act\/","nextItem":{"@type":"ListItem","@id":"https:\/\/www.lablogic.pl\/en\/who-is-responsible-for-ai-act-transparency-obligations\/#listItem","name":"Who is responsible for AI Act transparency obligations?"},"previousItem":{"@type":"ListItem","@id":"https:\/\/www.lablogic.pl\/en\/#listItem","name":"LabLogic"}},{"@type":"ListItem","@id":"https:\/\/www.lablogic.pl\/en\/who-is-responsible-for-ai-act-transparency-obligations\/#listItem","position":3,"name":"Who is responsible for AI Act transparency obligations?","previousItem":{"@type":"ListItem","@id":"https:\/\/www.lablogic.pl\/en\/baza-wiedzy\/eu-ai-act\/#listItem","name":"AI Act"}}]},{"@type":"Organization","@id":"https:\/\/www.lablogic.pl\/#organization","name":"LabLogic","description":"LabLogic is the advisory practice of Micha\u0142 Rutkowski, based in Gdynia, Poland. It acts as an external data protection officer and supports NIS2 and Polish KSC Act implementation, incident and breach response, and AI Act readiness for medium and large organisations, on site in the Tricity area and remotely across Poland.","url":"https:\/\/www.lablogic.pl\/en\/","email":"m.rutkowski@lablogic.pl","foundingDate":"2004","logo":{"@type":"ImageObject","url":"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/08\/cropped-lablogic-site-icon-512.png","@id":"https:\/\/www.lablogic.pl\/en\/who-is-responsible-for-ai-act-transparency-obligations\/#organizationLogo","width":512,"height":512},"image":{"@id":"https:\/\/www.lablogic.pl\/en\/who-is-responsible-for-ai-act-transparency-obligations\/#organizationLogo"},"sameAs":["https:\/\/www.linkedin.com\/in\/michal-rutkowski-iod"],"additionalType":"https:\/\/schema.org\/ProfessionalService","legalName":"LabLogic Consulting Micha\u0142 Rutkowski","address":{"@type":"PostalAddress","streetAddress":"ul. Wolno\u015bci 15","postalCode":"81-327","addressLocality":"Gdynia","addressRegion":"pomorskie","addressCountry":"PL"},"vatID":"PL9580972114","taxID":"9580972114","areaServed":{"@type":"Country","name":"Poland"},"knowsAbout":["GDPR","Data Protection Officer (DPO)","NIS2 Directive","Polish National Cybersecurity System Act (KSC)","Cybersecurity incident and data breach response","EU AI Act","ISO\/IEC 27001","Information security management"],"founder":{"@id":"https:\/\/www.lablogic.pl\/#michal-rutkowski"},"hasOfferCatalog":{"@type":"OfferCatalog","name":"Services","itemListElement":[{"@type":"Offer","itemOffered":{"@type":"Service","name":"External Data Protection Officer (DPO)","url":"https:\/\/www.lablogic.pl\/en\/external-dpo\/"}},{"@type":"Offer","itemOffered":{"@type":"Service","name":"NIS2 and KSC implementation support","url":"https:\/\/www.lablogic.pl\/en\/nis2-ksc\/"}},{"@type":"Offer","itemOffered":{"@type":"Service","name":"Incident and data breach response","url":"https:\/\/www.lablogic.pl\/en\/incident-response\/"}},{"@type":"Offer","itemOffered":{"@type":"Service","name":"GDPR and NIS2 training","url":"https:\/\/www.lablogic.pl\/en\/training\/"}},{"@type":"Offer","itemOffered":{"@type":"Service","name":"AI Act: roles, obligations and preparation","url":"https:\/\/www.lablogic.pl\/en\/ai-act\/"}}]}},{"@type":"Person","@id":"https:\/\/www.lablogic.pl\/#michal-rutkowski","url":"https:\/\/www.lablogic.pl\/michal-rutkowski\/","name":"Micha\u0142 Rutkowski","image":{"@type":"ImageObject","@id":"https:\/\/www.lablogic.pl\/#michal-rutkowski-portret","url":"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/08\/michal-rutkowski-iod-dpo-rodo-nis2-lablogic.webp","width":864,"height":1080,"caption":"Micha\u0142 Rutkowski"},"sameAs":["https:\/\/www.linkedin.com\/in\/michal-rutkowski-iod"],"jobTitle":"Data Protection Officer (DPO), NIS2\/KSC and cybersecurity advisor","description":"Data protection and cybersecurity practitioner, owner of LabLogic. Since 2004 he has supported medium and large organisations: audits, implementations, incidents and training.","email":"m.rutkowski@lablogic.pl","knowsAbout":["GDPR","Data Protection Officer (DPO)","NIS2 Directive","Polish National Cybersecurity System Act (KSC)","Cybersecurity incident and data breach response","EU AI Act","ISO\/IEC 27001","Information security management"],"worksFor":{"@id":"https:\/\/www.lablogic.pl\/#organization"}},{"@type":"WebPage","@id":"https:\/\/www.lablogic.pl\/en\/who-is-responsible-for-ai-act-transparency-obligations\/#webpage","url":"https:\/\/www.lablogic.pl\/en\/who-is-responsible-for-ai-act-transparency-obligations\/","name":"AI Act transparency obligations \u2014 who is responsible","description":"Article 50 of the AI Act splits obligations by role, not by risk level. Two of the four fall on the deployer. See what the provider will not do for you.","inLanguage":"en-US","isPartOf":{"@id":"https:\/\/www.lablogic.pl\/en\/#website"},"breadcrumb":{"@id":"https:\/\/www.lablogic.pl\/en\/who-is-responsible-for-ai-act-transparency-obligations\/#breadcrumblist"},"author":{"@id":"https:\/\/www.lablogic.pl\/#michal-rutkowski"},"creator":{"@id":"https:\/\/www.lablogic.pl\/#michal-rutkowski"},"image":{"@type":"ImageObject","url":"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/09\/ll-og-obowiazki-przejrzystosci-ai-act-en.jpg","@id":"https:\/\/www.lablogic.pl\/en\/who-is-responsible-for-ai-act-transparency-obligations\/#mainImage","width":1200,"height":630,"caption":"Four obligations, two roles \u2014 LabLogic article graphic by Micha\u0142 Rutkowski"},"primaryImageOfPage":{"@id":"https:\/\/www.lablogic.pl\/en\/who-is-responsible-for-ai-act-transparency-obligations\/#mainImage"},"datePublished":"2026-08-21T09:00:00+02:00","dateModified":"2026-11-05T23:18:17+01:00"},{"@type":"WebSite","@id":"https:\/\/www.lablogic.pl\/en\/#website","url":"https:\/\/www.lablogic.pl\/en\/","name":"Micha\u0142 Rutkowski - LabLogic","alternateName":"LabLogic","description":"DPO, GDPR, NIS2 and cybersecurity in practice","inLanguage":"en-US","publisher":{"@id":"https:\/\/www.lablogic.pl\/#organization"}}]},"og:locale":"en_US","og:site_name":"LabLogic - Micha\u0142 Rutkowski | DPO, GDPR, NIS2 and cybersecurity in practice","og:type":"article","og:title":"AI Act transparency \u2014 the obligations follow the role","og:description":"Two of the four transparency obligations fall on the organisation that only deploys AI.","og:url":"https:\/\/www.lablogic.pl\/en\/who-is-responsible-for-ai-act-transparency-obligations\/","og:image":"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/09\/ll-og-obowiazki-przejrzystosci-ai-act-en.jpg","og:image:secure_url":"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/09\/ll-og-obowiazki-przejrzystosci-ai-act-en.jpg","og:image:width":1200,"og:image:height":630,"article:section":"AI Act","article:tag":["ai act","transparency","deepfake","compliance"],"article:published_time":"2026-08-21T07:00:00+00:00","article:modified_time":"2026-11-05T22:18:17+00:00","twitter:card":"summary_large_image","twitter:title":"AI Act transparency \u2014 the obligations follow the role","twitter:description":"Two of the four transparency obligations fall on the organisation that only deploys AI.","twitter:image":"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/09\/ll-og-obowiazki-przejrzystosci-ai-act-en.jpg"},"aioseo_meta_data":{"post_id":"4577","title":"AI Act transparency obligations \u2014 who is responsible","description":"Article 50 of the AI Act splits obligations by role, not by risk level. Two of the four fall on the deployer. See what the provider will not do for you.","keywords":null,"keyphrases":{"focus":{"keyphrase":"AI Act transparency obligations","score":61},"additional":[{"keyphrase":"Article 50 AI Act","score":69},{"keyphrase":"marking AI-generated content","score":69},{"keyphrase":"deployer obligations AI Act","score":69},{"keyphrase":"deepfake disclosure","score":69}]},"primary_term":null,"canonical_url":null,"og_title":"AI Act transparency \u2014 the obligations follow the role","og_description":"Two of the four transparency obligations fall on the organisation that only deploys AI.","og_object_type":"article","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":"","og_custom_url":null,"og_article_section":"AI Act","og_article_tags":[{"label":"AI Act","value":"AI Act"},{"label":"transparency","value":"transparency"},{"label":"deepfake","value":"deepfake"},{"label":"compliance","value":"compliance"}],"twitter_use_og":true,"twitter_card":"summary_large_image","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"Article","isEnabled":true},"graphs":[]},"schema_type":"default","schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":"-1","robots_max_videopreview":"-1","robots_max_imagepreview":"large","priority":null,"frequency":"default","local_seo":null,"breadcrumb_settings":null,"limit_modified_date":false,"ai":{"faqs":[],"keyPoints":[],"schemas":[],"titles":[],"descriptions":[],"socialPosts":{"email":{"subject":"","preview":"","content":""},"linkedin":[],"twitter":[],"facebook":[],"instagram":[]}},"created":"2026-08-21 17:15:17","updated":"2026-11-05 22:20:53","seo_analyzer_scan_date":null,"focus_keyword":"AI Act transparency obligations","additional_keywords":[{"word":"Article 50 AI Act","score":69,"items":{"introductionKeyword":{"score":3},"keyphraseLength":{"score":9},"keyphraseDensity":{"score":4},"functionWordsInKeyphrase":{"score":9},"textCompetingLinks":{"score":9},"imageKeyphrase":{"score":3}}},{"word":"marking AI-generated content","score":69,"items":{"introductionKeyword":{"score":3},"keyphraseLength":{"score":9},"keyphraseDensity":{"score":4},"functionWordsInKeyphrase":{"score":9},"textCompetingLinks":{"score":9},"imageKeyphrase":{"score":3}}},{"word":"deployer obligations AI Act","score":69,"items":{"introductionKeyword":{"score":3},"keyphraseLength":{"score":9},"keyphraseDensity":{"score":4},"functionWordsInKeyphrase":{"score":9},"textCompetingLinks":{"score":9},"imageKeyphrase":{"score":3}}},{"word":"deepfake disclosure","score":69,"items":{"introductionKeyword":{"score":3},"keyphraseLength":{"score":9},"keyphraseDensity":{"score":4},"functionWordsInKeyphrase":{"score":9},"textCompetingLinks":{"score":9},"imageKeyphrase":{"score":3}}}],"truseo_locale":null},"spectra_blocks_featured_image_url":{"thumbnail":{"url":"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/09\/ll-og-obowiazki-przejrzystosci-ai-act-en-150x150.jpg","width":150,"height":150},"medium":{"url":"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/09\/ll-og-obowiazki-przejrzystosci-ai-act-en-300x158.jpg","width":300,"height":158},"medium_large":{"url":"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/09\/ll-og-obowiazki-przejrzystosci-ai-act-en-768x403.jpg","width":768,"height":403},"large":{"url":"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/09\/ll-og-obowiazki-przejrzystosci-ai-act-en-1024x538.jpg","width":1024,"height":538},"full":{"url":"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/09\/ll-og-obowiazki-przejrzystosci-ai-act-en.jpg","width":1200,"height":630}},"spectra_blocks_author_info":{"display_name":"Micha\u0142 Rutkowski","avatar_url":"https:\/\/secure.gravatar.com\/avatar\/29f5af5a0ce65a4307813722032192bdf08e740cbda98b61aa73b548422ff768?s=96&d=mm&r=g","author_link":"https:\/\/www.lablogic.pl\/en\/author\/michal-rutkowski\/","description":"Micha\u0142 Rutkowski \u2014 praktyk ochrony danych i cyberbezpiecze\u0144stwa, w\u0142a\u015bciciel LabLogic. Od 2004 roku pracuje na styku technologii, ochrony danych i zarz\u0105dzania ryzykiem. Pe\u0142ni funkcj\u0119 zewn\u0119trznego IOD\/DPO, prowadzi audyty RODO, kwalifikacj\u0119 i wdro\u017cenia NIS2 oraz ustawy o KSC, wspiera organizacje przy incydentach i naruszeniach ochrony danych, szkoli zarz\u0105dy, kadr\u0119 kierownicz\u0105 oraz zespo\u0142y IT i compliance. Pracuje ze \u015brednimi i du\u017cymi organizacjami, w tym z sektora finansowego i bran\u017c regulowanych."},"_links":{"self":[{"href":"https:\/\/www.lablogic.pl\/en\/wp-json\/wp\/v2\/posts\/4577","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.lablogic.pl\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.lablogic.pl\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.lablogic.pl\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.lablogic.pl\/en\/wp-json\/wp\/v2\/comments?post=4577"}],"version-history":[{"count":8,"href":"https:\/\/www.lablogic.pl\/en\/wp-json\/wp\/v2\/posts\/4577\/revisions"}],"predecessor-version":[{"id":6036,"href":"https:\/\/www.lablogic.pl\/en\/wp-json\/wp\/v2\/posts\/4577\/revisions\/6036"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.lablogic.pl\/en\/wp-json\/wp\/v2\/media\/5561"}],"wp:attachment":[{"href":"https:\/\/www.lablogic.pl\/en\/wp-json\/wp\/v2\/media?parent=4577"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.lablogic.pl\/en\/wp-json\/wp\/v2\/categories?post=4577"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.lablogic.pl\/en\/wp-json\/wp\/v2\/tags?post=4577"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}