--- title: "EU Data Act FAQ: scope, access rights, B2G, cloud switching, GDPR, and dates" canonical_url: "https://www.sorena.io/artifacts/eu/data-act/faq" source_url: "https://www.sorena.io/artifacts/eu/data-act/faq/items/page/19" author: "Sorena AI" description: "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." published_at: "2026-05-06" updated_at: "2026-05-25" keywords: - "EU Data Act FAQ" - "Data Act scope" - "connected product data" - "B2G data sharing" - "cloud switching" - "GDPR Data Act" - "EU Data Act" - "Data Act FAQ" - "Regulation (EU) 2023/2854" --- **[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 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. *FAQ* *EU* *Data Act* ## EU Data Act FAQ hub Answers to the recurring EU Data Act questions that decide whether connected-product data, related-service data, B2G requests, cloud contracts, or smart-contract tooling need a compliance review. Use this index to orient product, legal, cloud, procurement, data protection, security, and public-sector request teams before opening the deeper topic modules. The EU Data Act, Regulation (EU) 2023/2854, creates horizontal rules for fair access to and use of data. Its FAQ set is not only about IoT data portability: it also covers mandatory B2B sharing terms, unfair contractual terms, public-sector access in exceptional need, cloud and edge switching, safeguards against unlawful third-country government access to non-personal data, interoperability, smart contracts, enforcement, and the boundary with GDPR. ## Browse sub-FAQ modules ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 13 items ### [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. - 12 items ### [EU Data Act Connected Product Scope FAQ](/artifacts/eu/data-act/faq/scope-connected-products.md) FAQ explaining when connected products, related services, generated data, EU market placement, and SME exceptions fall within EU Data Act scope. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items ### [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. - 12 items Browse all indexed questions: [/artifacts/eu/data-act/faq/items](/artifacts/eu/data-act/faq/items.md) ## All FAQ items *Page 19 of 24. Showing 20 of 469 items.* ### [What evidence makes the EU Data Act pre-contract information answer usable for a later reviewer?](/artifacts/eu/data-act/faq/pre-contractual-information.md#what-evidence-makes-the-eu-data-act-pre-contract-information-answer-usable-for-a-later-reviewer) *Module: [EU Data Act Pre-Contractual Information](/artifacts/eu/data-act/faq/pre-contractual-information.md)* For pre contractual information, the Data Act evidence should be concrete enough for a later reviewer to reconstruct why the team classified the product, service, request, or contract in scope. - Keep the source materials that show why Article 3 applies to the product or service. - Retain contract wording, notices, and technical descriptions that match the published answer. - Preserve approval records so the implementation team can explain the final disclosure choices. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Primary legal source for Article 3 pre-contract information duties, data access design duties, trade secret disclosure, GDPR boundary, and complaint rights. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission implementation FAQ used for data categories, direct and indirect access, data holder identity, GDPR interaction, and third-party sharing limits. - [European Commission - Data Act Explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer used for connected-product and related-service context, user access, data holder roles, and limits on third-party sharing. - [European Commission - Data Act policy page](https://digital-strategy.ec.europa.eu/en/policies/data-act?ref=sorena.io) - Official Commission policy context for user control over connected-device data under the Data Act. ### [What is product data under the EU Data Act, and which use-generated fields does it cover?](/artifacts/eu/data-act/faq/product-data-and-service-data.md#what-is-product-data-under-the-eu-data-act-and-which-use-generated-fields-does-it-cover) *Module: [EU Data Act Product Data vs Related Service Data](/artifacts/eu/data-act/faq/product-data-and-service-data.md)* The Data Act context is the starting point for this answer. Product data is data obtained, generated, or collected by a connected product and related to that product's performance, use, or environment. The key test is whether the connected product itself obtains, generates, or collects the data through its components or operating systems, not whether the business labels the record as telemetry, diagnostics, or customer data. - Start with the connected product and the data it is designed to obtain, generate, or collect. - Classify data tied to performance, use, or environment before applying internal labels. - Do not treat manuals, packaging copy, or other descriptive product information as product data for Chapter II access. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Defines product data and explains that connected products generate data about performance, use, or environment. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Clarifies that product data is obtained, generated, or collected by a connected product and excludes purely descriptive product information. ### [What is related service data under the EU Data Act, and when is it generated during a service?](/artifacts/eu/data-act/faq/product-data-and-service-data.md#what-is-related-service-data-under-the-eu-data-act-and-when-is-it-generated-during-a-service) *Module: [EU Data Act Product Data vs Related Service Data](/artifacts/eu/data-act/faq/product-data-and-service-data.md)* The Data Act context is the starting point for this answer. Related service data is data representing user actions, inaction, or events related to the connected product during the provision of a related service. A related service is not every service sold near the product; it must be linked to the operation of the connected product's functions, such as a service or app that exchanges data or commands with the product and can affect its action or behaviour. - Check whether the service is explicitly linked to the product's functions. - Look for exchanged data or commands that can affect product action or behaviour. - Separate related service data from unrelated services, content, consulting, analytics, repair, maintenance, power, and connectivity supply. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Defines related service data and explains when a service is linked closely enough to the connected product to be a related service. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Gives a practical related-service example involving an app connected to a washing machine. ### [Does the EU Data Act cover both raw and pre-processed data, and where does inferred data stop?](/artifacts/eu/data-act/faq/product-data-and-service-data.md#does-the-eu-data-act-cover-both-raw-and-pre-processed-data-and-where-does-inferred-data-stop) *Module: [EU Data Act Product Data vs Related Service Data](/artifacts/eu/data-act/faq/product-data-and-service-data.md)* The Data Act context is the starting point for this answer. Yes, Chapter II covers raw data and pre-processed data when the data is product data or related service data and is readily available to a data holder. Raw data means source or primary data points generated automatically without further processing. Pre-processed data can include data prepared to make it understandable and usable before further analysis, such as sensor data converted into a physical quantity or quality. - Treat source data and raw sensor readings as potentially in scope when they are readily available. - Include pre-processed measurements that make collected data understandable, such as temperature, speed, pressure, position, or flow rate. - Do not convert the Data Act into an obligation to build new enriched datasets for the requester. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Recital 15 distinguishes raw and pre-processed data from inferred or derived information and gives physical measurement examples. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Explains that raw and pre-processed data are in scope when they are readily available to the data holder. ### [What metadata must travel with product data or related service data under the Data Act?](/artifacts/eu/data-act/faq/product-data-and-service-data.md#what-metadata-must-travel-with-product-data-or-related-service-data-under-the-data-act) *Module: [EU Data Act Product Data vs Related Service Data](/artifacts/eu/data-act/faq/product-data-and-service-data.md)* The Data Act treats relevant metadata as part of what makes product data and related service data usable. The metadata must be necessary to interpret and use the data, such as basic context, timestamp, or conditions under which the data was collected or generated. - Include timestamps, basic context, and collection conditions when they are needed to interpret the data. - Align metadata with the data fields actually being accessed or shared. - Exclude unrelated internal annotations or enriched analytics that are not necessary to interpret the in-scope 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) - Requires relevant metadata necessary to interpret and use product data and related service data. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Explains metadata as information needed to understand collection or generation conditions such as time, weather, or location. ### [When is inferred or derived information outside the EU Data Act access route?](/artifacts/eu/data-act/faq/product-data-and-service-data.md#when-is-inferred-or-derived-information-outside-the-eu-data-act-access-route) *Module: [EU Data Act Product Data vs Related Service Data](/artifacts/eu/data-act/faq/product-data-and-service-data.md)* Information inferred or derived from product data or related service data is generally outside Chapter II when it results from additional investment into assigning values or insights, especially through proprietary, complex algorithms. The Data Act draws this line to preserve incentives to build analytics, transformations, and autonomous decision processes. - Ask whether the record is a measurement or usable pre-processing, or instead an insight created by additional investment. - Treat proprietary, complex algorithmic outputs and highly enriched analytics as outside the ordinary Chapter II sharing obligation unless separately agreed. - Do not classify data as out of scope only because it has been encrypted, pseudonymised, or anonymised. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Recital 15 excludes inferred or derived information produced through additional investment, including proprietary complex algorithms. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Explains the enrichment boundary and notes that privacy-preserving processing alone should not exclude data from Chapter II. ### [What does readily available data mean for connected product and related service datasets under the Data Act?](/artifacts/eu/data-act/faq/product-data-and-service-data.md#what-does-readily-available-data-mean-for-connected-product-and-related-service-datasets-under-the-data-act) *Module: [EU Data Act Product Data vs Related Service Data](/artifacts/eu/data-act/faq/product-data-and-service-data.md)* The Data Act context is the starting point for this answer. Readily available data means product data and related service data that a data holder lawfully obtains or can lawfully obtain from the connected product or related service without disproportionate effort going beyond a simple operation. This availability test matters because Chapter II access duties focus on data the data holder can access, not every possible signal a device could theoretically generate. - Classify each field by whether the data holder lawfully obtains it or can lawfully obtain it by a simple operation. - Do not add unavailable internal possibilities to the user export just because the product could theoretically be redesigned. - For in-scope readily available data, document the access route, quality, format, and metadata needed for use. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Defines readily available data and sets the Article 4 access format and metadata requirements. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Summarizes readily available data as product and related service data accessible without effort beyond a simple operation. ### [How can teams classify Data Act examples without inventing unsupported categories?](/artifacts/eu/data-act/faq/product-data-and-service-data.md#how-can-teams-classify-data-act-examples-without-inventing-unsupported-categories) *Module: [EU Data Act Product Data vs Related Service Data](/artifacts/eu/data-act/faq/product-data-and-service-data.md)* The Data Act context is the starting point for this answer. Use a field-level inventory rather than broad buckets. A smart-home thermostat may generate product data such as temperature readings and device status; a control app may generate related service data when it records user settings or sends commands that affect product behaviour; a vendor's proprietary comfort score or predictive energy model may be inferred or derived information if it results from additional analytics investment. - Use the Data Act categories: product data, related service data, readily available data, metadata, and inferred or derived information. - Avoid unsupported internal categories such as premium telemetry, diagnostic intelligence, or product insights unless they are mapped back to a Data Act category. - Keep example classifications tied to actual fields, generation source, availability, and enrichment level. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Provides examples of connected products and explains the boundary between product data, related service data, and inferred or derived information. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Provides practical examples of connected products and a related service connected to a washing machine. ### [What should a Data Act classification record contain for this FAQ?](/artifacts/eu/data-act/faq/product-data-and-service-data.md#what-should-a-data-act-classification-record-contain-for-this-faq) *Module: [EU Data Act Product Data vs Related Service Data](/artifacts/eu/data-act/faq/product-data-and-service-data.md)* A useful classification record should be narrow: product or service name, data field, generation source, whether the field is product data or related service data, whether it is readily available, the metadata needed to interpret it, the enrichment level, and the reason for any exclusion. For personal data, trade secrets, or security-sensitive data, classification should be paired with the relevant safeguards rather than used as a reason to ignore the Data Act category. - Track each field's Data Act category and whether it is raw, pre-processed, inferred, derived, content, or unavailable. - Record necessary metadata, format, access route, storage, retention, and data holder identity. - Separate classification from safeguards for GDPR, trade secrets, security, and contractual use limits. 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 3 lists pre-contractual information for connected products and related services, including data type, format, volume, frequency, retention, access, and data holder details. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Explains the practical factors for deciding which data is in scope of Data Act access rights. ### [What source evidence should teams keep for a Data Act classification decision?](/artifacts/eu/data-act/faq/product-data-and-service-data.md#what-source-evidence-should-teams-keep-for-a-data-act-classification-decision) *Module: [EU Data Act Product Data vs Related Service Data](/artifacts/eu/data-act/faq/product-data-and-service-data.md)* For product data and service data, the Data Act record should identify the source clause, Commission guidance, actor role, dataset, request or contract trigger, and the owner who approved the interpretation. - Map the decision to a cited Data Act source URL. - Store the owner, affected workflow, evidence artifact, and review trigger. - Keep the record tied to the actual dataset and contract or request context. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Binding Data Act source for product data, related service data, readily available data, metadata, user access, and inferred or derived information boundaries. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ source for in-scope raw and pre-processed data, metadata, readily available data, and the derived or inferred data boundary. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer source for connected product and related service examples under Chapter II. ### [How should teams assign ownership for Data Act classification work?](/artifacts/eu/data-act/faq/product-data-and-service-data.md#how-should-teams-assign-ownership-for-data-act-classification-work) *Module: [EU Data Act Product Data vs Related Service Data](/artifacts/eu/data-act/faq/product-data-and-service-data.md)* For product data and service data, the Data Act workflow should name the legal, product, procurement, cloud, support, or security owner who can change the affected process. - Map the decision to a cited Data Act source URL. - Store the owner, affected workflow, evidence artifact, and review trigger. - Keep ownership separate from the underlying legal classification. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Binding Data Act source for product data, related service data, readily available data, metadata, user access, and inferred or derived information boundaries. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ source for in-scope raw and pre-processed data, metadata, readily available data, and the derived or inferred data boundary. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer source for connected product and related service examples under Chapter II. ### [Which evidence makes the Data Act classification answer usable later?](/artifacts/eu/data-act/faq/product-data-and-service-data.md#which-evidence-makes-the-data-act-classification-answer-usable-later) *Module: [EU Data Act Product Data vs Related Service Data](/artifacts/eu/data-act/faq/product-data-and-service-data.md)* For product data and service data, the Data Act evidence should be concrete enough for a later reviewer to reconstruct why the team classified the product, service, request, or contract in scope. - Map the decision to a cited Data Act source URL. - Store the owner, affected workflow, evidence artifact, and review trigger. - Keep the evidence focused on the concrete product, service, or request. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Binding Data Act source for product data, related service data, readily available data, metadata, user access, and inferred or derived information boundaries. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ source for in-scope raw and pre-processed data, metadata, readily available data, and the derived or inferred data boundary. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer source for connected product and related service examples under Chapter II. ### [When should the Data Act classification answer be reviewed again?](/artifacts/eu/data-act/faq/product-data-and-service-data.md#when-should-the-data-act-classification-answer-be-reviewed-again) *Module: [EU Data Act Product Data vs Related Service Data](/artifacts/eu/data-act/faq/product-data-and-service-data.md)* For product data and service data, the Data Act answer should be reviewed when the product, service model, dataset, customer role, public-sector request path, or contract wording changes. - Map the decision to a cited Data Act source URL. - Store the owner, affected workflow, evidence artifact, and review trigger. - Review again after any material change in product design, service design, or contract scope. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Binding Data Act source for product data, related service data, readily available data, metadata, user access, and inferred or derived information boundaries. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ source for in-scope raw and pre-processed data, metadata, readily available data, and the derived or inferred data boundary. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer source for connected product and related service examples under Chapter II. ### [What does readily available data mean under the EU Data Act for Readily Available Data implementation evidence?](/artifacts/eu/data-act/faq/readily-available-data.md#what-does-readily-available-data-mean-under-the-eu-data-act-for-readily-available-data-implementation-evidence) *Module: [EU Data Act Readily Available Data](/artifacts/eu/data-act/faq/readily-available-data.md)* The Data Act defines readily available data as product data and related service data that a data holder lawfully obtains, or can lawfully obtain, from the connected product or related service without disproportionate effort beyond a simple operation. It is a scope boundary for Chapter II user access and sharing rights. - Treat readily available data as a defined Data Act category, not as a synonym for every log, analytics table, or support record connected to a device. - Document the system or interface through which the data holder obtains or can obtain the data. - Record when a field is excluded because it is not product data or related service data, is not lawfully obtainable, or would require disproportionate effort beyond a simple operation. 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 defines readily available data as product data and related service data that the data holder lawfully obtains or can obtain without disproportionate effort beyond a simple operation. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - The Commission FAQ explains that raw and pre-processed data that are readily available to the data holder are subject to Chapter II mandatory data-sharing obligations. ### [Which product data and related service data are in scope under the Data Act?](/artifacts/eu/data-act/faq/readily-available-data.md#which-product-data-and-related-service-data-are-in-scope-under-the-data-act) *Module: [EU Data Act Readily Available Data](/artifacts/eu/data-act/faq/readily-available-data.md)* The Data Act context is the starting point for this answer. Product data is data generated by use of a connected product that the manufacturer designed to be retrievable through an electronic communications service, physical connection, or on-device access. Related service data is data representing user actions, inaction, or events related to the connected product during the related service. - Classify each requested field as product data, related service data, or outside Chapter II before assessing access mechanics. - Map the user, data holder, and any third-party recipient because the same ecosystem can have several data holders. - For related services, check whether the service changes, updates, adapts, or enables functions of the connected product rather than standing apart from 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) - Article 2 defines product data, related service data, users, data holders, and related services for the Chapter II access analysis. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - The Commission explainer gives connected-product and related-service examples and describes the Chapter II focus on data generated by connected products and related services. ### [Does readily available data include metadata under the Data Act for Readily Available Data implementation evidence?](/artifacts/eu/data-act/faq/readily-available-data.md#does-readily-available-data-include-metadata-under-the-data-act-for-readily-available-data-implementation-evidence) *Module: [EU Data Act Readily Available Data](/artifacts/eu/data-act/faq/readily-available-data.md)* Yes, where metadata is needed to interpret and use the product data or related service data. The Data Act definition of metadata covers structured descriptions that facilitate discovery or use of data, and Articles 3, 4, and 5 attach relevant metadata to access and sharing duties. - Do not provide raw field values without the labels, units, timestamps, and collection context needed to use them. - Include metadata in the same access design review as the underlying product or related-service data. - Identify trade-secret claims in relevant metadata where Articles 4 or 5 safeguards are being used. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - The Data Act defines metadata and requires relevant metadata necessary to interpret and use data in Articles 3, 4, and 5. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - The Commission FAQ explains that metadata helps users understand conditions such as time, weather, or location under which data was collected or generated. ### [Are inferred, derived, highly enriched, or content data readily available data under the Data Act?](/artifacts/eu/data-act/faq/readily-available-data.md#are-inferred-derived-highly-enriched-or-content-data-readily-available-data-under-the-data-act) *Module: [EU Data Act Readily Available Data](/artifacts/eu/data-act/faq/readily-available-data.md)* The Data Act context is the starting point for this answer. Inferred or derived data is outside the Chapter II scope described by the Commission. The boundary turns on enrichment: raw and pre-processed data are in scope, while highly enriched data, inferred or derived data, and data resulting from additional investments such as proprietary complex algorithms are out of scope. - Keep raw sensor measurements and ordinary pre-processing separate from model outputs, risk scores, predictions, recommendations, and proprietary analytics. - Do not exclude data merely because it was cleaned, formatted, encrypted, pseudonymised, or anonymised; the Commission FAQ says privacy-enhancing processing alone does not make data inferred or derived. - Record the enrichment step that changes an in-scope measurement into an out-of-scope derived insight. Sources for this answer: - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - The Commission FAQ distinguishes raw and pre-processed data from inferred or derived data and explains that privacy-enhancing technologies alone do not exclude data from scope. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - The Commission explainer states that inferred or derived data and content are out of scope for Chapter II access to connected-product and related-service data. ### [How do direct and indirect access work for readily available data under the Data Act?](/artifacts/eu/data-act/faq/readily-available-data.md#how-do-direct-and-indirect-access-work-for-readily-available-data-under-the-data-act) *Module: [EU Data Act Readily Available Data](/artifacts/eu/data-act/faq/readily-available-data.md)* The Data Act uses two access routes. Article 3 addresses design for direct access where relevant and technically feasible. Articles 4 and 5 address indirect access, where the user or a party acting for the user asks the data holder to make readily available data and relevant metadata accessible to the user or a chosen third party. - For direct access, confirm whether the user can stream or download the data without intervention by the data holder. - For indirect access, provide a simple electronic request path where technically feasible. - Use formats and interfaces that allow reuse, such as commonly used machine-readable exports or APIs, rather than screenshots or manual reports. 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, 4, and 5 set the direct-access, user-access, and third-party-sharing mechanics for readily available data and relevant metadata. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - The Commission FAQ explains direct access, indirect access, and technical expectations for format, quality, timeliness, latency, convenience, and security. ### [What if data is processed at the edge or only temporarily stored under the Data Act?](/artifacts/eu/data-act/faq/readily-available-data.md#what-if-data-is-processed-at-the-edge-or-only-temporarily-stored-under-the-data-act) *Module: [EU Data Act Readily Available Data](/artifacts/eu/data-act/faq/readily-available-data.md)* The Data Act context is the starting point for this answer. Edge processing does not automatically remove data from Chapter II. Commission guidance says readily available data includes raw or pre-processed data that is stored even temporarily, retrievable, or transmitted externally. If raw or pre-processed data was at any point accessible or externally transmittable, the access analysis should not stop merely because the product later processes it locally. - Check whether raw or pre-processed data is stored temporarily, retrievable, or externally transmitted before labeling it unavailable. - Do not treat derived cloud insights as a substitute for the underlying co-generated raw or pre-processed data if that underlying data is obtainable. - Use architecture evidence, not a policy label, to support an edge-processing exclusion. Sources for this answer: - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - The Commission FAQ explains how Chapter II applies to edge processing and when stored, retrievable, or externally transmitted raw or pre-processed data remains readily available. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - The Commission explainer ties Chapter II to raw and pre-processed data that can be easily accessed without disproportionate effort. ### [Which safeguards can limit access to readily available data under the Data Act?](/artifacts/eu/data-act/faq/readily-available-data.md#which-safeguards-can-limit-access-to-readily-available-data-under-the-data-act) *Module: [EU Data Act Readily Available Data](/artifacts/eu/data-act/faq/readily-available-data.md)* The readily-available-data analysis does not override privacy, security, trade-secret, or intellectual-property rules. For personal data, the Data Act is without prejudice to GDPR and privacy law, and Articles 4 and 5 require a valid legal basis where the user is not the data subject whose personal data is requested. - Separate field availability from the safeguard applied to that field; a safeguard is not the same as saying the data is not readily available. - Identify trade secrets, including in relevant metadata, before disclosure and agree confidentiality measures with the user or third party. - For security restrictions, tie the restriction to security requirements in Union or national law and serious adverse effects on health, safety, or security. 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 4 and 5 set conditions for personal data, security restrictions, trade-secret measures, withholding, suspension, and exceptional refusal. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - The Commission FAQ describes the trade-secret safeguard process and confirms that trade-secret claims alone do not prevent Data Act access rights. ## FAQ Pagination - Canonical index (page 1): [/artifacts/eu/data-act/faq/items](/artifacts/eu/data-act/faq/items.md) - Page 1 rule: `/page/1` is intentionally not generated; use the canonical index markdown URL. - Current page: 19 of 24 Pages: [1](/artifacts/eu/data-act/faq/items.md) | [2](/artifacts/eu/data-act/faq/items/page/2.md) | [3](/artifacts/eu/data-act/faq/items/page/3.md) | [4](/artifacts/eu/data-act/faq/items/page/4.md) | [5](/artifacts/eu/data-act/faq/items/page/5.md) | [6](/artifacts/eu/data-act/faq/items/page/6.md) | [7](/artifacts/eu/data-act/faq/items/page/7.md) | [8](/artifacts/eu/data-act/faq/items/page/8.md) | [9](/artifacts/eu/data-act/faq/items/page/9.md) | [10](/artifacts/eu/data-act/faq/items/page/10.md) | [11](/artifacts/eu/data-act/faq/items/page/11.md) | [12](/artifacts/eu/data-act/faq/items/page/12.md) | [13](/artifacts/eu/data-act/faq/items/page/13.md) | [14](/artifacts/eu/data-act/faq/items/page/14.md) | [15](/artifacts/eu/data-act/faq/items/page/15.md) | [16](/artifacts/eu/data-act/faq/items/page/16.md) | [17](/artifacts/eu/data-act/faq/items/page/17.md) | [18](/artifacts/eu/data-act/faq/items/page/18.md) | [19](/artifacts/eu/data-act/faq/items/page/19.md) | [20](/artifacts/eu/data-act/faq/items/page/20.md) | [21](/artifacts/eu/data-act/faq/items/page/21.md) | [22](/artifacts/eu/data-act/faq/items/page/22.md) | [23](/artifacts/eu/data-act/faq/items/page/23.md) | [24](/artifacts/eu/data-act/faq/items/page/24.md) [Previous page](/artifacts/eu/data-act/faq/items/page/18.md) | [Next page](/artifacts/eu/data-act/faq/items/page/20.md) *Recommended next step* *Placement: before sources* ## Turn a Data Act FAQ answer into a scoped review Review one product, dataset, cloud contract, public-sector request, or smart-contract deployment against the cited Data Act source and keep the scope, role, evidence, and unresolved questions together. - [Open Research Copilot](/solutions/research-copilot.md): Check Data Act scope, GDPR boundaries, cloud switching, and contract questions with cited source outputs. - [Talk through Data Act implementation](/contact.md): Review one connected product, data-sharing contract, cloud switch, or public-sector request before committing to an implementation path. --- [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/items/page/19