EU Data Act Article 13 Unfair Contractual Terms

Article 13 does not review every commercial term in a technology contract. It applies to terms about access to and use of data, or liability and remedies for breach or termination of data-related obligations, when one enterprise has unilaterally imposed the term on another enterprise.

Chapter IV applies to contracts concluded after 12 September 2025. From 12 September 2027, it also applies to contracts concluded on or before 12 September 2025 if they are indefinite or are due to expire at least 10 years after 11 January 2024. Record the contract date, duration, expiry, and renewal mechanics before classifying a legacy contract.

Separate this Article 13 review from ordinary price negotiation and from the contract's main subject matter. The Data Act says Article 13 does not apply to terms defining the main subject matter of the contract or to the adequacy of the price as against the data supplied in exchange. A term that reflects mandatory Union law, or a Union-law rule that would govern if the contract were silent, is not unfair under Article 13.

The Article 13 threshold depends on negotiation facts. A term is treated as unilaterally imposed when one contracting party supplied it and the other party could not influence its content despite an attempt to negotiate it.

The supplier of the contested term bears the burden of proving that it was not unilaterally imposed and cannot defend its own supplied term by arguing that the term is unfair. Contract teams should therefore keep more than the final signed PDF: they need the redline trail, issue log, fallback language, and the counterparty response.

Article 13 has a general unfairness standard: the term must grossly deviate from good commercial practice in data access and use, contrary to good faith and fair dealing. It then gives examples that are always unfair and examples presumed to be unfair.

The distinction affects the analysis. Article 13(4) says its three categories shall be unfair. An Article 13(5) category is presumed to be unfair, so the imposing enterprise may rebut that presumption with the facts of the specific case. A term outside both lists can still fail the general standard.

Treat these examples as review categories for clause remediation. A clause can be problematic because it removes remedies, gives one side exclusive interpretive power, lets one side exploit the other party's data, blocks use or copies of generated data, traps the other party in the arrangement, or allows unjustified unilateral changes.

The European Commission has published non-binding Model Contractual Terms for Data Act data access and use, plus cloud Standard Contractual Clauses. Their use is voluntary, but they are useful remediation references because they were developed to help parties implement the Data Act and to support fairer contract design.

For this page's topic, the most relevant Commission material is the model-term package's explanation that the mandatory data-sharing MCT sets were drafted for data-holder, user, and data-recipient relationships, and that an additional voluntary data-sharing set was drafted to comply with Chapter IV unfairness control.

An Article 13 review should produce a clause-level record, not only a general legal note. The record should let a later reviewer see the original wording, the negotiation history, the Article 13 category, the proposed remediation, and the final business decision.

This evidence is especially important for standard terms, supplier paper, procurement frameworks, and repeated fallback clauses, because the unilateral-imposition question often turns on how the clause was supplied and handled in negotiations.

Remediation should turn Article 13 findings into controlled contract changes. When an unfair term is severable, Article 13 keeps the remaining terms binding. The Regulation does not state the contract-wide result when an unfair term is not severable, so that consequence depends on the contract and applicable law.

Prioritise recurring clauses first. A problematic clause in one live deal may also sit in public terms, supplier templates, procurement forms, API terms, product-data addenda, or partner playbooks.