---
title: "Scope, Connected Products and Data Types"
canonical_url: "https://www.sorena.io/artifacts/eu/data-act/scope-connected-products-and-data-types"
source_url: "https://www.sorena.io/artifacts/eu/data-act/scope-connected-products-and-data-types"
author: "Sorena AI"
description: "EU Data Act scope explained: connected products vs related services, product data vs related service data, readily available data."
published_at: "2026-02-23"
updated_at: "2026-02-23"
keywords:
  - "EU Data Act scope connected products"
  - "product data vs related service data"
  - "readily available data definition"
  - "inferred derived data excluded Data Act"
  - "Data Act Chapter II scope"
  - "Data Act data holder definition"
  - "Data Act user rights IoT data"
  - "EU compliance"
  - "data-act compliance"
  - "Scope Connected Products and DATA Types"
  - "compliance timeline"
  - "compliance decision flow"
---
**[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)

---

# Scope, Connected Products and Data Types

EU Data Act scope explained: connected products vs related services, product data vs related service data, readily available data.

*Artifact Guide* *EU*

## EU Data Act: Fair Access to Connected Product Data and Cloud Switching Scope, Connected Products and Data Types

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.

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.

## The four scope terms you must get right (Chapter II)

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.

- Connected product: generates data from use (IoT-style devices and systems)
- Related service: a digital service linked to a connected product whose behaviour is influenced by data from that product
- Product data and related service data: data relating to performance/use/environment, and data representing user actions/events during service provision
- Readily available data: data a data holder can obtain without disproportionate effort going beyond a simple operation

*Recommended next step*

*Placement: after the scope or definition section*

## Use EU Data Act: Fair Access to Connected Product Data and Cloud Switching Scope, Connected Products and Data Types as a cited research workflow

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.

- [Open Research Copilot for EU Data Act: Fair Access to Connected Product Data and Cloud Switching Scope, Connected Products and Data Types](/solutions/research-copilot.md): 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.
- [Talk through EU Data Act: Fair Access to Connected Product Data and Cloud Switching](/contact.md): 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.

## What is typically in scope (raw and pre-processed data) vs out of scope (inferred/derived)

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.

- In scope: sensor readings, logs/events, operational metrics, device state, usage events (when readily available)
- Often out of scope: inferred/derived insights created through complex analysis or enrichment (document your rationale)
- Pre-contract transparency (Article 3): descriptive information "about" the product can still matter even if it is not product data

## Personal vs non-personal data (and why GDPR still governs processing)

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).

- Design your export so personal and non-personal fields can be handled separately where needed
- Keep an audit log of access and sharing requests, approvals, and data delivered
- Document "who is the data subject" vs "who is the user" in B2B scenarios (e.g., fleet/rental)

## Role mapping: user vs data holder vs data recipient

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.

- User: person/entity using/owning/renting/benefiting from the connected product or related service
- Data holder: entity that controls access to the readily available data
- Data recipient/third party: entity receiving data at the user's request (e.g., repair, analytics, maintenance providers)

## Scope memo template (audit ready output)

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.

- Inventory: connected products + related services in scope; versions; EU market placement model
- Data classification: product data vs related service data; readily available extraction path; exclusions (inferred/derived)
- Role mapping: user/data holder/data recipient; outsourced data holder logic if applicable
- Delivery design: direct access vs portal requests; export formats; security and privacy controls
- Evidence links: schema registry, API docs, access logs, and test results for exports

## Primary sources

- [Regulation (EU) 2023/2854 (Data Act) - Official Journal (ELI)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Legal definitions and Chapter II scope and access rights.
- [European Commission - Data Act FAQs (library page)](https://digital-strategy.ec.europa.eu/en/library/commission-publishes-frequently-asked-questions-about-data-act?ref=sorena.io) - Practical definitions: product data, related service data, readily available data, and examples of Chapter II in practice.
- [European Commission - Data Act (policy page)](https://digital-strategy.ec.europa.eu/en/policies/data-act?ref=sorena.io) - Commission overview and implementation context.

## Related Topic Guides

- [Access Rights and Portability | EU Data Act: Fair Access to Connected Product Data and Cloud Switching](/artifacts/eu/data-act/access-rights-and-portability.md): EU Data Act access rights and portability (Chapter II) made practical: direct vs indirect access, "readily available" data.
- [Applicability Test | EU Data Act: Connected Products, B2B Data Sharing, B2G Exceptional Need, Cloud Switching](/artifacts/eu/data-act/applicability-test.md): A practical EU Data Act applicability test you can run in 15 minutes: determine if Chapter II IoT access rights apply (connected products + related services).
- [B2B Data Sharing Contract Clauses | EU Data Act: Mandatory Sharing, Unfair Terms, Trade Secrets](/artifacts/eu/data-act/b2b-data-sharing-contract-clauses.md): EU Data Act contract clauses for B2B data sharing made practical: clause library for Chapter III access/use (purpose limits, compensation, security.
- [B2B Data Sharing Contract Template | EU Data Act: Data Access and Use Agreement (Drafting Checklist)](/artifacts/eu/data-act/b2b-data-sharing-contract-template.md): A practical EU Data Act-aligned B2B data sharing contract template: sections, annexes, and drafting checklist for dataset definition, permitted use.
- [B2G Exceptional Need Requests | EU Data Act: Public Emergency Data Requests, Safeguards, Compensation](/artifacts/eu/data-act/b2g-exceptional-need-requests.md): EU Data Act Chapter V B2G 'exceptional need' requests made practical.
- [Cloud Switching and Exit Plans | EU Data Act Chapter VI: Switch Providers, Port Data, Remove Egress Barriers](/artifacts/eu/data-act/cloud-switching-and-exit-plans.md): EU Data Act Chapter VI cloud switching made practical: Article 23 obstacle removal, Article 25 required contract terms (max 2-month notice, 30-day transition.
- [Cloud Switching Compliance Checklist | EU Data Act Chapter VI: Contracts, Exportable Data, Fees, Transparency](/artifacts/eu/data-act/cloud-switching-compliance-checklist.md): A detailed EU Data Act Chapter VI cloud switching compliance checklist: Article 25 contract terms (max notice period, 30-day transition, retrieval period).
- [Compliance Program | EU Data Act Implementation Playbook: Governance, Controls, Evidence, Operating Cadence](/artifacts/eu/data-act/compliance.md): Turn the EU Data Act into an implementation program: chapter scoping, roles and ownership, product workflows for Chapter II access.
- [Deadlines and Compliance Calendar | EU Data Act](/artifacts/eu/data-act/deadlines-and-compliance-calendar.md): Plan EU Data Act delivery with real dates: Regulation applies from 12 Sep 2025.
- [EU Data Act Checklist | Chapter II Access, B2B Sharing, Unfair Terms, B2G Requests, Cloud Switching](/artifacts/eu/data-act/checklist.md): A comprehensive EU Data Act checklist organized by roles and chapters: Chapter II connected product data access (direct vs indirect access).
- [EU Data Act vs GDPR | Differences, Overlap, Portability, Lawful Basis, Implementation Playbook](/artifacts/eu/data-act/data-act-vs-gdpr.md): EU Data Act vs GDPR made practical: how Chapter II access/portability for connected product data differs from GDPR data subject rights.
- [FAQ | EU Data Act Explained: Key Dates, Access Rights, Trade Secrets, B2G Requests, Cloud Switching](/artifacts/eu/data-act/faq.md): EU Data Act FAQ with practical answers grounded in official sources: when the Data Act applies (Article 50), direct vs indirect access.
- [Penalties and Fines | EU Data Act Enforcement: Member State Penalties, GDPR-Linked Fines, Risk Controls](/artifacts/eu/data-act/penalties-and-fines.md): EU Data Act penalties and fines made practical: how Member States set penalties (Article 40), the criteria authorities must consider.
- [Requirements | EU Data Act Obligations Explained: Chapter II Access, Chapter IV Unfair Terms, Chapter V B2G, Chapter VI Switching](/artifacts/eu/data-act/requirements.md): A structured EU Data Act requirements breakdown across Chapters II-VI: connected product data transparency and access workflows.
- [Trade Secrets and Protection | EU Data Act: Confidentiality Measures, Withholding Rules, Evidence Pack](/artifacts/eu/data-act/trade-secrets-and-protection.md): EU Data Act trade secrets protection made practical: how to identify trade secret fields before disclosure, how to agree confidentiality measures (NDAs.


---

[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/scope-connected-products-and-data-types
