---
title: "EU Data Act and Common European Data Spaces FAQ"
canonical_url: "https://www.sorena.io/artifacts/eu/data-act/faq/data-act-and-common-european-data-spaces"
source_url: "https://www.sorena.io/artifacts/eu/data-act/faq/data-act-and-common-european-data-spaces"
author: "Sorena AI"
description: "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."
published_at: "2026-05-06"
updated_at: "2026-05-06"
keywords:
  - "EU Data Act"
  - "Regulation (EU) 2023/2854"
  - "common European data spaces"
  - "Article 33"
  - "data-space interoperability"
---
**[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 and Common European Data Spaces FAQ

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.

*FAQ* *EU* *Data Act*

## EU Data Act and common European data spaces FAQ

How Data Act interoperability duties apply when a data-space participant offers data or data services to other participants.

Use this FAQ to separate binding Data Act duties from Data Governance Act trust rules, sector data-space governance, and voluntary participation choices.

Common European data spaces are not a shortcut around the EU Data Act. They combine data infrastructure, governance rules, standards, and sector arrangements. The binding Data Act question is narrower: when an organisation participates in a data space and offers data or data services to other participants, Article 33 interoperability requirements can apply alongside any separate connected-product, B2B, B2G, cloud-switching, privacy, trade-secret, or sector rules.

## Does the EU Data Act require companies to join common European data spaces?

No. The grounding sources support common European data spaces as EU-backed infrastructure and governance initiatives, not as a general Data Act duty for every company to join. The Data Act creates obligations for specific actors and fact patterns, including connected-product data access, B2B data sharing, public-sector exceptional-need requests, cloud switching, interoperability, and smart contracts.

For data spaces, the relevant Data Act trigger is usually narrower: Article 33 applies to participants in data spaces that offer data or data services to other participants. Participation can still be commercially or sectorally important, but do not describe it as mandatory unless a separate sector rule, procurement condition, contract, or programme requirement says so.

- Ask whether the organisation is a data-space participant offering data or data services to other participants.
- Separate voluntary participation, sector programme conditions, and binding Data Act obligations.
- Do not treat data-space membership as proof that connected-product access, B2B sharing, B2G requests, or cloud-switching duties are already satisfied.

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 narrow Article 33 trigger for data-space participants that offer data or data services to other participants.
- [European Commission staff working document on data spaces](https://digital-strategy.ec.europa.eu/en/library/staff-working-document-data-spaces?ref=sorena.io) - Supports the explanation that common European data spaces are strategic sector and public-interest initiatives.

## What Data Act obligations matter most for common European data spaces?

The most direct Data Act obligation is Article 33 on interoperability of data, data-sharing mechanisms and services, and common European data spaces. It requires relevant data-space participants to describe dataset content, use restrictions, licences, collection methodology, data quality, uncertainty, data structures, formats, vocabularies, classification schemes, taxonomies, code lists, access methods, terms of use, quality of service, and, where applicable, tools such as smart contracts.

Those duties are not generic documentation advice. They are meant to make data discoverable, accessible, usable, and technically interoperable across data-sharing arrangements.

- Maintain machine-readable metadata where Article 33 calls for it.
- Publish or make consistently available the formats, vocabularies, taxonomies, code lists, and API terms needed for interoperability.
- If automated data-sharing agreements or smart contracts are used, document the means that enable tool interoperability.

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 list of Article 33 interoperability requirements for data, mechanisms, services, and data spaces.

## How do common European data spaces differ from ordinary data portals or file downloads under the Data Act?

The Data Act context is the starting point for this answer. The Commission describes common European data spaces as combining data infrastructures with governance frameworks for data pooling and sharing. The data.europa.eu panel report adds that data spaces are service-focused, user-centric, decentralised, automated, and based on common standards. That is a different operating model from simply publishing a static catalogue or downloadable files.

For Data Act implementation, this difference matters because Article 33 focuses on interoperability across data, services, mechanisms, technical access, and automation. A data-space operating file should therefore include more than a dataset list: it should include participant roles, governance rules, metadata, access controls, APIs or other technical means, licence and use restrictions, data quality information, and escalation paths.

- Treat the data space as a governed exchange environment, not just a publication page.
- Record who controls participant admission, access rights, data quality, standards, and dispute handling.
- Keep API, bulk download, real-time access, or other technical-access terms aligned with the actual service.

Sources for this answer:

- [European Commission staff working document on data spaces](https://digital-strategy.ec.europa.eu/en/library/staff-working-document-data-spaces?ref=sorena.io) - Supports the definition of common European data spaces as infrastructure plus governance for pooling and sharing.
- [Publications Office report on European data spaces](https://op.europa.eu/en/publication-detail/-/publication/70d01867-8ce1-11ee-8aa6-01aa75ed71a1/language-en?ref=sorena.io) - Supports the distinction between data spaces and conventional portals or simple downloads.

## How do the Data Act and Data Governance Act fit together in data-space governance?

The Data Act and the Data Governance Act address different parts of the EU data-sharing framework. The Data Act supplies horizontal rules on fair access and use of data and Article 33 interoperability requirements for data spaces. The Data Governance Act supports trust in voluntary data sharing through rules for protected public-sector data reuse, data intermediation services, data altruism, and the European Data Innovation Board.

A data-space governance file should therefore show which rule is doing the work. For example, a neutral data intermediary or data altruism organisation raises Data Governance Act questions, while a participant offering data services inside a common European data space raises Data Act Article 33 questions.

- Tag each exchange as Data Act, Data Governance Act, GDPR, open-data, sector-law, contract, or programme-governance driven.
- If a data intermediary is used, check neutrality, transparency, structural separation, notification, and recognised-provider claims under the Data Governance Act.
- If personal data is present, keep the GDPR legal basis and data-subject protections separate from the Data Act interoperability analysis.

Sources for this answer:

- [European Commission - Data Governance Act explained](https://digital-strategy.ec.europa.eu/en/policies/data-governance-act-explained?ref=sorena.io) - Supports the distinction between voluntary data-sharing trust tools, data intermediaries, data altruism, and public-sector reuse under the Data Governance Act.
- [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Supports the Data Act role in fair access, use, and interoperability rather than Data Governance Act intermediary status.

## Which sector data spaces should teams treat as examples, not universal Data Act templates?

The Data Act context is the starting point for this answer. The Commission's staff working document identifies data spaces in strategic fields such as health, agriculture, manufacturing, energy, mobility, finance, public administration, skills, the European Open Science Cloud, and the Green Deal priority, with later examples including media and cultural heritage. Individual data spaces then add sector-specific datasets, identifiers, services, governance, and access arrangements.

That means teams should not copy one data-space rulebook into another sector. A procurement data space, a legal data space, a health data space, and a mobility data space can all share Data Act interoperability logic while still having different legal bases, data categories, confidentiality needs, technical standards, and public-interest objectives.

- Use Article 33 as the horizontal interoperability baseline, then add the sector data-space rulebook.
- For procurement data, verify TED, API, open-data, confidentiality, and procurement-specific standards before reuse.
- For legal data, verify legal-identifier, case-law, EUR-Lex, and national legal-depository arrangements before reuse.

Sources for this answer:

- [European Commission staff working document on data spaces](https://digital-strategy.ec.europa.eu/en/library/staff-working-document-data-spaces?ref=sorena.io) - Supports the list of strategic fields and the warning that data spaces are sector and domain specific.
- [data.europa.eu - Public Procurement Data Space](https://data.europa.eu/en/PPDS?ref=sorena.io) - Supports the procurement example, including TED resources and automated procurement-data access.
- [data.europa.eu - European Legal Data Space](https://data.europa.eu/en/ELDS?ref=sorena.io) - Supports the legal-data example, including legal depositories and case-law collections.

## What safeguards should be built into a Data Act data-space participation file?

A useful participation file should show both access and protection. Under Article 33, recipients need enough metadata, format, vocabulary, taxonomy, licence, quality, and access information to find and use data. Under the Data Act more broadly, technical protection measures such as encryption and smart contracts may be used to prevent unauthorised access, but they must not become a disguised barrier to lawful access.

The file should also flag trade secrets, commercially confidential material, personal data, protected public-sector data, and sector restrictions. Those safeguards should explain what is protected, what remains available, and which legal or governance rule supports the limitation.

- Document the data category, metadata, licence, use restriction, quality statement, uncertainty, and access method.
- Record protection measures such as identity management, access control, encryption, secure processing, or confidentiality terms.
- Explain any refusal, delay, redaction, aggregation, anonymisation, or restricted-access environment with a source-linked reason.

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 need to describe metadata, restrictions, access means, and protection measures without hindering lawful rights.
- [European Commission - Data Governance Act explained](https://digital-strategy.ec.europa.eu/en/policies/data-governance-act-explained?ref=sorena.io) - Supports examples of reuse safeguards such as anonymisation, pseudonymisation, secure processing environments, and confidentiality agreements.

## What evidence should show that a data-space exchange is Data Act ready?

The Data Act context is the starting point for this answer. Keep evidence that connects the legal trigger to the operational exchange. The minimum useful set is a participant-role map, data catalogue, metadata profile, licence and use-restriction record, standards mapping, API or access specification, quality-of-service terms, security controls, smart-contract assessment where relevant, and a log of requests, refusals, restrictions, and changes.

For sector data spaces, add the sector-specific documents that make the exchange understandable: procurement ontologies or TED access material for procurement data, ELI/ECLI and legal-depository references for legal data, or the equivalent identifiers and standards in another sector.

- Keep the Article 33 checklist beside the data-space rulebook, not buried in general compliance notes.
- Version metadata, vocabularies, code lists, APIs, quality statements, and access terms when they change.
- Retain the source and owner for any decision that limits access because of confidentiality, personal data, trade secrets, security, or sector rules.

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 evidence fields tied to Article 33 interoperability requirements.
- [Publications Office report on European data spaces](https://op.europa.eu/en/publication-detail/-/publication/70d01867-8ce1-11ee-8aa6-01aa75ed71a1/language-en?ref=sorena.io) - Supports evidence needs around decentralisation, automation, common standards, governance, legal, and compliance building blocks.

## What is the main implementation risk when mapping the Data Act to common European data spaces?

The main risk is overgeneralising. A team may say that a data space is interoperable or EU-backed without proving the specific Article 33 items for the exchange it operates. The opposite risk is also common: treating a sector data-space participation decision as only a policy project and missing binding Data Act access, interoperability, contract, cloud-switching, or public-sector request duties.

The practical control is to maintain one exchange-by-exchange matrix. Each row should identify the participant role, data or data service, applicable Data Act chapter, Data Governance Act or sector overlay, interoperability evidence, protection measure, owner, and review trigger.

- Avoid unsupported claims that participation is mandatory, complete, compliant, or sufficient by itself.
- Do not reuse one sector data-space rulebook for another sector without checking the source and governance model.
- Re-check the matrix when standards, APIs, participant roles, datasets, access restrictions, or sector rules change.

Sources for this answer:

- [European Commission second staff working document on data spaces](https://digital-strategy.ec.europa.eu/en/library/second-staff-working-document-data-spaces?ref=sorena.io) - Supports the need to track evolving data-space support actions, sector initiatives, standards, and interoperability work.
- [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Supports the binding Article 33 analysis that should sit behind each data-space exchange row.

## What evidence should teams keep for a Data Act and common European data spaces decision?

For a Data Act and common European data spaces decision, keep the source clause, Commission guidance, actor role, dataset or service, request or contract trigger, and the owner who approved the interpretation.

Also keep the cited external URL, decision date, reviewer, unresolved assumptions, and implementation artifact together so the answer stays auditable and can be revisited when the exchange, standards, or sector rulebook changes.

- Link the decision to a cited Data Act source URL and the relevant Article 33 requirement.
- Store the owner, affected workflow, evidence artifact, and review trigger.
- Keep unresolved assumptions and the review date together with the implementation record.

## Who should own Data Act implementation work for common European data spaces?

For Data Act and common European data spaces work, the workflow should name the legal, product, procurement, cloud, support, or security owner who can change the affected process.

Use one accountable owner per action, then record consulted teams and evidence dependencies separately so the Article 33 interpretation, sector rulebook, and operational change remain linked.

- Assign one accountable owner per action.
- Record the affected workflow and the implementation artifact.
- Keep consulted teams and dependencies in a separate note, not as the owner.

## When should the Data Act and common European data spaces FAQ answer be reviewed again?

Review the Data Act and common European data spaces answer when the product, service model, dataset, customer role, public-sector request path, contract wording, or sector rulebook changes.

Set a review date and an event trigger so the answer is not treated as a one-time legal note. That keeps the Article 33 analysis aligned with the live exchange and its governance framework.

- Review on any material change to the data space exchange or governance model.
- Review when standards, APIs, or access terms change.
- Review when the owner or the legal basis for the exchange changes.

## Which EU Data Act obligations follow a connected-product dataset when it enters a common European data space?

Under the Data Act, the access, use, and trade-secret rules that attach to connected-product and related-service data do not disappear when that data is contributed to a data space; the Article 33 interoperability duties apply on top, but the underlying user access right and any safeguards still travel with the dataset. The data space is a sharing venue, not a way to shed those obligations.

Teams should map which obligation governs each layer, so the interoperability descriptions for the data space sit alongside, rather than override, the user and recipient rights that already apply to the data.

- Carry the Data Act access, use, and trade-secret obligations with the dataset into the data space.
- Layer the Article 33 interoperability descriptions on top without displacing user and recipient rights.

## 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 Article 33 data-space interoperability duties, smart-contract references, and broader fair-access context.
- [European Commission - Data Governance Act explained](https://digital-strategy.ec.europa.eu/en/policies/data-governance-act-explained?ref=sorena.io) - Explains Data Governance Act trust mechanisms for voluntary sharing, protected public-sector data reuse, intermediaries, and data altruism.
- [European Commission staff working document on data spaces](https://digital-strategy.ec.europa.eu/en/library/staff-working-document-data-spaces?ref=sorena.io) - Defines common European data spaces as infrastructure plus governance in strategic sectors and public-interest domains.
- [European Commission second staff working document on data spaces](https://digital-strategy.ec.europa.eu/en/library/second-staff-working-document-data-spaces?ref=sorena.io) - Provides current data-space context, including sector initiatives, support actions, Simpl, EDICs, standards, and interoperability work.
- [Publications Office report on European data spaces](https://op.europa.eu/en/publication-detail/-/publication/70d01867-8ce1-11ee-8aa6-01aa75ed71a1/language-en?ref=sorena.io) - Explains data-space design concepts such as decentralisation, automation, common standards, governance, and protected access.
- [data.europa.eu - Public Procurement Data Space](https://data.europa.eu/en/PPDS?ref=sorena.io) - Sector example for public procurement data, TED resources, APIs, open data services, and procurement standards.
- [data.europa.eu - European Legal Data Space](https://data.europa.eu/en/ELDS?ref=sorena.io) - Sector example for legal data, legal depositories, case-law collections, EUR-Lex material, and legal identifiers.
- [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission overview for Data Act chapters, connected-product access, B2G requests, cloud switching, interoperability, and implementation support.

## 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 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 evidence section*

## Review Data Act data-space obligations

Map each planned data-space exchange to Article 33 interoperability fields, sector governance rules, safeguards, and evidence owners before launch or contract renewal.

- [Open Research Copilot](/solutions/research-copilot.md): Get cited answers on Data Act interoperability, Data Governance Act overlap, and data-space governance.
- [Discuss Data Act data spaces](/contact.md): Review data-space participation, Article 33 evidence, and sector-specific sharing arrangements.


---

[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/data-act-and-common-european-data-spaces