--- title: "Data Act Exportable Data and Metadata FAQ" canonical_url: "https://www.sorena.io/artifacts/eu/data-act/faq/exportable-data-and-metadata" source_url: "https://www.sorena.io/artifacts/eu/data-act/faq/exportable-data-and-metadata" author: "Sorena AI" description: "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." published_at: "2026-05-06" updated_at: "2026-05-06" keywords: - "EU Data Act" - "exportable data" - "metadata" - "readily available data" - "product data" - "related service data" - "cloud switching" - "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) --- # Data Act Exportable Data and Metadata FAQ 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. *FAQ* *EU* *Data Act* ## EU Data Act Exportable Data and Metadata FAQ Which connected-product, related-service, and cloud-switching data must be exportable under the Data Act. Use this FAQ to separate readily available data from excluded material, identify required metadata, document export formats, and prepare cloud switching information. The Data Act uses exportability in two related settings. For connected products and related services, users must be able to access readily available product data, related service data, and the metadata needed to interpret and use that data. For data processing services such as cloud and edge services, customers must be able to port exportable data and digital assets when switching provider or moving to on-premises infrastructure. ## What does the Data Act mean by readily available product and related service data? The Data Act context is the starting point for this answer. For connected products and related services, the key scope term is readily available data. It 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 beyond a simple operation. Product data is generated by the use of a connected product and designed to be retrievable from that product. Related service data represents user actions or events related to the connected product during the provision of a related service. The Commission explains the practical scope as raw and pre-processed data generated from use of a connected product or related service, where that data is readily available to the data holder. - Include sensor and status data that the product or related service generates and the data holder can access without disproportionate effort. - Treat pre-processed data as in scope when the processing makes the data understandable and usable before later analysis. - Do not label data as out of scope merely because the company calls it telemetry, logs, diagnostics, or operational 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) - Defines product data, related service data, and readily available data, and sets the Article 3 and 4 access duties. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Explains that Chapter II covers raw and pre-processed connected-product and related-service data, including relevant metadata. ## What metadata has to be provided with Data Act product and related service data? The Data Act context is the starting point for this answer. The metadata obligation is not a separate nice-to-have documentation exercise. Article 3 requires product data and related service data to include relevant metadata necessary to interpret and use the data. Article 4 uses the same standard where the user cannot directly access the data and the data holder must make readily available data accessible. In practice, an export that contains values but omits basic context can fail the point of the access right. The metadata set should let the user or an authorized third party understand what each field is, when and how it was generated, how units and identifiers work, and what quality or access limitations apply. - Map field names, units, timestamps, device or service identifiers, collection frequency, retention limits, and known quality constraints. - Explain data structures, data formats, vocabularies, classification schemes, taxonomies, and code lists where those are available and needed for use. - Flag trade-secret or security-related metadata only where a grounded Data Act limitation applies; do not use vague confidentiality labels to strip interpretive context. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Requires relevant metadata necessary to interpret and use connected-product and related-service data. - [Commission standardisation request for a European Trusted Data Framework](https://ec.europa.eu/transparency/documents-register/api/files/C(2025)4135_1/de00000001072897?rendition=false&ref=sorena.io) - Grounds practical metadata categories for discoverability, data structures, formats, vocabularies, taxonomies, code lists, and auditability in Data Act-related standardisation work. ## Which export format should be used for connected-product and related-service data under the Data Act? The Data Act does not name one universal file type for every connected product or related service. Instead, it requires access in a comprehensive, structured, commonly used and machine-readable format. Where relevant and technically feasible, Article 3 also expects direct access by default, and Article 4 expects continuous and real-time access where relevant and technically feasible. A practical export catalogue should therefore state the actual delivery method and format for each dataset: API, bulk file, real-time stream, device interface, or another technical route. The format should be understandable outside the vendor's internal systems and should include the metadata needed to interpret and use the data. - Document the chosen format and why it is commonly used and machine-readable for the data category. - Test that a user or authorized third party can parse the export with the published metadata, not just receive a file. - State any technical limits on continuous or real-time access in the access documentation. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Sets the required format standard for connected-product and related-service data access. ## What must be disclosed before a connected product or related service contract is concluded under the Data Act? The Data Act context is the starting point for this answer. Before a connected product purchase, rent, or lease contract is concluded, the seller, renter, or lessor must give the user clear and comprehensible information about the type, format, and estimated volume of product data the product can generate, whether it can generate data continuously and in real time, where it can store data, retention information, and how the user can access, retrieve, or erase data. Before a related service contract is concluded, the provider must disclose the nature, estimated volume, and collection frequency of product data it expects to obtain, the nature and estimated volume of related service data to be generated, access and retrieval arrangements, storage and retention arrangements, whether readily available data will be used by the prospective data holder, and how the user can request sharing with a third party. - Keep pre-contract copy aligned with the actual export catalogue and access route. - Use stable documentation or a durable web page where the user can store and reproduce the information. - Refresh the disclosure when product updates, related service changes, or retention changes affect generated or accessible 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 3 lists pre-contract information duties for connected products and related services. ## What does exportable data mean for cloud and other data processing services under the Data Act? The Data Act context is the starting point for this answer. For cloud and other data processing services, exportable data is a defined term used for switching obligations. It covers input and output data, including metadata, directly or indirectly generated or cogenerated by the customer's use of the data processing service. It excludes assets or data protected by intellectual property rights, or constituting a trade secret, of the provider or third parties. The customer-facing question is not only whether data can be downloaded. The provider must remove obstacles that inhibit customers from porting exportable data and digital assets to another provider of the same service type or to on-premises ICT infrastructure. - List customer input data, output data, customer-generated digital assets, and metadata needed to restore use after switching. - Separate provider-owned service internals from customer exportable data so exclusions are narrow and reviewable. - Cover both switching to another provider and porting to on-premises ICT infrastructure. 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 exportable data for Articles 23 to 31 and sets cloud switching and porting obligations. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Explains that cloud switching data includes input and output data, including metadata, generated by customer use of the service. ## What cloud switching format and register information should customers receive under the Data Act? The Data Act context is the starting point for this answer. A provider of data processing services must give customers information on available switching and porting procedures, including available methods and formats, and known restrictions or technical limitations. The provider must also refer customers to an up-to-date online register with details of data structures, data formats, relevant standards, and open interoperability specifications in which the exportable data is available. Where switching is between services of the same service type and no relevant common specifications or harmonised interoperability standards have been published in the central Union standards repository, the provider must, at the customer's request, export all exportable data in a structured, commonly used and machine-readable format. - Publish a register that names data structures, formats, standards, and open interoperability specifications for exportable data. - Put known switching restrictions and technical limitations in the customer documentation before they become an exit dispute. - Keep the register current when interfaces, formats, common specifications, or harmonised standards 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) - Articles 26 and 30 require switching procedure information, an online register, and machine-readable export where standards are not yet published. ## Which data can be excluded from Data Act exports for exportability records? The Data Act context is the starting point for this answer. For connected products and related services, the ordinary access scope does not include inferred or derived information that results from additional investments into assigning values or insights, particularly through proprietary complex algorithms, unless the user and data holder agree otherwise. The Commission gives examples such as highly enriched data and content being outside the Chapter II scope. For cloud switching, exportable data excludes provider or third-party assets or data protected by intellectual property rights or constituting trade secrets. Providers are also not required to develop new technologies or services, disclose protected digital assets, or compromise customer or provider security and service integrity. - Do not exclude raw or pre-processed connected-product data just because it is commercially sensitive. - Do not include films, media content, proprietary algorithms, provider service internals, or protected third-party assets simply because they appear in the same system. - Document each exclusion with the specific category: inferred or derived data, protected intellectual property, trade secret, security and integrity risk, or unavailable 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) - Distinguishes in-scope raw and pre-processed data from inferred or derived information and excludes protected provider or third-party assets in cloud switching. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Explains that inferred or derived data and content are out of scope, and gives practical connected-product examples. ## How should trade secrets and security limits be handled without blocking legitimate exports under the Data Act? The Data Act preserves trade secrets, but it does not allow a broad confidentiality label to erase the access right. For user access and third-party sharing, the data holder or trade secret holder must identify protected data, including in the relevant metadata, and agree proportionate technical and organisational measures to preserve confidentiality. Withholding, suspending, or refusing access on trade-secret grounds is limited and must be substantiated. Security restrictions for connected products require a risk that security requirements laid down by Union or national law would be undermined with serious adverse effects on health, safety, or security of natural persons. - Identify trade-secret data and related metadata precisely before applying confidentiality measures. - Use proportionate safeguards such as confidentiality agreements, access controls, technical standards, and strict protocols where supported by the facts. - Keep written reasons for any withholding, suspension, refusal, or security restriction. 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 trade-secret safeguards, withholding and refusal conditions, and security restriction rules. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Summarizes the Data Act trade-secret and security limitation mechanisms for connected-product data sharing. ## What evidence should an exportability register contain under the Data Act? A useful exportability register should make the Data Act answer reproducible. For each connected product, related service, or cloud service, record the data category, role, user or customer route, format, metadata, access method, retention or retrieval constraint, exclusion reason, safeguard, and owner. The register should be specific enough to support pre-contract disclosures, user requests, third-party sharing requests, cloud switching requests, and complaints. It should also show whether the same dataset is governed by connected-product access rules, cloud switching rules, or both. - For connected products and related services, include type, format, estimated volume, collection frequency where relevant, storage location, retention, and access or retrieval method. - For cloud services, include exportable data categories, digital assets, methods and formats, known restrictions, technical limits, and the online register entry. - For exclusions, include the source-linked reason and the remaining data and metadata that will still be provided. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Supports the register fields through Article 3 pre-contract disclosures, Article 4 access obligations, and Article 26 switching information duties. - [Commission standardisation request for a European Trusted Data Framework](https://ec.europa.eu/transparency/documents-register/api/files/C(2025)4135_1/de00000001072897?rendition=false&ref=sorena.io) - Supports using catalogue metadata, semantic assets, access descriptions, and auditability fields for data-sharing records. ## How should teams document the Data Act source and review trail for exportability decisions? For exportable data and metadata, 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 exportable data and metadata, keep the cited external URL, decision date, reviewer, unresolved assumptions, and implementation artifact together so the answer remains auditable. - Record the Data Act article or recital and the source URL that supports the interpretation. - Store the owner, affected workflow, evidence artifact, and review trigger in the same register entry. - Keep the review date and unresolved assumptions so later reviewers can see why the decision was made. ## Who should own Data Act exportability decisions and follow-up work? For exportable data and metadata, the Data Act workflow should name the legal, product, procurement, cloud, support, or security owner who can change the affected process. For exportable data and metadata, use one accountable owner per action, then record consulted teams and evidence dependencies separately. - Assign one accountable owner for each exportability decision, with clear backup responsibility. - Note which teams must update contracts, technical export routes, customer notices, or security controls. - Keep the owner linked to the evidence artifact and the next review trigger. ## What Data Act implementation evidence should teams keep so exportability decisions can be reused later? For exportable data and metadata, 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 exportable data and metadata, useful evidence includes source URLs, data inventories, contract clauses, request logs, technical controls, customer notices, and approval records. - Keep evidence that shows the actual data category, format, metadata, and exclusion handling. - Attach the supporting source URL and the approval record to the same implementation note. - Retain request logs, notices, and technical controls so the decision can be checked later. ## 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 text for readily available data, product data, related service data, metadata, access formats, cloud switching, exportable data, exclusions, trade secrets, and security limits. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer used for practical scope examples covering raw and pre-processed connected-product data, relevant metadata, exclusions, trade secrets, security limits, and cloud switching. - [Commission standardisation request for a European Trusted Data Framework](https://ec.europa.eu/transparency/documents-register/api/files/C(2025)4135_1/de00000001072897?rendition=false&ref=sorena.io) - Official Commission standardisation request used for practical metadata and catalogue fields relevant to discoverability, data formats, vocabularies, access descriptions, and auditability. ## 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 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 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 implementation section* ## Build a Data Act Exportability Register Turn Data Act export obligations into a maintained register of datasets, metadata, formats, access routes, cloud switching information, safeguards, and exclusions. - [Open Research Copilot](/solutions/research-copilot.md): Get cited answers on Data Act exportable data, metadata, connected-product access, and cloud switching obligations. - [Discuss Data Act Exportability](/contact.md): Review export formats, metadata, switching registers, and exclusions across product, cloud, legal, and support 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/exportable-data-and-metadata