--- title: "EU Data Act Data Processing Service Switching" canonical_url: "https://www.sorena.io/artifacts/eu/data-act/data-processing-services-switching" source_url: "https://www.sorena.io/artifacts/eu/data-act/data-processing-services-switching" author: "Sorena AI" description: "A grounded EU Data Act guide for provider and customer switching duties: exit assistance, exportable data, contract clauses, charges, interoperability, retrieval, and erasure." published_at: "2026-05-06" updated_at: "2026-05-06" keywords: - "EU Data Act" - "data processing services" - "switching" - "exportable data" - "cloud exit" - "interoperability" - "Regulation (EU) 2023/2854" --- **[SORENA](https://www.sorena.io/)** - AI-Powered GRC Platform [Home](https://www.sorena.io/) | [Solutions](https://www.sorena.io/solutions) | [Artifacts](https://www.sorena.io/artifacts) | [About Us](https://www.sorena.io/about-us) | [Contact](https://www.sorena.io/contact) | [Portal](https://app.sorena.io) --- # EU Data Act Data Processing Service Switching A grounded EU Data Act guide for provider and customer switching duties: exit assistance, exportable data, contract clauses, charges, interoperability, retrieval, and erasure. *Artifact Guide* *EU* *Data Act* ## EU Data Act Data Processing Service Switching Translate Chapter VI switching rules into provider and customer actions for cloud, edge, and other data processing services: contract terms, exit support, exportable data, fees, and interoperability. Focused on the binding Data Act text and Commission materials for switching, in-parallel use, data export, and non-binding cloud contract clauses. This page is for providers and customers working through a Data Act switch, exit, or in-parallel-use scenario for data processing services. It explains what the provider must support, what the customer needs to specify, what the contract should contain, and where the technical and charge limits sit. ## Data Act Confirm the service, customer route, and provider roles The Data Act switching chapter is about customers of data processing services, including cloud and edge services. Start by identifying the source provider, the customer, the destination provider or on-premises ICT infrastructure, the service type, and whether the customer wants a switch, export to on-premises infrastructure, erasure at termination, or in-parallel use of several providers. Article 23 requires providers to remove obstacles that inhibit termination after the allowed notice period and successful switching, conclusion of a replacement contract, porting of exportable data and digital assets, functional equivalence where applicable, and technically feasible unbundling. Article 24 limits the source provider's technical responsibilities to the services, contracts, or commercial practices it provides. - Name the source provider, customer, destination provider or on-premises target, affected service type, contract, and requested switching action. - Separate switching from in-parallel use because Article 34 applies selected switching duties to parallel use and has its own egress-cost rule. - Check whether Article 31 narrows or excludes obligations for a custom-built individual-customer service or a limited non-production test service. - Do not present the source provider as responsible for capabilities outside its own service, contract, or commercial practice. 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 23, 24, 31, and 34 support the service classification, obstacle-removal duties, scope limits, exclusions, and in-parallel-use treatment. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission overview explaining that Chapter VI applies to providers of data processing services and addresses cloud and edge switching barriers. ## Data Act Put switching and exit rights in a written contract Article 25 requires the customer's switching rights and the provider's obligations to be clearly set out in a written contract that the customer can store and reproduce before signing. The contract should not only say that switching is possible; it should describe the route, assistance, continuity, security, data retrieval, erasure, and any permitted switching charges. The customer must be able to choose, after the maximum notice period, whether to switch to another provider, switch to on-premises ICT infrastructure, or erase exportable data and digital assets. The provider must support an exit strategy relevant to the contracted services, including by providing relevant information. - Include a maximum notice period for starting the switching process that does not exceed two months. - Include a mandatory maximum transitional period of 30 calendar days after notice, unless the provider notifies technical unfeasibility within 14 working days and states an alternative period not exceeding seven months. - Maintain service continuity and a high level of security during transfer and during the retrieval period. - Allow the customer to extend the transitional period once for a period the customer considers more appropriate. - Include at least 30 calendar days for data retrieval after the transitional period ends, followed by erasure of qualifying exportable data and digital assets when the switch has completed successfully. 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 25 supports the written contract requirement, notice cap, transitional period, technical-unfeasibility notice, retrieval period, erasure clause, exit support, continuity, and security duties. - [European Commission - Model contractual terms and cloud standard clauses](https://digital-strategy.ec.europa.eu/en/library/draft-recommendation-non-binding-model-contractual-terms-data-access-and-use-and-non-binding?ref=sorena.io) - Commission source for voluntary cloud standard contractual clauses covering switching and exit, termination, security, and business continuity. ## Data Act Define exportable data, digital assets, formats, and exclusions A useful switching file lists the categories of data and digital assets that can be ported during the switching process, including at least all exportable data. It should also list provider-internal categories exempted because export would risk disclosure of trade secrets, provided those exemptions do not impede or delay the switching process. Article 26 requires providers to give customers information on switching and porting procedures, available methods and formats, and known restrictions or technical limitations. Providers must also point customers to an up-to-date online register with data structures, data formats, relevant standards, and open interoperability specifications for exportable data. - For each export category, record whether it is customer input data, output data, metadata, a digital asset, configuration material, or another service-specific artifact. - Record the export method, file or API format, schema or data structure, validation step, known limitation, and destination dependency. - Identify provider-internal exclusions separately and state the trade-secret or security reason without using those exclusions to slow the switch. - Keep a dated copy or evidence snapshot of the provider's online register used for the customer switch. 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 25 and 26 support the exportable-data inventory, digital-asset categories, provider-internal exclusions, format information, technical limits, and online-register requirement. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explanation that switching data includes customer-generated input and output data, metadata, and excludes provider IP or trade-secret-protected material. ## Data Act Control switching charges and egress-cost treatment Article 29 phases out switching charges for data processing services. From 11 January 2024 to 12 January 2027, providers may impose reduced switching charges, but only up to costs directly linked to the switching process. From 12 January 2027, providers may not impose switching charges on the customer for the switching process. Before contracting, providers must give clear information on standard service fees, early termination penalties, and any reduced switching charges that may be imposed during the phase-out period. Where relevant, they must also inform customers about services with highly complex or costly switching, or where switching is impossible without significant interference in data, digital assets, or service architecture. - Keep standard service fees, early termination penalties, switching charges, and in-parallel egress charges in separate fields. - For any reduced switching charge before 12 January 2027, document the directly linked cost basis and customer-facing disclosure. - For in-parallel use, Article 34 allows data egress charges only to pass on incurred egress costs and only without exceeding those costs. - Publish or otherwise make easily accessible the required charge and complex-switching information where Article 29 applies. 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 29 and 34 support the switching-charge phase-out, direct-cost cap, pre-contract fee disclosures, complex-switching disclosure, and in-parallel egress-cost limit. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission overview confirms the transition period for switching charges and the later removal of switching charges, including data egress for switching. ## Data Act Match technical support to the service type for implementation evidence and owner review Article 30 treats infrastructure-like services differently from other data processing services. For scalable and elastic computing resources limited to infrastructure elements, the source provider must take all reasonable measures in its power to help the customer achieve functional equivalence in the destination service for the same service type. For other data processing services, providers must make open interfaces available free of charge to customers and destination providers to facilitate switching. Where no common specification or harmonised standard has been published for a same-service-type switch, the provider must, at the customer's request, export all exportable data in a structured, commonly used, machine-readable format. - Classify whether the service is limited to infrastructure resources under Article 30(1) or falls under the open-interface route in Article 30(2)-(5). - For infrastructure services, record the capabilities, information, documentation, technical support, and tools provided to support functional equivalence. - For other services, record the open interfaces made available and whether a relevant common specification or harmonised standard has been published in the central Union standards repository. - Respect Article 30 limits: providers need not develop new technology, disclose protected intellectual property or trade secrets, or compromise service security and integrity. 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 30 supports the technical switching distinction between infrastructure services and other services, including functional equivalence, open interfaces, structured export, and security/IP limits. - [CEN and 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) - Grounding source for ongoing Data Act standardization work touching interoperability, portability, and switchability. *Recommended next step* *Placement: after implementation section* ## Review your Data Act switching file Use the switching file to align contracts, export documentation, fee disclosures, interface support, and closure evidence before a customer exit or in-parallel-use request reaches escalation. - [Open Research Copilot](/solutions/research-copilot.md): Answer Data Act scope, timing, and interpretation questions with cited outputs. - [Talk through implementation](/contact.md): Review your product scope, contracts, export process, evidence model, and next actions. ## Data Act Use voluntary cloud clauses as drafting support, not as binding law The Commission has published non-binding model contractual terms and standard contractual clauses for cloud computing contracts. The cloud clauses are useful for drafting because they translate Chapter VI into contract language for switching and exit, termination, and security and business continuity during switching. Keep the hierarchy clear in the contract file: the Data Act is the binding source, while the Commission model terms and standard contractual clauses are voluntary implementation support. If the parties amend the model language, keep the clause-to-Data-Act cross-reference so customer rights, provider duties, and technical limits remain visible. - Use the SCC Switching & Exit clauses to check that switching assistance, customer route, export scope, continuity, and exit steps are covered. - Use the SCC Termination clauses to align the termination moment with successful switching or erasure after the maximum notice period. - Use the SCC Security & Business Continuity clauses to connect switching support with incident notification, continuity risk, and security during transfer and retrieval. - Mark every model clause as voluntary and verify the final wording against Articles 23 to 31 and 34 before relying on it. Sources for this answer: - [European Commission - Model contractual terms and cloud standard clauses](https://digital-strategy.ec.europa.eu/en/library/draft-recommendation-non-binding-model-contractual-terms-data-access-and-use-and-non-binding?ref=sorena.io) - Commission source for voluntary MCTs and SCCs, including cloud clauses for switching and exit, termination, security, business continuity, non-dispersion, non-amendment, and liability. - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Article 41 requires the Commission to develop and recommend non-binding model contractual terms and cloud standard clauses. ## Data Act Keep a switching evidence pack for provider and customer review The evidence pack should prove that the provider removed relevant obstacles, gave the customer the required information, supported the selected switching route, maintained continuity and security, applied the correct charge position, enabled retrieval, and completed erasure when required. Make the record readable outside the migration team. Legal, procurement, security, engineering, support, and account teams should be able to see the contract clause, source article, customer communication, technical export proof, and closure evidence without reconstructing the switch from ticket comments. - Scope evidence: service type, source provider, customer, destination provider or on-premises target, selected route, Article 31 exclusion analysis if relevant, and in-parallel-use flag if relevant. - Contract evidence: signed switching terms, pre-signing availability, notice date, transition period, retrieval period, erasure clause, assistance clause, fee terms, and customer extension if used. - Export evidence: exportable data and digital asset inventory, online register snapshot, formats, interfaces, restrictions, exclusions, transfer logs, and customer validation result. - Operational evidence: support contacts, assistance delivered, continuity-risk notices, security controls, destination-provider cooperation, incident notes, and closure confirmation. - Fee evidence: standard fees, early termination penalties, reduced switching-charge calculation if used, public or customer-facing disclosures, and egress-cost basis for in-parallel use. 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 23-31 and 34-35 support the evidence categories for obstacle removal, contract content, information duties, good-faith cooperation, charges, technical support, interoperability, retrieval, and erasure. - [European Commission - Model contractual terms and cloud standard clauses](https://digital-strategy.ec.europa.eu/en/library/draft-recommendation-non-binding-model-contractual-terms-data-access-and-use-and-non-binding?ref=sorena.io) - Commission cloud clauses provide voluntary drafting structure for switching, termination, security, business continuity, and related contract evidence. ## Primary sources - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Binding source for Data Act Chapter VI switching between data processing services, Article 34 in-parallel use, Article 35 interoperability, Article 41 model terms, and the related contract, charge, export, retrieval, and erasure rules. - [European Commission - Data Act explained](https://digital-strategy.ec.europa.eu/en/factpages/data-act-explained?ref=sorena.io) - Commission explainer for Data Act cloud and edge switching scope, key barriers, charge removal, data categories, open interfaces, functional equivalence, and interoperability context. - [European Commission - Model contractual terms and cloud standard clauses](https://digital-strategy.ec.europa.eu/en/library/draft-recommendation-non-binding-model-contractual-terms-data-access-and-use-and-non-binding?ref=sorena.io) - Commission source for voluntary model contractual terms and non-binding standard contractual clauses for cloud computing contracts, including switching, exit, termination, security, and business continuity. - [CEN and 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) - Grounding source for Data Act standardization work relevant to interoperability, portability, and switchability. ## Related Topic Guides - [Data Act and Common European Data Spaces](/artifacts/eu/data-act/data-act-and-common-european-data-spaces.md): How Data Act Article 33 connects data-space participation with metadata, vocabularies, APIs, access terms, data quality, governance, and standards monitoring. - [Data Act and Data Governance Act Overlap FAQ](/artifacts/eu/data-act/faq/data-governance-act-overlap.md): FAQ explaining where the EU Data Act and Data Governance Act overlap, how they differ, and how to route product, cloud, public-sector reuse, intermediary, and data altruism workflows. - [Data Act and GDPR Personal Data Overlap FAQ](/artifacts/eu/data-act/faq/gdpr-personal-data-overlap.md): FAQ on how the EU Data Act works when connected-product or related-service data includes personal data, mixed datasets, GDPR roles, lawful basis, trade secrets, and third-party sharing. - [Data Act Audit Evidence And Request Logs FAQ](/artifacts/eu/data-act/faq/audit-evidence-and-request-logs.md): FAQ for Data Act request logs covering user and third-party access, B2G exceptional need requests, cloud switching records, contract terms, trade secrets, and GDPR boundaries. - [Data Act B2B Data-Sharing Contract Clauses](/artifacts/eu/data-act/b2b-data-sharing-contract-clauses.md): Clause guide for EU Data Act B2B data sharing: FRAND terms, compensation, trade secret safeguards, recipient limits, termination, logs, and GDPR boundaries. - [Data Act B2B Data-Sharing Contract Template](/artifacts/eu/data-act/b2b-data-sharing-contract-template.md): A usable EU Data Act B2B data-sharing template outline covering access requests, data schedules, permitted use, trade secrets, security, compensation, GDPR boundaries, audit records, and termination. - [Data Act B2G Exceptional-Need Requests](/artifacts/eu/data-act/b2g-exceptional-need-requests.md): A grounded guide to EU Data Act Chapter V requests from public bodies: exceptional need, public emergencies, request contents, limits, safeguards, costs, and records. - [Data Act Cloud Switching Compliance Checklist](/artifacts/eu/data-act/cloud-switching-compliance-checklist.md): A grounded EU Data Act checklist for cloud and data processing service providers covering switching clauses, notices, export formats, charges, interoperability, and evidence. - [Data Act Cloud Switching Contract Terms FAQ](/artifacts/eu/data-act/faq/cloud-switching-contract-terms.md): FAQ on EU Data Act cloud switching contract terms: Article 25 clauses, assistance, notice, transition, charges, export, termination, interoperability, and records. - [Data Act Cloud Switching Fees And Deadlines FAQ](/artifacts/eu/data-act/faq/cloud-switching-fees-and-deadlines.md): FAQ on EU Data Act cloud switching charges, 2027 fee removal, notice periods, transition windows, data retrieval, contract terms, and evidence records. - [Data Act Complaints and Dispute Settlement FAQ](/artifacts/eu/data-act/faq/complaints-and-dispute-settlement.md): FAQ on EU Data Act complaints, competent authorities, dispute settlement bodies, B2B data-sharing disputes, B2G requests, cloud switching disputes, and evidence records. - [Data Act Exportable Data and Metadata FAQ](/artifacts/eu/data-act/faq/exportable-data-and-metadata.md): FAQ explaining which product, related service, metadata, and cloud switching data must be exportable under the EU Data Act, and which data can be excluded. - [Data Act FAQ for Aftermarket Repair and Mobility Services](/artifacts/eu/data-act/faq/aftermarket-repair-and-mobility-services.md): FAQ on EU Data Act vehicle-data access for repairers, independent service providers, fleets, insurers, and mobility services. - [Data Act Functional Equivalence FAQ](/artifacts/eu/data-act/faq/functional-equivalence.md): FAQ on Data Act functional equivalence for cloud switching: IaaS scope, customer outcomes, export support, interoperability duties, limits, and evidence. - [Data Act Indirect Access Request Flows FAQ](/artifacts/eu/data-act/faq/indirect-access-request-flows.md): FAQ for Data Act teams handling user and third-party data requests when direct connected-product access is unavailable, incomplete, or limited. - [Data Act International Government Access FAQ](/artifacts/eu/data-act/faq/international-government-access.md): FAQ on EU Data Act safeguards for non-EU government access to non-personal data held in the Union by data processing service providers. - [Data Act Interoperability Standards FAQ](/artifacts/eu/data-act/faq/interoperability-standards.md): FAQ on EU Data Act interoperability standards for data spaces, cloud switching, smart contracts, harmonised standards, common specifications, and M/614. - [Data Act Model Contractual Terms FAQ](/artifacts/eu/data-act/faq/model-contractual-terms.md): FAQ on the EU Data Act non-binding model contractual terms for data access and use, cloud switching clauses, B2B use, unfair terms, and evidence. - [Data Act Public Emergency Requests FAQ](/artifacts/eu/data-act/faq/public-emergency-requests.md): FAQ on EU Data Act public emergency requests: exceptional need, request content, timing, data holder response, compensation, confidentiality, and records. - [Data Act Smart Contracts for Data Sharing](/artifacts/eu/data-act/smart-contracts-for-data-sharing.md): Data Act Article 36 smart contract guide for data-sharing agreements: scope, robustness, access control, termination, interruption, archiving, standards status, and conformity evidence. - [Data Act SME Exceptions and Startups FAQ](/artifacts/eu/data-act/faq/sme-exceptions-and-startups.md): FAQ on where the EU Data Act gives micro, small, medium-sized, startup, and SME actors narrower treatment for access duties, compensation, and B2B terms. - [Data Act Trade Secret Technical Protection Measures FAQ](/artifacts/eu/data-act/faq/trade-secret-technical-protection-measures.md): FAQ on how EU Data Act data holders can protect trade secrets with confidentiality safeguards, technical measures, limited withholding, suspension, refusal, and evidence. - [Data Act Trade Secrets and Protection Measures](/artifacts/eu/data-act/trade-secrets-and-protection.md): Data Act guide for protecting trade secrets during access and sharing: classification, safeguards, refusal thresholds, notices, evidence records, and reviews. - [Data Act Unfair Contractual Terms | Article 13 B2B Contract Review](/artifacts/eu/data-act/unfair-contractual-terms.md): Review B2B data-sharing clauses under EU Data Act Article 13: unilateral terms, always unfair examples, presumed unfair terms, model clauses, evidence, and remediation. - [Data Act Vehicle Data Guidance](/artifacts/eu/data-act/vehicle-data-guidance.md): Commission-grounded guide to Data Act vehicle data access: connected vehicles, vehicle-related services, raw and pre-processed data, aftermarket use cases, access routes, safeguards, and GDPR boundaries. - [Data Act vs GDPR: connected-product data access](/artifacts/eu/data-act/data-act-vs-gdpr.md): Compare EU Data Act connected-product access duties with GDPR personal-data rules: scope, roles, lawful basis, data subject rights, third-party sharing, trade secrets, and conflicts. - [EU Data Act and Common European Data Spaces FAQ](/artifacts/eu/data-act/faq/data-act-and-common-european-data-spaces.md): FAQ on how EU Data Act interoperability duties, Data Governance Act rules, and sector data-space governance fit together without treating participation as a general obligation. - [EU Data Act Applicability Test](/artifacts/eu/data-act/applicability-test.md): Check whether a product, related service, data holder, cloud service, data-space role, smart contract, or B2G request is in scope of the EU Data Act. - [EU Data Act Application Dates And Transition FAQ](/artifacts/eu/data-act/faq/application-dates-and-transition.md): FAQ on when the EU Data Act applies, which obligations are delayed, and what product, contract, cloud, and evidence records teams should maintain. - [EU Data Act Article 3 Pre-Contract Information](/artifacts/eu/data-act/pre-contractual-information-obligations.md): What Article 3 of the EU Data Act requires before connected-product purchase, rent, lease, or related-service contracting: data categories, access, data holder identity, third-party sharing, complaints, and evidence. - [EU Data Act Article 36 Smart Contract Controls FAQ](/artifacts/eu/data-act/faq/article-36-smart-contract-controls.md): FAQ explaining when EU Data Act Article 36 applies to smart contracts for data-sharing agreements and what controls, conformity evidence, and limits it requires. - [EU Data Act B2B Data Sharing Compensation FAQ](/artifacts/eu/data-act/faq/compensation-for-b2b-data-sharing.md): FAQ on when Data Act data holders may charge B2B data recipients, what reasonable compensation can include, SME limits, unfair terms, disputes, and trade secret safeguards. - [EU Data Act B2G Compensation and Costs FAQ](/artifacts/eu/data-act/faq/b2g-compensation-and-costs.md): FAQ on when Data Act B2G exceptional-need requests are free, when fair compensation may be claimed, which costs can be included, and what records to keep. - [EU Data Act B2G Exceptional Need FAQ](/artifacts/eu/data-act/faq/b2g-exceptional-need.md): When public-sector bodies can request business-held data under the EU Data Act, what a valid request must contain, and how data holders handle limits, trade secrets, compensation, and evidence. - [EU Data Act Checklist for Product, Cloud, and Contract Teams](/artifacts/eu/data-act/checklist.md): A grounded EU Data Act checklist for connected-product data access, third-party sharing, B2G requests, cloud switching, unfair terms, smart contracts, personal data boundaries, evidence, and owners. - [EU Data Act Cloud Switching and Exit Plans](/artifacts/eu/data-act/cloud-switching-and-exit-plans.md): A grounded EU Data Act guide for data processing service exit plans: switching contracts, exportable data, assistance, charges, interoperability, retrieval, erasure, and records. - [EU Data Act Cloud Switching Procurement FAQ](/artifacts/eu/data-act/faq/cloud-switching-procurement-checklist.md): Procurement checklist FAQ for EU Data Act cloud switching: contract terms, exit support, exportable data, switching charges, interoperability, termination, and supplier evidence. - [EU Data Act Compliance Program](/artifacts/eu/data-act/compliance.md): Build a Data Act compliance program for connected-product data access, contracts, B2G requests, cloud switching, smart contracts, GDPR boundaries, records, and ownership. - [EU Data Act Connected Product Scope and Data Types](/artifacts/eu/data-act/scope-connected-products-and-data-types.md): Classify EU Data Act connected products, related services, product data, related-service data, readily available data, metadata, and excluded derived outputs. - [EU Data Act Connected Product Scope FAQ](/artifacts/eu/data-act/faq/scope-connected-products.md): FAQ explaining when connected products, related services, generated data, EU market placement, and SME exceptions fall within EU Data Act scope. - [EU Data Act data 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-processing-services-switching