Clarify what is in scope and how to decide quickly.
This guide supports implementation for EU Data Act: Fair Access to Connected Product Data and Cloud Switching using source grounded analysis and execution oriented recommendations.
Structured answer sets in this page tree.
Cited legal and guidance references.
Scope is the hardest part of the EU Data Act. Your obligations depend on whether you have a connected product or a related service, and whether the data is product data/related service data that is "readily available" to the data holder. This page gives you a practical classification method, with examples and a scope memo template you can reuse per product line.
Chapter II access rights apply to specific kinds of data generated by the use of connected products and related services. The Data Act FAQs summarize the core terms and how they fit together.
Write these definitions into your internal scope memo and tie them to your architecture.
Research Copilot can take EU Data Act: Fair Access to Connected Product Data and Cloud Switching Scope, Connected Products and Data Types from clarifying scope and applicability with cited answers 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 Scope, Connected Products and Data Types 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 Scope, Connected Products and Data Types.
In practice, Chapter II is about raw and pre-processed data that exists because of the product's technical design and that the data holder can access without disproportionate effort.
A frequent mistake is treating analytics outputs and business intelligence as mandatory shareable data. The Act and FAQs draw a boundary: inferred/derived data is generally treated differently than raw and pre-processed data.
Users may be entitled to access data whether it is personal or non-personal. But personal data processing remains governed by GDPR rules, including legal basis and data subject rights.
Operationally: build one access pipeline, then apply GDPR checks when personal data is involved (identity, legal basis, redaction where necessary).
Scope decisions and obligations depend on roles. A manufacturer is often the data holder, but not always: the Data Act allows the data holder role to be outsourced, and a related service provider can also be the data holder.
Your scope memo should name the data holder(s) and explain how control over readily available data is exercised.
Create one scope memo per product line. Keep it short, and link to evidence (architecture diagrams, interface specs, data schemas).
This memo becomes your foundation for contract work, API implementation, and dispute handling.