GovCompass
AI governance

Art. 26.8 EU AI Act: registration in the EU database

By GovCompass.ai· Last verified June 2026· Aligned with the consolidated EU AI Act, including the 2026 Omnibus amendments.

Art. 26.8 requires deployers that are public authorities (or act on their behalf) to verify that a high-risk AI system is registered in the EU database before putting it into use, and to refrain from using it if it is not.

Updated: June 2026

Introduction: the EU AI database

The EU AI Act establishes a publicly accessible EU database for high-riskriskIn the EU AI Act's terms, the combination of the probability that a harm occurs and the severity of it if it does. The link between a principle (via the harm that would breach it) and a control (the measure that reduces it). Naming the harm and assessing its risk is required by Art. 9 before any mitigation measure is chosen. See harm, control, residual risk.Open full entry → AI systems. Art. 49 creates registration obligations for providers. Art. 26.8 extends a more limited registration obligation to deployers, specifically deployers operating high-risk AI systems in areas of particular public interest: public authorities and bodies deploying AI in migration, asylum, and border controlcontrolThe concrete, testable measure that reduces a specific risk, and through that risk protects the principle behind it. Also called a risk management measure, risk response, or risk treatment. Always traceable to the risk it addresses: under EU AI Act Art. 9 every control must map back to a specific risk, and controls recorded separately from their risks is a recognized compliance failure. It works in one of three types: preventive, detective, or corrective. See risk, control types, evidence.Open full entry →, and in biometric identification contexts.

Who must register under Art. 26.8?

Art. 26.8 creates deployerdeployerAn organization using an AI system under its own authority in its activities — carrying operator duties: use per instructions, oversight, input relevance, monitoring, notices.Open full entry → registration obligations for:

  1. Public authorities using high-risk AI systems listed in Annex IIIAnnex IIIThe EU AI Act's list of high-risk use-case areas — biometrics, critical infrastructure, education, employment, essential services, law enforcement, migration, justice.Open full entry → points 1, 6, 7, or 8 (biometric identification, law enforcement, migration/asylum, justice)
  2. Any deployer using a high-risk AI systemAI systemA machine-based system that, for explicit or implicit objectives, infers from input how to generate outputs — predictions, content, recommendations or decisions — that can influence physical or virtual environments. The OECD-style definition followed by the EU AI Act.Open full entry → where the providerproviderThe actor who develops an AI system (or has it developed) and places it on the market or into service under its own name — carrying manufacturer-style duties: design controls, documentation, conformity.Open full entry → is established outside the EU, in this case the deployer takes on provider-equivalent registration obligations

For most private-sector Dutch organizations deploying AI in HR, credit, or healthcare contexts: Art. 26.8 registration is not directly required. However, the provider is required to register under Art. 49, and deployers should verify that their provider has done so.

What must be registered?

Deployer registrations must include:

  • The deployer's name, registered address, and contact details
  • The registration number of the AI system (assigned by the provider's registration)
  • The deployer's use case, how and in what context the system is deployed
  • The categories of individuals affected
  • Geographic scope of deployment within the EU

Verification obligations for all deployers

Even where Art. 26.8 does not directly require deployer registration, all deployers of high-risk AI should verify that their provider has fulfilled their registration obligations under Art. 49. Request the system's EU database registration number from your provider and cross-check it against the public database once it is operational.

Compliance checklist

  1. Are any of your high-risk AI deployments in Annex III points 1, 6, 7, or 8 contexts?
  2. Is your organization a public authority? If so, Art. 26.8 registration may apply directly.
  3. Are any of your AI providers established outside the EU? If so, verify registration obligations carefully.
  4. Have you requested and verified the EU database registration number from each of your high-risk AI providers?
Legal referencesArt. 26
Share Share on LinkedIn

More on Accountability

Art. 10 EU AI Act: data and data governance for high-risk AI

Reference

Art. 10 requires that the training, validation, and testing data for high-risk AI systems meets quality criteria: relevant, sufficiently representative, and as free of errors and complete as possible for the intended purpose. It also requires documented data governance practices covering collection, preparation, bias examination, and gap mitigation, and it permits the limited processing of special-category data where strictly necessary to detect and correct bias, under safeguards.

Art. 12 EU AI Act: record-keeping and logging for high-risk AI

Reference

Art. 12 requires high-risk AI systems to technically allow for the automatic recording of events (logs) over their lifetime. The logging must enable traceability of the system's functioning at a level appropriate to its intended purpose, support post-market monitoring, and help identify situations that may lead to risk or substantial modification. It is a design obligation on the provider that makes the system auditable by construction.

Art. 19 EU AI Act: keeping the automatically generated logs

Reference

Art. 19 requires providers of high-risk AI systems to keep the logs that the system automatically generates (under Art. 12) for as long as they control them, for a period appropriate to the intended purpose and at least six months unless other law requires longer. It is the retention counterpart to the Art. 12 logging capability, and it works alongside the deployer retention duty in Art. 26.6.

Art. 26.1 EU AI Act: following provider instructions as a deployer

Reference

Art. 26.1 requires deployers to use high-risk AI systems strictly in accordance with the provider's instructions for use. This means using the system only for its intended purpose, within its specified technical configuration, and by qualified users, and documenting that compliance. Deviating from the instructions can shift liability entirely to the deployer.

More on Transparency & explainability

Art. 12 EU AI Act: record-keeping and logging for high-risk AI

Reference

Art. 12 requires high-risk AI systems to technically allow for the automatic recording of events (logs) over their lifetime. The logging must enable traceability of the system's functioning at a level appropriate to its intended purpose, support post-market monitoring, and help identify situations that may lead to risk or substantial modification. It is a design obligation on the provider that makes the system auditable by construction.

Art. 26.7 EU AI Act: transparency obligations towards individuals

Reference

Art. 26.7 requires deployers of high-risk AI to inform the people who are subject to the system's decisions that a high-risk AI system is being used. This applies even where there is no direct interaction, such as CV screening or credit scoring.

Art. 49 EU AI Act: registration in the EU database for providers

Reference

Art. 49 requires providers of high-risk AI systems to register the system in the EU database before placing it on the market. The database serves both market surveillance and public accountability, letting citizens see which high-risk systems are in use.

Art. 52 EU AI Act: the systemic-risk notification procedure

Reference

Art. 52 sets out the procedure that connects to the systemic-risk classification of Art. 51. A provider must notify the Commission without delay, and within two weeks, when its general-purpose AI model meets or is foreseen to meet the systemic-risk threshold. The provider can argue, with the notification, that its model does not present systemic risk despite crossing the threshold. The Commission maintains and publishes a list of GPAI models with systemic risk.