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

# Data Act vs GDPR

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

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

[GDPR](https://grc.plus/regulation/general-data-protection-regulation-gdpr/)Controllers and processors

## At a Glance

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

- **Data Act** Asks more on 0 topics Alone on 2 topics More detailed on 4 topics
- **GDPR** Asks more on 0 topics Alone on 14 topics More detailed on 1 topic

| Topic | Data Act | GDPR | Verdict |
| --- | --- | --- | --- |
| Governance |  |  |  |
| Roles and independence | Data Act: – | GDPR: 2 | **Only GDPR**no specific requirement on the other side in the acts covered |
| Risk management |  |  |  |
| Risk management framework | Data Act: – | GDPR: 1 | **Only GDPR**no specific requirement on the other side in the acts covered |
| Risk assessment | Data Act: – | GDPR: 1 | **Only GDPR**no specific requirement on the other side in the acts covered |
| Protection |  |  |  |
| Cryptography and encryption | Data Act: – | GDPR: 1 | **Only GDPR**no specific requirement on the other side in the acts covered |
| Data security | Data Act: 6 | GDPR: 2 | **Data Act more detailed**more requirements on this, not necessarily stricter |
| Secure acquisition and development | Data Act: 1 | GDPR: – | **Only Data Act**no specific requirement on the other side in the acts covered |
| Human resources security | Data Act: – | GDPR: 1 | **Only GDPR**no specific requirement on the other side in the acts covered |
| Detection and response |  |  |  |
| Incident handling | Data Act: – | GDPR: 1 | **Only GDPR**no specific requirement on the other side in the acts covered |
| Reporting to authorities | Data Act: – | GDPR: 3 | **Only GDPR**no specific requirement on the other side in the acts covered |
| Informing customers and the public | Data Act: 1 | GDPR: 1 | **Both cover it**read the wording below |
| Continuity and resilience |  |  |  |
| Backup and recovery | Data Act: – | GDPR: 1 | **Only GDPR**no specific requirement on the other side in the acts covered |
| Security testing | Data Act: – | GDPR: 1 | **Only GDPR**no specific requirement on the other side in the acts covered |
| Third parties and supply chain |  |  |  |
| Supplier and third-party risk | Data Act: – | GDPR: 2 | **Only GDPR**no specific requirement on the other side in the acts covered |
| Contract requirements | Data Act: 8 | GDPR: 1 | **Data Act more detailed**more requirements on this, not necessarily stricter |
| Exit and termination | Data Act: 7 | GDPR: – | **Only Data Act**no specific requirement on the other side in the acts covered |
| Privacy and data protection |  |  |  |
| Lawful processing | Data Act: 2 | GDPR: 7 | **GDPR more detailed**more requirements on this, not necessarily stricter |
| Transparency | Data Act: 4 | GDPR: 2 | **Data Act more detailed**more requirements on this, not necessarily stricter |
| Rights of individuals | Data Act: 4 | GDPR: 7 | **Both cover it**read the wording below |
| Privacy by design and by default | Data Act: – | GDPR: 2 | **Only GDPR**no specific requirement on the other side in the acts covered |
| Impact assessment | Data Act: – | GDPR: 3 | **Only GDPR**no specific requirement on the other side in the acts covered |
| Records of processing | Data Act: – | GDPR: 2 | **Only GDPR**no specific requirement on the other side in the acts covered |
| Data protection officer | Data Act: – | GDPR: 2 | **Only GDPR**no specific requirement on the other side in the acts covered |
| International transfers | Data Act: 3 | GDPR: 4 | **Both cover it**read the wording below |
| Supervision and enforcement |  |  |  |
| Cooperation with supervisors | Data Act: 3 | GDPR: 1 | **Data Act more detailed**more requirements on this, not necessarily stricter |
| Penalties and liability | Data Act: 1 | GDPR: 2 | **Both cover it**read the wording below |

## 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

- [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.

Included

- [GDPR](https://grc.plus/regulation/general-data-protection-regulation-gdpr/) Regulation (EU) 2016/679 Articles 5 to 10, 12 to 22, 24 to 39, 44 to 49, 58, 83 · 50 requirements

Status

Reviewed against the official texts.

## Key Numbers

### Deadline

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)

GDPR: At the time the data are obtained (Controllers); Within a reasonable period and at the latest one month after obtaining the data; if used to contact the person, at the latest at first communication; if disclosure is envisaged, at the latest at first disclosure (Controllers); Without undue delay and in any event within one month of receipt of the request; extendable by two further months where necessary (Controllers); Without undue delay and in any event within one month of receipt of the request (Article 12(3)); extendable by two further months where necessary (Controllers); Without undue delay after becoming aware (Processors); Without undue delay (Controllers); Before the processing starts (Controllers); Before the processing starts; where the authority considers the processing would infringe, it gives written advice within up to eight weeks of receipt of the request, extendable by six weeks (Controllers)

### Threshold

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)

GDPR: Under 16; Member States may lower the age, not below 13 (Controllers offering information society services directly to children); Exemption only below 250 persons, and only if none of the listed conditions applies (Controllers)

### Goes to

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)

GDPR: Controller (Processors); Data subjects (Controllers)

### Evidence to keep

Data Act: Not in the acts covered

GDPR: Written record of processing activities (Controllers); Written record of processing activities (Processors); Internal record of each breach: facts, effects and remedial action (Controllers)

### Incident reports go to

Data Act: Not in the acts covered

GDPR: Competent supervisory authority (Controllers)

### First notice of an incident

Data Act: Not in the acts covered

GDPR: Without undue delay and, where feasible, within 72 hours of becoming aware (Controllers)

### Intermediate report

Data Act: Not in the acts covered

GDPR: In phases, without undue further delay (Controllers)

### Deadline to have the measures in place

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

GDPR: Not in the acts covered

### External assessment or certification

Data Act: Not in the acts covered

GDPR: Approved code of conduct or certification may help show compliance (Controllers)

### Review of the risk framework

Data Act: Not in the acts covered

GDPR: Where necessary (Controllers)

### Testing of critical systems

Data Act: Not in the acts covered

GDPR: Regularly

### Maximum fines

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)

GDPR: Up to EUR 10 million or, for an undertaking, 2% of total worldwide annual turnover of the preceding financial year, whichever is higher; Up to EUR 20 million or, for an undertaking, 4% of total worldwide annual turnover of the preceding financial year, whichever is higher

## Governance

### Roles and independence

**Only GDPR** 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

Nothing in the acts covered.

- Joint controllers
  Applies to: Joint controllers
  Joint controllers set out their respective responsibilities in an arrangement, unless EU or Member State law determines them, including who handles rights requests and information duties, and make its essence available to people. A person may exercise their rights against any of them regardless of the arrangement.
  [GDPR, Article 26](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- EU representative
  Applies to: Controllers and processors not established in the EU, under Article 3(2)
  A controller or processor outside the EU that falls under Article 3(2) designates a representative in writing, established in a Member State where the affected people are. Occasional low-risk processing without large-scale special category or criminal data, and public bodies, are exempt.
  [GDPR, Article 27](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

## Risk management

### Risk management framework

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

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

Nothing in the acts covered.

- Measures to ensure and show compliance
  Applies to: Controllers
  Put in place technical and organisational measures suited to the risks of the processing, so that it complies and the controller can show it does. Review and update them where needed. Where proportionate, these include data protection policies.
  [GDPR, Article 24](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

### Risk assessment

**Only GDPR** 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

Nothing in the acts covered.

- Assess security risk
  When judging the right level of security, weigh the risks of processing, in particular accidental or unlawful destruction, loss, alteration, and unauthorised disclosure of or access to personal data.
  [GDPR, Article 32(2)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

## Protection

### Cryptography and encryption

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

NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.8.24

Nothing in the acts covered.

- Pseudonymisation and encryption
  Apply pseudonymisation and encryption of personal data, as appropriate to the risk.
  [GDPR, Article 32(1)(a)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

### 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

- 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)

- Integrity and confidentiality
  Applies to: Controllers
  Process personal data with appropriate security, using appropriate technical or organisational measures, including protection against unauthorised or unlawful processing and against accidental loss, destruction or damage.
  [GDPR, Article 5(1)(f)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Security of systems and services
  Be able to keep processing systems and services confidential, intact, available and resilient on an ongoing basis, as appropriate to the risk.
  [GDPR, Article 32(1)(b)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

### Secure acquisition and development

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

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

- 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)

Nothing in the acts covered.

### Human resources security

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

NIST CSF 2.0 GV.RR · ISO/IEC 27001:2022 A.6.1 to A.6.6

Nothing in the acts covered.

- Staff act only on instructions
  Processors, and anyone with access to personal data under the authority of a controller or processor, process it only on the controller's instructions unless EU or Member State law requires otherwise. Controllers and processors take steps to ensure this.
  [GDPR, Articles 29 and 32(4)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

## Detection and response

### Incident handling

**Only GDPR** 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

Nothing in the acts covered.

- Document every breach
  Applies to: Controllers
  Record each personal data breach, whether notified or not, with its facts, effects and remedial action, so the authority can check compliance.
  [GDPR, Article 33(5)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

### Reporting to authorities

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

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

Nothing in the acts covered.

- Notify a personal data breach
  Applies to: Controllers
  Notify the competent supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware, unless the breach is unlikely to risk people's rights and freedoms. Give reasons if the notice is late.
  [GDPR, Article 33(1)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Processor tells the controller
  Applies to: Processors
  Tell the controller of a personal data breach without undue delay after becoming aware of it.
  [GDPR, Article 33(2)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- What the breach notice contains
  Applies to: Controllers
  Describe the breach, including the categories and approximate numbers of people and records where possible, the DPO or other contact point, the likely consequences, and the measures taken or proposed. Information not yet available may follow in phases.
  [GDPR, Article 33(3) and (4)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

### Informing customers and the public

**Both cover it** read the wording below

NIST CSF 2.0 RS.CO, RC.CO

- 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)

- Tell the people affected
  Applies to: Controllers
  Where a breach is likely to cause high risk to people, tell them in plain language without undue delay, with the contact point, likely consequences and measures. This is not needed where the data was unintelligible, for example encrypted, where later measures remove the high risk, or where a public notice replaces disproportionate effort. The authority may require notice.
  [GDPR, Article 34(1) to (4)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

## Continuity and resilience

### Backup and recovery

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

NIST CSF 2.0 PR.DS, RC.RP · ISO/IEC 27001:2022 A.8.13, A.8.14

Nothing in the acts covered.

- Restoring access after an incident
  Be able to restore availability of and access to personal data in a timely way after a physical or technical incident, as appropriate to the risk.
  [GDPR, Article 32(1)(c)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

### Security testing

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

NIST CSF 2.0 ID.IM · ISO/IEC 27001:2022 A.5.35, A.8.29, A.8.34

Nothing in the acts covered.

- Testing the measures
  Have a process to test and evaluate regularly whether the technical and organisational security measures work, as appropriate to the risk.
  [GDPR, Article 32(1)(d)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

## Third parties and supply chain

### Supplier and third-party risk

**Only GDPR** 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

Nothing in the acts covered.

- Use only processors with sufficient guarantees
  Applies to: Controllers
  Use only processors that give adequate assurances of technical and organisational measures that meet the Regulation and protect people's rights.
  [GDPR, Article 28(1)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Sub-processors
  Applies to: Processors
  Do not engage another processor without the controller's prior written authorisation, specific or general, and under general authorisation give notice of changes so the controller can object. Bind the sub-processor by contract to the same data protection obligations. The initial processor stays fully liable for the sub-processor's failures.
  [GDPR, Article 28(2) and (4)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

### 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

- 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)

- Processing contract
  Govern processing by a written contract or other legal act covering subject matter, duration, nature and purpose, data types, the people concerned and the controller's obligations and rights. It requires the processor to act on documented instructions, keep staff bound to confidentiality, secure the data, follow the sub-processor requirements, help with rights and Articles 32 to 36, delete or return data at the end at the controller's choice, provide compliance information and allow audits. The processor warns the controller at once if an instruction appears to breach data protection law.
  [GDPR, Article 28(3) and (9)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

### Exit and termination

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

NIST CSF 2.0 GV.SC

- 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)

Nothing in the acts covered.

## Privacy and data protection

### Lawful processing

**GDPR more detailed** more requirements on this, not necessarily stricter

NIST Privacy Framework CT.PO-P

- 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)

- Purpose limitation and data minimisation
  Applies to: Controllers
  Collect personal data for specified, explicit and legitimate purposes and do not use it later in a way that conflicts with them. Keep the data adequate, relevant and limited to what those purposes need.
  [GDPR, Article 5(1)(b) and (c)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Accuracy and storage limitation
  Applies to: Controllers
  Keep personal data accurate and, where needed, up to date, and take every reasonable step to erase or correct inaccurate data without delay. Keep data in a form that identifies people only for as long as the purpose needs, or longer solely for archiving, research or statistics under Article 89(1) with safeguards.
  [GDPR, Article 5(1)(d) and (e)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Accountability
  Applies to: Controllers
  The controller is responsible for meeting the data protection principles and must be able to demonstrate that it does.
  [GDPR, Article 5(2)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Lawful basis
  Applies to: Controllers
  Process personal data lawfully, fairly and transparently, and only where at least one basis applies: consent, contract, legal obligation, vital interests, a public-interest task or official authority, or legitimate interests. Legitimate interests do not apply where the person's interests or rights override them, and are not open to public authorities performing their tasks.
  [GDPR, Articles 5(1)(a) and 6(1)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Conditions for consent
  Applies to: Controllers
  Be able to prove consent, and keep a written consent request separate from other matters and in plain language. Let people withdraw at any time, as easily as they gave consent, and tell them so beforehand. Consent tied to a contract for data the contract does not need may not count as freely given.
  [GDPR, Article 7](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Children's consent to online services
  Applies to: Controllers offering information society services directly to children
  Where consent is the basis for processing in relation to offering an information society service directly to a child under the age limit, make sure consent is given or authorised by the holder of parental responsibility. Make reasonable efforts, given the available technology, to verify it.
  [GDPR, Article 8(1) and (2)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Special category and criminal offence data
  Applies to: Controllers
  Do not process special category data, such as health, biometric identification or genetic data, unless a condition in Article 9(2) applies. Process criminal conviction and offence data only under official authority or where EU or Member State law authorises it with safeguards.
  [GDPR, Articles 9 and 10](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

### Transparency

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

NIST Privacy Framework CM.AW-P

- 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)

- Information when collecting from the person
  Applies to: Controllers
  Tell people, concisely and in plain language, who the controller and any DPO are, the purposes and legal basis, any legitimate interests relied on, recipients, transfers, retention, their rights, whether they must provide the data, and any automated decision-making. Before using the data for a new purpose, give information on that purpose and any relevant further details. This is not needed where the person already has the information.
  [GDPR, Articles 12(1) and 13](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Information when data comes from elsewhere
  Applies to: Controllers
  Give the same information, plus the categories of data and their source, when the data was not obtained from the person. Exceptions include where the person already has it, where this proves impossible or takes disproportionate effort, in which case take appropriate measures to protect the person, including making the information public, or where law requires the obtaining or disclosure or professional secrecy applies.
  [GDPR, Article 14](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

### Rights of individuals

**Both cover it** read the wording below

NIST Privacy Framework CT.DM-P

- 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)

- Answer rights requests in time
  Applies to: Controllers
  Act on a request under Articles 15 to 22 and tell the person the outcome free of charge. If more time is needed for complex or numerous requests, say so and why within the first month. If no action will be taken, say why without delay and within the first month, and explain the right to complain to an authority and seek a judicial remedy. Manifestly unfounded or excessive requests may be charged for or refused, and the controller must show why.
  [GDPR, Article 12(3) to (5)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Right of access
  Applies to: Controllers
  Confirm whether personal data about the person is processed and give access to it, with a copy and information on purposes, data categories, recipients, retention, rights, source and automated decision-making. A reasonable fee may be charged for further copies. The right to a copy must not adversely affect the rights and freedoms of others.
  [GDPR, Article 15](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Rectification, restriction and telling recipients
  Applies to: Controllers
  Correct inaccurate data without undue delay and, taking account of the purposes, complete incomplete data. On request, restrict processing while accuracy is contested or an Article 21(1) objection is being checked, where processing is unlawful and the person prefers restriction to erasure, or where the controller no longer needs the data but the person needs it for legal claims. Tell each recipient of any rectification, erasure or restriction unless this proves impossible or takes disproportionate effort, and tell the person who the recipients are if asked.
  [GDPR, Articles 16, 18 and 19](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Right to erasure
  Applies to: Controllers
  Erase personal data without undue delay where it is no longer needed, consent is withdrawn with no other basis, the person objects under Article 21(1) without overriding grounds or objects to direct marketing, processing was unlawful, law requires it, or it was collected for an information society service under Article 8(1). If the data was made public, take reasonable steps to tell other controllers of the request. The right does not apply where processing is needed for freedom of expression, a legal obligation or public task, public health, archiving, research or statistics where erasure would seriously impair them, or legal claims.
  [GDPR, Article 17](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Right to data portability
  Applies to: Controllers
  Where processing is automated and rests on consent or contract, give people, on request, the data they provided in a structured, commonly used, machine-readable format. On request, send it directly to another controller where technically feasible. The right does not apply to public-task processing and must not adversely affect the rights of others.
  [GDPR, Article 20](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Right to object
  Applies to: Controllers
  Stop processing based on a public task or legitimate interests when the person objects on grounds of their particular situation, unless the controller demonstrates compelling legitimate grounds that override the person's interests, or legal claims. Stop direct marketing, and related profiling, on objection without exception. Present this right clearly and separately, at the latest at first communication.
  [GDPR, Article 21](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Solely automated decisions
  Applies to: Controllers
  Do not subject people to decisions based solely on automated processing, including profiling, with legal or similarly significant effects, unless a contract need, law or explicit consent allows it. In the contract and consent cases, provide human intervention, a chance to give a view and a way to contest the decision. Special category data needs further conditions and safeguards.
  [GDPR, Article 22](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

### Privacy by design and by default

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

NIST Privacy Framework CT.DP-P

Nothing in the acts covered.

- Data protection by design
  Applies to: Controllers
  When deciding how to process and during processing, apply measures such as pseudonymisation that put the data protection principles into effect and build safeguards into the processing. Take account of the state of the art, cost and risk.
  [GDPR, Article 25(1)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Data protection by default
  Applies to: Controllers
  By default, process only the data needed for each purpose, in amount, extent, storage period and accessibility. Do not make personal data available to an indefinite number of people without the person's intervention.
  [GDPR, Article 25(2)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

### Impact assessment

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

NIST Privacy Framework ID.RA-P

Nothing in the acts covered.

- When an impact assessment is needed
  Applies to: Controllers
  Assess the impact on personal data before processing that is likely to cause high risk, especially with new technologies. It is required for systematic and extensive automated evaluation with legal or similarly significant effects, large-scale special category or criminal data, and large-scale systematic monitoring of a publicly accessible area.
  [GDPR, Article 35(1) and (3)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- What the assessment contains
  Applies to: Controllers
  Describe the processing and its purposes, assess necessity and proportionality, assess the risks to people, and set out the measures to address them. Seek the advice of the DPO where one is designated, and where appropriate the views of those affected. Where necessary, review whether processing follows the assessment, at least when the risk changes.
  [GDPR, Article 35(2), (7), (9) and (11)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Prior consultation
  Applies to: Controllers
  Consult the supervisory authority before processing if the assessment shows the processing would result in a high risk in the absence of measures taken by the controller to mitigate it. Provide responsibilities, purposes and means, safeguards, DPO contact details, the assessment and anything else the authority asks for.
  [GDPR, Article 36(1) to (3)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

### Records of processing

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

NIST Privacy Framework ID.IM-P

Nothing in the acts covered.

- Controller's record of processing
  Applies to: Controllers
  Keep a written or electronic record of the name and contact details of the controller and any joint controller, representative and DPO, purposes, categories of people, data and recipients, transfers, erasure time limits and security measures where possible, and show it to the authority on request. The duty does not apply to organisations under 250 persons, unless the processing is likely to risk people's rights, is not occasional, or includes special category or criminal data.
  [GDPR, Article 30(1), (3), (4) and (5)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Processor's record of processing
  Applies to: Processors
  Keep a written or electronic record of the name and contact details of the processor, each controller served and any representative and DPO, the categories of processing for each controller, transfers and, where possible, security measures. Show it to the authority on request. The same 250-person exemption applies.
  [GDPR, Article 30(2) to (5)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

### Data protection officer

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

NIST Privacy Framework GV.PO-P

Nothing in the acts covered.

- Designate a data protection officer
  Designate a DPO if the organisation is a public body, except courts acting in their judicial capacity, if its core activities need regular and systematic large-scale monitoring of people, or if they involve large-scale special category or criminal data. Choose the DPO for expertise in data protection law and practice. Publish the DPO's contact details and give them to the authority.
  [GDPR, Article 37(1), (5) and (7)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Position and tasks of the DPO
  Involve the DPO promptly in all data protection issues and give the resources and access needed. The DPO takes no instructions on these tasks, cannot be dismissed or penalised for doing them, and reports to the highest management level, and other duties must not create a conflict of interests. The DPO advises, monitors compliance including staff training and audits, advises on impact assessments and acts as contact point for the authority.
  [GDPR, Articles 38 and 39](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

### International transfers

**Both cover it** read the wording below

- 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)

- Transfers need a Chapter V ground
  Transfer personal data to a third country or international organisation, including onward transfers, only under the conditions of Chapter V. A Commission adequacy decision allows a transfer without specific authorisation.
  [GDPR, Articles 44 and 45](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Appropriate safeguards
  Without an adequacy decision, transfer only with appropriate safeguards and enforceable rights and remedies for people. Options without specific authority approval include binding corporate rules approved under Article 47, standard data protection clauses, and approved codes or certification with binding commitments. Bespoke contractual clauses need the authority's authorisation.
  [GDPR, Articles 46 and 47](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Third-country orders
  Treat a third-country court or authority order to transfer or disclose personal data as recognised or enforceable only where it rests on an international agreement, such as a mutual legal assistance treaty, without prejudice to other Chapter V grounds.
  [GDPR, Article 48](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Derogations for specific situations
  Without adequacy or safeguards, transfer only on a listed ground such as explicit informed consent, contract need, important public interest, legal claims or vital interests. As a last resort, a non-repetitive transfer about few people may rest on compelling legitimate interests not overridden by the person's interests or rights, if the controller assesses it, applies safeguards, informs the authority and the people concerned, and records it. Public authorities exercising public powers cannot use the consent, contract or last-resort grounds.
  [GDPR, Article 49](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

## Supervision and enforcement

### Cooperation with supervisors

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

- 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)

- Cooperate with supervisory authority powers
  Cooperate with the supervisory authority on request. The authority can order information, audit, access data and premises, and issue warnings, reprimands and orders, including a processing ban, suspension of data flows or a fine.
  [GDPR, Articles 31 and 58](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)

### Penalties and liability

**Both cover it** read the wording below

- 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)

- Fines for operational obligations
  Infringing the duties of controllers and processors in Articles 8, 11, 25 to 39, 42 and 43, or of certification and monitoring bodies, can be fined, and fines are set case by case to be effective, proportionate and dissuasive. Several infringements in the same or linked processing operations are capped at the amount for the gravest one.
  [GDPR, Article 83(1) to (4)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements)
- Fines for principles, rights and transfers
  Infringing the principles and consent requirements in Articles 5, 6, 7 and 9, rights in Articles 12 to 22, transfer requirements in Articles 44 to 49, Member State law adopted under Chapter IX, or ignoring an authority's order or denying it access can be fined at the higher level.
  [GDPR, Article 83(5) and (6)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#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 Data Act](https://grc.plus/compare/data-act/)
- [Compare GDPR](https://grc.plus/compare/gdpr/)

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