Article 25: Responsibilities along the AI value chain
Article 25 states that a distributor, importer, deployer or third party is considered a provider if they place the AI system on the market under their own name, modify the intended purpose, or make a substantial modification.
Praxikon tracks Article 25 (Responsibilities along the AI value chain) under the EU AI Act, citing the source for every statement.
Official text
Source: EUR-Lex, Regulation (EU) 2024/1689. Text reproduced verbatim.
Download AI Act (PDF) →Decision tree
Do you become the provider of a high-risk AI system?
Article 25 shifts the provider role to whoever puts someone else’s system under their own name, substantially modifies it or deploys it for another purpose. The outcome is always: you become the provider of a high-risk system, with the obligations of Article 16.
Question 1 · Art. 25(1)
Are you a distributor, importer, deployer or other third party in relation to an AI system that someone else has already placed on the market or put into service?
Full diagram
- 1
Are you a distributor, importer, deployer or other third party in relation to an AI system that someone else has already placed on the market or put into service?
Art. 25(1)
- Yes → Question 2
- No, we developed it ourselves → Outcome A
- 2
Do you put your name or trademark on a high-risk AI system already placed on the market or put into service?
Art. 25(1)(a)
- Yes → Outcome B
- No → Question 3
- 3
Do you make a substantial modification to a high-risk AI system, such that it remains a high-risk system?
Art. 25(1)(b) · Art. 3(23)
- Yes → Outcome C
- No → Question 4
- 4
Do you modify the intended purpose of an AI system that has not been classified as high risk, including a general-purpose AI system such as a general chatbot?
Art. 25(1)(c)
- Yes → Question 5
- No → Question 6
- 5
Does your new purpose make the system a high-risk system under Article 6, for example because you use it to select job applicants or assess creditworthiness?
Art. 25(1)(c) · art. 6
- Yes → Outcome D
- No → Outcome E
- 6
Is the high-risk system a safety component of a product under Section A of Annex I, placed on the market or put into service under your name or trademark as product manufacturer?
Art. 25(3)
- Yes → Outcome F
- No → Outcome G
Outcome A · Check further
You are probably already the provider
Whoever develops an AI system or has it developed and places it on the market or puts it into service under their own name is the provider. Article 25 is then not needed. Check with Article 6 whether the system is high risk.
Art. 3(3) · art. 6
Outcome B · Applies
You become the provider through your own name or trademark
You take on the provider obligations of Article 16. The regulation leaves contractual arrangements that allocate the obligations differently unaffected. Record such an allocation in writing, but do not assume that it releases you from your obligations towards the supervisory authority: the text is not explicit on that. The initial provider cooperates with you and provides the necessary information, documentation and technical access (paragraph 2).
Art. 25(1)(a) · Art. 25(2) · art. 16
Outcome C · Applies
You become the provider through a substantial modification
You take on the obligations of Article 16 and the modified system must undergo a new conformity assessment (Article 43(4)). The initial provider is no longer considered the provider of that system, but must cooperate closely: documentation, known limitations and failure modes, and targeted technical access for testing.
Art. 25(1)(b) · Art. 25(2) · art. 16 · Art. 43(4)
Outcome D · Applies
You become the provider through a new intended purpose
The new purpose makes the system high risk and you are the provider, with the obligations of Article 16. If the initial provider clearly specified that the system is not to be changed into a high-risk system, it does not have to hand over documentation. For Annex III the requirements apply from 2 December 2027.
Art. 25(1)(c) · Art. 25(2) · art. 16 · art. 113 onder c
Outcome E · Does not apply
No shift under Article 25
If the system stays outside Article 6 after your change of purpose, you do not become the provider of a high-risk system. If you do put the system into service under your own name, you may be the provider of an ordinary AI system, with for example the obligations of Article 50.
Art. 25(1)(c) · Art. 3(3) · art. 50
Outcome F · Applies
As product manufacturer you are the provider
The product manufacturer is considered the provider of the high-risk system and takes on the obligations of Article 16. For systems under Annex I the requirements apply from 2 August 2028.
Art. 25(3) · art. 16 · art. 113 onder c
Outcome G · Does not apply
You do not become the provider through Article 25
You keep your own role. If you supply as a third party a system, model, tool, service, component or process used or integrated in a high-risk system, you and the provider specify in writing which information, technical access and assistance you provide (paragraph 4). That does not apply if you make tools, services, processes or components, other than general-purpose AI models, accessible to the public under a free and open-source licence.
Art. 25(4)
Related enforcement
No enforcement actions for this article yet. Follow developments via the Enforcement Tracker.
Related blog posts
Related articles
Frequently asked questions
When is someone considered a provider under Article 25 AI Act?+
What are the consequences of a role change in the AI value chain?+
What documentation does Article 25 of the AI Act require?+
Connections
What connects to Article 25 AI Act
Themes where this returns
The counterpart in the other law
GDPR interpretation that also applies here6 of 10
- Guidelines 07/2020 on the concepts of controller and processor in the GDPR
2021-07-07 · final, European Data Protection Board (EDPB) · via Who is responsible: roles in both laws
- IAB Europe: the TC String is personal data and the industry body is a joint controller
2024-03-07 · final, Hof van Justitie van de EU (Vierde kamer), IAB Europe tegen Gegevensbeschermingsautoriteit (België) · via Who is responsible: roles in both laws
- Council of State: 600,000 euro fine for wifi tracking in Enschede stays annulled
2026-07-29 · final, Raad van State, Afdeling bestuursrechtspraak · via Who is responsible: roles in both laws
- Guidelines 02/2026 on Anonymisation
2026-07-07 · under consultation, European Data Protection Board (EDPB) · via Who is responsible: roles in both laws
- EDPS v SRB: pseudonymised data are not always personal data for everyone, but the information duty applies from collection
2025-09-04 · final, Hof van Justitie van de EU (Eerste kamer), Europese Toezichthouder voor gegevensbescherming (EDPS) tegen Gemeenschappelijke Afwikkelingsraad (SRB) · via Who is responsible: roles in both laws
- Gelderland District Court: bankruptcy trustee is controller, DPA fine for unsecured hard drive cut to 58,125 euros
2025-08-07 · status not established, Rechtbank Gelderland · via Who is responsible: roles in both laws