> AI Act vs Data Act side by side, topic by topic: where they overlap, where they differ and which asks more, with incident deadlines, testing, third parties and fines.

# AI Act vs Data Act

Where they overlap, where they differ and which asks more, topic by topic, with their deadlines and fines side by side.

[AI Act](https://grc.plus/regulation/artificial-intelligence-act-ai-act/)Providers and deployers of AI systems

[Data Act](https://grc.plus/regulation/eu-data-act/)Manufacturers and related service providers, data holders, providers of data processing services

## At a Glance

They differ on 27 of 28 topics. Each verdict names what it rests on; read the wording before relying on it.

- **AI Act** Asks more on 0 topics Alone on 17 topics More detailed on 1 topic
- **Data Act** Asks more on 0 topics Alone on 6 topics More detailed on 3 topics

| Topic | AI Act | Data Act | Verdict |
| --- | --- | --- | --- |
| Governance |  |  |  |
| Roles and independence | AI Act: 3 | Data Act: – | **Only AI Act**no specific requirement on the other side in the acts covered |
| Awareness and training | AI Act: 1 | Data Act: – | **Only AI Act**no specific requirement on the other side in the acts covered |
| Risk management |  |  |  |
| Risk management framework | AI Act: 1 | Data Act: – | **Only AI Act**no specific requirement on the other side in the acts covered |
| Risk assessment | AI Act: 1 | Data Act: – | **Only AI Act**no specific requirement on the other side in the acts covered |
| Review, audit and improvement | AI Act: 1 | Data Act: – | **Only AI Act**no specific requirement on the other side in the acts covered |
| Protection |  |  |  |
| Data security | AI Act: 1 | Data Act: 6 | **Data Act more detailed**more requirements on this, not necessarily stricter |
| Secure acquisition and development | AI Act: 1 | Data Act: 1 | **Both cover it**read the wording below |
| Detection and response |  |  |  |
| Monitoring and detection | AI Act: 2 | Data Act: – | **Only AI Act**no specific requirement on the other side in the acts covered |
| Incident handling | AI Act: 2 | Data Act: – | **Only AI Act**no specific requirement on the other side in the acts covered |
| Reporting to authorities | AI Act: 4 | Data Act: – | **Only AI Act**no specific requirement on the other side in the acts covered |
| Informing customers and the public | AI Act: – | Data Act: 1 | **Only Data Act**no specific requirement on the other side in the acts covered |
| Continuity and resilience |  |  |  |
| Threat-led penetration testing | AI Act: 1 | Data Act: – | **Only AI Act**no specific requirement on the other side in the acts covered |
| Third parties and supply chain |  |  |  |
| Supplier and third-party risk | AI Act: 2 | Data Act: – | **Only AI Act**no specific requirement on the other side in the acts covered |
| Contract requirements | AI Act: 1 | Data Act: 8 | **Data Act more detailed**more requirements on this, not necessarily stricter |
| Exit and termination | AI Act: – | Data Act: 7 | **Only Data Act**no specific requirement on the other side in the acts covered |
| Privacy and data protection |  |  |  |
| Lawful processing | AI Act: – | Data Act: 2 | **Only Data Act**no specific requirement on the other side in the acts covered |
| Transparency | AI Act: – | Data Act: 4 | **Only Data Act**no specific requirement on the other side in the acts covered |
| Rights of individuals | AI Act: – | Data Act: 4 | **Only Data Act**no specific requirement on the other side in the acts covered |
| Impact assessment | AI Act: 1 | Data Act: – | **Only AI Act**no specific requirement on the other side in the acts covered |
| International transfers | AI Act: – | Data Act: 3 | **Only Data Act**no specific requirement on the other side in the acts covered |
| Artificial intelligence |  |  |  |
| Risk classification of AI systems | AI Act: 4 | Data Act: – | **Only AI Act**no specific requirement on the other side in the acts covered |
| Data and data governance | AI Act: 3 | Data Act: – | **Only AI Act**no specific requirement on the other side in the acts covered |
| Transparency to users | AI Act: 6 | Data Act: – | **Only AI Act**no specific requirement on the other side in the acts covered |
| Human oversight | AI Act: 2 | Data Act: – | **Only AI Act**no specific requirement on the other side in the acts covered |
| Conformity assessment and monitoring | AI Act: 5 | Data Act: – | **Only AI Act**no specific requirement on the other side in the acts covered |
| Supervision and enforcement |  |  |  |
| Registration with authorities | AI Act: 2 | Data Act: – | **Only AI Act**no specific requirement on the other side in the acts covered |
| Cooperation with supervisors | AI Act: 1 | Data Act: 3 | **Data Act more detailed**more requirements on this, not necessarily stricter |
| Penalties and liability | AI Act: 4 | Data Act: 1 | **AI Act more detailed**more requirements on this, not necessarily stricter |

## What This Covers

The obligations below are summarised from the acts listed here, grouped by topic. Where a side shows nothing on a topic, the acts covered have no specific requirement on it; an act not yet included, national guidance or a supervisor's expectations may still say more. Use it to see where the regimes differ, not as a compliance checklist.

Included

- [AI Act](https://grc.plus/regulation/artificial-intelligence-act-ai-act/) Articles 4 to 6, 8 to 27, 43, 47 to 50, 53, 55, 72, 73, 99, 101, 111 · 49 requirements
- [KI-loven](https://grc.plus/regulation/norway-artificial-intelligence-act-ki-loven/) Draft act on artificial intelligence (KI-loven), consultation of 30 June 2025 Articles 5, 50 · 4 requirements
- [Decreet 16 oktober 2026](https://grc.plus/regulation/flanders-media-decree-ai-act-amendment/) Decreet van 16 oktober 2026, Belgisch Staatsblad 19 November 2026, numac 2026008360 3 requirements
- [No. 31/2026](https://grc.plus/regulation/ireland-regulation-of-artificial-intelligence-act/) Regulation of Artificial Intelligence Act 2026 (No. 31 of 2026) 5 requirements

Status

Reviewed against the official texts.

Included

- [Data Act](https://grc.plus/regulation/eu-data-act/) Regulation (EU) 2023/2854 of the European Parliament and of the Council of 13 December 2023 Articles 3 to 9, 11, 13, 14, 18, 23, 25, 26, 28 to 32, 40 · 33 requirements
- [Druk nr 3266](https://grc.plus/regulation/poland-data-act-implementing-bill/) Druk nr 3266 (government bill) and Druk nr 3288 (committee report), Sejm of the Republic of Poland, 10th term 4 requirements

Status

Reviewed against the official texts.

## Key Numbers

### Deadline

AI Act: Immediately on identifying a serious incident (Deployers of high-risk AI systems); Without undue delay (Providers of general-purpose AI models with systemic risk); Within 2 days of becoming aware (Providers of high-risk AI systems); Within 10 days of becoming aware (Providers of high-risk AI systems)

Data Act: Without undue delay after a simple request (Data holders); Without undue delay after the user's request (Data holders and gatekeepers designated under the Digital Markets Act); Without undue delay after a reasoned request (Data holders obliged to make data available); Decline within five working days of receipt for a public emergency, 30 working days of receipt otherwise (Data holders that are legal persons, other than public sector bodies); Notice of at most two months; transition of at most 30 calendar days after the notice period (Providers of data processing services); Retrieval for at least 30 calendar days after the end of the transitional period (Providers of data processing services); Notify within 14 working days of the switching request; alternative period of at most seven months (Providers of data processing services); No switching charges from 12 January 2027 (Providers of data processing services); Compatibility at least 12 months after publication of the references in the central Union standards repository (Providers of data processing services)

### Threshold

AI Act: Not in the acts covered

Data Act: Micro and small enterprises; medium-sized for under one year; a medium-sized enterprise's products for one year after market placement (Micro and small enterprises, and medium-sized enterprises in their first year or for products in their first year on the market)

### Goes to

AI Act: Market surveillance authorities and, where applicable, the notified body (Providers of high-risk AI systems); Provider first, then importer or distributor and market surveillance authorities (Deployers of high-risk AI systems); Market surveillance authority (Public law bodies and private providers of public services deploying Article 6(2) systems (except Annex III, point 2), and deployers of Annex III, points 5(b) and (c) systems)

Data Act: Competent authority designated under Article 37 (Data holders); User or third party in writing; competent authority notified (Data holders); Customer, before complying (Providers of data processing services)

### Evidence to keep

AI Act: Documented assessment, provided on request (Providers of Annex III AI systems they consider not high-risk); Annex IV technical documentation (Providers of high-risk AI systems); Automatically generated logs, at least six months (Providers of high-risk AI systems); Documentation, 10 years after placing on the market or putting into service (Providers of high-risk AI systems); Provider contact details, EU declaration, technical documentation and any notified body certificate, 10 years (Providers of high-risk AI systems established in third countries); Certificate, instructions and EU declaration, 10 years (Importers of high-risk AI systems); Logs under the deployer's control, at least six months (Deployers of high-risk AI systems); EU declaration of conformity, 10 years (Providers of high-risk AI systems); Annex XI and Annex XII documentation (Providers of general-purpose AI models); Post-market monitoring plan in the technical documentation (Providers of high-risk AI systems)

Data Act: Not in the acts covered

### Incident reports go to

AI Act: AI Office and, as appropriate, national competent authorities (Providers of general-purpose AI models with systemic risk); Market surveillance authorities of the Member States where the incident occurred (Providers of high-risk AI systems); Market surveillance authorities of the Member States where the incident occurred (Providers of high-risk AI systems); Market surveillance authorities of the Member States where the incident occurred (Providers of high-risk AI systems)

Data Act: Not in the acts covered

### First notice of an incident

AI Act: Within 2 days of becoming aware for a widespread infringement or critical infrastructure disruption; 10 days for a death; 15 days otherwise (Providers of high-risk AI systems)

Data Act: Not in the acts covered

### Deadline to have the measures in place

AI Act: By 2 December 2026 (Operators of AI systems); By 2 December 2027 (Annex III) and 2 August 2028 (Annex I) (Providers of AI systems); By 2 December 2027 (Annex III) and 2 August 2028 (Annex I) (Providers of high-risk AI systems); By 2 December 2026 for systems on the market before 2 August 2026 (Providers of AI systems, including general-purpose AI systems, that generate synthetic content)

Data Act: Products and related services placed on the market after 12 September 2026 (Manufacturers of connected products and providers of related services)

### External assessment or certification

AI Act: Internal control, or a notified body where Article 43 requires one (Providers of high-risk AI systems)

Data Act: Not in the acts covered

### Review of the risk framework

AI Act: Regular systematic review throughout the lifecycle (Providers of high-risk AI systems)

Data Act: Not in the acts covered

### Registration with the authority

AI Act: EU database, under Article 49(2) (Providers of Annex III AI systems they consider not high-risk); EU database under Article 71, before placing on the market or putting into service (Providers of Annex III AI systems or their authorised representatives); EU database under Article 71, before putting into service or use (Deployers that are public authorities, Union bodies or persons acting on their behalf)

Data Act: Not in the acts covered

### Maximum fines

AI Act: Up to EUR 35,000,000 or 7% of worldwide annual turnover, whichever is higher (Operators of AI systems); Up to EUR 15,000,000 or 3% of worldwide annual turnover, whichever is higher (Operators of AI systems and notified bodies); Up to EUR 7,500,000 or 1% of worldwide annual turnover, whichever is higher (Anyone supplying information to notified bodies or national competent authorities in reply to a request); Up to EUR 15,000,000 or 3% of worldwide annual turnover, whichever is higher (Providers of general-purpose AI models)

Data Act: Set by each Member State; for Chapters II, III and V, data protection authorities may fine up to the GDPR Article 83(5) amount (Member States)

## Governance

### Roles and independence

**Only AI Act** no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.RR · ISO/IEC 27001:2022 A.5.2, A.5.3

- Provider obligations
  Applies to: Providers of high-risk AI systems
  Ensure the system meets the Section 2 requirements, taking account of its intended purpose and the state of the art. Show your name and contact address, run a quality management system, keep documentation and logs, complete conformity assessment, the EU declaration and CE marking, register, take corrective action, demonstrate conformity on request and meet accessibility requirements.
  [AI Act, Articles 8(1), 16](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Appoint an authorised representative
  Applies to: Providers of high-risk AI systems established in third countries
  Before making a high-risk system available in the Union, appoint an EU-established authorised representative by written mandate. The representative verifies the conformity documents, keeps them for 10 years, deals with authorities and ends the mandate, informing the authority, if the provider acts against the Regulation.
  [AI Act, Article 22(1), (3), (4)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- When others become the provider
  Applies to: Distributors, importers, deployers, other third parties and initial providers
  A distributor, importer, deployer or other third party takes on provider obligations if it puts its name or trademark on a high-risk system (unless a contract allocates them otherwise), substantially modifies one, or changes the purpose of an AI system so that it becomes high-risk. The initial provider then stops being the provider of that system but cooperates and hands over information and access, unless it clearly specified that the system is not to be changed into a high-risk one.
  [AI Act, Article 25(1), (2)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

Nothing in the acts covered.

### Awareness and training

**Only AI Act** no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.AT · ISO/IEC 27001:2022 A.6.3

- Support AI literacy
  Take measures to support the AI literacy of staff and others who operate or use AI systems on your behalf, taking account of their knowledge, experience and training, the context of use and the people affected. The duty does not require you to guarantee a specific level of literacy for any individual.
  [AI Act, Article 4(1)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

Nothing in the acts covered.

## Risk management

### Risk management framework

**Only AI Act** no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.RM · ISO/IEC 27001:2022 Clause 6.1

- Risk management system
  Applies to: Providers of high-risk AI systems
  Establish, implement, document and maintain a risk management system for each high-risk AI system. Run it as a continuous, iterative process across the whole lifecycle, with regular systematic review and updating.
  [AI Act, Article 9(1), (2)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

Nothing in the acts covered.

### Risk assessment

**Only AI Act** no specific requirement on the other side in the acts covered

NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 Clauses 6.1.2, 8.2

- Assess, treat and test for risk
  Applies to: Providers of high-risk AI systems
  Identify and evaluate known and foreseeable risks to health, safety and fundamental rights, including under foreseeable misuse and from post-market data, and adopt targeted measures until residual risk is acceptable. Consider the effect on under-18s and other vulnerable groups. Test against predefined metrics and probabilistic thresholds, in any event before placing the system on the market or putting it into service.
  [AI Act, Article 9(2), (5), (6), (8), (9)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

Nothing in the acts covered.

### Review, audit and improvement

**Only AI Act** no specific requirement on the other side in the acts covered

NIST CSF 2.0 ID.IM, GV.OV · ISO/IEC 27001:2022 A.5.35, A.5.36, Clauses 9, 10

- Quality management system
  Applies to: Providers of high-risk AI systems
  Run a documented quality management system with written policies and procedures, covering regulatory strategy, design and development controls, testing, data management, risk management, post-market monitoring, incident reporting, record-keeping, resources and an accountability framework for management and staff. Scale it to the size of the organisation, without lowering the level of protection.
  [AI Act, Article 17(1), (2)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

Nothing in the acts covered.

## Protection

### Data security

**Data Act more detailed** more requirements on this, not necessarily stricter

NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.5.12, A.8.10 to A.8.12

- Protect the model and its infrastructure
  Applies to: Providers of general-purpose AI models with systemic risk
  Ensure an adequate level of cybersecurity protection for the model and its physical infrastructure.
  [AI Act, Article 55(1)(d)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

- Restricting access for product security Optional
  Applies to: Data holders
  Users and data holders may agree by contract to restrict or prohibit access, use or further sharing where it could undermine the product's legal security requirements and seriously harm the health, safety or security of people. A data holder that refuses to share on this ground notifies the competent authority.
  [Data Act, Article 4(2)](https://grc.plus/regulation/eu-data-act/#requirements)
- Protect trade secrets when sharing
  Applies to: Data holders and trade secret holders
  Identify data protected as trade secrets, including in the metadata, and agree with the user or third party proportionate technical and organisational measures to keep it confidential. Disclosure happens only once those measures are in place, and to a third party only as far as strictly necessary for the purpose agreed with the user.
  [Data Act, Articles 4(6) and 5(9)](https://grc.plus/regulation/eu-data-act/#requirements)
- Withhold or refuse data to protect trade secrets Optional
  Applies to: Data holders
  A data holder may withhold or suspend trade secret data where measures are not agreed, not implemented or confidentiality is undermined. In exceptional cases a trade secret holder may refuse a specific request if it shows serious economic damage is highly likely. The decision is reasoned and given in writing without undue delay, and the competent authority is notified.
  [Data Act, Articles 4(7), 4(8), 5(10) and 5(11)](https://grc.plus/regulation/eu-data-act/#requirements)
- Third party limits on received data
  Applies to: Third parties receiving data at the user's request
  Process the data only for the purposes and under the conditions agreed with the user, and erase it when no longer needed for that purpose unless otherwise agreed for non-personal data. Do not make the user's choices unduly difficult, profile people unless needed for the requested service, or pass the data to another third party except under a contract with the user and with the agreed trade secret measures. Do not pass it to a gatekeeper, use it to develop a competing product or derive insights about the data holder, harm the product's security, disregard agreed trade secret measures, or stop a consumer user from sharing the data.
  [Data Act, Article 6(1) and (2)](https://grc.plus/regulation/eu-data-act/#requirements)
- Data retrieval and erasure
  Applies to: Providers of data processing services
  Specify all categories of data and digital assets that can be ported, including at least all exportable data. Give a data retrieval period of at least 30 calendar days after the transitional period, and guarantee full erasure of exportable data and digital assets after that period once switching has succeeded.
  [Data Act, Article 25(2)(e), (g) and (h)](https://grc.plus/regulation/eu-data-act/#requirements)
- Prevent unlawful governmental access
  Applies to: Providers of data processing services
  Take all adequate technical, organisational and legal measures, including contracts, to prevent international and third-country governmental access to or transfer of non-personal data held in the Union where it would conflict with Union or national law. A third-country decision is recognised or enforceable only if it is based on an international agreement.
  [Data Act, Article 32(1) and (2)](https://grc.plus/regulation/eu-data-act/#requirements)

### Secure acquisition and development

**Both cover it** read the wording below

NIST CSF 2.0 PR.PS · ISO/IEC 27001:2022 A.8.25 to A.8.31

- Accuracy, robustness and cybersecurity
  Applies to: Providers of high-risk AI systems
  Achieve an appropriate level of accuracy, robustness and cybersecurity throughout the lifecycle and declare accuracy metrics in the instructions. Make the system resilient to errors and to attempts to alter its use or output, with measures where appropriate against data poisoning, model poisoning, adversarial examples, confidentiality attacks and model flaws.
  [AI Act, Article 15(1), (3) to (5)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

- Data accessible by design and by default
  Applies to: Manufacturers of connected products and providers of related services
  Design and manufacture connected products, and design and provide related services, so that product and related service data and the metadata needed to use them are accessible to the user by default. Access is easy, secure, free of charge and in a comprehensive, structured, commonly used and machine-readable format, and direct where relevant and technically feasible. This applies to products and services placed on the market after 12 September 2026.
  [Data Act, Article 3(1)](https://grc.plus/regulation/eu-data-act/#requirements)

## Detection and response

### Monitoring and detection

**Only AI Act** no specific requirement on the other side in the acts covered

NIST CSF 2.0 DE.CM, DE.AE · ISO/IEC 27001:2022 A.8.15, A.8.16

- Automatic logs
  Applies to: Providers of high-risk AI systems
  Build the system so it records events automatically over its lifetime, supporting risk identification, post-market monitoring and deployer monitoring. Keep the logs under your control for a period that suits the intended purpose and is at least six months, unless other law says otherwise.
  [AI Act, Articles 12(1), (2), 19(1)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Keep deployer logs
  Applies to: Deployers of high-risk AI systems
  Keep the logs generated by the system, to the extent you control them, for a period that suits the intended purpose and is at least six months, unless other law says otherwise. Financial institutions keep them with their financial services documentation.
  [AI Act, Article 26(6)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

Nothing in the acts covered.

### Incident handling

**Only AI Act** no specific requirement on the other side in the acts covered

NIST CSF 2.0 RS.MA, RS.AN, RS.MI · ISO/IEC 27001:2022 A.5.24 to A.5.28

- Corrective action and duty to inform
  Applies to: Providers of high-risk AI systems
  If a system may not conform, immediately correct, withdraw, disable or recall it and tell distributors and, where applicable, deployers, the authorised representative and importers. If it presents a risk under Article 79(1), immediately investigate the causes and inform the market surveillance authorities and, where applicable, the notified body.
  [AI Act, Article 20](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Investigate a serious incident
  Applies to: Providers of high-risk AI systems
  After reporting, investigate without delay, including a risk assessment and corrective action, and cooperate with authorities. Do not alter the system in a way that could affect later evaluation of the causes without first informing the authorities.
  [AI Act, Article 73(6)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

Nothing in the acts covered.

### Reporting to authorities

**Only AI Act** no specific requirement on the other side in the acts covered

NIST CSF 2.0 RS.CO · ISO/IEC 27001:2022 A.5.5

- Report serious incidents on models
  Applies to: Providers of general-purpose AI models with systemic risk
  Track, document and report relevant information about serious incidents and possible corrective measures without undue delay.
  [AI Act, Article 55(1)(c)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Report a serious incident
  Applies to: Providers of high-risk AI systems
  Report any serious incident immediately after establishing a causal link, or its reasonable likelihood, between the system and the incident, taking account of its severity. An incomplete initial report may be followed by a complete one.
  [AI Act, Article 73(1), (2), (5)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Report widespread infringements and critical infrastructure disruption
  Applies to: Providers of high-risk AI systems
  Report immediately in the event of a widespread infringement, or a serious and irreversible disruption of the management or operation of critical infrastructure.
  [AI Act, Article 73(3)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Report a death
  Applies to: Providers of high-risk AI systems
  Where a person dies, report immediately after establishing, or as soon as you suspect, a causal relationship between the system and the incident.
  [AI Act, Article 73(4)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

Nothing in the acts covered.

### Informing customers and the public

**Only Data Act** no specific requirement on the other side in the acts covered

NIST CSF 2.0 RS.CO, RC.CO

Nothing in the acts covered.

- Handling third-country access requests
  Applies to: Providers of data processing services
  Without an international agreement, give access only where the Article 32(3) conditions on reasons, review and consideration of protected interests are met. If the provider asks the competent national body for its opinion and gets no reply within one month, or the body finds the conditions are not met, the provider may reject the request. It must ask that body where national security or defence may be affected. Provide the minimum data permissible, and inform the customer before complying unless the request serves law enforcement and only for as long as needed to keep that effective.
  [Data Act, Article 32(3) to (5)](https://grc.plus/regulation/eu-data-act/#requirements)

## Continuity and resilience

### Threat-led penetration testing

**Only AI Act** no specific requirement on the other side in the acts covered

NIST CSF 2.0 ID.IM

- Evaluate models and mitigate systemic risk
  Applies to: Providers of general-purpose AI models with systemic risk
  Evaluate the model using standardised protocols and tools reflecting the state of the art, including documented adversarial testing. Assess and mitigate possible systemic risks at Union level and their sources.
  [AI Act, Article 55(1)(a), (b)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

Nothing in the acts covered.

## Third parties and supply chain

### Supplier and third-party risk

**Only AI Act** no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.SC · ISO/IEC 27001:2022 A.5.19, A.5.21 to A.5.23

- Importer checks
  Applies to: Importers of high-risk AI systems
  Before placing a high-risk system on the market, verify the conformity assessment, technical documentation, CE marking, EU declaration, instructions and authorised representative. Hold back a system you have reason to think is non-conforming or falsified, and report risks. Keep the certificate, instructions and declaration for 10 years and cooperate with authorities.
  [AI Act, Article 23(1), (2), (5) to (7)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Distributor checks
  Applies to: Distributors of high-risk AI systems
  Before making a high-risk system available, verify the CE marking, EU declaration and instructions, that the provider and importer show their name and contact address, and that the provider has a quality management system. Hold back a system you consider non-conforming. If one is already on the market, ensure it is corrected, withdrawn or recalled, inform the provider or importer and authorities of any risk, and cooperate with them.
  [AI Act, Article 24(1), (2), (4) to (6)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

Nothing in the acts covered.

### Contract requirements

**Data Act more detailed** more requirements on this, not necessarily stricter

NIST CSF 2.0 GV.SC · ISO/IEC 27001:2022 A.5.20

- Written agreements with suppliers
  Applies to: Providers of high-risk AI systems and their third-party suppliers
  Specify by written agreement the information, capabilities, technical access and other assistance a supplier of AI systems, models, tools, services, components or processes gives so that the provider can comply. This does not apply to open-source tools, services, processes or components that are made public, other than general-purpose AI models.
  [AI Act, Article 25(4)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

- Protect trade secrets when sharing
  Applies to: Data holders and trade secret holders
  Identify data protected as trade secrets, including in the metadata, and agree with the user or third party proportionate technical and organisational measures to keep it confidential. Disclosure happens only once those measures are in place, and to a third party only as far as strictly necessary for the purpose agreed with the user.
  [Data Act, Articles 4(6) and 5(9)](https://grc.plus/regulation/eu-data-act/#requirements)
- Limits on the data holder's own use
  Applies to: Data holders
  Use readily available non-personal data only under a contract with the user, and do not use it to derive insights that could undermine the commercial position of the user. Do not pass non-personal product data to third parties beyond fulfilling the user contract, and bind third parties not to share further. The same insight ban protects third parties unless they give a permission they can easily withdraw.
  [Data Act, Articles 4(13), 4(14) and 5(6)](https://grc.plus/regulation/eu-data-act/#requirements)
- Fair, reasonable and non-discriminatory terms
  Applies to: Data holders obliged to make data available
  Where a business-to-business data sharing duty applies under Article 5 or other law, agree the arrangements with the data recipient on fair, reasonable and non-discriminatory terms and in a transparent manner. Terms that are unfair under Article 13, or that reduce the user's Chapter II rights to the user's detriment, are not binding.
  [Data Act, Article 8(1) and (2)](https://grc.plus/regulation/eu-data-act/#requirements)
- No discrimination and no unrequested sharing
  Applies to: Data holders obliged to make data available
  Do not discriminate between comparable categories of data recipients, including partner and linked enterprises, and on a reasoned request show that no discrimination took place. Do not make data available to a recipient, including exclusively, unless the user requested it under Chapter II.
  [Data Act, Article 8(3) and (4)](https://grc.plus/regulation/eu-data-act/#requirements)
- Reasonable compensation
  Applies to: Data holders obliged to make data available
  Compensation agreed between businesses is non-discriminatory and reasonable and may include a margin, taking into account the costs of making data available and investments in collecting and producing it. For an SME or not-for-profit research organisation without larger partner or linked enterprises it does not exceed those costs of making data available. Give the recipient enough detail on the calculation to check this.
  [Data Act, Article 9(1), (2), (4) and (7)](https://grc.plus/regulation/eu-data-act/#requirements)
- Unfair terms imposed unilaterally are not binding
  Applies to: Enterprises contracting on data
  A term on data access and use, or on liability and remedies for data obligations, that one enterprise imposes unilaterally on another is not binding on that other enterprise if it is unfair. A term is unfair if its use grossly deviates from good commercial practice, contrary to good faith and fair dealing. The party that supplied the term has to prove it was not imposed unilaterally.
  [Data Act, Article 13(1), (3) and (6)](https://grc.plus/regulation/eu-data-act/#requirements)
- Terms that are or are presumed unfair
  Applies to: Enterprises contracting on data
  Always unfair: excluding liability for intent or gross negligence, excluding remedies for non-performance, or reserving the sole right to judge conformity or interpret the contract. Presumed unfair: among others, limiting remedies inappropriately, significantly detrimental use of the other party's data, blocking its use of or copies of its own data, blocking termination within a reasonable period, terminating at unreasonably short notice, or substantially changing price or conditions without a valid reason and a right to terminate.
  [Data Act, Article 13(4) and (5)](https://grc.plus/regulation/eu-data-act/#requirements)
- Switching terms in a written contract
  Applies to: Providers of data processing services
  Set out switching rights and obligations in a written contract, available to the customer before signing. Allow the customer to switch or port on request after a notice period of at most two months, within a transitional period of at most 30 calendar days. During the transition give reasonable assistance, keep the service running, tell the customer about known risks to continuity and keep a high level of security. Support the customer's exit strategy.
  [Data Act, Article 25(1) and (2)(a), (b) and (d)](https://grc.plus/regulation/eu-data-act/#requirements)

### Exit and termination

**Only Data Act** no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.SC

Nothing in the acts covered.

- Remove obstacles to switching
  Applies to: Providers of data processing services
  Take the measures in Articles 25, 26, 27, 29 and 30, and neither impose nor keep pre-commercial, commercial, technical, contractual or organisational obstacles to terminating the contract, signing with another provider, porting exportable data and digital assets, achieving functional equivalence, or unbundling where technically feasible.
  [Data Act, Article 23](https://grc.plus/regulation/eu-data-act/#requirements)
- Switching terms in a written contract
  Applies to: Providers of data processing services
  Set out switching rights and obligations in a written contract, available to the customer before signing. Allow the customer to switch or port on request after a notice period of at most two months, within a transitional period of at most 30 calendar days. During the transition give reasonable assistance, keep the service running, tell the customer about known risks to continuity and keep a high level of security. Support the customer's exit strategy.
  [Data Act, Article 25(1) and (2)(a), (b) and (d)](https://grc.plus/regulation/eu-data-act/#requirements)
- Data retrieval and erasure
  Applies to: Providers of data processing services
  Specify all categories of data and digital assets that can be ported, including at least all exportable data. Give a data retrieval period of at least 30 calendar days after the transitional period, and guarantee full erasure of exportable data and digital assets after that period once switching has succeeded.
  [Data Act, Article 25(2)(e), (g) and (h)](https://grc.plus/regulation/eu-data-act/#requirements)
- Longer transition where 30 days is not feasible
  Applies to: Providers of data processing services
  Where the 30 day transition is technically unfeasible, notify the customer within 14 working days of the switching request, justify it and propose an alternative period of at most seven months, keeping the service running throughout. The contract also lets the customer extend the transitional period once.
  [Data Act, Article 25(4) and (5)](https://grc.plus/regulation/eu-data-act/#requirements)
- Information on switching
  Applies to: Providers of data processing services
  Tell the customer about available switching and porting procedures, methods, formats and known limitations, and refer it to an up-to-date online register of data structures, formats, standards and open interoperability specifications for the exportable data.
  [Data Act, Article 26](https://grc.plus/regulation/eu-data-act/#requirements)
- Withdrawal of switching charges
  Applies to: Providers of data processing services
  Charge nothing for switching from 12 January 2027. From 11 January 2024 to 12 January 2027, reduced charges may be applied, limited to the costs directly linked to the switching. Before contracting, give clear information on standard fees, early termination penalties and any reduced switching charges, and on services where switching is highly complex or costly.
  [Data Act, Article 29(1) to (6)](https://grc.plus/regulation/eu-data-act/#requirements)
- Technical support for switching
  Applies to: Providers of data processing services
  Infrastructure providers take all reasonable measures in their power to help the customer reach functional equivalence with the destination service. Other providers offer open interfaces free of charge to customers and destination providers, and become compatible with common specifications or harmonised standards within 12 months of their publication in the central Union standards repository. Until those are published, export all exportable data in a structured, commonly used and machine-readable format on request.
  [Data Act, Article 30(1), (2), (3) and (5)](https://grc.plus/regulation/eu-data-act/#requirements)

## Privacy and data protection

### Lawful processing

**Only Data Act** no specific requirement on the other side in the acts covered

NIST Privacy Framework CT.PO-P

Nothing in the acts covered.

- Legal basis for personal data
  Applies to: Data holders
  Where the user is not the data subject, make personal data available to the user or third party only with a valid legal basis under GDPR Article 6 and, where relevant, under GDPR Article 9 and ePrivacy Article 5(3).
  [Data Act, Articles 4(12) and 5(7)](https://grc.plus/regulation/eu-data-act/#requirements)
- Third party limits on received data
  Applies to: Third parties receiving data at the user's request
  Process the data only for the purposes and under the conditions agreed with the user, and erase it when no longer needed for that purpose unless otherwise agreed for non-personal data. Do not make the user's choices unduly difficult, profile people unless needed for the requested service, or pass the data to another third party except under a contract with the user and with the agreed trade secret measures. Do not pass it to a gatekeeper, use it to develop a competing product or derive insights about the data holder, harm the product's security, disregard agreed trade secret measures, or stop a consumer user from sharing the data.
  [Data Act, Article 6(1) and (2)](https://grc.plus/regulation/eu-data-act/#requirements)

### Transparency

**Only Data Act** no specific requirement on the other side in the acts covered

NIST Privacy Framework CM.AW-P

Nothing in the acts covered.

- Pre-contract information on the data
  Applies to: Sellers, rentors and lessors of connected products, and providers of related services
  Before the contract, tell the user clearly what data the product generates or the service obtains, its type, format and estimated volume, where it is stored and for how long, and how the user can access, retrieve or erase it. Related service providers also state who the data holder is, how it intends to use the data, how to share data with a third party, the right to complain, any trade secrets, and the contract term and exit arrangements.
  [Data Act, Article 3(2) and (3)](https://grc.plus/regulation/eu-data-act/#requirements)
- Information on switching
  Applies to: Providers of data processing services
  Tell the customer about available switching and porting procedures, methods, formats and known limitations, and refer it to an up-to-date online register of data structures, formats, standards and open interoperability specifications for the exportable data.
  [Data Act, Article 26](https://grc.plus/regulation/eu-data-act/#requirements)
- Publish jurisdiction and access safeguards
  Applies to: Providers of data processing services
  Publish on the website, and keep up to date, the jurisdiction of the ICT infrastructure used for each service and a general description of the measures against international governmental access to non-personal data held in the Union where that conflicts with Union or national law. List those websites in contracts.
  [Data Act, Article 28](https://grc.plus/regulation/eu-data-act/#requirements)
- Withdrawal of switching charges
  Applies to: Providers of data processing services
  Charge nothing for switching from 12 January 2027. From 11 January 2024 to 12 January 2027, reduced charges may be applied, limited to the costs directly linked to the switching. Before contracting, give clear information on standard fees, early termination penalties and any reduced switching charges, and on services where switching is highly complex or costly.
  [Data Act, Article 29(1) to (6)](https://grc.plus/regulation/eu-data-act/#requirements)

### Rights of individuals

**Only Data Act** no specific requirement on the other side in the acts covered

NIST Privacy Framework CT.DM-P

Nothing in the acts covered.

- Data accessible by design and by default
  Applies to: Manufacturers of connected products and providers of related services
  Design and manufacture connected products, and design and provide related services, so that product and related service data and the metadata needed to use them are accessible to the user by default. Access is easy, secure, free of charge and in a comprehensive, structured, commonly used and machine-readable format, and direct where relevant and technically feasible. This applies to products and services placed on the market after 12 September 2026.
  [Data Act, Article 3(1)](https://grc.plus/regulation/eu-data-act/#requirements)
- Give the user access to readily available data
  Applies to: Data holders
  Where the user cannot access data directly, make readily available data and metadata accessible on a simple request, without undue delay, of the same quality as the data holder has, easily, securely, free of charge and in a machine-readable format, and continuously and in real time where relevant and technically feasible. Do not make the user's choices unduly difficult, ask only for the information needed to verify the user, and keep no access logs beyond what is necessary.
  [Data Act, Article 4(1), (4) and (5)](https://grc.plus/regulation/eu-data-act/#requirements)
- Share data with a third party at the user's request
  Applies to: Data holders and gatekeepers designated under the Digital Markets Act
  At the request of the user, or a party acting for the user, make readily available data and metadata available to a third party without undue delay, of the same quality as the data holder has, free of charge to the user and in a machine-readable format, under the terms of Articles 8 and 9. Gatekeepers under the Digital Markets Act are not eligible third parties.
  [Data Act, Article 5(1) and (3)](https://grc.plus/regulation/eu-data-act/#requirements)
- Exclusion for micro and small enterprises Optional
  Applies to: Micro and small enterprises, and medium-sized enterprises in their first year or for products in their first year on the market
  The Chapter II access and sharing obligations do not apply to data from products made or designed, or related services provided, by a micro or small enterprise, unless it has a larger partner or linked enterprise or is subcontracted to make, design or provide them. The same applies to an enterprise that has been medium-sized for less than one year, and to a medium-sized enterprise's products for one year after market placement.
  [Data Act, Article 7(1)](https://grc.plus/regulation/eu-data-act/#requirements)

### Impact assessment

**Only AI Act** no specific requirement on the other side in the acts covered

NIST Privacy Framework ID.RA-P

- Fundamental rights impact assessment
  Applies to: Public law bodies and private providers of public services deploying Article 6(2) systems (except Annex III, point 2), and deployers of Annex III, points 5(b) and (c) systems
  Before first use, assess the impact on fundamental rights: the processes involved, period and frequency of use, people affected, specific risks of harm, human oversight, and measures if risks materialise, including governance and complaints. Update it when elements change and notify the market surveillance authority of the results. You may cross-refer to an existing data protection impact assessment.
  [AI Act, Article 27(1) to (4)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

Nothing in the acts covered.

### International transfers

**Only Data Act** no specific requirement on the other side in the acts covered

Nothing in the acts covered.

- Publish jurisdiction and access safeguards
  Applies to: Providers of data processing services
  Publish on the website, and keep up to date, the jurisdiction of the ICT infrastructure used for each service and a general description of the measures against international governmental access to non-personal data held in the Union where that conflicts with Union or national law. List those websites in contracts.
  [Data Act, Article 28](https://grc.plus/regulation/eu-data-act/#requirements)
- Prevent unlawful governmental access
  Applies to: Providers of data processing services
  Take all adequate technical, organisational and legal measures, including contracts, to prevent international and third-country governmental access to or transfer of non-personal data held in the Union where it would conflict with Union or national law. A third-country decision is recognised or enforceable only if it is based on an international agreement.
  [Data Act, Article 32(1) and (2)](https://grc.plus/regulation/eu-data-act/#requirements)
- Handling third-country access requests
  Applies to: Providers of data processing services
  Without an international agreement, give access only where the Article 32(3) conditions on reasons, review and consideration of protected interests are met. If the provider asks the competent national body for its opinion and gets no reply within one month, or the body finds the conditions are not met, the provider may reject the request. It must ask that body where national security or defence may be affected. Provide the minimum data permissible, and inform the customer before complying unless the request serves law enforcement and only for as long as needed to keep that effective.
  [Data Act, Article 32(3) to (5)](https://grc.plus/regulation/eu-data-act/#requirements)

## Artificial intelligence

### Risk classification of AI systems

**Only AI Act** no specific requirement on the other side in the acts covered

- Prohibited AI practices
  Applies to: Operators of AI systems
  Do not place on the market, put into service or use AI that manipulates people or exploits their vulnerabilities causing, or likely to cause, significant harm, scores people socially leading to unjustified or out-of-context detriment, predicts crime from profiling alone, builds facial recognition databases by untargeted scraping, infers emotions at work or in education other than for medical or safety reasons, or categorises people biometrically to infer sensitive traits. Real-time remote biometric identification in public spaces for law enforcement is banned outside narrow exceptions.
  [AI Act, Article 5(1)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Intimate imagery and child sexual abuse material
  Applies to: Operators of AI systems
  Do not place on the market, put into service or use AI that generates or manipulates realistic non-consensual intimate or sexually explicit material of an identifiable person, or child sexual abuse material unless a national 'without right' defence applies. For providers the ban bites where this is the intended purpose, or a foreseeable and reproducible outcome without adequate safeguards. For deployers it bites where the system is used for that purpose. Manipulation that adds no exposure and does not alter the nature of the activity is outside the ban.
  [AI Act, Article 5(1)(ba), (bb), (1a), (1b)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Classify high-risk AI systems
  Applies to: Providers of AI systems
  Treat an AI system as high-risk where it is a safety component of a product, or is itself a product, under Annex I legislation that requires third-party conformity assessment, or where it falls in an Annex III use case. A third-party assessment required only for risks other than health and safety does not count. AI used only for non-safety assistance, optimisation, efficiency, convenience or quality control is not a safety component, unless its failure would endanger health and safety.
  [AI Act, Article 6(1), (1a) to (1c), (2)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Document an Annex III opt-out
  Applies to: Providers of Annex III AI systems they consider not high-risk
  An Annex III system is not high-risk only if it poses no significant risk and meets one of four conditions, such as a narrow procedural or preparatory task. It is always high-risk if it profiles people. A provider relying on this documents its assessment before placing the system on the market or putting it into service, registers it and gives the assessment to authorities on request.
  [AI Act, Article 6(3), (4)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

Nothing in the acts covered.

### Data and data governance

**Only AI Act** no specific requirement on the other side in the acts covered

- Special category data for bias correction Optional
  Providers may exceptionally process special categories of personal data where strictly necessary to detect and correct bias. Other data, including synthetic or anonymised data, must not be able to do the job, and the data must be secured, not passed to others, deleted once the bias is corrected or the retention period ends, and the reasons recorded.
  [AI Act, Article 4a(1)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Data sets and data governance
  Applies to: Providers of high-risk AI systems
  Apply governance to training, validation and testing data covering design choices, origin, preparation, data gaps and examination for bias, with measures to detect, prevent and mitigate it. Data sets must be relevant, sufficiently representative, as error-free and complete as possible, and fit the intended setting. Where no model is trained, this applies to testing data only.
  [AI Act, Article 10(1) to (4), (6)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Copyright policy and training content summary
  Applies to: Providers of general-purpose AI models
  Put in place a policy to comply with Union copyright law, including identifying and respecting rights reservations. Publish a sufficiently detailed summary of the content used for training, using the AI Office template.
  [AI Act, Article 53(1)(c), (d)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

Nothing in the acts covered.

### Transparency to users

**Only AI Act** no specific requirement on the other side in the acts covered

- Transparency and instructions for use
  Applies to: Providers of high-risk AI systems
  Design the system so deployers can interpret its output and use it properly. Supply clear instructions covering the provider's identity, intended purpose, tested accuracy, robustness and cybersecurity, foreseeable risks, human oversight measures, maintenance needs and how to collect and interpret logs.
  [AI Act, Article 13(1) to (3)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Tell workers and affected people
  Applies to: Deployers of high-risk AI systems, including employers
  Before using a high-risk system at the workplace, employers inform workers' representatives and affected workers. Deployers of Annex III systems that make or assist decisions about people tell those people that the system is used.
  [AI Act, Article 26(7), (11)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Disclose interaction with AI
  Applies to: Providers of AI systems that interact directly with people
  Design systems that interact directly with people so those people are told they are dealing with AI, unless this is obvious to a reasonably well-informed person. Give the information clearly at the latest at the first interaction, in an accessible form.
  [AI Act, Article 50(1), (5)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Mark synthetic content
  Applies to: Providers of AI systems, including general-purpose AI systems, that generate synthetic content
  Ensure outputs are marked in a machine-readable format and detectable as artificially generated or manipulated, with solutions that are effective, interoperable, robust and reliable as far as technically feasible. This does not apply to assistive standard editing or where the input is not substantially altered.
  [AI Act, Articles 50(2), 111(4)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Disclose emotion recognition and deep fakes
  Applies to: Deployers of emotion recognition, biometric categorisation or content-generating AI systems
  Inform people exposed to emotion recognition or biometric categorisation. Disclose that deep fake content, and text published to inform the public on matters of public interest, is artificially generated or manipulated. Artistic works carry a limited disclosure, and reviewed text under editorial responsibility is exempt.
  [AI Act, Article 50(3), (4)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Model documentation
  Applies to: Providers of general-purpose AI models
  Keep up-to-date technical documentation of the model for the AI Office and national authorities (Annex XI), and information for providers integrating the model (Annex XII). Open-source models with public parameters are exempt unless they carry systemic risk.
  [AI Act, Article 53(1)(a), (b), (2)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

Nothing in the acts covered.

### Human oversight

**Only AI Act** no specific requirement on the other side in the acts covered

- Design for human oversight
  Applies to: Providers of high-risk AI systems
  Design the system so people can effectively oversee it in use: understand its limits, watch for automation bias, interpret output, disregard or override it, and stop it safely. For remote biometric identification under Annex III, point 1(a), no action is taken on an identification unless at least two competent people verify it separately. This does not apply in law enforcement, migration, border control or asylum where Union or national law considers it disproportionate.
  [AI Act, Article 14(1), (3) to (5)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Use as instructed and assign oversight
  Applies to: Deployers of high-risk AI systems
  Use the system in line with its instructions through appropriate technical and organisational measures. Assign human oversight to people with the necessary competence, training, authority and support. Where you control input data, ensure it is relevant and sufficiently representative for the intended purpose.
  [AI Act, Article 26(1), (2), (4)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

Nothing in the acts covered.

### Conformity assessment and monitoring

**Only AI Act** no specific requirement on the other side in the acts covered

- Technical documentation
  Applies to: Providers of high-risk AI systems
  Draw up technical documentation with at least the Annex IV elements before placing the system on the market or putting it into service, and keep it up to date. SMEs and small mid-caps may use the Commission's simplified form. Products under Annex I, Section A legislation need a single set of documentation.
  [AI Act, Article 11(1), (2)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Monitor use and report problems
  Applies to: Deployers of high-risk AI systems
  Monitor operation on the basis of the instructions. If use may present a risk, inform the provider or distributor and the market surveillance authority without undue delay and suspend use. If you identify a serious incident, immediately inform the provider first, then the importer or distributor and the market surveillance authorities.
  [AI Act, Article 26(5)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Conformity assessment
  Applies to: Providers of high-risk AI systems
  Annex III, point 1 systems may choose internal control or a notified body where harmonised standards or common specifications are fully applied, and otherwise use a notified body. Annex III, points 2 to 8 use internal control, and Annex I, Section A systems follow the sectoral procedure. A substantial modification needs a new assessment. For systems that continue to learn, changes pre-determined at the initial assessment and documented are not a substantial modification.
  [AI Act, Article 43(1) to (4)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- EU declaration of conformity and CE marking
  Applies to: Providers of high-risk AI systems
  Draw up an EU declaration for each system with the Annex V content, keep it up to date and available for 10 years, and accept responsibility for compliance by drawing it up. Affix the CE marking visibly, legibly and indelibly, or digitally for systems provided digitally, with the notified body number where applicable.
  [AI Act, Articles 47, 48](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Post-market monitoring
  Applies to: Providers of high-risk AI systems
  Establish and document a post-market monitoring system, proportionate to the technology and risk, that actively collects and analyses performance data throughout the system's lifetime to evaluate continuing compliance. Base it on a plan held in the technical documentation.
  [AI Act, Article 72(1) to (3)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

Nothing in the acts covered.

## Supervision and enforcement

### Registration with authorities

**Only AI Act** no specific requirement on the other side in the acts covered

- Register in the EU database
  Applies to: Providers of Annex III AI systems or their authorised representatives
  Before placing on the market or putting into service an Annex III high-risk system, or a system you concluded is not high-risk under Article 6(3), register yourself and the system in the EU database. Critical infrastructure systems under Annex III, point 2 are registered at national level.
  [AI Act, Article 49(1), (2), (5)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Public bodies register their use
  Applies to: Deployers that are public authorities, Union bodies or persons acting on their behalf
  Before putting into service or using an Annex III high-risk system, other than a critical infrastructure system under point 2, register yourself, select the system and register its use in the EU database. Do not use a system that is not registered, and inform the provider or distributor.
  [AI Act, Articles 26(8), 49(3)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

Nothing in the acts covered.

### Cooperation with supervisors

**Data Act more detailed** more requirements on this, not necessarily stricter

- Keep documents and cooperate with authorities
  Applies to: Providers of high-risk AI systems
  Keep technical and quality system documentation, notified body decisions and the EU declaration available to authorities for 10 years. On a reasoned request, give the authority the information needed to show conformity and access to logs under your control.
  [AI Act, Articles 18(1), 21](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

- Restricting access for product security Optional
  Applies to: Data holders
  Users and data holders may agree by contract to restrict or prohibit access, use or further sharing where it could undermine the product's legal security requirements and seriously harm the health, safety or security of people. A data holder that refuses to share on this ground notifies the competent authority.
  [Data Act, Article 4(2)](https://grc.plus/regulation/eu-data-act/#requirements)
- Withhold or refuse data to protect trade secrets Optional
  Applies to: Data holders
  A data holder may withhold or suspend trade secret data where measures are not agreed, not implemented or confidentiality is undermined. In exceptional cases a trade secret holder may refuse a specific request if it shows serious economic damage is highly likely. The decision is reasoned and given in writing without undue delay, and the competent authority is notified.
  [Data Act, Articles 4(7), 4(8), 5(10) and 5(11)](https://grc.plus/regulation/eu-data-act/#requirements)
- Provide data to public bodies on an exceptional need
  Applies to: Data holders that are legal persons, other than public sector bodies
  On a duly reasoned request showing an exceptional need, make the data available to the public sector body, Commission, European Central Bank or Union body without undue delay. Decline or seek a change only on the listed grounds, within five working days for a public emergency and within 30 working days in other cases. Where declining because of an earlier request for the same purpose, name the body that made it. Anonymise personal data, or pseudonymise it where the request requires personal data.
  [Data Act, Articles 14 and 18(1) to (4)](https://grc.plus/regulation/eu-data-act/#requirements)

### Penalties and liability

**AI Act more detailed** more requirements on this, not necessarily stricter

- Fines for prohibited practices
  Applies to: Operators of AI systems
  Breach of the Article 5 prohibitions carries fines of up to EUR 35 million or 7% of total worldwide annual turnover, whichever is higher. For SMEs and start-ups the lower of the two applies.
  [AI Act, Article 99(3), (6)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Fines for operator obligations
  Applies to: Operators of AI systems and notified bodies
  Breach of the obligations of providers, authorised representatives, importers, distributors, deployers and notified bodies, or of Article 50 transparency, carries fines of up to EUR 15 million or 3% of total worldwide annual turnover, whichever is higher. For SMEs and small mid-caps the lower of the two applies.
  [AI Act, Article 99(4), (6), (6a)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Fines for misleading information
  Applies to: Anyone supplying information to notified bodies or national competent authorities in reply to a request
  Supplying incorrect, incomplete or misleading information to notified bodies or national authorities in reply to a request carries fines of up to EUR 7.5 million or 1% of total worldwide annual turnover, whichever is higher. For SMEs and small mid-caps the lower of the two applies.
  [AI Act, Article 99(5), (6), (6a)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)
- Fines for general-purpose AI model providers Optional
  Applies to: Providers of general-purpose AI models
  The Commission may fine a provider that intentionally or negligently infringes the Regulation, fails to answer an information request correctly, or does not comply with a requested measure or evaluation access, up to 3% of annual total worldwide turnover or EUR 15 million, whichever is higher.
  [AI Act, Article 101(1)](https://grc.plus/regulation/artificial-intelligence-act-ai-act/#requirements)

- Penalties
  Applies to: Member States
  Member States set effective, proportionate and dissuasive penalties and notify the requirements to the Commission by 12 September 2025. For Chapters II, III and V, data protection supervisory authorities may also impose fines within their competence, up to the GDPR Article 83(5) amount.
  [Data Act, Article 40(1), (2) and (4)](https://grc.plus/regulation/eu-data-act/#requirements)

Requirements are summarised in plain words; the official text prevails. Verdicts compare what the acts covered state, not how a supervisor applies them. Most topics are cross-referenced to NIST CSF 2.0 and ISO/IEC 27001:2022.

## More Comparisons

- [Compare AI Act](https://grc.plus/compare/ai-act/)
- [Compare Data Act](https://grc.plus/compare/data-act/)

Source: https://grc.plus/compare/ai-act-vs-data-act/
