--- title: "EU Data Act Connected Product Scope FAQ" canonical_url: "https://www.sorena.io/artifacts/eu/data-act/faq/scope-connected-products" source_url: "https://www.sorena.io/artifacts/eu/data-act/faq/scope-connected-products" author: "Sorena AI" description: "FAQ explaining when connected products, related services, generated data, EU market placement, and SME exceptions fall within EU Data Act scope." published_at: "2026-05-06" updated_at: "2026-05-06" keywords: - "EU Data Act" - "connected product" - "related service" - "product data" - "readily available data" - "Chapter II" - "Regulation (EU) 2023/2854" - "connected products" - "related services" --- **[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 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. *FAQ* *EU* *Data Act* ## EU Data Act Connected Product Scope FAQ When a device, machine, vehicle, app, or service falls into EU Data Act connected-product scope. Use this FAQ to classify connected products, related services, generated data, market-scope triggers, exclusions, and SME manufacturer context. A product is not in EU Data Act Chapter II scope just because it is digital. The core test is whether the item obtains, generates, or collects data about its use or environment, can communicate product data, and is placed on the Union market for a user in the Data Act sense. ## What counts as a connected product under the EU Data Act, and which items fall outside that test? Under the Data Act, a connected product is an item that obtains, generates, or collects data concerning its use or environment and can communicate product data through an electronic communications service, a physical connection, or on-device access. The definition also excludes items whose primary function is storing, processing, or transmitting data for a party other than the user. The practical question is whether the product itself produces or captures operational data and has a route to communicate that data. Smart-home appliances, connected cars, medical or fitness devices, industrial machinery, agricultural machinery, planes, robots, and similar sensor-equipped products are typical examples when the rest of the scope test is met. - Check what data the item obtains, generates, or collects about use, performance, status, or environment. - Check whether the item can communicate product data by network connection, cable, maintenance interface, or on-device access. - Do not treat servers, routers, or other products primarily used to store, process, or transmit another party's data as connected products for Chapter II unless the user owns, rents, or leases the relevant product. 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 2(5) defines connected product; Recital 14 gives examples and explains communication routes. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ Question 7 explains connected-product examples and the exclusion for products whose primary function is storing, processing, or transmitting data. ## Does the product have to be placed on the EU market under the Data Act? Yes. For connected-product scope, the Data Act applies to manufacturers of connected products placed on the market in the Union and providers of related services, regardless of where those manufacturers or providers are established. It also applies to users in the Union of those connected products or related services. The Commission FAQ explains that placing on the market happens once for each individual product after the manufacturing stage, when ownership, possession, or another property right is transferred between economic actors. Later transactions are making available on the market, not a new first placement. - Classify each individual product, not only the product type or model line. - For mobile products such as cars, trains, ships, or aircraft, mere circulation in EU territory or EU waters is not enough if the product was not placed on the Union market. - If a connected product was placed on the EU market and later generates data outside the EU, the Commission FAQ says the generated data should still be made available to the user under the Data Act. 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 1(3) sets territorial scope for manufacturers, providers, and users; Article 2(21)-(22) defines making available and placing on the market. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ Questions 8 and 9 explain EU market placement, mobile connected products, and use outside the EU after EU placement. ## Who is the EU Data Act user for connected-product access rights, and how is that status established? Under the Data Act, a user is a natural or legal person that owns the connected product, has contractually received temporary rights to use it, or receives related services. The user can be a consumer, business, or public sector body; the key point is a stable ownership, rental, lease, or related-service position rather than casual physical interaction. The Commission FAQ gives the example of an airplane passenger: use of a connected aircraft through a transport service does not itself transfer property-type rights over the aircraft, so the passenger is not a Data Act user of the aircraft. - Identify owners, renters, lessees, and recipients of related services before processing an access request. - Expect multiple users in some arrangements, such as fleet leasing, rentals, or layered business use. - Verify only what is necessary to establish that the requester is a user; avoid turning scope checks into unnecessary data collection. 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 2(12) defines user; Recital 18 explains owners, renters, lessees, multiple users, and related-service recipients. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ Questions 14, 16, and 30 explain users, multiple users, and user verification. ## What is a related service, and when does an app count under the Data Act? Under the Data Act, a related service is a digital service, other than an electronic communications service, that is connected with the product at purchase, rent, or lease so that the product would lose one or more functions without it, or that is later connected to add, update, or adapt product functions. Software can be a related service when it is linked to product operation. The Commission FAQ describes two practical conditions: there must be bidirectional exchange of data between the connected product and service provider, and the service must affect the product's functions, behavior, or operation. An app that adjusts light brightness or regulates a fridge temperature can be a related service; connectivity, power supply, auxiliary consulting, analytics, financial services, and regular repair or maintenance are not related services merely because they interact with the product ecosystem. - Look for commands, settings, updates, or data flows that affect how the product behaves. - Review user expectations, marketing, contract terms, replaceability, and whether the service is pre-installed or bundled. - Separate related services from ordinary connectivity, electricity, analytics, consulting, finance, repair, and maintenance services. 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 2(6) defines related service; Recital 17 distinguishes related services from connectivity, power supply, consulting, analytics, finance, repair, and maintenance. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ Question 10 gives the bidirectional-data and product-function tests for related services. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer gives a washing-machine app example of a related service that uses sensor data and adjusts a cycle. ## Which generated data is inside connected-product scope under the Data Act? Under the Data Act, Chapter II focuses on product data and related service data that is readily available to the data holder. Product data is data generated by use of the connected product and designed to be retrievable. Related service data is data representing user actions or events related to the product during the related service. The scope includes raw data and pre-processed data, together with relevant metadata needed to interpret and use it. Commission materials describe this as raw or pre-processed data that is readily available, such as sensor measurements, status data, timestamps, or event logs where the data holder can obtain them without disproportionate effort beyond a simple operation. - Include data about use, performance, status, environment, user action, inaction, and product-related events when it is readily available. - Include relevant metadata such as basic context and timestamps where needed to make the data usable. - Treat personal and non-personal data separately for privacy compliance, but do not exclude data from Data Act scope just because it may include personal 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 2(15)-(17), Recital 15, Article 3, and Article 4 define product data, related service data, readily available data, metadata, and access duties. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ Questions 4, 5, and 5a explain raw data, pre-processed data, metadata, readily available data, and edge-processing scenarios. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer states that Chapter II applies to raw and pre-processed data generated from use of connected products or related services that is readily available to the data holder. ## What data and products are outside this connected-product scope under the Data Act? Under the Data Act, several exclusions matter. Prototypes are outside scope because their manufacturing stage has not been completed. Data that is inferred or derived from product data through additional investment, including proprietary complex algorithms, is not treated as data that must be made available under Chapter II unless the parties agree otherwise. The Data Act also distinguishes connected-product data from content. If a user watches a film on a smart TV, the film itself is not the Chapter II product data, but product-generated data such as screen brightness may be in scope if otherwise readily available. Data generated by infrastructure that the user does not own, rent, lease, or otherwise have rights over is not pulled into scope merely because the user's connected product uses that infrastructure. - Exclude prototypes, unless a specific contractual arrangement permits use of data from testing products or processes not yet placed on the market. - Separate raw and pre-processed data from inferred or derived insights produced by proprietary or complex analytics. - Do not convert third-party infrastructure data, audiovisual content, or unrelated software content into product data merely because the connected product interacts with it. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Recitals 14-16 and Article 5(2) support the prototype, inferred-or-derived-data, content, and testing exclusions. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ Questions 5, 6, and 7 explain derived data, content, infrastructure data, and prototypes. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer gives the smart-TV film example and distinguishes content from product-generated data. ## How do micro, small, and newer medium-sized manufacturers affect scope under the Data Act? Article 7 of the Data Act creates an important Chapter II limitation. The Chapter II obligations do not apply to data generated through connected products manufactured or designed, or related services provided, by a microenterprise or small enterprise, if the linked-enterprise and subcontracting conditions in Article 7 are satisfied. The same Article also covers data generated through connected products manufactured by, or related services provided by, an enterprise that has qualified as a medium-sized enterprise for less than one year, and connected products for one year after they were placed on the market by a medium-sized enterprise. This is a narrow status-and-timing check; it should not be generalized into an SME exemption for every data-sharing issue. - Verify the actual manufacturer, designer, related-service provider, linked enterprises, and subcontracting position. - For medium-sized enterprises, record when the enterprise first qualified as medium-sized and when the individual connected product was placed on the market. - Do not use SME context to remove GDPR, contract, product-safety, or other non-Data-Act obligations. 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 7 sets Chapter II scope limitations for microenterprises, small enterprises, and newer medium-sized enterprises. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer confirms that micro and small companies as manufacturers or related-service providers are not subject to the same Chapter II obligations as larger companies. ## What access and disclosure duties follow once a product is in scope under the Data Act? If the connected product or related service is in scope, Article 3 of the Data Act requires product data and related service data, including relevant metadata, to be designed or provided so that they are easily, securely, free of charge, and in a comprehensive, structured, commonly used, machine-readable format accessible to the user, where relevant and technically feasible directly. Before contracts for a connected product or related service are concluded, the seller, rentor, lessor, or related-service provider must provide clear information about the type, format, volume, frequency, storage, retention, access or retrieval arrangements, data-holder identity, trade-secret status where relevant, and third-party sharing process. Where direct access is not available, Article 4 requires the data holder to make readily available data accessible to the user on request. - Build a data map that names product data, related service data, metadata, storage location, retention period, access method, and prospective data holder. - Use customer-facing disclosures before purchase, rent, lease, or related-service contract conclusion. - Give users a simple electronic request path where technically feasible when data cannot be directly accessed. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Articles 3 and 4 set design, pre-contractual information, direct access, and request-based access duties for connected products and related services. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer summarizes user access, free availability to users, simple request processes, and contracts defining data access, use, and sharing rights. ## What examples should teams use when applying the scope test under the Data Act? Use Data Act examples that separate the product, the user, the data holder, and the data. A company operating a connected bulldozer may be the user, while the bulldozer manufacturer is typically the data holder. A connected fridge with an app can involve two data holders: the entity placing the fridge on the market and the provider of the related app. Vehicle and infrastructure examples are useful because they show the boundary. If a vehicle receives data from roadside sensors or records road conditions and the vehicle data holder has access to that data, the vehicle user may request the vehicle data. But driving on a road does not make the driver a Data Act user of the road infrastructure sensors. - For each example, name the connected product, related service if any, user, likely data holder, and generated data category. - For connected TVs, separate product telemetry such as brightness from the film or audiovisual content itself. - For second-hand products, remember that the Data Act does not distinguish first-hand and second-hand connected products for user access rights. 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 gives examples involving bulldozers, connected fridges, smart TVs, connected cars, medical and fitness devices, planes, robots, and industrial machines. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ Questions 7, 9, 10, and 11 give examples for infrastructure boundaries, mobile products, related services, and second-hand connected products. - [European Commission - Data Act press release](https://ec.europa.eu/commission/presscorner/detail/en/ip_25_2078?ref=sorena.io) - Commission press release uses examples such as smartwatches, cars, smart TVs, and industrial machinery to describe connected-device user control. ## What evidence should a connected-product scope file keep under the Data Act? A useful Data Act scope file should be narrow: product identifier, EU market-placement basis, manufacturer or designer, related-service provider if any, user categories, data holder, generated data categories, readiness of access, exclusions applied, and source citation. It should be written so product, legal, engineering, support, and sales teams can apply the same classification. For each product family, keep the architecture facts that support the decision: sensor list, data fields, metadata, communication routes, storage location, retention period, whether direct access is technically feasible, and where customer disclosures describe access and third-party sharing. If the answer relies on Article 7 SME status, keep the linked-enterprise, subcontracting, and timing evidence. - Keep one product-scope record per product family and update it when architecture, related services, market placement, or contracts change. - Record exclusions separately for prototypes, content, infrastructure data, inferred or derived data, security restrictions, trade secrets, and personal-data limits. - Attach public-source citations to factual claims about scope, exclusions, users, and data categories. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Articles 1-7 and Recitals 14-18 provide the legal fields needed to classify connected-product scope, users, data holders, related services, generated data, and SME limitations. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ provides implementation checks for connected-product status, EU market placement, related services, users, data categories, and exclusions. ## What source evidence should teams keep for the EU Data Act connected-product scope decision later? Keep the Data Act legal basis and the practical facts together. For each scope decision, store the cited clause or recital, the Commission guidance relied on, the product family or service, the data categories involved, the trigger for the review, and the person who approved the classification. A concise evidence file should also preserve the source URL, the date of the decision, any unresolved assumptions, and the implementation artifact that reflects the conclusion. That makes the classification auditable when the product design, data flow, or contract changes. - Map the scope decision to a cited Data Act source URL. - Store the owner, affected workflow, evidence artifact, and review trigger. - Note any assumptions about market placement, user status, related services, or SME status so they can be rechecked later. ## How should teams assign ownership for EU Data Act connected-product scope work and later reviews? Assign one accountable owner who can change the affected process under the Data Act, then record the supporting teams separately. Legal, product, procurement, cloud, support, and security may all be involved, but the scope file should name a single owner for follow-up. The owner should be the person who can update the product record when architecture, contractual terms, or data flows change and who can trigger a new review when the scope facts move. - Map the scope decision to a cited Data Act source URL. - Store the owner, affected workflow, evidence artifact, and review trigger. - Use one named owner per product family so updates and reviews do not get lost between teams. ## 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 connected-product definitions, territorial scope, product and related-service data, Article 3 access-by-design duties, Article 4 request access, Article 5 third-party sharing, and Article 7 SME limitations. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ source for connected-product classification, EU market placement, related-service tests, raw and pre-processed data, exclusions, users, and examples. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer source for Chapter II IoT scope, connected-product and related-service examples, user and data-holder roles, and user access mechanics. - [European Commission - Data Act press release](https://ec.europa.eu/commission/presscorner/detail/en/ip_25_2078?ref=sorena.io) - Commission source for public examples of connected devices and practical user-control framing. ## 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 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 Unfair Contractual Terms FAQ](/artifacts/eu/data-act/faq/unfair-contractual-terms.md): 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](/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 evidence section* ## Data Act Classify connected-product scope Turn connected-product scope into a product-family record covering EU market placement, related services, generated data, exclusions, user access paths, and source-linked evidence. - [Open Research Copilot](/solutions/research-copilot.md): Get cited answers on Data Act connected-product scope and adjacent access duties. - [Discuss connected-product scope](/contact.md): Review how product architecture, related services, generated data, and contracts affect Data Act implementation. --- [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/scope-connected-products