--- 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/25" author: "Sorena AI" description: "EU Data Act FAQ index covering connected-product access, third-party sharing, B2G exceptional need, cloud switching, smart contracts, GDPR boundaries, unfair terms, and application dates." published_at: "2026-05-06" updated_at: "2026-07-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 EU Data Act FAQ index covering connected-product access, third-party sharing, B2G exceptional need, cloud switching, smart contracts, GDPR boundaries, unfair terms, 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. This index helps orient product, legal, cloud, procurement, data protection, security, and public-sector request teams before opening the deeper topic modules. The Data Act, Regulation (EU) 2023/2854, has applied generally since 12 September 2025. It gives qualifying users access to readily available data from connected products and related services, sets terms for mandatory business-to-business data sharing, creates a narrow public-sector exceptional-need route, and regulates switching between data processing services. It also addresses unfair contract terms, unlawful third-country government access to non-personal data, interoperability, and smart contracts. GDPR and sector-specific EU rules continue to apply alongside it. ## Definitions ### EU Data Act **Term:** Data Act The Data Act is Regulation (EU) 2023/2854, a directly applicable EU regulation on access to and use of data. It covers connected-product and related-service data, legally required business-to-business data sharing, exceptional public-sector requests, switching between data processing services, unfair data-contract terms, interoperability, and smart contracts. **Why it matters here:** The applicable chapter depends on the actor, data, product or service, and transaction. The regulation has applied generally since 12 September 2025, but several duties have separate transition rules. Sources: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) ## 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 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 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 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 ### [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 32: Foreign 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 ### [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. - 13 items ### [EU Data Act Functional Equivalence: IaaS Switching 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 ### [EU Data Act Indirect Access Request Workflow 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 ### [EU Data Act Interoperability Standards: Articles 33-36](/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 ### [EU Data Act Model Terms and Cloud Clauses 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 ### [EU Data Act Non-Emergency Public-Sector Request 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 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](/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 Public Emergency Request 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 ### [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 ### [EU Data Act: Non-Personal Data and Mixed Datasets](/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 Browse all indexed questions: [/artifacts/eu/data-act/faq/items](/artifacts/eu/data-act/faq/items.md) ## All FAQ items *Page 25 of 32. Showing 15 of 470 items.* ### [How should teams assign ownership for Data Act Public Emergency Requests implementation work?](/artifacts/eu/data-act/faq/public-emergency-requests.md#how-should-teams-assign-ownership-for-data-act-public-emergency-requests-implementation-work) *Module: [EU Data Act Public Emergency Request](/artifacts/eu/data-act/faq/public-emergency-requests.md)* Assign one accountable owner for the Data Act legal assessment and one for the operational response, then keep the rest of the stakeholders as consulted teams. The legal owner should assess Article 15, Article 17, Article 18, and Article 19 issues; the operational owner should coordinate data extraction, security controls, delivery, and recordkeeping. - Use one owner for legal review, one for technical delivery, and one for records retention. - Record the business unit that controls the requested data and the people who can approve disclosure or refusal. - Track the review trigger and any escalation path separately so the workflow does not depend on ad hoc decisions. 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 Chapter V public emergency exceptional-need requests, required request content, data holder response duties, confidentiality, compensation, erasure, and onward sharing. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer for Chapter V business-to-government data sharing, public emergency examples, data type expectations, compensation context, and the once-only principle. - [European Commission Data Act FAQ](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Technical FAQ used for non-binding implementation context on verifying Chapter V requests, cross-border requests, reuse limits, repetitive requests, and safeguards. ### [Which records make a public-emergency decision reviewable later?](/artifacts/eu/data-act/faq/public-emergency-requests.md#which-records-make-a-public-emergency-decision-reviewable-later) *Module: [EU Data Act Public Emergency Request](/artifacts/eu/data-act/faq/public-emergency-requests.md)* Data Act evidence should show the full chain from request to response. The most useful artifacts are the written request, the Article 17 completeness check, the decision memo on Article 15 exceptional need, the refusal or modification notice if any, the delivery log, and the notices sent to the competent authority or other authorities. - Map the public emergency decision to a cited Data Act source URL. - Store the owner, affected workflow, evidence artifact, and review trigger. - Keep all request, response, and escalation records together instead of splitting them across teams. 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 Chapter V public emergency exceptional-need requests, required request content, data holder response duties, confidentiality, compensation, erasure, and onward sharing. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer for Chapter V business-to-government data sharing, public emergency examples, data type expectations, compensation context, and the once-only principle. - [European Commission Data Act FAQ](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Technical FAQ used for non-binding implementation context on verifying Chapter V requests, cross-border requests, reuse limits, repetitive requests, and safeguards. ### [What does readily available data mean under the EU Data Act?](/artifacts/eu/data-act/faq/readily-available-data.md#what-does-readily-available-data-mean-under-the-eu-data-act) *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)* 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?](/artifacts/eu/data-act/faq/readily-available-data.md#does-readily-available-data-include-metadata) *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 help people discover or use 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)* 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)* 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. ### [What should a data holder keep to answer readily available data requests consistently under the Data Act?](/artifacts/eu/data-act/faq/readily-available-data.md#what-should-a-data-holder-keep-to-answer-readily-available-data-requests-consistently-under-the-data-act) *Module: [EU Data Act Readily Available Data](/artifacts/eu/data-act/faq/readily-available-data.md)* Maintain a field-level readily-available-data register for each connected product and related service. The register should identify the product or service, user-facing data category, field name, source system, format, metadata supplied, retention period, access route, quality level, latency, and the reason for any exclusion or safeguard. - Add a short reason for each out-of-scope field, such as content, inferred or derived insight, unavailable due to product design, or not product or related-service data. - Keep request logs showing the requester, user relationship, requested fields, access route, delivery format, metadata supplied, and safeguard decisions. - Update the register when product architecture, related-service contracts, APIs, telemetry pipelines, retention settings, or data-holder roles change. 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 requires pre-contractual information about generated data, storage, retention, access, retrieval, erasure, data holders, and third-party sharing mechanics. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - The Commission FAQ provides the practical criteria needed for a field-level register: data category, enrichment level, metadata, access route, and technical feasibility. ### [What records help justify a readily available data decision later under the EU Data Act?](/artifacts/eu/data-act/faq/readily-available-data.md#what-records-help-justify-a-readily-available-data-decision-later-under-the-eu-data-act) *Module: [EU Data Act Readily Available Data](/artifacts/eu/data-act/faq/readily-available-data.md)* Keep the Data Act source clause, the relevant product or service description, the field-level classification, and the reason each field is in scope or out of scope. Add the access route, the metadata supplied, and any safeguard relied on so the decision can be rechecked if the product or service changes. - Keep the Data Act source URL with each decision record. - Store the classification basis, the decision owner, and the review date. - Link the decision to the relevant inventory or request log. 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 source for Article 2 definitions, Chapter II access duties, safeguards, and Article 50 timing: general application from 12 September 2025 and the Article 3(1) design duty for connected products and related services placed on the market after 12 September 2026. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ used for practical interpretation of in-scope raw and pre-processed data, metadata, enrichment boundaries, edge processing, direct and indirect access, and trade-secret handling. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer used for accessible examples of connected products, related services, Chapter II data sharing, inferred or derived data, content exclusions, and user access mechanics. ### [Which team should own readily available data implementation work under the EU Data Act long term?](/artifacts/eu/data-act/faq/readily-available-data.md#which-team-should-own-readily-available-data-implementation-work-under-the-eu-data-act-long-term) *Module: [EU Data Act Readily Available Data](/artifacts/eu/data-act/faq/readily-available-data.md)* Ownership of the Data Act answer should sit with the team that can change the data path or the access process, usually product, engineering, or platform operations, with legal and privacy input where needed. The owner should be able to explain how the field is generated, where it is stored, and how a user or third party receives it. - Name one accountable owner for each connected product or related service. - List legal, privacy, security, and support teams as contributors. - Tie ownership to the system or workflow that actually serves the 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) - Binding source for Article 2 definitions, Chapter II access duties, safeguards, and Article 50 timing: general application from 12 September 2025 and the Article 3(1) design duty for connected products and related services placed on the market after 12 September 2026. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ used for practical interpretation of in-scope raw and pre-processed data, metadata, enrichment boundaries, edge processing, direct and indirect access, and trade-secret handling. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer used for accessible examples of connected products, related services, Chapter II data sharing, inferred or derived data, content exclusions, and user access mechanics. ### [What evidence makes a readily available data answer usable later under the EU Data Act for reviewers?](/artifacts/eu/data-act/faq/readily-available-data.md#what-evidence-makes-a-readily-available-data-answer-usable-later-under-the-eu-data-act-for-reviewers) *Module: [EU Data Act Readily Available Data](/artifacts/eu/data-act/faq/readily-available-data.md)* Useful Data Act evidence is concrete and easy to revisit: source URLs, data inventories, contract clauses, API descriptions, request logs, and any technical or organisational safeguards. The evidence should show why the field was treated as product data, related service data, metadata, or out of scope. - Save the source URL and the relevant clause reference. - Keep inventories, request logs, and architecture notes together. - Record any safeguard or exclusion that affects the answer. 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 source for Article 2 definitions, Chapter II access duties, safeguards, and Article 50 timing: general application from 12 September 2025 and the Article 3(1) design duty for connected products and related services placed on the market after 12 September 2026. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ used for practical interpretation of in-scope raw and pre-processed data, metadata, enrichment boundaries, edge processing, direct and indirect access, and trade-secret handling. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer used for accessible examples of connected products, related services, Chapter II data sharing, inferred or derived data, content exclusions, and user access mechanics. ### [When should the Data Act Readily Available Data FAQ answer be reviewed again?](/artifacts/eu/data-act/faq/readily-available-data.md#when-should-the-data-act-readily-available-data-faq-answer-be-reviewed-again) *Module: [EU Data Act Readily Available Data](/artifacts/eu/data-act/faq/readily-available-data.md)* Review the Data Act answer when the product design, related service, telemetry path, retention policy, or access interface changes. A new firmware release, a changed API, or a new contract term can move a field into or out of scope, or change how the user receives it. - Review after architecture, contract, or retention changes. - Review when the legal basis or safeguard changes. - Set both a calendar review date and an event trigger. 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 source for Article 2 definitions, Chapter II access duties, safeguards, and Article 50 timing: general application from 12 September 2025 and the Article 3(1) design duty for connected products and related services placed on the market after 12 September 2026. - [European Commission - Data Act FAQs v1.4](https://ec.europa.eu/newsroom/dae/redirection/document/108144?ref=sorena.io) - Commission FAQ used for practical interpretation of in-scope raw and pre-processed data, metadata, enrichment boundaries, edge processing, direct and indirect access, and trade-secret handling. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer used for accessible examples of connected products, related services, Chapter II data sharing, inferred or derived data, content exclusions, and user access mechanics. ### [What is a related service under the EU Data Act?](/artifacts/eu/data-act/faq/related-services.md#what-is-a-related-service-under-the-eu-data-act) *Module: [EU Data Act Related Services](/artifacts/eu/data-act/faq/related-services.md)* 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. - 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. ## 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: 25 of 32 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) | [25](/artifacts/eu/data-act/faq/items/page/25.md) | [26](/artifacts/eu/data-act/faq/items/page/26.md) | [27](/artifacts/eu/data-act/faq/items/page/27.md) | [28](/artifacts/eu/data-act/faq/items/page/28.md) | [29](/artifacts/eu/data-act/faq/items/page/29.md) | [30](/artifacts/eu/data-act/faq/items/page/30.md) | [31](/artifacts/eu/data-act/faq/items/page/31.md) | [32](/artifacts/eu/data-act/faq/items/page/32.md) [Previous page](/artifacts/eu/data-act/faq/items/page/24.md) | [Next page](/artifacts/eu/data-act/faq/items/page/26.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.md) | [Terms of Use](https://www.sorena.io/terms-of-use.md) | [DMCA](https://www.sorena.io/dmca.md) | [About Us](https://www.sorena.io/about-us.md) (c) 2026 Sorena AB (559573-7338). All rights reserved. Source: https://www.sorena.io/artifacts/eu/data-act/faq/items/page/25.md