Fast answers to the questions teams ask right before they ship (or get stuck).
Focus: dates, access workflows, trade secrets, B2G exceptional need, and cloud switching.
Structured answer sets in this page tree.
Cited legal and guidance references.
This FAQ focuses on implementation questions that cause real delays: what applies when, what data must be made available, how to design direct vs indirect access, how to coordinate with GDPR for mixed datasets, how trade secret safeguards work, how B2G requests are validated, and what Chapter VI cloud switching means for contracts and fees.
The Data Act applies from 12 September 2025. Article 50 also sets specific timing gates for certain obligations (for example, a connected-product design duty tied to products placed on the market after 12 September 2026) and clarifies how some contract-related rules apply based on contract dates.
The Commission's FAQs describe two patterns. Direct access means the user can access/port data via technical means without requesting the data holder each time. Indirect access means the user requests access via the data holder (e.g., a portal) and the data holder delivers the data.
Both can be compliant. The choice affects security, operational cost, and how you handle sensitive fields.
Chapter II focuses on data generated by use of connected products and related services, including the metadata needed to interpret and use the data. Implementation depends on what is "readily available" for the data holder to provide.
Operationally, the scoping deliverable is a dataset manifest: fields, formats, metadata, and delivery method.
The Data Act does not replace GDPR. Many connected product datasets are mixed (personal + non-personal). When personal data is involved, GDPR principles still govern lawfulness, minimisation, transparency, and security.
The safest implementation is one workflow with two decision layers: Data Act eligibility + GDPR safeguards.
Trade secret protection is handled through safeguards, not blanket refusals. The Data Act expects confidentiality measures such as agreements, strict access protocols, and technical controls.
Withholding/suspension is a targeted mechanism when the necessary measures cannot be agreed or are breached.
Chapter V allows certain public sector bodies (and EU bodies) to request data from private data holders only when an 'exceptional need' is demonstrated and the request is duly reasoned. Article 15 defines the exceptional need lanes.
Your intake workflow should validate: lane selection, completeness (Article 17), safeguards, and deadlines.
Compensation depends on the lane. For public emergencies, the required data is provided free of charge. For non-emergency statutory tasks, data holders are entitled to fair compensation covering costs (including safeguards work) and a reasonable margin (Article 20).
Build a repeatable cost model so you can respond quickly and defend it.
Chapter VI requires providers of data processing services to remove switching obstacles and to support customer switching to another provider (same service type) or to on-prem infrastructure. Article 25 sets required contract terms and timing gates.
Even if you're only a customer, Chapter VI is a procurement checklist: require proof before renewal.
Most disputes are about what you delivered, under what authority, with what safeguards. Build an evidence pack that is generated automatically by your workflows.
Evidence is also procurement fuel: buyers increasingly ask for proof of exit readiness and switching posture.
Research Copilot can take EU Data Act: Fair Access to Connected Product Data and Cloud Switching FAQ from cited answers to recurring questions on this topic to a reusable workflow inside Sorena. Teams working on EU Data Act: Fair Access to Connected Product Data and Cloud Switching can keep owners, evidence, and next steps aligned without copying this guide into separate documents.
Start from EU Data Act: Fair Access to Connected Product Data and Cloud Switching FAQ and answer scope, timing, and interpretation questions with cited outputs.
Review your current process, evidence gaps, and next steps for EU Data Act: Fair Access to Connected Product Data and Cloud Switching FAQ.