Artifact GuideEUData Act

EU Data Act B2B Data Sharing Contract Clauses

Draft B2B data-sharing clauses around the Data Act rule that data holders make data available to data recipients on fair, reasonable, non-discriminatory, and transparent terms.

Use this as a contract drafting map for access scope, recipient duties, compensation, trade secrets, unfair-term review, audit evidence, termination, and personal data boundaries.

Author
Sorena AI
Published
May 6, 2026
Updated
May 6, 2026
Sections
10

Structured answer sets in this page tree.

Primary sources
4

Cited legal and guidance references.

Publication metadata
Sorena AI
Published May 6, 2026
Updated May 6, 2026
Overview

This page turns the Data Act's B2B data-sharing rules into a clause checklist for contracts between data holders, users, and data recipients. It is not a model contract; it shows what each clause needs to decide, document, and keep separate from unsupported negotiation preferences.

Section 1

Start with the statutory Data Act B2B access scenario before drafting clauses

A Data Act B2B data-sharing clause should first state why the data holder is making data available. Article 8 applies where, in a business-to-business relationship, a data holder is obliged under Article 5 or other applicable Union or national law to make data available to a data recipient.

Define the user, data holder, data recipient, connected product or related service, dataset, and request route before drafting commercial protections. The Commission's model contractual terms separate the data-holder-to-user, user-to-data-recipient, and data-holder-to-data-recipient relationships, which is a useful drafting structure even when the parties use their own language.

  • Identify whether the recipient receives data at the user's request or under another legal obligation.
  • State that access terms are subject to fair, reasonable, non-discriminatory, and transparent conditions.
  • Separate mandatory Data Act rights from voluntary data sharing or broader commercial data licenses.
  • Do not make the user's Data Act sharing right conditional on the parties first signing a bespoke contract.
Recommended next step

Review Data Act B2B data-sharing clauses against source-linked obligations

Use Sorena to check data-holder, user, and data-recipient clause packs against Data Act source text, Commission model terms, compensation guidance, and the personal-data boundary.

Section 2

Describe the data package precisely so the Data Act sharing scope is unambiguous

The data schedule should be specific enough for engineering to deliver the package and for legal to test the Data Act scope. Include the connected product or related service, data categories, metadata, quality, format, update frequency, delivery route, security controls, exclusions, and any dependencies on the user's request.

For Chapter II connected-product data, the access right targets readily available product data and related service data, including metadata necessary to interpret and use the data. The Commission FAQs describe the practical boundary as raw and pre-processed data, while inferred or derived outputs from additional investments are outside that access scope unless the parties agree otherwise.

  • List raw and pre-processed data separately from inferred, derived, enriched, or excluded data.
  • Include metadata such as timestamp, basic context, units, source system, and delivery schema when needed for use.
  • State whether access is direct, indirect, continuous, real-time, batch, API-based, or file-based.
  • Record why each exclusion applies instead of using broad labels such as proprietary data or confidential information.
Section 3

Draft FRAND terms that can be checked against the Data Act fairness requirements

FRAND wording should be measurable. A clause that says access is provided on FRAND terms is weak unless it also explains delivery quality, request verification, support, availability, change notice, security conditions, and how the data holder will show comparable recipients are not treated differently without objective reasons.

Article 8 requires the data holder not to discriminate between comparable categories of data recipients. If a data recipient gives a reasoned request, the data holder must provide information showing there has been no discrimination without undue delay.

  • Define comparable recipient categories, such as repair providers, analytics vendors, fleet operators, or research recipients.
  • Keep a pricing and delivery matrix that explains differences in volume, format, interface, service level, or risk controls.
  • Avoid exclusivity unless it is requested by the user and compatible with the Data Act scenario.
  • Limit information requests to what is necessary to verify contractual compliance or legal obligations.
Section 4

Set compensation in line with the Data Act without charging for the data itself

A compensation clause should show the calculation basis. Article 9 allows reasonable, non-discriminatory compensation that may include a margin, but the calculation must take account of costs incurred in making data available and, where applicable, investments in collecting and producing the data.

For SME data recipients and not-for-profit research organisations without non-SME partner or linked enterprises, compensation cannot exceed the costs incurred in making the data available. The Data Act also requires the data holder to give the data recipient enough detail to assess whether the Article 9 requirements are met.

  • Separate formatting, electronic dissemination, storage, interface, support, and request-handling costs.
  • Identify any margin separately and switch it off where the recipient is covered by the SME or not-for-profit research organisation cap.
  • Do not describe compensation as a purchase price for the data itself.
  • Attach a calculation note to each negotiated fee or subscription model.
Section 5

Build trade secret safeguards before disclosure as the Data Act allows

Trade secret clauses should not be blanket refusals. Articles 4 and 5 require protected trade secrets to be identified, including in relevant metadata, and disclosed only where the parties take necessary measures before disclosure to preserve confidentiality.

The clause should list the technical and organisational measures that apply to the recipient: confidentiality undertakings, access controls, named users, secure environments, encryption, logging, onward-sharing limits, deletion duties, and incident notice. If no agreement is reached on necessary measures, or if agreed measures are not implemented or confidentiality is undermined, the data holder may withhold or suspend the sharing of identified trade-secret data with written reasons.

  • Identify the trade secret holder when it is not the data holder.
  • Mark protected data and metadata at field or dataset level where possible.
  • Use proportionate safeguards instead of excluding an entire dataset by default.
  • Write the suspension notice clause so it records the missing safeguard, affected data, and competent-authority notification where required.
Section 6

Limit recipient use, onward sharing, and misuse remedies under the Data Act

Recipient clauses should state the permitted purpose, prohibited uses, onward-sharing controls, data security duties, deletion triggers, and remedies for misuse. Article 11 allows data holders to use technical protection measures such as smart contracts and encryption, provided those measures do not discriminate between data recipients or hinder the user's rights.

The Data Act gives specific response tools when a recipient uses false information, deceptive or coercive means, abuses technical gaps, uses data for unauthorised purposes, unlawfully discloses data, fails to maintain trade-secret safeguards, or removes technical protection measures without agreement.

  • Ban use of the data to develop a competing connected product where the Data Act prohibits it.
  • Require deletion of data and copies when the purpose ends, the contract terminates, or misuse is substantiated.
  • Require notice to the user for unauthorised use or disclosure where Article 11 calls for it.
  • Include compensation for misuse or disclosure of unlawfully accessed or used data.
Section 7

Screen data clauses for unfair-term risk under the Data Act fairness test

Article 13 applies to B2B terms concerning access to and use of data, or liability and remedies for breach or termination of data-related obligations, when they are unilaterally imposed by one enterprise on another. If an unfair term is severable, the rest of the contract remains binding.

Do not give one party exclusive power to decide whether supplied data conforms to the contract, remove all remedies for non-performance, block termination within a reasonable period, block copies of data after termination, or allow unexplained unilateral changes to data price, format, quality, nature, or quantity.

  • Keep negotiation evidence showing whether a term was actually negotiable.
  • Give both parties usable remedies for data non-performance and safeguard breaches.
  • Avoid one-sided interpretation, conformity, audit, suspension, and termination rights.
  • Allow reasonable termination and post-termination data copy rights where Article 13 would presume the opposite unfair.
Section 8

Use logs for necessity, security, and audit evidence of Data Act compliance

Audit and logging clauses should be narrow enough to respect the Data Act's necessity limits. Article 4 says a data holder must not keep user access information, especially log data, beyond what is necessary for sound execution of the access request and for security and maintenance of the data infrastructure.

For B2B recipient access, the contract should keep enough evidence to verify compliance with the access terms and Data Act obligations, but Article 8 prevents the parties from demanding information beyond what is necessary for that verification.

  • Log request identity, authority check, dataset, delivery time, format, recipient endpoint, safeguard version, and suspension or refusal reasons.
  • Set retention by purpose: execution, security, maintenance, dispute evidence, and legal hold should not be mixed without explanation.
  • Avoid broad audit rights that expose unrelated systems, unrelated customers, or personal data not needed for verification.
  • Record data holder responses to discrimination, compensation, trade secret, and misuse disputes.
Section 9

Keep personal data boundaries outside the commercial bargain in Data Act deals

The Data Act covers personal and non-personal data, but it does not supersede GDPR or ePrivacy rules. Article 1 says that where there is a conflict, Union or national personal data and privacy law prevails.

If the user is not the data subject, the data holder may make personal data generated by the connected product or related service available to the user only where there is a valid GDPR legal basis and, where relevant, the conditions for special category data and terminal-equipment access are met. The clause should therefore separate Data Act access mechanics from controller, processor, lawful basis, transparency, minimisation, security, and data-subject-rights terms.

  • Classify each field as personal data, non-personal data, mixed data, anonymised data, or excluded content.
  • Identify the controller and processor roles for each personal data flow.
  • Use anonymisation, filtering, or field suppression where the user is not the data subject and no valid basis supports disclosure.
  • Do not present the Data Act as a standalone legal basis for collecting, generating, or sharing personal data.
Section 10

Assemble a Data Act clause pack that survives negotiation and later audits

The finished contract pack should include the operative clauses, a dataset schedule, a recipient-use schedule, a compensation calculation note, trade-secret safeguard schedule, personal-data boundary note, logging and audit schedule, and termination and post-termination data handling terms.

Use Commission model contractual terms as drafting support, not as mandatory wording. The public Commission page says the model terms are voluntary, mainly drafted for B2B contracts, and designed to help parties implement the Data Act.

  • For data holder-to-recipient terms, include access route, data package, FRAND commitments, compensation, safeguards, technical protection measures, and dispute route.
  • For user-to-recipient terms, include the user's instruction, permitted use, data security, onward sharing, deletion, and misuse remedies.
  • For data holder-to-user terms, include user request mechanics, direct or indirect access, trade-secret controls, personal-data handling, and termination of sharing.
  • For all terms, keep source citations, negotiation history, calculation evidence, and version control with the contract record.
Primary sources

References and citations

ec.europa.eu
Referenced sections
  • Confirms that GDPR applies to personal data processing under the Data Act and that data protection authorities remain competent for personal-data issues.
eur-lex.europa.eu
Referenced sections
  • Article 41 required the Commission to develop non-binding model terms covering data access, reasonable compensation, trade secret protection, and FRAND rights and obligations.
Related guides

Explore more topics

Data Act and Common European Data Spaces
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
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
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
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 Template
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
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
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
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
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
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
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
FAQ on EU Data Act vehicle-data access for repairers, independent service providers, fleets, insurers, and mobility services.
Data Act Functional Equivalence FAQ
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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 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.
EU Data Act User Access and Portability Rights
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
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
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
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.