--- title: "EU Data Act Product Data vs Related Service Data FAQ" canonical_url: "https://www.sorena.io/artifacts/eu/data-act/faq/product-data-and-service-data" source_url: "https://www.sorena.io/artifacts/eu/data-act/faq/product-data-and-service-data" author: "Sorena AI" description: "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." published_at: "2026-05-06" updated_at: "2026-05-06" keywords: - "EU Data Act" - "product data" - "related service data" - "connected product data" - "readily available data" - "raw data" - "pre-processed data" - "metadata" - "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 Product Data vs Related Service Data FAQ 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. *FAQ* *EU* *Data Act* ## EU Data Act Product Data vs Related Service Data FAQ A practical FAQ on the Data Act line between connected product data, related service data, and material outside Chapter II access rights. Use it to classify raw and pre-processed data, necessary metadata, related-service outputs, and inferred or derived analytics without turning every internal dataset into a Data Act export. The EU Data Act gives users access to certain data generated by connected products and related services, but the category is not unlimited. This FAQ explains the Data Act definitions that matter for connected-product telemetry, app or service data, metadata, raw and pre-processed records, and inferred or derived information. ## What is product data under the EU Data Act, and which use-generated fields does it cover? 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. Examples can include sensor measurements, hardware status, malfunction data, position, acceleration, speed, temperature, pressure, pH value, liquid level, flow rate, or similar data generated from the product's use or environment. Purely descriptive material that accompanies a product, such as a manual or packaging text, is not product data simply because it is about the product. - 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? 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. A fridge app that regulates temperature or a machine service that changes operating parameters can generate related service data. Auxiliary consulting, analytics, financial services, regular repair, maintenance, power supply, or connectivity supply are not treated as related services merely because they concern the same product. - 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? 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. Pre-processing does not require the data holder to make substantial new investments in cleaning or transforming data for a requester. The boundary is between making raw data usable and creating enriched outputs or insights from additional investment. - 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? 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. Metadata should not become a catch-all for every internal note, model feature, support annotation, or analytics output. The practical question is whether the metadata is needed to understand and use the raw or pre-processed data being made available. - 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? 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. Examples of out-of-scope material can include highly enriched data, proprietary sensor-fusion outputs, predictive insights, and textual, audio, or audiovisual content often protected by intellectual property rights. Privacy-preserving processes such as anonymisation, pseudonymisation, or encryption should not by themselves be treated as enough to exclude otherwise in-scope data. - 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? 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. If data cannot be directly accessed by the user, the data holder must make readily available data and the necessary metadata accessible without undue delay, in the same quality available to the data holder, easily, securely, free of charge, and in a comprehensive, structured, commonly used, machine-readable format. Where relevant and technically feasible, this can include continuous and real-time access. - 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? 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. For vehicles, industrial machines, health devices, home equipment, agricultural machinery, or similar connected products, the same structure applies: identify the connected product, identify any related service that affects product functions, list raw and pre-processed fields, add necessary metadata, then separate enriched insights, content, trade-secret handling, personal-data handling, and unavailable data. - 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? 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. The record should also support pre-contractual transparency. Before a connected-product or related-service contract, users need clear information about the type, format, estimated volume, frequency, storage, retention, access or retrieval arrangements, data holder identity, third-party sharing route, and trade-secret holder where relevant. - 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? 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. For product data and service data, keep the cited external URL, decision date, reviewer, unresolved assumptions, and implementation artifact together so the answer remains auditable. - 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. ## How should teams assign ownership for Data Act classification work? 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. For product data and service data, use one accountable owner per action, then record consulted teams and evidence dependencies separately. - 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. ## Which evidence makes the Data Act classification answer usable later? 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. For product data and service data, useful evidence includes source URLs, data inventories, contract clauses, request logs, technical controls, customer notices, and approval records. - 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. ## When should the Data Act classification answer be reviewed again? 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. For product data and service data, set a review date and an event trigger instead of relying on a one-time legal note. - 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. ## Primary sources - [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. ## 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 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. - [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 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 classification section* ## Classify Data Act Product and Related Service Data Turn connected-product telemetry, app records, metadata, and enriched outputs into a field-level Data Act classification record for product, legal, privacy, and engineering review. - [Open Research Copilot](/solutions/research-copilot.md): Get cited Data Act answers on product data, related services, metadata, and access boundaries. - [Discuss Data Classification](/contact.md): Review Data Act classification impacts across product design, contracts, request handling, and evidence records. --- [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/product-data-and-service-data