{"id":5408,"date":"2026-09-10T08:00:00","date_gmt":"2026-09-10T06:00:00","guid":{"rendered":"https:\/\/www.lablogic.pl\/?p=5408"},"modified":"2026-10-20T18:12:21","modified_gmt":"2026-10-20T16:12:21","slug":"high-risk-ai-system","status":"publish","type":"post","link":"https:\/\/www.lablogic.pl\/en\/high-risk-ai-system\/","title":{"rendered":"Is the AI tool we use a high-risk system?"},"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 compliance teams and DPOs \u2022 published September 10, 2026 \u2022 updated October 20, 2026 \u2022 11 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 class=\"wp-block-heading\" id=\"krotka-odpowiedz\">Short answer<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Whether a given tool is a high-risk AI system is not settled by its name or by how advanced its model is. What settles it is the intended purpose given to the system by the provider, and it is the provider that carries out the classification. An organisation that modifies that intended purpose so that a high-risk AI system results becomes the provider itself. Two independent routes lead to high risk. The first is a safety component of a product covered by Annex I or such a product itself, where the product is subject to a third-party conformity assessment. The second is a use case listed in Annex III. The second route has an exit under the conditions of Article 6(3), but profiling of natural persons closes that exit without exception. A deployer of a high-risk AI system performs the obligations under Article 26 from 2 December 2027 for Annex III and from 2 August 2028 for Annex I. For systems placed on the market or put into service before those dates, Article 111(2) is decisive.<\/p>\n<\/div>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"dlaczego\">Why this question arises at all<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Regulation (EU) 2026\/1744 postponed the application of the requirements for high-risk AI systems. Sections 1\u20133 of Chapter III apply from 2 December 2027 to systems listed in Annex III and from 2 August 2028 to systems covered by Annex I. The postponement also covers the classification rules themselves, because Article 6 belongs to the first section of that chapter. For operators of high-risk AI systems placed on the market or put into service before those dates, including deployers, the Regulation applies only after a significant change in the design of those systems (Article 111(2)). The prohibitions in Article 5 apply to those systems without that limitation. In any case, for high-risk AI systems intended to be used by public authorities, providers and deployers must take the necessary steps to comply with the Regulation by 2 August 2030. It is easy to read these changes as a reason to put the subject off.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">What can be postponed is implementing the requirements, not establishing the scope. The requirements of Chapter III for which the provider is responsible range from data quality to conformity assessment. The deployer has a shorter list of obligations under Article 26, but those too require preparation. Classification therefore determines the budget and the order of work, not a deadline that is about to expire.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">One provision of Article 6 was not postponed. Paragraph 5 obliges the European Commission to issue guidelines on the practical implementation of that Article, and the deadline passed on 2 February 2026. The Commission published the draft guidelines on 19 May 2026 and closed the consultation on 23 July 2026. In October 2026 the document is still a draft, and the Commission has announced adoption of the final version by the end of 2026. An organisation that classifies its use cases today relies on the wording of the Regulation.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"co-ustalic\">What has to be established before a decision<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">High-risk AI system \u2014 two routes to classification<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The first route concerns products. A system becomes a high-risk AI system by this route when two conditions are met at the same time (Article 6(1)). The system must be intended to be used as a safety component of a product covered by the Union harmonisation legislation listed in Annex I, or be such a product itself. The second condition is that this product is required to undergo a third-party conformity assessment under that legislation. Annex I covers toys, lifts and medical devices among other products, so the first route mainly concerns manufacturers. Machinery has been moved to Section B of Annex I, and for AI systems classified as high-risk under Article 6(1) that relate to products covered by that section the Regulation applies only to a narrow extent (Article 2(2)).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The second route concerns use cases. A system listed in Annex III is, as a rule, a high-risk AI system (Article 6(2)). This route does not require any link to a product covered by Annex I. In my assessment this is the route through which most organisations outside manufacturing encounter classification, because Annex III describes mainly use cases rather than industries.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The two routes are checked separately. A manufacturer that builds an AI module into its own products and at the same time uses a tool to assess job candidates faces two independent classification questions.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">When a system is not a safety component<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Regulation 2026\/1744 added three paragraphs to Article 6 that clarify the first route. AI systems used solely for non-safety related aspects listed in the provision do not qualify as safety components (paragraph 1a). The provision lists user assistance and performance optimisation. It also lists service efficiency, automation or convenience and quality control. There is one exception to this exclusion. Where failure or malfunctioning of the system would endanger health and safety, the system remains a safety component (paragraph 1b).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The third new paragraph concerns the conformity assessment procedure. A product that is required to undergo a third-party conformity assessment solely due to risks other than risks to health and safety is not considered to fulfil the condition in Article 6(1)(b) (paragraph 1c). The provision gives the example of risks relating to the distribution of radio spectrum or electromagnetic interference that do not affect health and safety.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What Annex III describes<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Annex III lists eight areas. Two of them concern the activities of public authorities or of those acting on their behalf. These are law enforcement (area 6) and migration, asylum and border control management (area 7). Area 8 covers AI systems that assist a judicial authority in researching and interpreting facts and the law and in applying the law to a concrete set of facts. It also covers similar use in alternative dispute resolution. It further includes AI systems intended to be used for influencing the outcome of an election or referendum or the voting behaviour of natural persons in the exercise of their vote in elections or referenda. This does not include AI systems to the output of which natural persons are not directly exposed. Examples are tools used to organise, optimise or structure political campaigns from an administrative or logistical point of view. Apart from support for judicial authorities, area 8 may also concern an ordinary organisation, as may the remaining five areas.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In my assessment the area that most often affects organisations is area 4, which covers employment, workers\u2019 management and access to self-employment. It includes tools for the recruitment or selection of candidates, among them tools for placing targeted job advertisements and filtering applications. It also includes systems intended to be used to make decisions affecting the terms of work-related relationships and the promotion or termination of work-related contractual relationships. Finally, the area covers allocating tasks based on individual behaviour or personal traits or characteristics and monitoring and evaluating the performance and behaviour of workers.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Area 5 covers access to essential services, including the creditworthiness assessment of natural persons and risk assessment and pricing in relation to natural persons in life and health insurance. Area 1 concerns biometrics, area 2 safety components of critical infrastructure and area 3 education and vocational training. The creditworthiness category expressly excludes systems used for detecting financial fraud.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The Annex describes the intended purpose of a system, not a category of tool. The same tool based on a language model stays outside the Annex when it suggests the content of a letter and enters area 4 when it filters candidates&#8217; applications. If the provider did not foresee such a purpose and the system becomes a high-risk AI system because of it, the organisation giving it that purpose becomes its provider (Article 25(1)(c)).<\/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<p class=\"wp-block-paragraph\">It is the use case that is classified, not the purchased licence.<\/p>\n\n<\/div>\n\n\n\n<h3 class=\"wp-block-heading\">When the Article 6(3) derogation really applies<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The derogation requires two conditions to be met together. The first is general. The system must not pose a significant risk of harm to the health, safety or fundamental rights of natural persons. The provision adds that this includes not materially influencing the outcome of decision making. The second condition is one of the four situations listed in the provision.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>the system is intended to perform a narrow procedural task;<\/li>\n\n\n<li>the system is intended to improve the result of a previously completed human activity;<\/li>\n\n\n<li>the system is intended to detect decision-making patterns or deviations from prior decision-making patterns and is not meant to replace or influence the previously completed human assessment without proper human review;<\/li>\n\n\n<li>the system is intended to perform a preparatory task to an assessment relevant for the purposes of the use cases listed in Annex III.<\/li>\n\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Reducing this provision to the list alone leads to misclassification. A tool performing a narrow procedural task remains a high-risk AI system if it nevertheless poses a significant risk of harm.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Profiling rules out the derogation<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A system listed in Annex III that performs profiling of natural persons is always a high-risk AI system (Article 6(3), third subparagraph). The Regulation does not create its own definition of profiling. It refers to Article 4(4) GDPR, that is, to automated processing of personal data used to evaluate personal aspects relating to a natural person (Article 3(52)).<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This cross-reference has a practical effect. The record of processing activities and the data protection impact assessment often already provide material for answering the question about profiling. However, the record under Article 30 GDPR does not require profiling to be indicated, and an impact assessment is mandatory only for processing likely to result in a high risk (Article 35 GDPR). The absence of an entry therefore does not prove that there is no profiling. Comparing the list of AI use cases with these documents is a starting point, not an answer. A tool that assesses candidates or measures employee performance usually falls within area 4 of Annex III and profiles natural persons at the same time.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Who documents the assessment that a system is not a high-risk AI system<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">The obligation to document the assessment rests with the provider. A provider that considers an AI system listed in Annex III not to be high-risk documents its assessment before the system is placed on the market or put into service. It is also subject to the registration obligation under Article 49(2) and provides the documentation of the assessment at the request of national competent authorities (Article 6(4)). The deployer has no documentation obligation of its own under this provision.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Even so, it is worth recording your own classification together with its justification. It determines which obligations the organisation will have to fulfil and when preparations should start. Changing the intended purpose of an off-the-shelf tool so that it becomes a high-risk AI system also transfers the provider role to the organisation, together with the obligations under Article 16 (Article 25(1)(c)). This and the two other circumstances in Article 25(1) are covered in <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>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The classification is carried out by the provider on the basis of the intended purpose it has itself given to the system (Article 3(12)). A provider that considers an Annex III system not to be high-risk must document its assessment before placing it on the market or putting it into service (Article 6(4)). The deployer checks whether its use falls within that intended purpose. The instructions for use of a high-risk AI system contain a description of its intended purpose (Article 13(3)(b)). In the EU database the provider or, where applicable, its authorised representative registers itself and a high-risk AI system listed in Annex III outside the area of critical infrastructure. It also registers a system the provider considers not to be high-risk, together with the condition or conditions under Article 6(3) (Article 49(1) and (2) and Annex VIII). The information in the database is, as a rule, publicly available (Article 71(4)). Where the provider does not state the classification, it is worth requesting it in writing. Until a reply is received, it is worth assuming that an AI system used for a use case listed in Annex III is a high-risk AI system (Article 6(2)).<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">What classification means for the deployer<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">A deployer of a high-risk AI system has obligations under Article 26. It uses the system in accordance with the instructions for use and assigns human oversight to natural persons with the necessary competence, training and authority as well as the necessary support (paragraphs 1 and 2). It monitors the operation of the system (paragraph 5). Where it has reason to consider that the system may present a risk within the meaning of Article 79(1), it informs the provider or distributor and the market surveillance authority without undue delay and suspends the use of the system. It keeps the logs under its control for at least six months, unless the law provides otherwise (paragraph 6). An employer informs the affected workers and their representatives before putting the system into service or using it at the workplace (paragraph 7). For high-risk AI systems listed in Annex III, the deployer informs natural persons that they are subject to the use of the system where it makes or assists in making decisions related to them (paragraph 11). These obligations apply from 2 December 2027 to high-risk AI systems listed in Annex III and from 2 August 2028 to high-risk AI systems covered by Annex I.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">From 2 December 2027, the entities identified in Article 27(1) also carry out a fundamental rights impact assessment before deploying a high-risk AI system listed in Annex III outside the area of critical infrastructure. These are bodies governed by public law or private entities providing public services and deployers of high-risk AI systems used to evaluate the creditworthiness of natural persons or for risk assessment and pricing in relation to natural persons in life and health insurance.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Six questions that structure classification<\/h3>\n\n\n\n<figure class=\"wp-block-table ll-art-table\"><table class=\"has-fixed-layout\"><thead><tr><th>Question<\/th><th>What to establish<\/th><th>Where to look<\/th><\/tr><\/thead><tbody><tr><td>Is the system a safety component of a product?<\/td><td>the intended purpose of the system and the conformity assessment procedure for the product<\/td><td>Article 6(1) and (1a)\u2013(1c), Annex I<\/td><\/tr><tr><td>Does the use case fall within Annex III?<\/td><td>the intended purpose given by the provider and what the organisation actually uses the tool for<\/td><td>Article 6(2), Annex III<\/td><\/tr><tr><td>Does the derogation apply?<\/td><td>no significant risk of harm and one of the four conditions<\/td><td>Article 6(3), first and second subparagraphs<\/td><\/tr><tr><td>Does the system profile natural persons?<\/td><td>how the system works, with the record of processing activities and the impact assessment as secondary sources<\/td><td>Article 6(3), third subparagraph, in conjunction with Article 3(52)<\/td><\/tr><tr><td>Does our use change the organisation&#8217;s role?<\/td><td>the extent of modification and the purpose given to the tool<\/td><td>Article 25(1)<\/td><\/tr><tr><td>When do the requirements actually become binding?<\/td><td>the classification route and the date the system was placed on the market or put into service<\/td><td>Article 113, third paragraph, point (c) and Article 111(2)<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"bledy\">Common mistakes<\/h2>\n\n\n\n<ul class=\"wp-block-list ll-art-errors\">\n\n<li><strong>Classifying the tool instead of the use case.<\/strong> A single licence may be used in several processes, and each of them is classified separately.<\/li>\n\n\n<li><strong>Accepting the provider&#8217;s declaration without comparing it with your own use.<\/strong> The declaration describes the intended purpose given by the provider, not how the recipient actually uses the tool.<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"wnioski\">Conclusions and next steps<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Classification is today an analytical task, not an obligation with a deadline. Its outcome, however, determines how much time the organisation really has and what it will spend that time on. The order of work may look like this.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n\n<li>Compile a list of AI use cases, with a description of the process in which the tool operates and the person responsible for its use.<\/li>\n\n\n<li>For each use case, check both classification routes and record the outcome together with its justification.<\/li>\n\n\n<li>Compare the list of use cases with the record of processing activities and establish for each use case whether the system profiles natural persons.<\/li>\n\n\n<li>For use cases listed in Annex III, check whether the Article 6(3) derogation really applies and describe both conditions separately.<\/li>\n\n\n<li>Collect from providers the instructions for use describing the intended purpose and limitations of the tool, together with a written classification of the system. If the system has an entry in the EU database, compare it with the classification given by the provider.<\/li>\n\n\n<li>Plan preparations for use cases classified as high-risk, taking 2 December 2027 as the reference date for systems listed in Annex III and 2 August 2028 for systems covered by Annex I. For systems placed on the market or put into service before those dates, check the effect of Article 111(2).<\/li>\n\n\n<li>Include classification in the periodic review, because a change in how a tool is used changes the outcome. It is also worth checking classification after the Commission adopts the guidelines on Article 6, because a market surveillance authority assesses a classification under Article 6(3) on the basis of that provision and those guidelines. It does so where it has sufficient reason to consider that the system is indeed high-risk (Article 80(1)).<\/li>\n\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"materialy-powiazane\">Related materials<\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n\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 three circumstances in which the obligations of a provider pass together with the role<\/li>\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 of use cases with which classification begins<\/li>\n\n\n<li><strong><a href=\"https:\/\/www.lablogic.pl\/en\/who-is-responsible-for-ai-act-transparency-obligations\/\">Who is responsible for AI Act transparency obligations?<\/a><\/strong> \u2014 obligations that apply regardless of the risk level<\/li>\n\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"zrodla\">Sources<\/h2>\n\n\n\n<ul class=\"wp-block-list ll-art-sources\">\n\n<li>Regulation (EU) 2024\/1689 of the European Parliament and of the Council (Artificial Intelligence Act), consolidated text as at 27 July 2026, Article 2(2), Article 3(8), (12) and (52), Articles 5 and 6, Article 13(3), Articles 16, 25, 26 and 27, Article 49(1) and (2), Article 71(4), Article 79(1), Article 80(1), Articles 111 and 113 and Annexes I, III and VIII \u2014 EUR-Lex: <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<li>Regulation (EU) 2026\/1744 of the European Parliament and of the Council of 8 July 2026 (digital omnibus on AI), Article 1 as regards the amendments to Articles 2, 6, 111 and 113 and Annex I to Regulation (EU) 2024\/1689 \u2014 EUR-Lex: <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<li>Regulation (EU) 2016\/679 of the European Parliament and of the Council (GDPR), Article 4(4), Article 30 and Article 35 \u2014 EUR-Lex: <a href=\"https:\/\/eur-lex.europa.eu\/legal-content\/EN\/TXT\/?uri=CELEX:32016R0679\" target=\"_blank\" rel=\"noreferrer noopener\">eur-lex.europa.eu<\/a><\/li>\n\n\n<li>European Commission, draft guidelines on the classification of high-risk AI systems, published 19 May 2026, consultation closed 23 July 2026 \u2014 the document remains a draft \u2014 European Commission: <a href=\"https:\/\/digital-strategy.ec.europa.eu\/en\/library\/draft-commission-guidelines-classification-high-risk-ai-systems\" target=\"_blank\" rel=\"noreferrer noopener\">digital-strategy.ec.europa.eu<\/a><\/li>\n\n\n<li>European Commission, targeted consultation on the draft guidelines on the classification of high-risk AI systems \u2014 deadline extended to 23 July 2026, adoption of the guidelines announced by the end of 2026 \u2014 European Commission: <a href=\"https:\/\/digital-strategy.ec.europa.eu\/en\/consultations\/targeted-consultation-draft-guidelines-classification-high-risk-artificial-intelligence-systems\" target=\"_blank\" rel=\"noreferrer noopener\">digital-strategy.ec.europa.eu<\/a><\/li>\n\n<\/ul>\n\n\n\n<div class=\"wp-block-group ll-art-cta is-layout-constrained wp-block-group-is-layout-constrained\">\n\n<h2 class=\"wp-block-heading ll-nietoc\">Find out which AI use cases will require the most work<\/h2>\n\n\n<p class=\"wp-block-paragraph\">Classification determines the scope of preparations and which tools need attention now. AI use case review covers compiling the list of use cases, establishing the organisation&#8217;s role and classifying each of them with a justification.<\/p>\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\/\">AI use case review<\/a><\/div>\n<\/div>\n\n<\/div>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>Whether a tool is a high-risk AI system is settled by its intended purpose and the way it is used, not by the product name. Two routes in Article 6 AI Act lead to high risk, and profiling of natural persons closes the derogation for Annex III use cases.<\/p>\n","protected":false},"author":2,"featured_media":5556,"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":"","footnotes":""},"categories":[83],"tags":[],"class_list":["post-5408","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.4 - aioseo.com -->\n\t<meta name=\"description\" content=\"Whether a tool is a high-risk AI system depends on its intended purpose and use. Two routes under Article 6 AI Act, the derogation conditions and profiling.\" \/>\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\/high-risk-ai-system\/\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.4\" \/>\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=\"What gets classified is the use case, not the licence\" \/>\n\t\t<meta property=\"og:description\" content=\"Two classification routes, two derogation conditions and the clause that closes them.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/www.lablogic.pl\/en\/high-risk-ai-system\/\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/09\/ll-og-high-risk-ai-system-en-1.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/09\/ll-og-high-risk-ai-system-en-1.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=\"high-risk system\" \/>\n\t\t<meta property=\"article:tag\" content=\"annex iii\" \/>\n\t\t<meta property=\"article:tag\" content=\"compliance\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2026-09-10T06:00:00+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2026-10-20T16:12:21+00:00\" \/>\n\t\t<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n\t\t<meta name=\"twitter:title\" content=\"What gets classified is the use case, not the licence\" \/>\n\t\t<meta name=\"twitter:description\" content=\"Two classification routes, two derogation conditions and the clause that closes them.\" \/>\n\t\t<meta name=\"twitter:image\" content=\"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/09\/ll-og-high-risk-ai-system-en-1.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\\\/high-risk-ai-system\\\/#article\",\"name\":\"High-risk AI system \\u2014 how to establish classification\",\"headline\":\"Is the AI tool we use a high-risk system?\",\"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-high-risk-ai-system-en-1.jpg\",\"width\":1200,\"height\":630,\"caption\":\"Classify the use case, not the licence \\u2014 LabLogic article graphic by Micha\\u0142 Rutkowski\"},\"datePublished\":\"2026-09-10T08:00:00+02:00\",\"dateModified\":\"2026-10-20T18:12:21+02:00\",\"inLanguage\":\"en-US\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/high-risk-ai-system\\\/#webpage\"},\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/high-risk-ai-system\\\/#webpage\"},\"articleSection\":\"AI Act\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/high-risk-ai-system\\\/#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\\\/high-risk-ai-system\\\/#listItem\",\"name\":\"Is the AI tool we use a high-risk system?\"},\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/#listItem\",\"name\":\"LabLogic\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/high-risk-ai-system\\\/#listItem\",\"position\":3,\"name\":\"Is the AI tool we use a high-risk system?\",\"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\":\"DPO, GDPR, NIS2 and cybersecurity in practice\",\"url\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/\",\"email\":\"m.rutkowski@lablogic.pl\",\"telephone\":\"+48586231777\",\"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\\\/high-risk-ai-system\\\/#organizationLogo\",\"width\":512,\"height\":512},\"image\":{\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/high-risk-ai-system\\\/#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\\\/high-risk-ai-system\\\/#webpage\",\"url\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/high-risk-ai-system\\\/\",\"name\":\"High-risk AI system \\u2014 how to establish classification\",\"description\":\"Whether a tool is a high-risk AI system depends on its intended purpose and use. Two routes under Article 6 AI Act, the derogation conditions and profiling.\",\"inLanguage\":\"en-US\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/#website\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/high-risk-ai-system\\\/#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-high-risk-ai-system-en-1.jpg\",\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/high-risk-ai-system\\\/#mainImage\",\"width\":1200,\"height\":630,\"caption\":\"Classify the use case, not the licence \\u2014 LabLogic article graphic by Micha\\u0142 Rutkowski\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/www.lablogic.pl\\\/en\\\/high-risk-ai-system\\\/#mainImage\"},\"datePublished\":\"2026-09-10T08:00:00+02:00\",\"dateModified\":\"2026-10-20T18:12:21+02: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":"High-risk AI system \u2014 how to establish classification","description":"Whether a tool is a high-risk AI system depends on its intended purpose and use. Two routes under Article 6 AI Act, the derogation conditions and profiling.","canonical_url":"https:\/\/www.lablogic.pl\/en\/high-risk-ai-system\/","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.lablogic.pl\/en\/high-risk-ai-system\/#article","name":"High-risk AI system \u2014 how to establish classification","headline":"Is the AI tool we use a high-risk system?","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-high-risk-ai-system-en-1.jpg","width":1200,"height":630,"caption":"Classify the use case, not the licence \u2014 LabLogic article graphic by Micha\u0142 Rutkowski"},"datePublished":"2026-09-10T08:00:00+02:00","dateModified":"2026-10-20T18:12:21+02:00","inLanguage":"en-US","mainEntityOfPage":{"@id":"https:\/\/www.lablogic.pl\/en\/high-risk-ai-system\/#webpage"},"isPartOf":{"@id":"https:\/\/www.lablogic.pl\/en\/high-risk-ai-system\/#webpage"},"articleSection":"AI Act"},{"@type":"BreadcrumbList","@id":"https:\/\/www.lablogic.pl\/en\/high-risk-ai-system\/#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\/high-risk-ai-system\/#listItem","name":"Is the AI tool we use a high-risk system?"},"previousItem":{"@type":"ListItem","@id":"https:\/\/www.lablogic.pl\/en\/#listItem","name":"LabLogic"}},{"@type":"ListItem","@id":"https:\/\/www.lablogic.pl\/en\/high-risk-ai-system\/#listItem","position":3,"name":"Is the AI tool we use a high-risk system?","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":"DPO, GDPR, NIS2 and cybersecurity in practice","url":"https:\/\/www.lablogic.pl\/en\/","email":"m.rutkowski@lablogic.pl","telephone":"+48586231777","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\/high-risk-ai-system\/#organizationLogo","width":512,"height":512},"image":{"@id":"https:\/\/www.lablogic.pl\/en\/high-risk-ai-system\/#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\/high-risk-ai-system\/#webpage","url":"https:\/\/www.lablogic.pl\/en\/high-risk-ai-system\/","name":"High-risk AI system \u2014 how to establish classification","description":"Whether a tool is a high-risk AI system depends on its intended purpose and use. Two routes under Article 6 AI Act, the derogation conditions and profiling.","inLanguage":"en-US","isPartOf":{"@id":"https:\/\/www.lablogic.pl\/en\/#website"},"breadcrumb":{"@id":"https:\/\/www.lablogic.pl\/en\/high-risk-ai-system\/#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-high-risk-ai-system-en-1.jpg","@id":"https:\/\/www.lablogic.pl\/en\/high-risk-ai-system\/#mainImage","width":1200,"height":630,"caption":"Classify the use case, not the licence \u2014 LabLogic article graphic by Micha\u0142 Rutkowski"},"primaryImageOfPage":{"@id":"https:\/\/www.lablogic.pl\/en\/high-risk-ai-system\/#mainImage"},"datePublished":"2026-09-10T08:00:00+02:00","dateModified":"2026-10-20T18:12:21+02: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":"What gets classified is the use case, not the licence","og:description":"Two classification routes, two derogation conditions and the clause that closes them.","og:url":"https:\/\/www.lablogic.pl\/en\/high-risk-ai-system\/","og:image":"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/09\/ll-og-high-risk-ai-system-en-1.jpg","og:image:secure_url":"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/09\/ll-og-high-risk-ai-system-en-1.jpg","og:image:width":1200,"og:image:height":630,"article:section":"AI Act","article:tag":["ai act","high-risk system","annex iii","compliance"],"article:published_time":"2026-09-10T06:00:00+00:00","article:modified_time":"2026-10-20T16:12:21+00:00","twitter:card":"summary_large_image","twitter:title":"What gets classified is the use case, not the licence","twitter:description":"Two classification routes, two derogation conditions and the clause that closes them.","twitter:image":"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/09\/ll-og-high-risk-ai-system-en-1.jpg"},"aioseo_meta_data":{"post_id":"5408","title":"High-risk AI system \u2014 how to establish classification","description":"Whether a tool is a high-risk AI system depends on its intended purpose and use. Two routes under Article 6 AI Act, the derogation conditions and profiling.","keywords":null,"keyphrases":{"focus":{"keyphrase":"high-risk AI system","score":0},"additional":[{"keyphrase":"AI system classification","score":69},{"keyphrase":"Annex III AI Act","score":69},{"keyphrase":"Article 6 AI Act","score":69},{"keyphrase":"high-risk derogation","score":69}]},"primary_term":null,"canonical_url":null,"og_title":"What gets classified is the use case, not the licence","og_description":"Two classification routes, two derogation conditions and the clause that closes them.","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":"high-risk system","value":"high-risk system"},{"label":"Annex III","value":"Annex III"},{"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":0,"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-09-10 19:36:20","updated":"2026-10-20 16:12:56","seo_analyzer_scan_date":null,"focus_keyword":"high-risk AI system","additional_keywords":[{"items":{"functionWordsInKeyphrase":{"score":9},"imageKeyphrase":{"score":3},"introductionKeyword":{"score":3},"keyphraseDensity":{"score":4},"keyphraseLength":{"score":9},"textCompetingLinks":{"score":9}},"score":69,"word":"AI system classification"},{"items":{"functionWordsInKeyphrase":{"score":9},"imageKeyphrase":{"score":3},"introductionKeyword":{"score":3},"keyphraseDensity":{"score":4},"keyphraseLength":{"score":9},"textCompetingLinks":{"score":9}},"score":69,"word":"Annex III AI Act"},{"items":{"functionWordsInKeyphrase":{"score":9},"imageKeyphrase":{"score":3},"introductionKeyword":{"score":3},"keyphraseDensity":{"score":4},"keyphraseLength":{"score":9},"textCompetingLinks":{"score":9}},"score":69,"word":"Article 6 AI Act"},{"items":{"functionWordsInKeyphrase":{"score":9},"imageKeyphrase":{"score":3},"introductionKeyword":{"score":3},"keyphraseDensity":{"score":4},"keyphraseLength":{"score":9},"textCompetingLinks":{"score":9}},"score":69,"word":"high-risk derogation"}],"truseo_locale":null},"spectra_blocks_featured_image_url":{"thumbnail":{"url":"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/09\/ll-og-high-risk-ai-system-en-1-150x150.jpg","width":150,"height":150},"medium":{"url":"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/09\/ll-og-high-risk-ai-system-en-1-300x158.jpg","width":300,"height":158},"medium_large":{"url":"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/09\/ll-og-high-risk-ai-system-en-1-768x403.jpg","width":768,"height":403},"large":{"url":"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/09\/ll-og-high-risk-ai-system-en-1-1024x538.jpg","width":1024,"height":538},"full":{"url":"https:\/\/www.lablogic.pl\/wp-content\/uploads\/2026\/09\/ll-og-high-risk-ai-system-en-1.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\/5408","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=5408"}],"version-history":[{"count":6,"href":"https:\/\/www.lablogic.pl\/en\/wp-json\/wp\/v2\/posts\/5408\/revisions"}],"predecessor-version":[{"id":6052,"href":"https:\/\/www.lablogic.pl\/en\/wp-json\/wp\/v2\/posts\/5408\/revisions\/6052"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.lablogic.pl\/en\/wp-json\/wp\/v2\/media\/5556"}],"wp:attachment":[{"href":"https:\/\/www.lablogic.pl\/en\/wp-json\/wp\/v2\/media?parent=5408"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.lablogic.pl\/en\/wp-json\/wp\/v2\/categories?post=5408"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.lablogic.pl\/en\/wp-json\/wp\/v2\/tags?post=5408"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}