--- title: "EU Data Act Unfair Contractual Terms FAQ" canonical_url: "https://www.sorena.io/artifacts/eu/data-act/faq/unfair-contractual-terms" source_url: "https://www.sorena.io/artifacts/eu/data-act/faq/unfair-contractual-terms" author: "Sorena AI" description: "FAQ on Article 13 of the EU Data Act: B2B unfair contract terms, unilateral take-it-or-leave-it clauses, always-unfair terms, presumed-unfair terms, SMEs, model terms, and review evidence." published_at: "2026-05-06" updated_at: "2026-05-06" keywords: - "EU Data Act Article 13" - "unfair contractual terms" - "B2B data contracts" - "unilaterally imposed terms" - "model contractual terms" - "EU Data Act" - "Regulation (EU) 2023/2854" - "Article 13" --- **[SORENA](https://www.sorena.io/)** - AI-Powered GRC Platform [Home](https://www.sorena.io/) | [Solutions](https://www.sorena.io/solutions) | [Artifacts](https://www.sorena.io/artifacts) | [About Us](https://www.sorena.io/about-us) | [Contact](https://www.sorena.io/contact) | [Portal](https://app.sorena.io) --- # EU Data Act Unfair Contractual Terms FAQ FAQ on Article 13 of the EU Data Act: B2B unfair contract terms, unilateral take-it-or-leave-it clauses, always-unfair terms, presumed-unfair terms, SMEs, model terms, and review evidence. *FAQ* *EU* *Data Act* ## EU Data Act Unfair Contractual Terms FAQ Article 13 of the Data Act makes certain unfair B2B data contract terms non-binding when one enterprise unilaterally imposes them on another. Use this FAQ to screen data access and use clauses, liability and remedy language, termination rights, unilateral change rights, and model-term evidence. This FAQ explains the Data Act rules on unfair contractual terms in business-to-business data contracts. It focuses on Article 13: when a data-related clause is treated as unilaterally imposed, which terms are always unfair, which terms are presumed unfair, what remains outside the unfairness test, and what contract review evidence teams should keep. ## What does Article 13 of the EU Data Act do for B2B data contracts? The Data Act context is the starting point for this answer. Article 13 protects one enterprise from unfair data-related contract terms unilaterally imposed by another enterprise. The rule covers terms about access to and use of data, and terms about liability and remedies for breach or termination of data-related obligations. If the term is unfair under Article 13, it is not binding on the enterprise on which it was imposed. The rest of the contract can still bind the parties if the unfair term can be severed from the remaining terms. - Use Article 13 for B2B terms about data access, data use, liability, remedies, breach, or termination of data-related obligations. - Do not treat Article 13 as a general review of every commercial clause; the term must be data-related in the Article 13 sense. - Record whether the challenged clause was imposed on one enterprise by another and whether it can be severed from the contract. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Article 13 defines the B2B unfair-terms rule, the data-related clauses it covers, and the effect that an unfair term is not binding. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer confirms that Chapter IV protects businesses, especially SMEs, from unfair contractual terms related to data sharing. ## When is a Data Act contract term considered unilaterally imposed? The Data Act context is the starting point for this answer. A term is treated as unilaterally imposed when one contracting party supplied it and the other party could not influence its content despite trying to negotiate it. This is the practical issue behind take-it-or-leave-it data access and data use clauses. The party that supplied the contested term bears the burden of proving that it was not unilaterally imposed. The same party cannot use Article 13 to argue that its own supplied term is unfair. - Keep the proposed template clause, negotiation comments, redlines, rejection emails, and fallback positions. - Mark whether the counterparty actually had a realistic chance to change the data-related term. - For standard templates, distinguish terms that were merely accepted from terms that were genuinely negotiated. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Article 13(6) explains unilateral imposition and places the burden of proving the opposite on the party that supplied the term. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer describes the practical trigger as a stronger party imposing a non-negotiable take-it-or-leave-it term. ## What is the general unfairness test under Article 13 under the Data Act? The Data Act context is the starting point for this answer. The general test is whether the term grossly deviates from good commercial practice in data access and use, contrary to good faith and fair dealing. That test matters for terms not already captured by the Article 13 always-unfair or presumed-unfair examples. A practical review should compare the clause against the Data Act purpose of fair data access and use, the parties' bargaining position, the data involved, the impact on legitimate interests, and the remedies available if obligations are not performed. - State the clause text and the data-related obligation it affects. - Explain the commercial impact on the enterprise that did not supply the term. - Record whether the clause blocks access, use, remedies, termination, data copies, or reasonable control of generated data. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Article 13(3) states the general unfairness standard based on good commercial practice, good faith, and fair dealing. ## Which Data Act terms are always considered unfair for Unfair Contractual Terms implementation evidence? The Data Act context is the starting point for this answer. Article 13 lists three types of terms that are unfair where their object or effect matches the list. These are the closest equivalent to a black-list review for B2B data contracts. The always-unfair examples cover terms that exclude or limit the imposing party's liability for intentional acts or gross negligence, remove remedies for the enterprise on which the term was imposed, or give the imposing party the exclusive right to decide data conformity or interpret the contract. - Flag any clause that limits the imposing party's liability for intentional acts or gross negligence. - Flag any clause that removes remedies for non-performance or breach of data-related obligations. - Flag any clause giving the imposing party sole power to decide whether supplied data conforms to the contract or what a term means. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Article 13(4) identifies terms that are unfair because of their object or effect, including liability exclusions, remedy exclusions, and exclusive interpretation rights. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer summarizes the Data Act's non-exhaustive list of terms always considered unfair. ## Which Data Act terms are presumed to be unfair for Unfair Contractual Terms implementation evidence? The Data Act context is the starting point for this answer. Article 13 also lists terms presumed unfair. These are not automatically final in the same way as the always-unfair terms: the party that imposed the term can try to show that the term is not unfair. The presumed-unfair group includes inappropriate limits on remedies or liability, harmful access to or use of the other party's data, preventing the other party from using data it provided or generated, blocking termination within a reasonable period, blocking a copy of provided or generated data, termination at unreasonably short notice, or substantial unilateral changes to price or data-sharing conditions without a valid reason and termination right. - Review remedy caps, liability extensions, data-use rights, termination rights, copy/export rights, notice periods, and unilateral change clauses. - Pay close attention to commercially sensitive data, trade secrets, and intellectual property rights when the imposing party claims broad access or use rights. - If the term is only presumed unfair, keep the imposing party's written justification and the reasons it does or does not overcome the presumption. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Article 13(5) lists presumed-unfair terms, including remedy limits, harmful data use, blocked data use, blocked copies, short-notice termination, and unilateral changes. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer confirms that presumed-unfair terms may be defended by the entity that imposed them. ## Are price and main-subject-matter clauses reviewed under the Data Act unfair-terms rule? The Data Act context is the starting point for this answer. 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. That exclusion should be recorded before treating a pricing or core-scope clause as an Article 13 unfair term. The exclusion is narrow in practice. A price number or core data-sharing description may sit beside other reviewable terms, such as unilateral changes to price, format, quality, quantity, termination, remedies, or copy rights. - Separate the main subject matter and price adequacy from surrounding data access, use, remedy, and unilateral-change clauses. - Do not use the exclusion to ignore a data-related remedy, liability, termination, or unilateral change term. - Keep the review note short: excluded under Article 13(8), reviewable elsewhere, or not an Article 13 issue. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Article 13(8) excludes main-subject-matter terms and adequacy of price against supplied data from the Article 13 unfairness control. ## When do the Data Act unfair-terms rules apply to new and older contracts? The Data Act applies from 12 September 2025, and Chapter IV applies to contracts concluded after 12 September 2025. Older contracts concluded on or before 12 September 2025 enter Chapter IV from 12 September 2027 only if they are of indefinite duration or are due to expire at least 10 years from 11 January 2024. For contract operations, keep a contract population view that separates new contracts, renewals or amendments, indefinite-duration contracts, and very long-running older contracts. Do not apply the older-contract rule to every legacy agreement without checking the duration criteria. - Record contract signature date, renewal or amendment date, expiry date, and whether the contract is indefinite. - Flag post-12 September 2025 templates for Article 13 review before signature. - For older contracts, flag only indefinite-duration contracts and contracts due to expire at least 10 years from 11 January 2024 for the 12 September 2027 Chapter IV review. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Article 50 sets the Data Act application date and the Chapter IV timing for new and qualifying older contracts. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer confirms that the Data Act applies since 12 September 2025. ## How do SMEs and larger enterprises fit into the unfair-contract-terms review under the Data Act? The Data Act context is the starting point for this answer. Chapter IV is framed as protection for all businesses, with particular relevance for SMEs facing stronger bargaining positions in data-sharing negotiations. Article 13 itself applies to an enterprise on which a covered unfair term has been unilaterally imposed by another enterprise. SME status is still operationally important. The Commission says the model contractual terms were developed to help parties, especially SMEs, implement the Data Act, and the Data Act explainer highlights Chapter IV as a tool against stronger parties imposing non-negotiable data access and use terms. - Capture whether the party receiving the term is an SME, but do not assume Article 13 is limited to SMEs. - Use bargaining position, template control, and negotiation evidence to assess unilateral imposition. - When an SME receives a take-it-or-leave-it data clause, prioritize review of liability, remedies, data-use restrictions, data-copy rights, termination, and unilateral-change language. Sources for this answer: - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer states that Chapter IV protects all businesses, especially SMEs, against unfair terms imposed by stronger players. - [European Commission - Model contractual terms and cloud SCCs](https://digital-strategy.ec.europa.eu/en/library/draft-recommendation-non-binding-model-contractual-terms-data-access-and-use-and-non-binding?ref=sorena.io) - Commission source says the non-binding model terms were developed to help parties, especially SMEs, implement the Data Act. ## How should teams use the Commission model contractual terms with Article 13 under the Data Act? The Commission model contractual terms are voluntary tools, not a replacement for Article 13. They can help draft Data Act data-sharing contracts and benchmark whether a clause structure is aligned with fair, reasonable, and non-discriminatory rights and obligations. The Commission source says the model contractual terms for Data Act data sharing are compliant with Chapter IV on unfair contract terms. Teams should still adapt them to the actual data-sharing relationship and keep a clause-by-clause rationale when changing them. - Start with the relevant relationship: data holder to user, user to data recipient, data holder to data recipient, or voluntary data sharer to data recipient. - Document any departure from the model term where the change affects access, use, remedies, liability, termination, compensation, or trade secret protection. - Do not present model terms as mandatory; keep the Article 13 fairness review separate from the decision to use model wording. Sources for this answer: - [European Commission - Model contractual terms and cloud SCCs](https://digital-strategy.ec.europa.eu/en/library/draft-recommendation-non-binding-model-contractual-terms-data-access-and-use-and-non-binding?ref=sorena.io) - Commission source describes the model contractual terms as voluntary and mainly drafted for B2B contracts, with sets for Data Act data-sharing relationships. - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Article 41 requires the Commission to develop and recommend non-binding model contractual terms for data access and use. ## What evidence should a Data Act unfair-terms contract review keep? The Data Act context is the starting point for this answer. Keep enough evidence to show the clause text, who supplied it, whether the other party tried to negotiate it, the data-related obligation affected, the Article 13 category considered, and the final outcome. The file should let a later reviewer distinguish a negotiated clause from a unilateral template clause. For practical contract review, use a matrix with fields for clause location, data type or dataset, contract relationship, Article 13 category, always-unfair or presumed-unfair flag, negotiation evidence, fallback wording, approver, and date. Add model-term comparison where the Commission wording was used or intentionally changed. - Retain clause versions, comments, counterparty objections, internal approvals, and final signed wording. - Record whether the term was removed, rewritten, justified, severed, or left because Article 13 did not apply. - Link the review to the contract population so older qualifying agreements can be found without repeating the whole analysis. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Article 13 makes negotiation history and supplier burden relevant because the party supplying the term must prove it was not unilaterally imposed. - [European Commission - Model contractual terms and cloud SCCs](https://digital-strategy.ec.europa.eu/en/library/draft-recommendation-non-binding-model-contractual-terms-data-access-and-use-and-non-binding?ref=sorena.io) - Commission source supports using model terms as practical drafting references while preserving voluntary adaptation. ## What Data Act source evidence should teams keep for the Unfair Contractual Terms FAQ decision? Keep the legal basis and the decision trail together. For Article 13 work, the record should cite the Data Act source clause, the specific Article 13 paragraph used, the Commission guidance or model-term reference relied on, and the contract version that was reviewed. That makes it clear why a term was treated as unilaterally imposed, always unfair, presumed unfair, or outside the scope of Article 13. Teams should also retain the implementation artifact that shows how the decision was applied in practice, such as the redlined contract, review memo, approved template, or deviation note. - Keep the cited Data Act article text, the source URL, the review date, and the reviewer or approver. - Store the clause draft, final wording, and any negotiation evidence together with the implementation artifact. - Note whether the outcome was removal, severance, rewrite, or no change because the clause fell outside Article 13. ## How should teams assign ownership for Data Act Unfair Contractual Terms implementation work? Assign one accountable owner who can change the contract or workflow affected by Article 13. For a Data Act unfair-terms review, that is usually the legal or commercial lead for the contract, with procurement, product, cloud, support, or security teams consulted where their process is affected. For implementation, ownership should track the action: one owner for template updates, one owner for contract review approvals, and one owner for operational follow-up on the workflow or system that uses the clause. That avoids a generic checklist and makes the decision executable. - Name a single accountable owner for each Article 13 action, such as template update, deal review, or process change. - Record the affected workflow, the evidence artifact, and the review trigger beside the owner. - List consulted teams separately so accountability stays with the team that can actually make the change. ## Primary sources - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Primary legal source for Article 13 unfair contractual terms, Article 41 model terms, and Article 50 application timing. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer for Chapter IV, including take-it-or-leave-it terms, SME relevance, always-unfair and presumed-unfair examples, and severability. - [European Commission - Model contractual terms and cloud SCCs](https://digital-strategy.ec.europa.eu/en/library/draft-recommendation-non-binding-model-contractual-terms-data-access-and-use-and-non-binding?ref=sorena.io) - Commission source for voluntary model contractual terms and standard contractual clauses developed to help parties, especially SMEs, implement the Data Act. ## Topic Guides - [Data Act and Common European Data Spaces](/artifacts/eu/data-act/data-act-and-common-european-data-spaces.md): How Data Act Article 33 connects data-space participation with metadata, vocabularies, APIs, access terms, data quality, governance, and standards monitoring. - [Data Act and Data Governance Act Overlap FAQ](/artifacts/eu/data-act/faq/data-governance-act-overlap.md): FAQ explaining where the EU Data Act and Data Governance Act overlap, how they differ, and how to route product, cloud, public-sector reuse, intermediary, and data altruism workflows. - [Data Act and GDPR Personal Data Overlap FAQ](/artifacts/eu/data-act/faq/gdpr-personal-data-overlap.md): FAQ on how the EU Data Act works when connected-product or related-service data includes personal data, mixed datasets, GDPR roles, lawful basis, trade secrets, and third-party sharing. - [Data Act Audit Evidence And Request Logs FAQ](/artifacts/eu/data-act/faq/audit-evidence-and-request-logs.md): FAQ for Data Act request logs covering user and third-party access, B2G exceptional need requests, cloud switching records, contract terms, trade secrets, and GDPR boundaries. - [Data Act B2B Data-Sharing Contract Clauses](/artifacts/eu/data-act/b2b-data-sharing-contract-clauses.md): Clause guide for EU Data Act B2B data sharing: FRAND terms, compensation, trade secret safeguards, recipient limits, termination, logs, and GDPR boundaries. - [Data Act B2B Data-Sharing Contract Template](/artifacts/eu/data-act/b2b-data-sharing-contract-template.md): A usable EU Data Act B2B data-sharing template outline covering access requests, data schedules, permitted use, trade secrets, security, compensation, GDPR boundaries, audit records, and termination. - [Data Act B2G Exceptional-Need Requests](/artifacts/eu/data-act/b2g-exceptional-need-requests.md): A grounded guide to EU Data Act Chapter V requests from public bodies: exceptional need, public emergencies, request contents, limits, safeguards, costs, and records. - [Data Act Cloud Switching Compliance Checklist](/artifacts/eu/data-act/cloud-switching-compliance-checklist.md): A grounded EU Data Act checklist for cloud and data processing service providers covering switching clauses, notices, export formats, charges, interoperability, and evidence. - [Data Act Cloud Switching Contract Terms FAQ](/artifacts/eu/data-act/faq/cloud-switching-contract-terms.md): FAQ on EU Data Act cloud switching contract terms: Article 25 clauses, assistance, notice, transition, charges, export, termination, interoperability, and records. - [Data Act Cloud Switching Fees And Deadlines FAQ](/artifacts/eu/data-act/faq/cloud-switching-fees-and-deadlines.md): FAQ on EU Data Act cloud switching charges, 2027 fee removal, notice periods, transition windows, data retrieval, contract terms, and evidence records. - [Data Act Complaints and Dispute Settlement FAQ](/artifacts/eu/data-act/faq/complaints-and-dispute-settlement.md): FAQ on EU Data Act complaints, competent authorities, dispute settlement bodies, B2B data-sharing disputes, B2G requests, cloud switching disputes, and evidence records. - [Data Act Exportable Data and Metadata FAQ](/artifacts/eu/data-act/faq/exportable-data-and-metadata.md): FAQ explaining which product, related service, metadata, and cloud switching data must be exportable under the EU Data Act, and which data can be excluded. - [Data Act FAQ for Aftermarket Repair and Mobility Services](/artifacts/eu/data-act/faq/aftermarket-repair-and-mobility-services.md): FAQ on EU Data Act vehicle-data access for repairers, independent service providers, fleets, insurers, and mobility services. - [Data Act Functional Equivalence FAQ](/artifacts/eu/data-act/faq/functional-equivalence.md): FAQ on Data Act functional equivalence for cloud switching: IaaS scope, customer outcomes, export support, interoperability duties, limits, and evidence. - [Data Act Indirect Access Request Flows FAQ](/artifacts/eu/data-act/faq/indirect-access-request-flows.md): FAQ for Data Act teams handling user and third-party data requests when direct connected-product access is unavailable, incomplete, or limited. - [Data Act International Government Access FAQ](/artifacts/eu/data-act/faq/international-government-access.md): FAQ on EU Data Act safeguards for non-EU government access to non-personal data held in the Union by data processing service providers. - [Data Act Interoperability Standards FAQ](/artifacts/eu/data-act/faq/interoperability-standards.md): FAQ on EU Data Act interoperability standards for data spaces, cloud switching, smart contracts, harmonised standards, common specifications, and M/614. - [Data Act Model Contractual Terms FAQ](/artifacts/eu/data-act/faq/model-contractual-terms.md): FAQ on the EU Data Act non-binding model contractual terms for data access and use, cloud switching clauses, B2B use, unfair terms, and evidence. - [Data Act Public Emergency Requests FAQ](/artifacts/eu/data-act/faq/public-emergency-requests.md): FAQ on EU Data Act public emergency requests: exceptional need, request content, timing, data holder response, compensation, confidentiality, and records. - [Data Act Smart Contracts for Data Sharing](/artifacts/eu/data-act/smart-contracts-for-data-sharing.md): Data Act Article 36 smart contract guide for data-sharing agreements: scope, robustness, access control, termination, interruption, archiving, standards status, and conformity evidence. - [Data Act SME Exceptions and Startups FAQ](/artifacts/eu/data-act/faq/sme-exceptions-and-startups.md): FAQ on where the EU Data Act gives micro, small, medium-sized, startup, and SME actors narrower treatment for access duties, compensation, and B2B terms. - [Data Act Trade Secret Technical Protection Measures FAQ](/artifacts/eu/data-act/faq/trade-secret-technical-protection-measures.md): FAQ on how EU Data Act data holders can protect trade secrets with confidentiality safeguards, technical measures, limited withholding, suspension, refusal, and evidence. - [Data Act Trade Secrets and Protection Measures](/artifacts/eu/data-act/trade-secrets-and-protection.md): Data Act guide for protecting trade secrets during access and sharing: classification, safeguards, refusal thresholds, notices, evidence records, and reviews. - [Data Act Unfair Contractual Terms | Article 13 B2B Contract Review](/artifacts/eu/data-act/unfair-contractual-terms.md): Review B2B data-sharing clauses under EU Data Act Article 13: unilateral terms, always unfair examples, presumed unfair terms, model clauses, evidence, and remediation. - [Data Act Vehicle Data Guidance](/artifacts/eu/data-act/vehicle-data-guidance.md): Commission-grounded guide to Data Act vehicle data access: connected vehicles, vehicle-related services, raw and pre-processed data, aftermarket use cases, access routes, safeguards, and GDPR boundaries. - [Data Act vs GDPR: connected-product data access](/artifacts/eu/data-act/data-act-vs-gdpr.md): Compare EU Data Act connected-product access duties with GDPR personal-data rules: scope, roles, lawful basis, data subject rights, third-party sharing, trade secrets, and conflicts. - [EU Data Act and Common European Data Spaces FAQ](/artifacts/eu/data-act/faq/data-act-and-common-european-data-spaces.md): FAQ on how EU Data Act interoperability duties, Data Governance Act rules, and sector data-space governance fit together without treating participation as a general obligation. - [EU Data Act Applicability Test](/artifacts/eu/data-act/applicability-test.md): Check whether a product, related service, data holder, cloud service, data-space role, smart contract, or B2G request is in scope of the EU Data Act. - [EU Data Act Application Dates And Transition FAQ](/artifacts/eu/data-act/faq/application-dates-and-transition.md): FAQ on when the EU Data Act applies, which obligations are delayed, and what product, contract, cloud, and evidence records teams should maintain. - [EU Data Act Article 3 Pre-Contract Information](/artifacts/eu/data-act/pre-contractual-information-obligations.md): What Article 3 of the EU Data Act requires before connected-product purchase, rent, lease, or related-service contracting: data categories, access, data holder identity, third-party sharing, complaints, and evidence. - [EU Data Act Article 36 Smart Contract Controls FAQ](/artifacts/eu/data-act/faq/article-36-smart-contract-controls.md): FAQ explaining when EU Data Act Article 36 applies to smart contracts for data-sharing agreements and what controls, conformity evidence, and limits it requires. - [EU Data Act B2B Data Sharing Compensation FAQ](/artifacts/eu/data-act/faq/compensation-for-b2b-data-sharing.md): FAQ on when Data Act data holders may charge B2B data recipients, what reasonable compensation can include, SME limits, unfair terms, disputes, and trade secret safeguards. - [EU Data Act B2G Compensation and Costs FAQ](/artifacts/eu/data-act/faq/b2g-compensation-and-costs.md): FAQ on when Data Act B2G exceptional-need requests are free, when fair compensation may be claimed, which costs can be included, and what records to keep. - [EU Data Act B2G Exceptional Need FAQ](/artifacts/eu/data-act/faq/b2g-exceptional-need.md): When public-sector bodies can request business-held data under the EU Data Act, what a valid request must contain, and how data holders handle limits, trade secrets, compensation, and evidence. - [EU Data Act Checklist for Product, Cloud, and Contract Teams](/artifacts/eu/data-act/checklist.md): A grounded EU Data Act checklist for connected-product data access, third-party sharing, B2G requests, cloud switching, unfair terms, smart contracts, personal data boundaries, evidence, and owners. - [EU Data Act Cloud Switching and Exit Plans](/artifacts/eu/data-act/cloud-switching-and-exit-plans.md): A grounded EU Data Act guide for data processing service exit plans: switching contracts, exportable data, assistance, charges, interoperability, retrieval, erasure, and records. - [EU Data Act Cloud Switching Procurement FAQ](/artifacts/eu/data-act/faq/cloud-switching-procurement-checklist.md): Procurement checklist FAQ for EU Data Act cloud switching: contract terms, exit support, exportable data, switching charges, interoperability, termination, and supplier evidence. - [EU Data Act Compliance Program](/artifacts/eu/data-act/compliance.md): Build a Data Act compliance program for connected-product data access, contracts, B2G requests, cloud switching, smart contracts, GDPR boundaries, records, and ownership. - [EU Data Act Connected Product Scope and Data Types](/artifacts/eu/data-act/scope-connected-products-and-data-types.md): Classify EU Data Act connected products, related services, product data, related-service data, readily available data, metadata, and excluded derived outputs. - [EU Data Act Connected Product Scope FAQ](/artifacts/eu/data-act/faq/scope-connected-products.md): FAQ explaining when connected products, related services, generated data, EU market placement, and SME exceptions fall within EU Data Act scope. - [EU Data Act Data Processing Service Switching](/artifacts/eu/data-act/data-processing-services-switching.md): A grounded EU Data Act guide for provider and customer switching duties: exit assistance, exportable data, contract clauses, charges, interoperability, retrieval, and erasure. - [EU Data Act data spaces interoperability FAQ](/artifacts/eu/data-act/faq/data-spaces-interoperability.md): FAQ explaining Article 33 Data Act interoperability requirements for data-space participants, common European data spaces, standards, APIs, metadata, and architecture evidence. - [EU Data Act deadlines and compliance calendar](/artifacts/eu/data-act/deadlines-and-compliance-calendar.md): A source-linked calendar for EU Data Act application dates, product design timing, contract remediation, cloud switching charges, response periods, standards work, and evidence records. - [EU Data Act Direct Access by Design FAQ](/artifacts/eu/data-act/faq/direct-access-by-design.md): FAQ for product and legal teams designing user access to connected-product and related-service data under the EU Data Act. - [EU Data Act Enforcement And Competent Authorities FAQ](/artifacts/eu/data-act/faq/enforcement-and-competent-authorities.md): FAQ on who enforces the EU Data Act, how complaints work, how Member States set penalties, when dispute settlement can be used, and when GDPR authorities remain responsible. - [EU Data Act FAQ: scope, access rights, B2G, cloud switching, GDPR, and dates](/artifacts/eu/data-act/faq.md): Grounded EU Data Act FAQ index covering connected-product data access, third-party sharing, B2G exceptional need, cloud switching, smart contracts, GDPR boundaries, unfair terms, trade secrets, and application dates. - [EU Data Act Non-Emergency Public-Sector Requests FAQ](/artifacts/eu/data-act/faq/non-emergency-public-sector-requests.md): FAQ on EU Data Act requests where a public body claims exceptional need outside a public emergency, including scope, request contents, limits, compensation, confidentiality, and evidence. - [EU Data Act Non-Personal Data and Mixed Datasets FAQ](/artifacts/eu/data-act/faq/non-personal-data-and-mixed-datasets.md): FAQ on how the EU Data Act treats non-personal data, mixed datasets, GDPR precedence, user and third-party access, trade-secret limits, and evidence records. - [EU Data Act Penalties and Enforcement](/artifacts/eu/data-act/penalties-and-fines.md): Grounded guide to Data Act penalties under Article 40, Member State enforcement, penalty factors, complaints, judicial remedies, and the GDPR enforcement boundary. - [EU Data Act Pre-Contractual Information FAQ](/artifacts/eu/data-act/faq/pre-contractual-information.md): FAQ on EU Data Act Article 3 pre-contract information for connected products and related services, including data categories, access methods, data holder identity, third-party sharing, and GDPR boundaries. - [EU Data Act Product Data vs Related Service Data FAQ](/artifacts/eu/data-act/faq/product-data-and-service-data.md): FAQ explaining how the EU Data Act separates connected product data, related service data, readily available raw and pre-processed data, metadata, and inferred or derived outputs. - [EU Data Act Readily Available Data FAQ](/artifacts/eu/data-act/faq/readily-available-data.md): FAQ on what counts as readily available data under the EU Data Act, including product data, related service data, metadata, inferred data, and access mechanics. - [EU Data Act Related Services FAQ](/artifacts/eu/data-act/faq/related-services.md): FAQ explaining when software is a Data Act related service, how it links to connected products, which product and service data are in scope, and what exclusions apply. - [EU Data Act requirements](/artifacts/eu/data-act/requirements.md): Source-grounded EU Data Act requirements for connected-product data access, B2B sharing terms, B2G exceptional needs, cloud switching, smart contracts, interoperability, GDPR boundaries, and records. - [EU Data Act Smart Contracts for Data Sharing FAQ](/artifacts/eu/data-act/faq/smart-contracts-for-data-sharing.md): Answers on Article 36 Data Act smart-contract requirements for data sharing: scope, robustness, access control, termination, archiving, conformity assessment, contract terms, and standards status. - [EU Data Act Third-Party Data Sharing FAQ](/artifacts/eu/data-act/faq/third-party-data-sharing.md): FAQ on user-directed third-party data sharing under the EU Data Act, covering data holder duties, recipient limits, trade secrets, security, GDPR, and gatekeepers. - [EU Data Act Trade Secret Safeguards FAQ](/artifacts/eu/data-act/faq/trade-secrets-safeguards.md): FAQ on protecting trade secrets when handling EU Data Act user and third-party data access requests, including safeguards, withholding, suspension, refusal, notices, and records. - [EU Data Act User Access and Portability Rights](/artifacts/eu/data-act/access-rights-and-portability.md): Practical guide to EU Data Act user access, connected-product data portability, third-party sharing, trade secret safeguards, and the GDPR boundary. - [EU Data Act Users, Data Holders, and Recipients FAQ](/artifacts/eu/data-act/faq/users-data-holders-and-recipients.md): FAQ explaining Data Act users, data holders, data recipients, connected products, related services, user access, third-party limits, and GDPR boundaries. - [EU Data Act Vehicle Data Guidance FAQ](/artifacts/eu/data-act/faq/vehicle-data-guidance.md): FAQ on EU Data Act vehicle data guidance for connected vehicles, aftermarket repair, mobility services, third-party access, trade secrets, security, and GDPR boundaries. - [EU Data Act vs Data Governance Act](/artifacts/eu/data-act/data-act-vs-data-governance-act.md): Compare the EU Data Act with the Data Governance Act: connected-product access, cloud switching, B2B/B2G duties, protected public-sector reuse, intermediaries, altruism, governance, and enforcement. *Recommended next step* *Placement: after implementation section* ## Review Data Act B2B Data Clauses Screen data access, data use, liability, remedies, termination, data-copy, and unilateral-change clauses against Article 13 and keep the negotiation evidence needed to support the outcome. - [Open Research Copilot](/solutions/research-copilot.md): Check Data Act contract clauses against Article 13, model terms, and related data-sharing obligations. - [Discuss Data Act Contract Review](/contact.md): Review B2B data contract templates, negotiation records, and model-term changes for Article 13 exposure. --- [Privacy Policy](https://www.sorena.io/privacy) | [Terms of Use](https://www.sorena.io/terms-of-use) | [DMCA](https://www.sorena.io/dmca) | [About Us](https://www.sorena.io/about-us) (c) 2026 Sorena AB (559573-7338). All rights reserved. Source: https://www.sorena.io/artifacts/eu/data-act/faq/unfair-contractual-terms