Skip to main content
Praxikon

What may the regulator do? Market surveillance, fundamental rights authorities, confidentiality and complaints under Articles 74, 77, 78 and 85 of the AI Act

··35 min read

Anyone who builds or uses a high-risk AI system will sooner or later receive a letter from a regulator. Four Articles determine what that letter may ask for. Article 74 governs who carries out market surveillance and with which powers, up to the training data and the source code. Article 77 gives authorities that protect fundamental rights, such as an equality body, access to documentation and a right to have a system tested. Article 78 lays down how all those authorities handle the information they obtain. And Article 85 gives everyone the right to lodge a complaint.

Suppose it is spring 2028. A Dutch municipality uses a system that gives every application for social assistance a score for the likelihood that a review is needed; a caseworker decides. The supplier placed the system on the market in January 2028. A resident whose application took longer after a high score lodges a complaint with the market surveillance authority. A month later the municipality receives a letter: the authority asks for the logs, the work instructions for caseworkers and the fundamental rights impact assessment, and says that the Netherlands Institute for Human Rights (College voor de Rechten van de Mens) has also asked for documents. The municipality's privacy officer wants to know what it must provide, what it may refuse and what happens to the documents. The example is fictitious.

In short

Regulation (EU) 2019/1020 on market surveillance applies to AI systems; every operator, including a deployer, counts as an economic operator for that purpose (Article 74(1)). The market surveillance authority can therefore request documents and information, inspect, and obtain a system, including under a cover identity, and exercise some powers remotely (paragraph 5). Providers of high-risk AI systems give it full access to the documentation and to the training, validation and testing data sets, in so far as needed (paragraph 12). The source code only on a reasoned request, where it is necessary to assess conformity with Chapter III, Section 2, and testing or auditing based on the provider's data has been exhausted or proved insufficient (paragraph 13). For high-risk AI systems of financial institutions, in so far as the use is directly connected with the financial service, the financial supervisor is the market surveillance authority (paragraph 6). Since the Digital Omnibus on AI, authorities protecting fundamental rights request information and documentation from the market surveillance authority, which grants them access and, where necessary, obtains the documents from the provider or deployer without undue delay; they can also ask for the system to be tested (Article 77). All authorities involved keep the information confidential, request only what is strictly necessary and delete it when it is no longer needed (Article 78). Anyone who considers that the AI Act has been infringed can lodge a complaint with the relevant market surveillance authority (Article 85). Articles 74, 77 and 85 have applied since 2 August 2026, Article 78 since 2 August 2025. The Netherlands has not yet designated its market surveillance authorities by law; the fundamental rights authorities are on a provisional list of 19 November 2024.

This piece is about the powers and what you do with them. What happens when the authority considers that a system presents a risk is covered in Articles 79 to 82. When the AI Office in Brussels is the supervisor is explained in the EU AI Office. A resident's right to an explanation of a decision is covered in Article 86. For an overview of supervision in the Netherlands, see who will supervise the AI Act in the Netherlands.

Who is the market surveillance authority?

A market surveillance authority is the national authority carrying out the activities and taking the measures under Regulation (EU) 2019/1020 (Article 3, point 26). As a rule the Member State designates it (Article 70(1)). For some cases Article 74 itself designates the authority or fixes the choice:

SituationMarket surveillance authority under the AI ActParagraph
High-risk AI systems related to products under Annex I, Section AThe authority responsible for market surveillance under that product legislation; in appropriate circumstances the Member State may designate another, with coordination3
High-risk AI systems of financial institutions, in so far as the use is directly connected with the financial serviceThe national authority responsible for the financial supervision of those institutions; in justified circumstances the Member State may designate another, with coordination6 and 7
Annex III, point 1 (biometrics) used for law enforcement, border management, justice and democracy, and Annex III, points 6, 7 and 8The data protection supervisory authority under Regulation (EU) 2016/679 or Directive (EU) 2016/680, or another authority designated under the same conditions laid down in Articles 41 to 44 of that Directive8
Union institutions, bodies, offices and agenciesThe European Data Protection Supervisor, except in relation to the Court of Justice acting in its judicial capacity9
All other cases, such as Annex III, point 5(a) (public assistance benefits and services)The authority the Member State designatesArticle 70(1)

Two details go with paragraphs 7 and 8. A banking supervisor participating in the Single Supervisory Mechanism reports to the European Central Bank without delay any information from its market surveillance that may be of potential interest for the ECB's prudential supervisory tasks (paragraph 7, second subparagraph). And market surveillance must in no way affect the independence of judicial authorities when they act in their judicial capacity (paragraph 8, last sentence). The AI Office has exclusive competence for AI systems based on a general-purpose AI model of the same provider or undertaking, with exceptions that apply only to those systems, including financial institutions under paragraph 6, and for AI systems that constitute or are integrated into a very large online platform or a very large online search engine. That exclusive competence applies to the providers of those systems, and to deployers only where they are also the provider or belong to the same undertaking (Article 75(1)).

In the Netherlands. No market surveillance authority has yet been designated by law. The draft bill for the Dutch AI Act Implementation Act (Uitvoeringswet AI-verordening) was in public consultation until 1 June 2026; submission to the House of Representatives is planned for the second quarter of 2027 (Parliamentary Paper 26643, no. 1554). For high-risk systems under Annex III the draft designates, among others: the Dutch Data Protection Authority (Autoriteit Persoonsgegevens, AP) for Annex III, points 1, 3, 4, 5(a) and (d), 6, 7 and 8(b); the Dutch Authority for the Financial Markets (AFM), De Nederlandsche Bank (DNB) and the AP for point 5(b) and (c), with a ministerial regulation delimiting the categories of operators for each supervisor; and for AI systems of the judiciary the Procurator General at the Supreme Court or the President of the Administrative Jurisdiction Division of the Council of State (Article 2.2(1)(c) and (2) of the draft). According to the draft explanatory memorandum, the AFM and DNB become the supervisor for the financial institutions they already supervise, and the AP for providers and deployers that are not financial institutions. This is a draft and not yet law. Until the Implementation Act applies, only the AI Act itself designates an authority (paragraphs 3, 6 and 9), but the national powers and rules on fines are missing; for paragraph 6 the AI Act moreover does not determine whether that is the AFM or DNB. Recital 158 speaks of the financial supervisors "within their respective competences".

Article 74: what the market surveillance authority may do

The powers of Regulation (EU) 2019/1020. Article 74(1) makes that Regulation apply to AI systems. References to an economic operator are read as references to all operators identified in Article 2(1), and references to a product as references to all AI systems within scope. An operator is a provider, product manufacturer, deployer, authorised representative, importer or distributor (Article 3, point 8). Article 14(4) of Regulation (EU) 2019/1020 lists the minimum powers the Member State must confer on its market surveillance authority (Article 14(1) of that Regulation): requiring economic operators to provide relevant documents, technical specifications, data or information on compliance and technical aspects (point (a)), carrying out unannounced on-site inspections and physical checks (point (d)), entering premises (point (e)), starting investigations on its own initiative (point (f)) and acquiring product samples, including under a cover identity, and inspecting them (point (j)). In the Netherlands the draft Implementation Act provides for this in Articles 3.1 to 3.3, alongside the powers in the General Administrative Law Act. A municipality using a system is therefore covered as well, not only the supplier.

Remotely. The authority may also exercise the powers in points (d) and (j), the inspections and acquiring samples, remotely (Article 74(5)). For a system running in the cloud, that is expected to be a common route.

Full access to documentation and data sets. Providers grant the market surveillance authority full access to the documentation and to the training, validation and testing data sets used for the development of high-risk AI systems, including, where appropriate and subject to security safeguards, through application programming interfaces (APIs) or other technical means and tools enabling remote access (paragraph 12). Three limits are in the text itself: the duty rests on the provider, it applies only to high-risk systems, and access is given "where relevant and limited to what is necessary" for the authority's tasks. According to the Dutch draft explanatory memorandum, that access may where appropriate include personal data, including special categories and criminal offence data (section 4.5.2.1). In addition, on a reasoned request the provider supplies all information and documentation necessary to demonstrate conformity with Section 2, and access to the logs under its control (Article 21(1) and (2)).

The source code. The authority is granted access to the source code only on a reasoned request and only when both conditions are fulfilled (paragraph 13):

  1. access to the source code is necessary to assess the conformity of the system with the requirements of Chapter III, Section 2; and
  2. the testing or auditing procedures and verifications based on the data and documentation provided by the provider have been exhausted or proved insufficient.

The source code is therefore the last step, not the first. A provider that keeps its documentation, data sets and test access in order makes it, in our reading, hard to meet the second condition.

The rest of Article 74. Authorities report annually to the Commission and the national competition authorities on information that may be of interest for competition law, and to the Commission on the use of prohibited practices and the measures taken (paragraph 2). The procedures in Articles 79 to 83 do not apply to products under Annex I, Section A, where the product legislation already provides for equivalent procedures (paragraph 4). Member States facilitate coordination between the AI Act authorities and other relevant authorities (paragraph 10). Authorities and the Commission may propose joint activities and investigations for high-risk systems found to present a serious risk across two or more Member States, with the AI Office providing coordination support (paragraph 11). And everything the authority obtains is subject to Article 78 (paragraph 14).

PowerTowards whomSource
Request documents, specifications, data and informationEvery operator, including the deployerArticle 74(1); Article 14(4)(a) of Regulation (EU) 2019/1020
Inspections and samples, also remotely and under a cover identityEvery operatorArticle 74(5); Article 14(4)(d) and (j) of Regulation (EU) 2019/1020
Full access to documentation and data sets, including through an APIProvider of a high-risk systemArticle 74(12)
Information, documentation and logs on requestProvider of a high-risk systemArticle 21
Source code, under two conditionsProvider of a high-risk systemArticle 74(13)
Cooperation with measuresDeployer of a high-risk systemArticle 26(12)

Anyone who supplies incorrect, incomplete or misleading information to a national competent authority in reply to a request risks a fine of up to EUR 7.5 million or, for an undertaking, 1 percent of worldwide annual turnover if higher (Article 99(5)); for SMEs and, since the Digital Omnibus on AI, small mid-cap enterprises the lower of the two applies (Article 99(6) and (6a)). Whether a public body can be fined is for the Member State to decide (Article 99(8)); according to the draft explanatory memorandum, the Dutch draft does not exclude it.

Article 77: authorities protecting fundamental rights

Who they are. These are national public authorities or bodies which supervise or enforce the respect of obligations under Union law protecting fundamental rights, including the right to non-discrimination (Article 77(1)). Each Member State had to identify them by 2 November 2024, make the list publicly available and keep it up to date (paragraph 2). As fundamental rights authorities they are not market surveillance authorities: they supervise their own legislation, and the AI Act gives them access to what is recorded under the AI Act. Recital 157 says the Regulation is without prejudice to their competences, tasks, powers and independence, and mentions equality bodies and data protection authorities as examples.

The Dutch list. On 19 November 2024 the Netherlands adopted a provisional list (in Dutch):

  • for fundamental rights in the broad sense: the Netherlands Institute for Human Rights, as national human rights institution and as equality body;
  • for data protection law (GDPR and Directive (EU) 2016/680): the AP;
  • for supervision in the exercise of judicial tasks: the Procurator General at the Supreme Court, the President of the Administrative Jurisdiction Division of the Council of State, and the court boards of the Central Appeals Tribunal and the Trade and Industry Appeals Tribunal.

According to the letter to parliament of the same day (Parliamentary Paper 22112, no. 3979, in Dutch), the list is a "living document" and further research is being done into whether other authorities should be added. We did not find a later version on 19 November 2026. The draft Implementation Act makes the Minister of the Interior and Kingdom Relations responsible for the list (Article 2.4 of the draft). If the draft becomes law, the AP will therefore have two roles: fundamental rights authority and, for public benefits and biometrics among other areas, market surveillance authority.

What they may do. Since the Digital Omnibus on AI, Article 77 reads:

  • Request through the market surveillance authority. The authorities have the power to request and access, electronically, information or documentation created or maintained under the AI Act, in accessible language and machine-readable format, from the relevant market surveillance authority, where access is necessary for effectively fulfilling their mandates within the limits of their jurisdiction (paragraph 1).
  • The market surveillance authority grants access. It gives the authority access, including, where necessary, by requesting the documents from the provider or deployer without undue delay (paragraph 1a).
  • Cooperation. Both cooperate closely and provide each other with mutual assistance, including by exchanging information (paragraph 1b).
  • Testing. Where the documentation is insufficient to ascertain whether fundamental rights have been infringed, the authority may make a reasoned request to the market surveillance authority to organise testing of the high-risk system through technical means. The market surveillance authority organises the testing within a reasonable time, with the close involvement of the requesting authority (paragraph 3).
  • Confidential. What the authority obtains this way is subject to Article 78 (paragraph 4).

These authorities also play a role in other procedures. After a notification of a serious incident involving an infringement of fundamental rights, the market surveillance authority informs them (Article 73(7)). Where it identifies risks to fundamental rights in a system presenting a risk, it informs them and cooperates fully with them (Article 79(2)). And before acting against a system that complies with the Regulation but still presents a risk, it consults them (Article 82(1)).

Article 78: confidentiality

The Commission, market surveillance authorities, notified bodies and any other natural or legal person involved in the application of the AI Act respect the confidentiality of information and data obtained in carrying out their tasks, in particular to protect (Article 78(1)):

  • intellectual property rights, confidential business information and trade secrets, including source code, except in the cases referred to in Article 5 of Directive (EU) 2016/943 (point (a));
  • the effective implementation of the Regulation, in particular for inspections, investigations or audits (point (b));
  • public and national security interests (point (c));
  • the conduct of criminal or administrative proceedings (point (d));
  • classified information (point (e)).

For anyone who has to supply documents, paragraph 2 matters most. The authorities request only data that is strictly necessary for assessing the risk posed by AI systems and for exercising their powers, put in place adequate and effective cybersecurity measures, and delete the data collected as soon as it is no longer needed for the purpose for which it was obtained. In our reading this is a test of its own next to the GDPR: a request for business data without any personal data must also be strictly necessary.

Paragraph 3 contains the rules for law enforcement, border control, immigration and asylum. Information exchanged on a confidential basis between competent authorities is not disclosed without prior consultation of the originating authority and the deployer, where high-risk systems in Annex III, point 1, 6 or 7 are used by those services and disclosure would jeopardise public and national security interests. Where law enforcement, immigration or asylum authorities are themselves the provider of such a system, the technical documentation referred to in Annex IV remains within their premises. They ensure that the market surveillance authority referred to in Article 74(8) and (9) can, upon request, immediately access the documentation or obtain a copy, and only staff of the market surveillance authority holding the appropriate level of security clearance may access it. Paragraph 4 leaves the exchange of information and warnings between authorities and duties under criminal law unaffected, and paragraph 5 allows exchanges with regulators of third countries where a confidentiality arrangement is in place. Recital 167 explains the purpose: trustful and constructive cooperation between authorities.

In our reading, Article 78 is not a ground for refusal for the provider or deployer. It limits what the authorities ask for and what they do with the documents; a trade secret is no reason to withhold documentation or data sets. What does help is indicating, when you supply documents, which parts contain confidential business information or trade secrets, so the authority knows what it must protect under paragraph 1(a).

Article 85: the right to lodge a complaint

Without prejudice to other administrative or judicial remedies, any natural or legal person having grounds to consider that there has been an infringement of the AI Act may submit a complaint to the relevant market surveillance authority. In accordance with Regulation (EU) 2019/1020, such complaints are taken into account for conducting market surveillance activities and are handled in line with the dedicated procedures established by the market surveillance authorities (Article 85). That Regulation requires authorities to establish such procedures and to take complaints into account when deciding which checks to carry out (Article 11(3) and (7)(a) of Regulation (EU) 2019/1020). Recital 170 speaks of a "reasoned" complaint.

The right is broad and at the same time thin. Broad, because anyone can complain: a resident, an advocacy group, a competitor or a trade union, and not only someone whose personal data has been processed. Thin, because the AI Act gives the complainant no right to an investigation, to an outcome or to feedback. That differs from a complaint under the GDPR:

Article 85 AI ActArticle 77 GDPR
WhoAny natural or legal personThe data subject whose personal data is processed
About whatAny alleged infringement of the AI ActProcessing of one's own personal data that infringes the GDPR
With whomThe relevant market surveillance authorityA supervisory authority, such as the AP
What the complainant gets backThe AI Act provides for no feedback; the complaint feeds into market surveillanceInformation on progress and outcome, and a judicial remedy against the supervisory authority (Article 77(2) and Article 78 GDPR)

How it works in the Netherlands. According to the draft explanatory memorandum, Article 85 has direct effect and needs no implementing rule. A complaint under Article 85 is something other than a complaint within the meaning of the Dutch General Administrative Law Act (Algemene wet bestuursrecht), which concerns the conduct of an administrative body. Depending on its content, the complaint can however be a request for enforcement, if it is specific enough and the complainant is an interested party; there is then a principle duty to enforce with remedial sanctions, the authority's written response is a decision, and objection and appeal are available (section 4.5.5.2 of the draft memorandum). For complaints about AI in the judiciary, the draft proposes a separate route through the Procurator General at the Supreme Court (Article 8.7 of the draft). This, too, is a draft and not yet law. Who the relevant market surveillance authority is in the Netherlands is therefore not yet settled, except in the cases where the AI Act designates it itself.

What the Digital Omnibus on AI changed

Regulation (EU) 2026/1744, in force since 27 July 2026, amended only Article 77 of these four Articles (Article 1, point 34). Articles 74, 78 and 85 appear in the consolidated text of 27 July 2026 as original text. The amendment to Article 77:

  • The title became "Powers of authorities protecting fundamental rights and cooperation with market surveillance authorities".
  • The route. In the original text the authority requested the documentation itself and informed the market surveillance authority. Now the request goes through the market surveillance authority, which grants access and, where necessary, obtains the documents without undue delay (paragraphs 1 and 1a).
  • The scope. The original text limited the circle of authorities to those supervising the use of high-risk AI systems referred to in Annex III, and spoke of "documentation". That limitation was removed; more authorities therefore fall under Article 77. The new text speaks of information or documentation created or maintained under the Regulation, and adds that it must be electronic and machine-readable. In our reading the authorities can therefore also request documents about other systems, such as the documentation of a provider that did not classify its system as high-risk under Article 6(3). The testing request in paragraph 3 remains limited to high-risk systems.
  • Cooperation in both directions became a duty (paragraph 1b).

According to recital 36 of the Omnibus, Article 77 does not limit the powers these authorities have under other Union or national law: on the basis of their own mandate they can still request information directly from operators. For the AP that means: under the GDPR it can order a controller itself to provide information (Article 58(1)(a) GDPR); the route through the market surveillance authority is for what has been recorded under the AI Act.

One other amendment affects Articles 74 and 85 indirectly. For the systems within its exclusive competence, the AI Office can exercise the powers in Article 74(12) and (13) by simple request or by decision, and can act on a complaint under Article 85 (Article 75a(2) and (3), inserted by Article 1, point 32).

Main example: the municipality, the letter and the complaint

The roles. The system helps assess whether someone qualifies for social assistance; that falls under Annex III, point 5(a). Because it gives every applicant a score, it is profiling in our reading, and the system is then always high-risk (last subparagraph of Article 6(3)). The supplier is the provider, the municipality the deployer. Because the system was placed on the market in January 2028, the high-risk requirements apply in full. For point 5(a) the AI Act itself designates no authority; in the Dutch draft it is the AP.

What the municipality must provide. The duties in Article 74(12) and (13) rest on the supplier, not on the municipality. The municipality must still cooperate. The authority can require it, as an operator, to provide documents and information (Article 74(1) with Article 14(4)(a) of Regulation (EU) 2019/1020), and as a deployer it cooperates with the authority's measures (Article 26(12)). The documents requested are in its hands: the logs it keeps (Article 26(6)), the work instructions for caseworkers, and the fundamental rights impact assessment, whose results it already had to notify to the market surveillance authority (Article 27(3)). In our reading the DPIA is also a document the authority will want to see, even though it was drawn up under the GDPR and not under the AI Act.

What the municipality may ask. In our reading, faced with a broad request the municipality may ask what purpose and which provision it serves, and propose to supply the logs first in pseudonymised form or as a sample where that is enough for the assessment; Article 78(2) requires the authority to request only strictly necessary data. Refusing because the documents contain personal data is not possible in our reading: the authority may process that data in so far as necessary, and according to the Dutch draft memorandum the processing of special categories of personal data is justified on the basis of Article 9(2)(g) GDPR (section 4.5.2.1). Article 78(2) binds the authority, however, not the municipality, and with a complaint from an identifiable resident pseudonymised logs will often not be enough. If the authority maintains the full request, the municipality supplies in time and in full; delay or incomplete supply risks the fine in Article 99(5). The legal basis for that supply is the legal obligation (Article 6(1)(c) GDPR), for special categories of personal data together with Article 9(2)(g) GDPR. The municipality records what it supplied, to whom and why, and marks confidential parts, such as the supplier's technical information.

The request from the Netherlands Institute for Human Rights. The Institute is on the Dutch list as a fundamental rights authority. It can request the documents created under the AI Act through the market surveillance authority, which obtains them from the municipality or the supplier without undue delay where necessary (Article 77(1) and (1a)). It can also itself demand from the municipality the information and documents it reasonably needs for its task, and everyone must provide them completely and truthfully (Article 6 of the Netherlands Institute for Human Rights Act (Wet College voor de rechten van de mens)); the second sentence of Article 77(1) and recital 36 of the Omnibus leave that power of its own intact. The municipality can therefore receive the question by either route. In addition, when the authority evaluates a system presenting a risk, the municipality cooperates as necessary with the market surveillance authority and with the fundamental rights authorities (Article 79(2)). If the documents prove insufficient to establish whether applicants with irregular incomes are disadvantaged, the Institute can ask the authority to have the system tested (Article 77(3)). What the Institute obtains through Article 77, it handles in accordance with Article 78 (Article 77(4)).

The resident's complaint. In our reading the resident has four routes, which run side by side:

  1. A complaint to the market surveillance authority (Article 85). It can prompt an evaluation under Article 79. Whether the resident receives a decision open to objection and appeal depends, in the Netherlands, on whether the complaint counts as a request for enforcement; that is in the draft memorandum and not yet law.
  2. A complaint to the AP under the GDPR (Article 77 GDPR), if he considers that the processing of his personal data infringes the GDPR. The AP already has that competence.
  3. An explanation of the decision under Article 86, if the decision is based on the system's output; see the right to explanation.
  4. Objection and appeal against the decision itself under the General Administrative Law Act. Article 85 expressly leaves those remedies unaffected.

In our reading the municipality does well to set up its own desk where such signals arrive first. If a substantiated complaint reaches it and it recognises the risk, it informs the supplier and the market surveillance authority and suspends use (Article 26(5)); see Articles 79 to 82.

In the contract. Because the authority requests the data sets and possibly the source code from the supplier, while the municipality bears the consequences, it is sensible in our reading to agree that the supplier informs the municipality of any request from a regulator about this system, and cooperates when the municipality has to supply documents. See AI procurement contracts.

Example 2: a bank with its own credit model

Suppose it is 2028. A bank has built its own model that assesses the creditworthiness of consumers, and uses it for its own loans. This example is fictitious too.

The roles and the authority. Creditworthiness falls under Annex III, point 5(b). The bank developed the system itself and put it into service under its own name, so it is provider and deployer at the same time. Because the use is directly connected with the financial service, the market surveillance authority is the authority responsible for the financial supervision of the bank (Article 74(6)); recital 158 explains that supervision can thus be integrated into existing supervisory mechanisms. The AI Act does not determine whether that is the AFM or DNB; recital 158 speaks of the competent authorities "within their respective competences". And as long as the Implementation Act does not apply, the national powers and rules on fines are missing. In the Dutch draft they are the AFM and DNB, according to the draft memorandum with DNB for the significant banks where the ECB supervises sound and ethical business operations. Where DNB, which participates in the Single Supervisory Mechanism, carries out the market surveillance, it reports without delay to the ECB information that may be of potential interest for the ECB's prudential supervisory tasks (Article 74(7), second subparagraph).

What the bank must give as provider. Unlike the municipality, the bank has the duties in Article 74(12): full access to the documentation and the training, validation and testing data sets, through an API where necessary. In our reading the bank sets up a secure environment for this in advance, so it does not have to make copies of customer data under time pressure. If the authority asks for the source code, the bank checks whether the request is reasoned and whether both conditions in paragraph 13 are met: is the source code necessary to assess compliance with Section 2, and have the tests based on its documentation and data been exhausted or proved insufficient? If not, the bank can in our reading first offer additional tests or documentation. The source code is a trade secret the authority protects under Article 78(1)(a).

The fundamental rights authority. Suppose the Netherlands Institute for Human Rights receives signals that the model rejects applicants of a certain origin more often. It can request the fundamental rights impact assessment (Article 27(1)), the documentation on the data (Article 10) and the test results through the financial supervisor, which obtains them from the bank (Article 77(1) and (1a)), but it can also itself demand information and documents from the bank (Article 6 of the Netherlands Institute for Human Rights Act (Wet College voor de rechten van de mens)). If the documents are insufficient, the Institute can ask for testing (Article 77(3)). For the processing of personal data, the AP can also request information itself under the GDPR. See also AI in credit decisions.

A complaint from a consumer organisation. A consumer organisation can lodge a complaint under Article 85 without any personal data of its own being involved, with the financial supervisor as the relevant market surveillance authority. An individual consumer can also complain to the AP under Article 77 GDPR and, for a decision based on the system's output, ask for an explanation under Article 86.

From when?

  • Articles 74, 77 and 85 sit in Chapter IX and have applied since 2 August 2026, the general date in Article 113, second paragraph. The new text of Article 77 entered into force on 27 July 2026 (Article 4 of Regulation (EU) 2026/1744) and therefore applies from 2 August 2026. The list in Article 77(2) had its own deadline: 2 November 2024.
  • Article 78 has applied since 2 August 2025 (Article 113, third paragraph, point (b)).
  • What the powers cover. Article 74(12) and (13) and Article 77(3) concern high-risk systems. The requirements and obligations the authority tests against, including the technical documentation and the data requirements, apply from 2 December 2027 for Annex III and from 2 August 2028 for Annex I (Article 113, third paragraph, point (c), as replaced by Article 1, point 40, of Regulation (EU) 2026/1744). For systems already placed on the market or put into service before that date, the requirements apply only after a significant change in design; systems intended to be used by public authorities must comply by 2 August 2030 (Article 111(2)). For prohibited practices and Article 50, the powers of Regulation (EU) 2019/1020 and the right to complain already apply, in so far as a Member State has designated and empowered an authority; in the Netherlands that has not yet happened for these provisions.
  • In the Netherlands. The market surveillance authorities have not yet been designated by law; submission of the bill is planned for the second quarter of 2027. Until then only the AI Act itself designates an authority for financial institutions, Annex I products and Union institutions (Article 74(3), (6) and (9)), but the national powers and rules on fines are missing; for paragraph 6 the AI Act moreover does not determine whether that is the AFM or DNB. The fundamental rights authorities are on the provisional list of 19 November 2024.

What you do now

As a deployer, such as a municipality:

  1. Know which documents you keep and where: logs (Article 26(6)), work instructions, the fundamental rights impact assessment and the DPIA. These are the first documents an authority asks for.
  2. Decide who handles a request from a regulator, how you check whether what is requested is strictly necessary (Article 78(2)), and how you mark confidential parts.
  3. Set up a desk for complaints and questions from residents, including for explanations under Article 86, and tell residents which routes exist: the market surveillance authority, the AP under the GDPR and objection against the decision.
  4. Agree in the contract that the supplier informs you of requests and investigations by regulators about the system.

As a provider, such as a supplier or a bank with its own model:

  1. Make sure you can give access to documentation and data sets, also remotely and with security safeguards (Article 74(12)), without sending copies of personal data around.
  2. Make the source code the last step. Keep testing and auditing options in order, so the authority can assess conformity without the source code (Article 74(13)), and check every request for source code against those two conditions.
  3. Mark trade secrets when supplying documents, so the authority knows what it protects under Article 78(1)(a); do not refuse on that ground.
  4. Give correct and complete answers. Incorrect, incomplete or misleading information is itself subject to a fine (Article 99(5)).

Want to know which AI Act and GDPR obligations come into view for your use case and what your role is? With the case check you describe the use case in a few questions.

Frequently asked questions about the powers of regulators under the AI Act

Sources

EUR-Lex: Regulation (EU) 2016/679 (GDPR), Articles 6, 9, 58, 77 and 78 (27 April 2016, accessed 19 November 2026)
Overheid.nl: Wet College voor de rechten van de mens (Netherlands Institute for Human Rights Act), Article 6 (in Dutch) (in force from 1 January 2026, accessed 19 November 2026)
House of Representatives of the Netherlands: Planningsbrief Digitale Zaken, Parliamentary Paper 26643, no. 1554 (in Dutch) (31 August 2026, accessed 19 November 2026)

Newsletter

Every Tuesday, the AI Act week ahead in 5 minutes

A practical briefing on deadlines, new guidance and enforcement, so you know what matters this week. No spam and you can unsubscribe in one click.

Practical and short · No spam · One-click unsubscribe

Written by

Zahed Ashkara, freelance AI and privacy consultant and legal adviser

Zahed Ashkara

Freelance AI and privacy consultant and legal adviser · AI governance & safety

Zahed Ashkara is a freelance AI and privacy consultant and legal adviser for the GDPR and the EU AI Act. Organisations hire him as AI governance consultant, privacy counsel, external DPO or AI governance lead, have him carry out a DPIA, FRIA or AI Act classification, or book an in-company training. He focuses on AI governance and safety, including AI agents. He works exclusively as a freelancer, through Embed AI (trade name Praxikon). He is a Certified AI Compliance Officer (CAICO) and has been a member of the NEN standards committee Artificial Intelligence & Big Data since July 2026.

Follow on LinkedInView expert profile

Use these sources in your AI assistant too: Praxikon in Claude and other assistants

Real-World Stories

Discover how organizations apply this in practice

Related articles

When the regulator knocks: Articles 79 to 82 of the AI Act on AI systems presenting a risk

What happens when a market surveillance authority considers that an AI system presents a risk? Article 79 sets out the national procedure: evaluation, corrective action within a period of at most 15 working days, and where needed a prohibition or recall. Article 80 deals with a system the provider wrongly classified as non-high-risk, Article 81 with the Union safeguard procedure and Article 82 with a system that complies with the Regulation and still presents a risk. With who will supervise in the Netherlands, from when it applies, and a municipality using a system for social assistance applications and a bank as examples.

EU AI ActArticle 79Article 80

Who checks the checkers? Notifying authorities and notified bodies under Articles 28 to 39 of the AI Act

A notified body is the external assessor that carries out the conformity assessment for some high-risk AI systems. Articles 28 to 39 govern who designates such bodies, which requirements they must meet and what happens when they no longer meet them. When a provider needs one, who will handle this in the Netherlands, what the Digital Omnibus on AI changed, and what a municipality and a bank check when a supplier shows up with a certificate.

EU AI ActArticle 28Article 31

Testing a high-risk AI system with real people: Articles 60, 61 and 76 of the AI Act

Anyone who wants to try out a high-risk AI system in practice before it goes into use is testing in real-world conditions. Article 60 governs who may do that outside an AI regulatory sandbox and under which conditions, Article 61 the consent the participants give, and Article 76 what the market surveillance authority can do. Whether a municipality may test on its own, what the Digital Omnibus on AI changed, and why consent under Article 61 is not GDPR consent.

EU AI ActArticle 60Article 61