---
title: "EU Data Act Related Services FAQ"
canonical_url: "https://www.sorena.io/artifacts/eu/data-act/faq/related-services"
source_url: "https://www.sorena.io/artifacts/eu/data-act/faq/related-services"
author: "Sorena AI"
description: "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."
published_at: "2026-05-06"
updated_at: "2026-05-06"
keywords:
  - "EU Data Act"
  - "Regulation (EU) 2023/2854"
  - "related services"
  - "connected products"
  - "product data"
  - "related service data"
---
**[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 Related Services FAQ

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.

*FAQ* *EU* *Data Act*

## EU Data Act Related Services FAQ

A related service is product-linked software or another digital service that affects how a connected product functions.

Use this FAQ to separate related services from connectivity, power, repair, unrelated software, content, and highly enriched derived data.

The EU Data Act treats related services as part of the connected-product data access framework. This FAQ explains the definition, the product link, product data and related service data, user and data holder roles, access rights, examples, safeguards, and exclusions without relying on generic compliance workflow language.

## What is a related service under the EU Data Act for Related Services implementation evidence?

Under the Data Act, a related service is a digital service, other than an electronic communications service, that is connected with a product at purchase, rent, or lease in a way that the product would lose one or more functions without it. A service can also become a related service later if the manufacturer or a third party connects it to the product to add, update, or adapt the product's functions.

The Commission FAQ describes the practical test as a digital service linked to the operation of a connected product that affects the product's functionality, for example by transmitting data or commands to it.

- Ask whether the service is digital and connected to the product's operation.
- Check whether the service is needed for, or changes, at least one product function.
- Do not classify ordinary connectivity, power supply, repair, maintenance, auxiliary analytics, consulting, or financial services as related services solely because they support the product ecosystem.

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 and excludes electronic communications services from that definition.
- [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Question 10 explains the operational test for identifying a related service and gives product-control examples.

## How does a related service link to a connected product under the Data Act?

The service must be tied to a connected product, not merely offered by the same company. Under the Data Act, a connected product is an item that obtains, generates, or collects data about its use or environment and can communicate product data through an electronic communications service, physical connection, or on-device access.

The Commission FAQ adds two practical conditions for related services: there must be bidirectional data exchange between the connected product and the service provider, and the service must affect the product's functions, behaviour, or operation.

- Document the product function the service enables, adds, updates, or adapts.
- Record the data or command path between the product and service provider.
- Treat product marketing, user expectations, contract wording, replaceability, and pre-installation as useful facts, not substitutes for the legal definition.

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 by data generation or collection, communication capability, and primary function.
- [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Question 10 identifies bidirectional data exchange and effect on product functions as practical related-service indicators.

## What are examples of related services for connected products under the Data Act?

Examples under the Data Act include an app that changes smart-light brightness, software that regulates a connected fridge's temperature, or a product-linked service that sends commands or updates to a connected device so that the device performs or changes a function.

A service is less likely to be a related service when it merely surrounds the product commercially, such as regular repair, maintenance, auxiliary consulting, analytics, or financing, without itself being connected to and affecting the connected product's functions.

- In scope: a product app that sends settings or commands to the connected product.
- Potentially in scope: software later connected to the product to add, update, or adapt functions.
- Not enough by itself: customer support, ordinary repair, maintenance, or analytics that does not affect the product's functions.

Sources for this answer:

- [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Question 10 gives practical examples of services that affect connected-product functions and lists services that cannot be related services.
- [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Article 2(6) supports the distinction between function-affecting product-linked services and adjacent services.

## What product data and related service data are in scope under the Data Act?

Under the Data Act, product data is data generated by use of the connected product that the manufacturer designed to be retrievable by the user, data holder, third party, or manufacturer through electronic communications, physical connection, or on-device access. Related service data is data representing digitised user actions or events related to the connected product during the provision of the related service.

The Commission FAQ summarises the Chapter II access scope as raw and pre-processed data that are readily available to a data holder, together with metadata needed to make the data understandable and usable. Highly enriched inferred or derived data is outside that access scope.

- Include raw and pre-processed product data and related service data where the data holder can lawfully obtain it without disproportionate effort.
- Include relevant metadata needed to interpret and use the data.
- Separate in-scope data from inferred insights, derived analytics, and content protected by intellectual property rights.

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), Article 2(16), and Article 2(17) define product data, related service data, and readily available data.
- [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Questions 4 and 5 explain that raw and pre-processed data are generally in scope, while highly enriched inferred or derived data is out of scope.

## Who is the user and who is the data holder for a related service under the Data Act?

Under the Data Act, a user is a natural or legal person that owns a connected product, has temporary contractual rights to use it, or receives related services. A data holder is the person or entity with the right or obligation to use and make available data, including product data or related service data retrieved or generated during the related service where the contract provides for that.

For a related service, the provider can become a data holder once it has a contractual relationship with the user and renders the service in a way that creates data. The same ecosystem may involve several users, such as an owner and a renter, so access arrangements should identify which user has rights over which product or service data.

- Identify the connected-product owner, lessee, renter, or other person with temporary contractual use rights.
- Identify any person receiving the related service as a user for that service.
- Name the service provider or other party that lawfully obtains or can obtain the readily available 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(12) defines user and Article 2(13) defines data holder for 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) - Questions 10, 14, and 16 explain how related-service providers and multiple users can fit into the Chapter II role model.

## What access rights apply to related service data under the Data Act?

Under the Data Act, related services must be designed and provided so product data and related service data, including relevant metadata, are by default easy, secure, free of charge, comprehensive, structured, commonly used, machine-readable, and where relevant and technically feasible directly accessible to the user.

Where the user cannot access the data directly from the connected product or related service, the data holder must make readily available data accessible to the user without undue delay and, where relevant and technically feasible, continuously and in real time. A user may also ask the data holder to make the readily available data available to a third party.

- Direct access means the user can access, stream, or download the data without asking the data holder to approve the request.
- Indirect access means the user asks the data holder, for example through a portal or other electronic request path.
- Third-party sharing is user-driven and is separate from the data holder's own permitted use of non-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) - Articles 3, 4, and 5 set the design, user access, and user-directed third-party sharing duties for 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) - Question 17 explains direct and indirect access routes for data generated by connected products or related services.

## What information should be provided before a related service contract under the Data Act?

Before concluding a related-service contract under the Data Act, the prospective provider must give the user clear information about product data expected to be obtained, related service data expected to be generated, data access or retrieval arrangements, storage arrangements and retention duration, intended use of readily available data, data holder identity, contact means, third-party sharing requests, complaint rights, trade-secret status, and contract duration and termination.

This pre-contractual information matters because users need to understand both the product data already produced by the connected product and the service data that will arise once the related service starts operating.

- Describe the nature, volume, and collection frequency of product data the provider expects to obtain.
- Describe the nature and volume of related service data expected to be generated.
- Explain access, retrieval, third-party sharing, retention, trade-secret, complaint, and termination arrangements in clear language.

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(3) lists the pre-contractual information that a prospective provider of a related service must provide to users.

## Which services or data are excluded from related-service treatment under the Data Act?

Under the Data Act, the related-service definition excludes electronic communications services. The Commission FAQ also states that connectivity, power supply, aftermarket services such as auxiliary consulting and analytics, financial services, and regular repair and maintenance cannot be considered related services.

The Chapter II data access scope also excludes certain material even when a connected product or related service is involved. Out-of-scope material includes highly enriched inferred or derived data resulting from additional investments, and content such as textual, audio, or audiovisual material often protected by intellectual property rights.

- Do not treat connectivity or power supply as a related service merely because the product needs them.
- Do not treat routine repair, maintenance, consulting, analytics, or financing as a related service unless the service itself meets the product-function test.
- Do not treat inferred insights, derived analytics, or creative content as ordinary product or related service data access outputs.

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) excludes electronic communications services from the related-service definition, while Recitals 15 and 16 distinguish in-scope data from derived data and content.
- [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Questions 4, 5, 6, and 10 explain exclusions for highly enriched data, content, and services that cannot be related services.

## How do privacy, trade secrets, and security safeguards affect related-service data access under the Data Act?

The Data Act does not override EU personal-data rules. If the user is not the data subject, personal data generated by use of a connected product or related service may be made available only where there is a valid legal basis under GDPR and any relevant conditions under EU privacy rules are met.

Trade secrets must be preserved. The data holder or trade-secret holder must identify protected data and agree proportionate technical and organisational measures with the user or third party. In defined circumstances, the data holder may withhold, suspend, or refuse access to specific trade-secret data, but the decision must be substantiated in writing and notified to the competent authority.

- Classify whether requested related-service data includes personal data, non-personal data, trade secrets, or mixed data.
- Use proportionate confidentiality, access, and security measures rather than blanket refusals.
- Keep written reasons for any withholding, suspension, or refusal based on security requirements or trade secrets.

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 personal-data, security, and trade-secret conditions for user access and user-directed third-party sharing.
- [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - The FAQ explains that Data Act access to personal and non-personal connected-product and related-service data must operate alongside GDPR and trade-secret safeguards.

## What record should a team keep when classifying a Data Act related service?

Keep a short Data Act related-service register for each product-linked digital service. The record should identify the connected product, the service, the product function affected, the bidirectional data or command path, the user, the data holder, the product data, the related service data, the access route, and any exclusions or safeguards.

The register should be operational, not just legal. It should connect contract text, product architecture, user access mechanisms, and support handling so that a user request can be answered without reclassifying the service from scratch.

- Record whether the service is connected at purchase, rent, or lease, or later connected to add, update, or adapt product functions.
- Record which raw or pre-processed data and metadata are readily available, and which data are excluded as derived, inferred, content, or not readily available.
- Record the access method, owner, source citation, safeguard, and reason for any refusal or limitation.

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 2 to 5 provide the classification fields needed to connect service status, data categories, roles, and access route.
- [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Question 10 and the data-in-scope section support a practical register that records product linkage, service effect, data type, and exclusions.

## What should a visitor check under the EU Data Act before treating software as a related service?

Start with three checks: is the service digital, is it linked to the connected product, and does it affect the product's function, behaviour, or operation? If the answer to any of those is no, the service is less likely to be a related service under the Data Act.

Examples and contract wording can help, but the legal test remains the same: the service must be more than an adjacent business service and must interact with the connected product in a way that matters to how the product works.

- Check whether the product would lose a function without the service.
- Check whether data or commands move between the product and the service provider.
- Check whether the service is simply connectivity, power, repair, or another excluded service.

Sources for this answer:

- [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Question 10 gives the practical test for identifying a related service and lists services that cannot be related services.
- [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Article 2(6) sets the legal definition of related service.

## How should a visitor decide what Data Act evidence to keep for a related-service classification?

Keep the legal source, the product or service description, the product function affected, the relevant data flows, and the reason the service was or was not treated as a related service. That makes it easier to show why the classification fits the Data Act definition.

If the service is later updated, repeat the check because the Data Act allows a service to become a related service when it is later connected to a product to add, update, or adapt functions.

- Save the source clause or FAQ reference you relied on.
- Save the product-function analysis and any bidirectional data-exchange notes.
- Review the classification again if the service changes or is newly connected to the 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(6) covers services connected at the time of purchase, rent or lease, and services later connected to add, update or adapt functions.
- [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Question 10 explains the practical indicators that help document a related-service classification.

## 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 Data Act definitions of connected product, related service, user, data holder, product data, related service data, readily available data, and user access and sharing duties.
- [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ source for the practical related-service test, examples, data-in-scope guidance, user and data holder role explanations, and exclusions.
- [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission overview source confirming that the Data Act gives users control over data generated by connected devices and helps them share it with third parties.

## 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 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 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 related services

Turn each product-linked app or digital add-on into a maintained related-service record covering product functions, generated data, access routes, exclusions, and safeguards.

- [Open Research Copilot](/solutions/research-copilot.md): Get cited answers on Data Act related-service scope, product data, related service data, and access rights.
- [Discuss Related Services](/contact.md): Review related-service classification for product apps, connected devices, contracts, data maps, and user access workflows.


---

[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/related-services