--- title: "Data Act and Common European Data Spaces" canonical_url: "https://www.sorena.io/artifacts/eu/data-act/data-act-and-common-european-data-spaces" source_url: "https://www.sorena.io/artifacts/eu/data-act/data-act-and-common-european-data-spaces" author: "Sorena AI" description: "How Data Act Article 33 connects data-space participation with metadata, vocabularies, APIs, access terms, data quality, governance, and standards monitoring." published_at: "2026-05-06" updated_at: "2026-05-25" keywords: - "EU Data Act" - "Regulation (EU) 2023/2854" - "common European data spaces" - "Article 33" - "interoperability" - "data sharing governance" --- **[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 and Common European Data Spaces How Data Act Article 33 connects data-space participation with metadata, vocabularies, APIs, access terms, data quality, governance, and standards monitoring. *Artifact Guide* *EU* *Data Act* ## EU Data Act and Common European Data Spaces Use this page to connect Data Act Article 33 with practical data-space readiness: metadata, semantics, technical access, data-sharing terms, and governance evidence. It separates binding Data Act interoperability requirements from Commission data-space policy material, examples, and ongoing standards work. The Data Act does not make every dataset a common European data-space asset. The key question is whether participants in a data space offer data or data services to other participants. Where they do, Article 33 turns interoperability into concrete duties around describing datasets, structures, formats, vocabularies, access mechanisms, terms of use, service quality, and, where relevant, tools such as smart contracts for data-sharing agreements. ## When does Data Act Article 33 matter for a common European data space? Article 33 applies to participants in data spaces that offer data or data services to other participants. It defines common European data spaces as purpose-specific, sector-specific, or cross-sectoral interoperable frameworks for common standards and practices to share or jointly process data. That framing matters because a policy statement about joining a data space is not enough. The operational review should start with the actual data or service being offered, the recipient or participant type, and the data-space rules that govern access and processing. - Confirm whether the organisation is a data-space participant offering data or a data service to another participant. - Name the sectoral, purpose-specific, or cross-sectoral data-space context instead of treating all data-sharing projects as the same. - Record whether the source being applied is binding Data Act text, Commission policy context, a data-space operating rule, a harmonised standard, or a draft standardisation deliverable. 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 Article 33 scope rule for data-space participants offering 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) - Explains common European data spaces as data infrastructures plus governance frameworks for pooling and sharing data. ## Data Act What Article 33 requires teams to make understandable and usable The Article 33 essentials are practical interoperability requirements. They cover whether a recipient can find, access, interpret, and use the data without guessing hidden context from internal systems. For each data-space offer, maintain a catalogue profile that describes the dataset content, use restrictions, licence position, collection methodology, quality limits, uncertainty, data structures, formats, vocabularies, classification schemes, taxonomies, and code lists where available. - Describe dataset content, restrictions, licences, collection method, data quality, and uncertainty in a form that can support machine-readable discovery where applicable. - Publish or reference the structures, formats, vocabularies, classification schemes, taxonomies, and code lists needed to interpret the data consistently. - Keep known semantic gaps visible, especially where a sector data space, public portal, or partner system uses a different vocabulary or classification scheme. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Lists the Article 33 metadata, licence, quality, format, vocabulary, taxonomy, and code-list requirements. - [Publications Office - Data spaces panel report](https://op.europa.eu/en/publication-detail/-/publication/70d01867-8ce1-11ee-8aa6-01aa75ed71a1/language-en?ref=sorena.io) - Shows why metadata quality and licence clarity are operational requirements for data-space participation. ## How access conditions, APIs, and service quality fit the Data Act Article 33 treats access mechanisms as part of interoperability. If data is exposed through an API, bulk channel, real-time feed, catalogue, or controlled-access service, the technical means and terms of use need enough detail for automatic access and transmission where technically feasible. Access design should therefore be reviewed with product, security, legal, and data governance together. Authentication, participant eligibility, service limits, quality of service, licence restrictions, personal-data boundaries, confidentiality limits, and trade-secret handling all affect whether the offer can be used lawfully and reliably. - Document APIs and other access channels with terms of use, authentication assumptions, service quality, rate or volume constraints, and availability expectations. - Tie access conditions to the participant role and data-space governance rule that justifies them. - Do not describe an export button or unpublished endpoint as data-space readiness unless the access method, terms, and quality limits are maintained. 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 requirement to describe technical access means, terms of use, and quality of service. - [Publications Office - Data spaces panel report](https://op.europa.eu/en/publication-detail/-/publication/70d01867-8ce1-11ee-8aa6-01aa75ed71a1/language-en?ref=sorena.io) - Supports treating API-like access, identity management, access control, and automation as practical data-space operating concerns. ## Data Act How sectoral data-space policy should be used without overstating it Commission staff working documents and data-space examples help identify sector context, support actions, and implementation patterns, but they should not be cited as if they create a standalone product obligation. The binding hook for this page remains Article 33 when the organisation offers data or data services as a data-space participant. Use policy materials to understand whether a sector has a recognised data-space initiative, support infrastructure, middleware work, or standards activity. Then translate only the applicable, supported requirements into product, contract, and governance work. - Use Commission data-space documents to identify the relevant sector, support programme, DSSC or Simpl context, and standards or interoperability workstream. - Keep sector policy, pilot activity, and examples separate from binding duties and adopted standards. - Escalate any data-space operator rule, participation agreement, or sector code that adds access, onboarding, identity, security, or quality requirements beyond the horizontal Data Act text. 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) - Provides policy context on sector- and domain-specific data spaces, support actions, and ongoing standards and interoperability work. - [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 distinction between data-space policy objectives and the operational concept of infrastructures and governance frameworks. ## Data Act What to monitor in standards, common specifications, and data-space building blocks Article 33 links conformity to harmonised standards and, in some situations, common specifications adopted by implementing acts. Participants meeting standards or common specifications are presumed to conform only to the extent those instruments cover the Article 33 essentials. Standardisation is active but should be handled as a monitored dependency. The Commission standardisation request covers trusted data transactions, catalogue implementation, semantic assets, data governance quality, and a maturity model for common European data spaces. Until a relevant standard or common specification is adopted and applicable to the specific requirement, do not treat it as a finished product mandate. - Maintain a standards watch log with the instrument name, Article 33 requirement covered, source status, affected dataset or service, owner, and product impact. - Track trusted data transaction interfaces, data catalogue implementation, semantic assets, internal data governance quality, and common European data-space maturity work separately. - When a harmonised standard or common specification is used, record exactly which metadata, access, semantic, quality, or smart-contract requirement it covers. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Explains the Article 33 conformity role of harmonised standards and common specifications. - [Commission Implementing Decision C(2025) 4135 - standardisation request annexes](https://ec.europa.eu/transparency/documents-register/api/files/C(2025)4135_1/de00000001072897?rendition=false&ref=sorena.io) - Lists Data Act standardisation deliverables for trusted data transactions, catalogues, semantic assets, data governance quality, and data-space maturity. - [CEN-CENELEC - Data Act standardization request accepted](https://www.cencenelec.eu/news-events/news/2025/brief-news/2025-07-11-data-act-standardization-request/?ref=sorena.io) - Confirms the accepted Data Act standardisation request and its link to Article 33 implementation. *Recommended next step* *Placement: after implementation section* ## Review a Data Act data-space readiness pack Use the Article 33 categories on this page to review one dataset or data service at a time: metadata, semantics, access terms, quality, governance, and standards dependencies. - [Open Research Copilot](/solutions/research-copilot.md): Check Data Act source claims and keep cited outputs together. - [Talk through implementation](/contact.md): Review data-space scope, access terms, governance evidence, and standards dependencies. ## Data Act What governance evidence should a data-space readiness pack contain? A useful Data Act readiness pack should show how the data-space offer is governed, not just that a dataset exists. It should connect each public claim and product control to a source, an owner, and a maintained artefact. The pack should be readable by product, legal, security, data governance, and engineering. It should show what is ready now, what depends on a sector data-space rule or standard, and what cannot be offered until access, quality, licence, or semantic issues are resolved. - Dataset or service profile: content, owner, purpose, source system, collection method, update logic, and participant-facing description. - Interoperability profile: formats, structures, vocabulary mappings, classifications, taxonomies, code lists, identifiers, and semantic gaps. - Access profile: API or channel documentation, terms of use, authentication, quality of service, service limits, and support model. - Governance profile: licence position, use restrictions, personal-data and confidentiality boundaries, trade-secret handling, approval owner, and review trigger. - Standards profile: harmonised standards, common specifications, draft deliverables, data-space rules, and evidence of which Article 33 requirement each one supports. Sources for this answer: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Provides the Article 33 checklist categories that the readiness pack should evidence. - [European Commission - Rolling Plan for ICT standardisation, Data Economy](https://interoperable-europe.ec.europa.eu/collection/rolling-plan-ict-standardisation/data-economy-rp-2025?ref=sorena.io) - Supports monitoring data economy topics such as availability, interoperability, quality, governance, infrastructure, lifecycle, and data-space interoperability. ## Overclaims to avoid when explaining Data Act readiness for data spaces Avoid saying a product is ready for common European data spaces just because data can be exported, a catalogue page exists, or the organisation participates in a sector initiative. Article 33 readiness depends on usable descriptions, consistent semantics, explained access mechanisms, stated terms, quality information, and governance evidence. Also avoid turning policy direction into a hard rule. Commission data-space documents, examples, and standards work are important context, but public claims should say whether a requirement is binding law, a participation rule, an adopted standard, a common specification, or a monitored future dependency. - Do not claim Data Act compliance from membership in a data-space project alone. - Do not cite future standards as implemented requirements unless the adopted instrument and covered Article 33 requirement are identified. - Do not omit licence, use restriction, quality, uncertainty, or access-service limitations from catalogue entries. - Do not treat open-data publication, controlled data-space sharing, and Data Act data access requests as one undifferentiated process. 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 map readiness claims to specific Article 33 requirements instead of generic participation claims. - [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 treating sector data-space progress and support actions as policy context rather than a substitute for legal analysis. ## Primary sources - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Primary legal source for Article 33 interoperability requirements, data-space participant scope, harmonised standards, common specifications, and EDIB-linked guidance. - [European Commission - Staff working document on data spaces](https://digital-strategy.ec.europa.eu/en/library/staff-working-document-data-spaces?ref=sorena.io) - Commission policy source for the concept of common European data spaces as infrastructure plus governance frameworks. - [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) - Commission policy source for sector and domain data-space status, support actions, and ongoing standards and interoperability work. - [Publications Office - Data spaces panel report](https://op.europa.eu/en/publication-detail/-/publication/70d01867-8ce1-11ee-8aa6-01aa75ed71a1/language-en?ref=sorena.io) - Supports practical governance points on metadata quality, licence clarity, standards convergence, access control, provenance, lineage, and API-like access. - [Commission Implementing Decision C(2025) 4135 - standardisation request annexes](https://ec.europa.eu/transparency/documents-register/api/files/C(2025)4135_1/de00000001072897?rendition=false&ref=sorena.io) - Official Commission standardisation request source for Data Act Article 33-related deliverables under the European Trusted Data Framework. - [CEN-CENELEC - Data Act standardization request accepted](https://www.cencenelec.eu/news-events/news/2025/brief-news/2025-07-11-data-act-standardization-request/?ref=sorena.io) - Confirms CEN, CENELEC, and ETSI acceptance of the Data Act standardisation request and the Article 33 implementation link. - [European Commission - Rolling Plan for ICT standardisation, Data Economy](https://interoperable-europe.ec.europa.eu/collection/rolling-plan-ict-standardisation/data-economy-rp-2025?ref=sorena.io) - Commission standardisation context for data economy topics including interoperability, quality, governance, lifecycle, and data-space interoperability. ## Related Topic Guides - [Data Act and Data Governance Act Overlap FAQ](/artifacts/eu/data-act/faq/data-governance-act-overlap.md): FAQ explaining where the EU Data Act and Data Governance Act overlap, how they differ, and how to route product, cloud, public-sector reuse, intermediary, and data altruism workflows. - [Data Act and GDPR Personal Data Overlap FAQ](/artifacts/eu/data-act/faq/gdpr-personal-data-overlap.md): FAQ on how the EU Data Act works when connected-product or related-service data includes personal data, mixed datasets, GDPR roles, lawful basis, trade secrets, and third-party sharing. - [Data Act Audit Evidence And Request Logs FAQ](/artifacts/eu/data-act/faq/audit-evidence-and-request-logs.md): FAQ for Data Act request logs covering user and third-party access, B2G exceptional need requests, cloud switching records, contract terms, trade secrets, and GDPR boundaries. - [Data Act B2B Data-Sharing Contract Clauses](/artifacts/eu/data-act/b2b-data-sharing-contract-clauses.md): Clause guide for EU Data Act B2B data sharing: FRAND terms, compensation, trade secret safeguards, recipient limits, termination, logs, and GDPR boundaries. - [Data Act B2B Data-Sharing Contract Template](/artifacts/eu/data-act/b2b-data-sharing-contract-template.md): A usable EU Data Act B2B data-sharing template outline covering access requests, data schedules, permitted use, trade secrets, security, compensation, GDPR boundaries, audit records, and termination. - [Data Act B2G Exceptional-Need Requests](/artifacts/eu/data-act/b2g-exceptional-need-requests.md): A grounded guide to EU Data Act Chapter V requests from public bodies: exceptional need, public emergencies, request contents, limits, safeguards, costs, and records. - [Data Act Cloud Switching Compliance Checklist](/artifacts/eu/data-act/cloud-switching-compliance-checklist.md): A grounded EU Data Act checklist for cloud and data processing service providers covering switching clauses, notices, export formats, charges, interoperability, and evidence. - [Data Act Cloud Switching Contract Terms FAQ](/artifacts/eu/data-act/faq/cloud-switching-contract-terms.md): FAQ on EU Data Act cloud switching contract terms: Article 25 clauses, assistance, notice, transition, charges, export, termination, interoperability, and records. - [Data Act Cloud Switching Fees And Deadlines FAQ](/artifacts/eu/data-act/faq/cloud-switching-fees-and-deadlines.md): FAQ on EU Data Act cloud switching charges, 2027 fee removal, notice periods, transition windows, data retrieval, contract terms, and evidence records. - [Data Act Complaints and Dispute Settlement FAQ](/artifacts/eu/data-act/faq/complaints-and-dispute-settlement.md): FAQ on EU Data Act complaints, competent authorities, dispute settlement bodies, B2B data-sharing disputes, B2G requests, cloud switching disputes, and evidence records. - [Data Act Exportable Data and Metadata FAQ](/artifacts/eu/data-act/faq/exportable-data-and-metadata.md): FAQ explaining which product, related service, metadata, and cloud switching data must be exportable under the EU Data Act, and which data can be excluded. - [Data Act FAQ for Aftermarket Repair and Mobility Services](/artifacts/eu/data-act/faq/aftermarket-repair-and-mobility-services.md): FAQ on EU Data Act vehicle-data access for repairers, independent service providers, fleets, insurers, and mobility services. - [Data Act Functional Equivalence FAQ](/artifacts/eu/data-act/faq/functional-equivalence.md): FAQ on Data Act functional equivalence for cloud switching: IaaS scope, customer outcomes, export support, interoperability duties, limits, and evidence. - [Data Act Indirect Access Request Flows FAQ](/artifacts/eu/data-act/faq/indirect-access-request-flows.md): FAQ for Data Act teams handling user and third-party data requests when direct connected-product access is unavailable, incomplete, or limited. - [Data Act International Government Access FAQ](/artifacts/eu/data-act/faq/international-government-access.md): FAQ on EU Data Act safeguards for non-EU government access to non-personal data held in the Union by data processing service providers. - [Data Act Interoperability Standards FAQ](/artifacts/eu/data-act/faq/interoperability-standards.md): FAQ on EU Data Act interoperability standards for data spaces, cloud switching, smart contracts, harmonised standards, common specifications, and M/614. - [Data Act Model Contractual Terms FAQ](/artifacts/eu/data-act/faq/model-contractual-terms.md): FAQ on the EU Data Act non-binding model contractual terms for data access and use, cloud switching clauses, B2B use, unfair terms, and evidence. - [Data Act Public Emergency Requests FAQ](/artifacts/eu/data-act/faq/public-emergency-requests.md): FAQ on EU Data Act public emergency requests: exceptional need, request content, timing, data holder response, compensation, confidentiality, and records. - [Data Act Smart Contracts for Data Sharing](/artifacts/eu/data-act/smart-contracts-for-data-sharing.md): Data Act Article 36 smart contract guide for data-sharing agreements: scope, robustness, access control, termination, interruption, archiving, standards status, and conformity evidence. - [Data Act SME Exceptions and Startups FAQ](/artifacts/eu/data-act/faq/sme-exceptions-and-startups.md): FAQ on where the EU Data Act gives micro, small, medium-sized, startup, and SME actors narrower treatment for access duties, compensation, and B2B terms. - [Data Act Trade Secret Technical Protection Measures FAQ](/artifacts/eu/data-act/faq/trade-secret-technical-protection-measures.md): FAQ on how EU Data Act data holders can protect trade secrets with confidentiality safeguards, technical measures, limited withholding, suspension, refusal, and evidence. - [Data Act Trade Secrets and Protection Measures](/artifacts/eu/data-act/trade-secrets-and-protection.md): Data Act guide for protecting trade secrets during access and sharing: classification, safeguards, refusal thresholds, notices, evidence records, and reviews. - [Data Act Unfair Contractual Terms | Article 13 B2B Contract Review](/artifacts/eu/data-act/unfair-contractual-terms.md): Review B2B data-sharing clauses under EU Data Act Article 13: unilateral terms, always unfair examples, presumed unfair terms, model clauses, evidence, and remediation. - [Data Act Vehicle Data Guidance](/artifacts/eu/data-act/vehicle-data-guidance.md): Commission-grounded guide to Data Act vehicle data access: connected vehicles, vehicle-related services, raw and pre-processed data, aftermarket use cases, access routes, safeguards, and GDPR boundaries. - [Data Act vs GDPR: connected-product data access](/artifacts/eu/data-act/data-act-vs-gdpr.md): Compare EU Data Act connected-product access duties with GDPR personal-data rules: scope, roles, lawful basis, data subject rights, third-party sharing, trade secrets, and conflicts. - [EU Data Act and Common European Data Spaces FAQ](/artifacts/eu/data-act/faq/data-act-and-common-european-data-spaces.md): FAQ on how EU Data Act interoperability duties, Data Governance Act rules, and sector data-space governance fit together without treating participation as a general obligation. - [EU Data Act Applicability Test](/artifacts/eu/data-act/applicability-test.md): Check whether a product, related service, data holder, cloud service, data-space role, smart contract, or B2G request is in scope of the EU Data Act. - [EU Data Act Application Dates And Transition FAQ](/artifacts/eu/data-act/faq/application-dates-and-transition.md): FAQ on when the EU Data Act applies, which obligations are delayed, and what product, contract, cloud, and evidence records teams should maintain. - [EU Data Act Article 3 Pre-Contract Information](/artifacts/eu/data-act/pre-contractual-information-obligations.md): What Article 3 of the EU Data Act requires before connected-product purchase, rent, lease, or related-service contracting: data categories, access, data holder identity, third-party sharing, complaints, and evidence. - [EU Data Act Article 36 Smart Contract Controls FAQ](/artifacts/eu/data-act/faq/article-36-smart-contract-controls.md): FAQ explaining when EU Data Act Article 36 applies to smart contracts for data-sharing agreements and what controls, conformity evidence, and limits it requires. - [EU Data Act B2B Data Sharing Compensation FAQ](/artifacts/eu/data-act/faq/compensation-for-b2b-data-sharing.md): FAQ on when Data Act data holders may charge B2B data recipients, what reasonable compensation can include, SME limits, unfair terms, disputes, and trade secret safeguards. - [EU Data Act B2G Compensation and Costs FAQ](/artifacts/eu/data-act/faq/b2g-compensation-and-costs.md): FAQ on when Data Act B2G exceptional-need requests are free, when fair compensation may be claimed, which costs can be included, and what records to keep. - [EU Data Act B2G Exceptional Need FAQ](/artifacts/eu/data-act/faq/b2g-exceptional-need.md): When public-sector bodies can request business-held data under the EU Data Act, what a valid request must contain, and how data holders handle limits, trade secrets, compensation, and evidence. - [EU Data Act Checklist for Product, Cloud, and Contract Teams](/artifacts/eu/data-act/checklist.md): A grounded EU Data Act checklist for connected-product data access, third-party sharing, B2G requests, cloud switching, unfair terms, smart contracts, personal data boundaries, evidence, and owners. - [EU Data Act Cloud Switching and Exit Plans](/artifacts/eu/data-act/cloud-switching-and-exit-plans.md): A grounded EU Data Act guide for data processing service exit plans: switching contracts, exportable data, assistance, charges, interoperability, retrieval, erasure, and records. - [EU Data Act Cloud Switching Procurement FAQ](/artifacts/eu/data-act/faq/cloud-switching-procurement-checklist.md): Procurement checklist FAQ for EU Data Act cloud switching: contract terms, exit support, exportable data, switching charges, interoperability, termination, and supplier evidence. - [EU Data Act Compliance Program](/artifacts/eu/data-act/compliance.md): Build a Data Act compliance program for connected-product data access, contracts, B2G requests, cloud switching, smart contracts, GDPR boundaries, records, and ownership. - [EU Data Act Connected Product Scope and Data Types](/artifacts/eu/data-act/scope-connected-products-and-data-types.md): Classify EU Data Act connected products, related services, product data, related-service data, readily available data, metadata, and excluded derived outputs. - [EU Data Act Connected Product Scope FAQ](/artifacts/eu/data-act/faq/scope-connected-products.md): FAQ explaining when connected products, related services, generated data, EU market placement, and SME exceptions fall within EU Data Act scope. - [EU Data Act Data Processing Service Switching](/artifacts/eu/data-act/data-processing-services-switching.md): A grounded EU Data Act guide for provider and customer switching duties: exit assistance, exportable data, contract clauses, charges, interoperability, retrieval, and erasure. - [EU Data Act data spaces interoperability FAQ](/artifacts/eu/data-act/faq/data-spaces-interoperability.md): FAQ explaining Article 33 Data Act interoperability requirements for data-space participants, common European data spaces, standards, APIs, metadata, and architecture evidence. - [EU Data Act deadlines and compliance calendar](/artifacts/eu/data-act/deadlines-and-compliance-calendar.md): A source-linked calendar for EU Data Act application dates, product design timing, contract remediation, cloud switching charges, response periods, standards work, and evidence records. - [EU Data Act Direct Access by Design FAQ](/artifacts/eu/data-act/faq/direct-access-by-design.md): FAQ for product and legal teams designing user access to connected-product and related-service data under the EU Data Act. - [EU Data Act Enforcement And Competent Authorities FAQ](/artifacts/eu/data-act/faq/enforcement-and-competent-authorities.md): FAQ on who enforces the EU Data Act, how complaints work, how Member States set penalties, when dispute settlement can be used, and when GDPR authorities remain responsible. - [EU Data Act FAQ: scope, access rights, B2G, cloud switching, GDPR, and dates](/artifacts/eu/data-act/faq.md): Grounded EU Data Act FAQ index covering connected-product data access, third-party sharing, B2G exceptional need, cloud switching, smart contracts, GDPR boundaries, unfair terms, trade secrets, and application dates. - [EU Data Act Non-Emergency Public-Sector Requests FAQ](/artifacts/eu/data-act/faq/non-emergency-public-sector-requests.md): FAQ on EU Data Act requests where a public body claims exceptional need outside a public emergency, including scope, request contents, limits, compensation, confidentiality, and evidence. - [EU Data Act Non-Personal Data and Mixed Datasets FAQ](/artifacts/eu/data-act/faq/non-personal-data-and-mixed-datasets.md): FAQ on how the EU Data Act treats non-personal data, mixed datasets, GDPR precedence, user and third-party access, trade-secret limits, and evidence records. - [EU Data Act Penalties and Enforcement](/artifacts/eu/data-act/penalties-and-fines.md): Grounded guide to Data Act penalties under Article 40, Member State enforcement, penalty factors, complaints, judicial remedies, and the GDPR enforcement boundary. - [EU Data Act Pre-Contractual Information FAQ](/artifacts/eu/data-act/faq/pre-contractual-information.md): FAQ on EU Data Act Article 3 pre-contract information for connected products and related services, including data categories, access methods, data holder identity, third-party sharing, and GDPR boundaries. - [EU Data Act Product Data vs Related Service Data FAQ](/artifacts/eu/data-act/faq/product-data-and-service-data.md): FAQ explaining how the EU Data Act separates connected product data, related service data, readily available raw and pre-processed data, metadata, and inferred or derived outputs. - [EU Data Act Readily Available Data FAQ](/artifacts/eu/data-act/faq/readily-available-data.md): FAQ on what counts as readily available data under the EU Data Act, including product data, related service data, metadata, inferred data, and access mechanics. - [EU Data Act 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. --- [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/data-act-and-common-european-data-spaces