--- title: "DMA vs Data Act: gatekeeper duties compared with EU data-sharing rules" canonical_url: "https://www.sorena.io/artifacts/eu/digital-markets-act/dma-vs-data-act" source_url: "https://www.sorena.io/artifacts/eu/digital-markets-act/dma-vs-data-act" author: "Sorena AI" description: "Compare the EU Digital Markets Act and EU Data Act by scope, actors, data access, interoperability, reporting, evidence, and enforcement without merging distinct obligations." published_at: "2026-05-09" updated_at: "2026-05-09" keywords: - "EU Digital Markets Act" - "DMA" - "EU Data Act" - "gatekeeper" - "core platform service" - "Article 11" - "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) --- # DMA vs Data Act: gatekeeper duties compared with EU data-sharing rules Compare the EU Digital Markets Act and EU Data Act by scope, actors, data access, interoperability, reporting, evidence, and enforcement without merging distinct obligations. *Comparison* *EU* ## DMA vs Data Act Gatekeeper obligations and data-sharing rules Use this comparison to separate DMA gatekeeper duties for core platform services from the Data Act's broader access-to-data framework. The DMA side focuses on gatekeeper designation, Articles 5 to 7 obligations, data access, interoperability, Article 11 reporting, and Commission enforcement. The EU Digital Markets Act and EU Data Act can both touch platform, product, cloud, and data teams, but they do not ask the same question. The DMA starts with whether a designated gatekeeper provides a listed core platform service and must comply with conduct obligations under Articles 5, 6, and 7. The Data Act starts from access to and use of data, especially data generated by connected products or related services, data-sharing terms, public-sector access requests, and switching between data processing services. Timings in this page are source-linked; verify current legal source language before implementation decisions. ## EU Digital Markets Act vs EU Data Act Compare the regimes by the factual trigger, obligated actor, operational duty, evidence, timing, enforcement path, and overlap rule. - **EU Digital Markets Act**: The DMA is a gatekeeper regime for designated core platform services. It imposes conduct, data access, choice, interoperability, reporting, and anti-circumvention duties on designated gatekeepers. - **EU Data Act**: The Data Act is a horizontal data-access and data-use regime. In this comparison, keep it focused on data generated by connected products or related services, data-sharing terms, public-sector access requests, and switching between data processing services. | Dimension | EU Digital Markets Act | EU Data Act | Operational implication | Sources | | --- | --- | --- | --- | --- | | Scope boundary | Starts with a designated gatekeeper and each core platform service listed in the Commission designation decision, including categories such as online intermediation, search, social networking, video sharing, number-independent messaging, operating systems, browsers, virtual assistants, cloud computing, and online advertising. | Starts with access to and use of data, especially connected-product and related-service data, data-holder availability duties, public-sector access where the Data Act permits it, and data-processing-service switching. | A large digital platform is not automatically a DMA workstream for every service, and a data access request is not automatically a Data Act workstream for every dataset. Record the gatekeeper/CPS trigger separately from the Data Act data trigger. | [Regulation (EU) 2022/1925 (Digital Markets Act)](https://eur-lex.europa.eu/eli/reg/2022/1925/2022-10-12/eng?ref=sorena.io) - Supports the DMA scope test based on designated gatekeepers and core platform services.
[Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Supports the Data Act comparator scope for access to and use of data.
[European Commission - DMA gatekeepers](https://digital-markets-act.ec.europa.eu/gatekeepers_en?ref=sorena.io) - Supports checking the Commission's gatekeeper and core-platform-service list before treating a service as DMA-covered. | | Covered actors | The obligated actor is the designated gatekeeper for the relevant core platform service. Implementation usually involves competition counsel, product owners, platform engineering, data teams, developer relations, advertising, search/ranking, app-store, browser, operating-system, or messaging teams depending on the obligation. | The relevant actors depend on the Data Act role: user, data holder, data recipient, product or related-service provider, public-sector requester, or provider of data processing services. | Assign owners by legal role and product surface, not by a generic 'data platform' label. | [Regulation (EU) 2022/1925 (Digital Markets Act)](https://eur-lex.europa.eu/eli/reg/2022/1925/2022-10-12/eng?ref=sorena.io) - Supports role-specific DMA implementation by obligation and core platform service.
[Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Supports high-level Data Act role separation across users, data holders, data recipients, public bodies, and data-processing-service providers. | | Trigger | Articles 5, 6, and 7 cover gatekeeper conduct duties such as limits on certain data combination, business-user offer freedom, complaint freedom, advertising transparency, non-public business-user data use, default settings, app-store access, self-preferencing in ranking, switching, interoperability, advertising measurement data, end-user portability, business-user data access, search-data access, fair access conditions, and messaging interoperability. | The Data Act comparator covers making data available, terms for data sharing, public-sector access where the Act permits it, and switching or interoperability requirements for data processing services. | Translate DMA duties into service-specific product controls and Article 11 evidence; translate Data Act duties into data-access, contract, request-handling, or switching controls. | [Regulation (EU) 2022/1925 (Digital Markets Act)](https://eur-lex.europa.eu/eli/reg/2022/1925/2022-10-12/eng?ref=sorena.io) - Supports the listed DMA obligation families in Articles 5, 6, and 7.
[Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Supports the Data Act comparator categories without importing DMA gatekeeper concepts.
[European Commission - Article 11 DMA compliance report template](https://digital-markets-act.ec.europa.eu/about-dma/practical-information_en?ref=sorena.io#templates) - Supports turning DMA obligations into detailed implementation explanations and supporting evidence. | | Core obligations | DMA data work is tied to gatekeeper obligations: business users can need access to data generated through their use of the relevant core platform service, end users can need portability, advertisers and publishers can need measurement data, and search competitors can request certain ranking, query, click, and view data on fair, reasonable, and non-discriminatory terms. | Data Act data work is broader and starts from the data covered by the Act, including connected-product and related-service data and the rules for making that data available to users, third parties, or public-sector bodies where applicable. | A DMA business-user data-access control should cite the relevant Article 6 obligation and CPS; a Data Act data-access control should cite the data category, data holder, user or recipient, and request route. | [Regulation (EU) 2022/1925 (Digital Markets Act)](https://eur-lex.europa.eu/eli/reg/2022/1925/2022-10-12/eng?ref=sorena.io) - Supports keeping DMA data controls tied to the relevant core platform service.
[Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Supports the Data Act comparator as a data-access and data-use framework. | | Evidence record | Article 11 requires a gatekeeper to provide the Commission, within 6 months after designation, a detailed and transparent report on measures implemented to ensure Articles 5 to 7 compliance, publish and provide a non-confidential summary, and update the report and summary at least annually. | The Data Act comparison should maintain evidence for the applicable data-access, data-sharing, public-sector request, contract-term, or switching obligation; it does not use the DMA Article 11 compliance-report template. | Use Article 11 evidence for DMA only. The report should be organized by core platform service and obligation, with supporting data, internal documents, implementation dates, product scope, geography, technical changes, user-interface changes, business-user terms, consultation evidence, and alternatives considered where applicable. | [Regulation (EU) 2022/1925 (Digital Markets Act)](https://eur-lex.europa.eu/eli/reg/2022/1925/2022-10-12/eng?ref=sorena.io) - Supports the Article 11 reporting trigger, non-confidential summary, and annual update requirement.
[European Commission - Article 11 DMA compliance report template](https://digital-markets-act.ec.europa.eu/about-dma/practical-information_en?ref=sorena.io#templates) - Supports the service-by-service and obligation-by-obligation organization of DMA reporting evidence.
[Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Supports maintaining Data Act evidence under the Data Act source rather than the DMA Article 11 template. | | Timing and deadlines | DMA timing is driven by designation and ongoing compliance. Article 11 sets the 6-month post-designation reporting point and at-least-annual updates; product changes that affect Articles 5 to 7 controls should be reviewed before release because the gatekeeper must ensure and demonstrate effective compliance. | Data Act timing should be checked against the applicable Data Act provision, product or service launch, access request, contract event, public-sector request, or data-processing-service switching event. | Do not reuse a single compliance calendar label. Track DMA designation and Article 11 cycles separately from Data Act product, request, contract, and switching milestones. | [Regulation (EU) 2022/1925 (Digital Markets Act)](https://eur-lex.europa.eu/eli/reg/2022/1925/2022-10-12/eng?ref=sorena.io) - Supports DMA timing based on designation, Article 11 reporting, annual updates, and the duty to ensure and demonstrate compliance.
[Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Supports checking Data Act timing in the Data Act source instead of importing DMA designation clocks.
[European Commission - Article 11 DMA compliance report template](https://digital-markets-act.ec.europa.eu/about-dma/practical-information_en?ref=sorena.io#templates) - Supports linking DMA evidence updates to reporting changes and updated compliance measures. | | Enforcement | The Commission is the sole DMA enforcer, with cooperation mechanisms for Member State authorities. DMA non-compliance can lead to Commission decisions, remedies, fines up to 10% of total worldwide turnover, up to 20% for certain repeat infringements, and periodic penalty payments up to 5% of average daily worldwide turnover. | The Data Act enforcement route is separate from DMA gatekeeper enforcement. Use the Data Act source and competent-authority analysis for Data Act penalties, rather than borrowing DMA fine caps. | Escalate DMA risk to the gatekeeper's Commission-facing team and Article 11 evidence owners. Escalate Data Act risk through the owners responsible for the relevant data-access, request, contract, or switching obligation. | [Regulation (EU) 2022/1925 (Digital Markets Act)](https://eur-lex.europa.eu/eli/reg/2022/1925/2022-10-12/eng?ref=sorena.io) - Supports using DMA-specific escalation for Commission proceedings, fines, and penalty payments.
[Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Supports treating Data Act enforcement separately from DMA Commission enforcement. | | Overlap and reuse | Keep DMA labels on facts tied to a designated gatekeeper, CPS, Articles 5 to 7 obligation, Article 11 report, Article 6(7) or Article 7 interoperability request, or Commission DMA proceeding. | Keep Data Act labels on facts tied to covered data, data-holder availability, user or third-party access, B2B terms, public-sector access, or data-processing-service switching. | A shared evidence pack is acceptable only if each item states which law it supports. Avoid one blended 'platform data compliance' control that hides the DMA gatekeeper/CPS test or the Data Act data-role test. | [Regulation (EU) 2022/1925 (Digital Markets Act)](https://eur-lex.europa.eu/eli/reg/2022/1925/2022-10-12/eng?ref=sorena.io) - Supports preserving the DMA's gatekeeper and CPS-specific obligation structure.
[Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Supports preserving the Data Act's access-to-data and data-use structure.
[European Commission - Article 11 DMA compliance report template](https://digital-markets-act.ec.europa.eu/about-dma/practical-information_en?ref=sorena.io#templates) - Supports labeling DMA evidence by core platform service and applicable obligation rather than keeping generic compliance records. | | Practical decision rule | DMA interoperability can arise under Article 6(7) for operating-system, virtual-assistant, hardware, and software features, and under Article 7 for number-independent interpersonal communications services. The Commission's interoperability Q&A shows how specification decisions can make this operational for business users and developers. | Data Act interoperability is a separate data and data-processing-services topic; do not use DMA Article 6(7) or Article 7 language unless the service is a designated DMA core platform service. | For DMA, keep records of requests, eligibility decisions, technical interfaces, API documentation, security or integrity justifications, developer communications, and Commission specification materials. For Data Act, keep the switching or data-interoperability record separate. | [European Commission - DMA interoperability questions and answers](https://digital-markets-act.ec.europa.eu/questions-and-answers/interoperability_en?ref=sorena.io) - Supports evidence fields for DMA interoperability request handling and developer-facing processes.
[Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Supports keeping Data Act interoperability and switching issues separate from DMA gatekeeper interoperability. | Sources for Scope boundary - EU Digital Markets Act: - [Regulation (EU) 2022/1925 (Digital Markets Act)](https://eur-lex.europa.eu/eli/reg/2022/1925/2022-10-12/eng?ref=sorena.io) - Supports the DMA scope test based on designated gatekeepers and core platform services. - Quote: "list in the designation decision" Sources for Scope boundary - EU Data 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 comparator scope for access to and use of data. - Quote: "access to and use of data" Sources for Scope boundary - operational implication: - [European Commission - DMA gatekeepers](https://digital-markets-act.ec.europa.eu/gatekeepers_en?ref=sorena.io) - Supports checking the Commission's gatekeeper and core-platform-service list before treating a service as DMA-covered. - Quote: "core platform services" Sources for Covered actors - EU Digital Markets Act: - [Regulation (EU) 2022/1925 (Digital Markets Act)](https://eur-lex.europa.eu/eli/reg/2022/1925/2022-10-12/eng?ref=sorena.io) - Supports the gatekeeper as the obligated DMA actor for listed core platform services. - Quote: "The gatekeeper shall" Sources for Covered actors - EU Data Act: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Supports high-level Data Act role separation across users, data holders, data recipients, public bodies, and data-processing-service providers. - Quote: "data holders" Sources for Covered actors - operational implication: - [Regulation (EU) 2022/1925 (Digital Markets Act)](https://eur-lex.europa.eu/eli/reg/2022/1925/2022-10-12/eng?ref=sorena.io) - Supports role-specific DMA implementation by obligation and core platform service. - Quote: "with respect to each" Sources for Trigger - EU Digital Markets Act: - [Regulation (EU) 2022/1925 (Digital Markets Act)](https://eur-lex.europa.eu/eli/reg/2022/1925/2022-10-12/eng?ref=sorena.io) - Supports the listed DMA obligation families in Articles 5, 6, and 7. - Quote: "obligations laid down in Articles 5, 6 and 7" Sources for Trigger - EU Data 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 comparator categories without importing DMA gatekeeper concepts. - Quote: "make data available" Sources for Trigger - operational implication: - [European Commission - Article 11 DMA compliance report template](https://digital-markets-act.ec.europa.eu/about-dma/practical-information_en?ref=sorena.io#templates) - Supports turning DMA obligations into detailed implementation explanations and supporting evidence. - Quote: "supporting data and internal documents" Sources for Core obligations - EU Digital Markets Act: - [Regulation (EU) 2022/1925 (Digital Markets Act)](https://eur-lex.europa.eu/eli/reg/2022/1925/2022-10-12/eng?ref=sorena.io) - Supports DMA data-access duties for business users, end users, advertisers, publishers, and third-party search engines. - Quote: "continuous and real-time access" Sources for Core obligations - EU Data 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 comparator as a data-access and data-use framework. - Quote: "users can access" Sources for Core obligations - operational implication: - [Regulation (EU) 2022/1925 (Digital Markets Act)](https://eur-lex.europa.eu/eli/reg/2022/1925/2022-10-12/eng?ref=sorena.io) - Supports keeping DMA data controls tied to the relevant core platform service. - Quote: "relevant core platform services" Sources for Evidence record - EU Digital Markets Act: - [Regulation (EU) 2022/1925 (Digital Markets Act)](https://eur-lex.europa.eu/eli/reg/2022/1925/2022-10-12/eng?ref=sorena.io) - Supports the Article 11 reporting trigger, non-confidential summary, and annual update requirement. - Quote: "detailed and transparent manner" - [European Commission - Article 11 DMA compliance report template](https://digital-markets-act.ec.europa.eu/about-dma/practical-information_en?ref=sorena.io#templates) - Supports the practical evidence fields expected in a DMA Article 11 compliance report. - Quote: "technical/engineering changes" Sources for Evidence record - EU Data Act: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Supports maintaining Data Act evidence under the Data Act source rather than the DMA Article 11 template. - Quote: "transparent manner" Sources for Evidence record - operational implication: - [European Commission - Article 11 DMA compliance report template](https://digital-markets-act.ec.europa.eu/about-dma/practical-information_en?ref=sorena.io#templates) - Supports the service-by-service and obligation-by-obligation organization of DMA reporting evidence. - Quote: "each applicable obligation" Sources for Timing and deadlines - EU Digital Markets Act: - [Regulation (EU) 2022/1925 (Digital Markets Act)](https://eur-lex.europa.eu/eli/reg/2022/1925/2022-10-12/eng?ref=sorena.io) - Supports DMA timing based on designation, Article 11 reporting, annual updates, and the duty to ensure and demonstrate compliance. - Quote: "within 6 months after its designation" Sources for Timing and deadlines - EU Data Act: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Supports checking Data Act timing in the Data Act source instead of importing DMA designation clocks. - Quote: "This Regulation" Sources for Timing and deadlines - operational implication: - [European Commission - Article 11 DMA compliance report template](https://digital-markets-act.ec.europa.eu/about-dma/practical-information_en?ref=sorena.io#templates) - Supports linking DMA evidence updates to reporting changes and updated compliance measures. - Quote: "highlight the differences" Sources for Enforcement - EU Digital Markets Act: - [Regulation (EU) 2022/1925 (Digital Markets Act)](https://eur-lex.europa.eu/eli/reg/2022/1925/2022-10-12/eng?ref=sorena.io) - Supports DMA enforcement by the Commission and the fine and periodic-penalty mechanics in Articles 29 to 31. - Quote: "sole enforcer" Sources for Enforcement - EU Data Act: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Supports treating Data Act enforcement separately from DMA Commission enforcement. - Quote: "effective, proportionate and dissuasive penalties" Sources for Enforcement - operational implication: - [Regulation (EU) 2022/1925 (Digital Markets Act)](https://eur-lex.europa.eu/eli/reg/2022/1925/2022-10-12/eng?ref=sorena.io) - Supports using DMA-specific escalation for Commission proceedings, fines, and penalty payments. - Quote: "non-compliance decision" Sources for Overlap and reuse - EU Digital Markets Act: - [Regulation (EU) 2022/1925 (Digital Markets Act)](https://eur-lex.europa.eu/eli/reg/2022/1925/2022-10-12/eng?ref=sorena.io) - Supports preserving the DMA's gatekeeper and CPS-specific obligation structure. - Quote: "each core platform service" Sources for Overlap and reuse - EU Data Act: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Supports preserving the Data Act's access-to-data and data-use structure. - Quote: "data sharing" Sources for Overlap and reuse - operational implication: - [European Commission - Article 11 DMA compliance report template](https://digital-markets-act.ec.europa.eu/about-dma/practical-information_en?ref=sorena.io#templates) - Supports labeling DMA evidence by core platform service and applicable obligation rather than keeping generic compliance records. - Quote: "applicable obligation" Sources for Practical decision rule - EU Digital Markets Act: - [European Commission - DMA interoperability questions and answers](https://digital-markets-act.ec.europa.eu/questions-and-answers/interoperability_en?ref=sorena.io) - Supports practical DMA interoperability treatment for developers, business users, and Commission specification decisions. - Quote: "request-based process" Sources for Practical decision rule - EU Data Act: - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Supports keeping Data Act interoperability and switching issues separate from DMA gatekeeper interoperability. - Quote: "data processing services" Sources for Practical decision rule - operational implication: - [European Commission - DMA interoperability questions and answers](https://digital-markets-act.ec.europa.eu/questions-and-answers/interoperability_en?ref=sorena.io) - Supports evidence fields for DMA interoperability request handling and developer-facing processes. - Quote: "public annual reports" ### How to decide which workstream owns an issue - Use DMA when the issue depends on a designated gatekeeper, a listed core platform service, or an Articles 5 to 7 obligation. - Use Data Act when the issue depends on access to or use of covered data, data sharing, public-sector access, contract terms, or data-processing-service switching. - Use both only when the same product or data flow independently satisfies both triggers; keep the source, article, actor, evidence, and enforcement path separate. - If the issue is a gatekeeper's product release, ranking change, app-store rule, data-access interface, interoperability process, or Article 11 report update, run a DMA review before treating it as a general data-governance change. Sources for the practical decision rule: - [Regulation (EU) 2022/1925 (Digital Markets Act)](https://eur-lex.europa.eu/eli/reg/2022/1925/2022-10-12/eng?ref=sorena.io) - Supports the DMA ownership rule for gatekeepers, core platform services, and Articles 5 to 7 obligations. - Quote: "designated as a gatekeeper" - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Supports the separate Data Act ownership rule for data access, data use, and switching workstreams. - Quote: "make data available" ## The fast distinction Use the DMA column when the work concerns a designated gatekeeper, a designated core platform service, or a change to business-user access, end-user choice, ranking, advertising transparency, data portability, business-user data access, app stores, operating systems, browsers, or messaging interoperability. Use the Data Act column when the work concerns access to data generated by connected products or related services, making data available to users or third parties, contractual terms for data sharing, public-sector access in exceptional-need scenarios, or switching between data processing services. - Do not treat a DMA data-access obligation as a general Data Act access request; tie it to the relevant gatekeeper core platform service and Article 6 duty. - Do not treat every Data Act data-sharing workflow as a DMA issue; the DMA applies to designated gatekeepers and their listed core platform services. - When both laws are relevant, keep one evidence file but label each item by source, article, actor, service, and request type. Sources for this answer: - [Regulation (EU) 2022/1925 (Digital Markets Act)](https://eur-lex.europa.eu/eli/reg/2022/1925/2022-10-12/eng?ref=sorena.io) - Supports the DMA scope test: gatekeepers, listed core platform services, and Articles 5 to 7 obligations. - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Supports the Data Act comparator at a high level: access to and use of data, data-holder availability duties, public-sector access, and switching between data processing services. ## Where DMA implementation gets concrete For DMA work, the practical unit is not a generic platform or account. It is a designated gatekeeper and each core platform service listed in the Commission designation decision. The Commission publishes and updates the gatekeeper and core-platform-service list, and the obligation analysis should follow that list. The strongest DMA evidence is service-by-service: Article 5 conduct controls, Article 6 controls that may need technical implementation or further specification, Article 7 number-independent interpersonal communications interoperability where applicable, and Article 11 reporting material that explains the measures in detail. - Keep a CPS register showing the gatekeeper, service, designation case, affected product surfaces, business users, end users, and owner. - Map each Articles 5 to 7 duty to the product, API, ranking, data, advertising, choice-screen, app-store, browser, operating-system, or messaging surface it affects. - For Article 11, retain the compliance statement, implementation explanation, supporting data, internal documents, user-interface evidence, technical change notes, consultation evidence, and non-confidential summary. Sources for this answer: - [European Commission - DMA gatekeepers](https://digital-markets-act.ec.europa.eu/gatekeepers_en?ref=sorena.io) - Supports using the Commission's gatekeeper and core-platform-service list as the live DMA scoping reference. - [European Commission - Article 11 DMA compliance report template](https://digital-markets-act.ec.europa.eu/about-dma/practical-information_en?ref=sorena.io#templates) - Supports the Article 11 evidence expectations for each designated core platform service and each applicable Articles 5 to 7 obligation. ## Overlap that teams commonly misread Both laws can use the language of data access, portability, interoperability, and business users. The source of the duty changes the implementation. Under the DMA, Article 6 includes duties such as business-user access to data generated in the context of relevant core platform services, end-user portability, search-data access, advertising measurement access, and interoperability with operating-system, hardware, or software features. The Data Act comparison should stay separate unless the fact pattern is really a Data Act data-availability, data-sharing, public-sector access, contract-term, or cloud-switching issue. A single product team may own both, but the legal trigger and evidence labels should not be merged. - For DMA self-preferencing, test ranking and related indexing or crawling for services and products offered by the gatekeeper itself versus similar third-party offerings. - For DMA interoperability, distinguish Article 6(7) operating-system, virtual-assistant, hardware, and software feature access from Article 7 messaging interoperability. - For Data Act work, keep the comparator at the data-access or switching layer unless the Data Act source being used supports a more specific claim. Sources for this answer: - [Regulation (EU) 2022/1925 (Digital Markets Act)](https://eur-lex.europa.eu/eli/reg/2022/1925/2022-10-12/eng?ref=sorena.io) - Supports DMA obligations on self-preferencing, interoperability, data portability, business-user data access, and advertising measurement access. - [European Commission - DMA interoperability questions and answers](https://digital-markets-act.ec.europa.eu/questions-and-answers/interoperability_en?ref=sorena.io) - Supports practical treatment of DMA interoperability requests, developer access, process transparency, and Commission specification decisions. *DMA vs Data Act next step* *Placement: before sources* ## Turn the DMA comparison into scoped implementation records Use the cited sources listed here to verify obligations and the supporting evidence requirements. - [Open Research Copilot for DMA questions](/solutions/research-copilot.md): Verify the following areas from the cited sources: gatekeepers, core platform services, Articles 5 to 7 obligations, interoperability, Article 11 reports, and Data Act overlap. - [Review a DMA vs Data Act scope file](/contact.md): Walk through which services, data flows, product changes, and evidence records belong under DMA, Data Act, or both. ## Primary sources - [Regulation (EU) 2022/1925 (Digital Markets Act)](https://eur-lex.europa.eu/eli/reg/2022/1925/2022-10-12/eng?ref=sorena.io) - Supports the DMA ownership rule for gatekeepers, core platform services, and Articles 5 to 7 obligations. - Quote: "designated as a gatekeeper" - [European Commission - DMA gatekeepers](https://digital-markets-act.ec.europa.eu/gatekeepers_en?ref=sorena.io) - Supports checking the Commission's gatekeeper and core-platform-service list before treating a service as DMA-covered. - Quote: "core platform services" - [European Commission - Article 11 DMA compliance report template](https://digital-markets-act.ec.europa.eu/about-dma/practical-information_en?ref=sorena.io#templates) - Supports labeling DMA evidence by core platform service and applicable obligation rather than keeping generic compliance records. - Quote: "applicable obligation" - [European Commission - DMA interoperability questions and answers](https://digital-markets-act.ec.europa.eu/questions-and-answers/interoperability_en?ref=sorena.io) - Supports evidence fields for DMA interoperability request handling and developer-facing processes. - Quote: "public annual reports" - [Regulation (EU) 2023/2854 (Data Act)](https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng?ref=sorena.io) - Supports the separate Data Act ownership rule for data access, data use, and switching workstreams. - Quote: "make data available" ## Related Topic Guides - [DMA Anti-Circumvention Design Review for Gatekeeper Product Changes](/artifacts/eu/digital-markets-act/anti-circumvention-design-review.md): Review DMA Article 13 anti-circumvention risks in gatekeeper product, interface, contractual, commercial, and technical changes with obligation mapping and evidence records. - [DMA Article 11 Compliance Report Template FAQ](/artifacts/eu/digital-markets-act/faq/compliance-report-template.md): How gatekeepers should use the DMA Article 11 compliance report template to document obligation-by-obligation measures, evidence, updates, and non-confidential summaries. - [DMA Article 6 Business User Data Access Guide](/artifacts/eu/digital-markets-act/business-user-data-access.md): Grounded guide to EU Digital Markets Act Article 6 data access for business users, end users, authorised third parties, consent boundaries, and evidence handoffs. - [DMA Article 6(7) and Article 7 interoperability obligations](/artifacts/eu/digital-markets-act/article-6-7-interoperability.md): Grounded guide to DMA interoperability duties: Article 6(7) operating-system feature access, Article 7 messaging interoperability, request handling, security conditions, and compliance evidence. - [DMA Articles 5, 6 and 7 obligations mapped to CPS evidence](/artifacts/eu/digital-markets-act/core-obligations-by-obligation.md): Map EU Digital Markets Act Articles 5, 6 and 7 obligations to affected core platform services, product evidence, legal owners, and Article 11 compliance-report artifacts. - [DMA compliance program and monitoring for gatekeepers](/artifacts/eu/digital-markets-act/compliance-program-and-monitoring.md): Build a DMA compliance program around Article 8 effective compliance, Article 11 reporting evidence, Article 13 anti-circumvention controls, and Article 28 compliance-function governance. - [DMA Core Platform Service Scoping](/artifacts/eu/digital-markets-act/core-platform-service-scoping-by-service.md): Scope EU Digital Markets Act core platform services by service category, designation evidence, user thresholds, and Form GD service-boundary records. - [DMA core platform services FAQ](/artifacts/eu/digital-markets-act/faq/core-platform-services.md): FAQ on EU Digital Markets Act core platform services: Article 2 service categories, gatekeeper designation evidence, user thresholds, service scoping, and Article 11 reporting. - [DMA CPS Obligation Matrix Workflow: Articles 5, 6, 7 and Article 11 Evidence](/artifacts/eu/digital-markets-act/cps-obligation-matrix-workflow.md): Build a DMA core platform service obligation matrix that links each designated CPS to Articles 5, 6 and 7 duties, product owners, designation evidence, Article 11 report artifacts and review gates. - [DMA designation intake workflow for gatekeeper notifications](/artifacts/eu/digital-markets-act/designation-intake-workflow.md): Build a grounded DMA designation intake record covering core platform service classification, Article 3 thresholds, Form GD evidence, Commission handoff, and Article 11 readiness. - [DMA enforcement, penalties, and remedies: Commission powers and evidence](/artifacts/eu/digital-markets-act/enforcement-penalties-and-remedies.md): EU Digital Markets Act enforcement guide covering Commission non-compliance decisions, DMA fine caps, periodic penalty payments, remedies, interim measures, commitments, and Article 11 evidence. - [DMA Gatekeeper Compliance Checklist for Articles 5, 6, 7 and 11](/artifacts/eu/digital-markets-act/gatekeeper-compliance-checklist.md): A grounded EU Digital Markets Act checklist for designated gatekeepers: core platform service scope, Article 5/6/7 controls, Article 11 report evidence, anti-circumvention checks, and review gates. - [DMA Gatekeeper Designation Guide: Article 3 thresholds, Form GD, and Article 11 readiness](/artifacts/eu/digital-markets-act/gatekeeper-designation-guide.md): A grounded EU Digital Markets Act guide for assessing Article 3 gatekeeper thresholds, scoping core platform services, preparing Form GD evidence, handling rebuttal annexes, and planning Article 11 compliance reporting. - [DMA gatekeeper thresholds: what counts and when to notify](/artifacts/eu/digital-markets-act/faq/gatekeeper-thresholds.md): Standalone FAQ on the EU Digital Markets Act gatekeeper thresholds, Article 3 notification timing, Form GD evidence, and active user-count methodology. - [DMA interoperability requests: Article 7 and Commission guidance](/artifacts/eu/digital-markets-act/faq/interoperability-requests.md): How EU Digital Markets Act interoperability requests work for Article 7 messaging services, Article 6(7) operating-system access, gatekeeper evidence, requester evidence, and security safeguards. - [DMA penalties and fines: caps, triggers, and enforcement evidence](/artifacts/eu/digital-markets-act/penalties-and-fines.md): EU Digital Markets Act penalties guide covering Article 30 fine caps, Article 31 periodic penalty payments, non-compliance decisions, remedies, and evidence records. - [DMA Product Change Review Workflow for Articles 5, 6, 7, 11 and 13](/artifacts/eu/digital-markets-act/product-change-review-workflow.md): Review DMA-relevant product releases for Article 5, Article 6, Article 7, anti-circumvention, Article 11 evidence, and product-owner/legal signoff. - [DMA Self-Preferencing Compliance Examples for Ranking and Display](/artifacts/eu/digital-markets-act/self-preferencing-compliance-examples.md): Examples and release-review controls for DMA Article 6(5) self-preferencing checks across ranking, indexing, crawling, search results, marketplaces, app stores, feeds, and virtual assistants. - [DMA vs DSA: Digital Markets vs Services Act](/artifacts/eu/digital-markets-act/dma-vs-dsa.md): A grounded comparison of the DMA and DSA focused on gatekeepers, core platform services, DMA obligations, Article 11 reporting, interoperability, data access, and enforcement. - [DMA vs EU competition law: gatekeeper obligations, Article 11 evidence, and enforcement](/artifacts/eu/digital-markets-act/dma-vs-eu-competition-law.md): Compare the EU Digital Markets Act with EU competition law: ex ante gatekeeper and core platform service duties, Articles 5 to 7, Article 11 reports, penalties, and evidence records. - [DMA vs GDPR: gatekeeper data obligations compared](/artifacts/eu/digital-markets-act/dma-vs-gdpr.md): Compare DMA gatekeeper obligations with high-level GDPR overlap for consent, combining personal data, data access, portability, and Article 11 reporting. - [EU Digital Markets Act Article 11 Evidence Calendar](/artifacts/eu/digital-markets-act/annual-report-evidence-calendar.md): Build a source-grounded DMA Article 11 compliance report calendar with evidence owners, annual update checkpoints, report sections, and review gates. - [EU Digital Markets Act checklist for gatekeeper compliance](/artifacts/eu/digital-markets-act/checklist.md): A source-grounded DMA checklist for designated gatekeepers and core platform services, covering scope, Articles 5, 6 and 7 obligations, Article 11 reporting, evidence, anti-circumvention, and governance. - [EU Digital Markets Act compliance: gatekeeper obligations and evidence](/artifacts/eu/digital-markets-act/compliance.md): DMA compliance guide for designated gatekeepers: core platform service scoping, Articles 5, 6 and 7 controls, Article 11 reports, anti-circumvention checks, interoperability evidence, and enforcement risk. - [EU Digital Markets Act deadlines and compliance calendar](/artifacts/eu/digital-markets-act/deadlines-and-compliance-calendar.md): Track DMA notification, designation, six-month obligation start, Article 11 reporting, Article 14 concentration notices, Article 15 profiling audits, and preparation milestones using official EU sources. - [EU Digital Markets Act FAQ: gatekeepers, DMA obligations, reports, and enforcement](/artifacts/eu/digital-markets-act/faq.md): Concise FAQ on the EU Digital Markets Act for gatekeeper designation, core platform services, Articles 5, 6 and 7 obligations, Article 11 reports, interoperability, business-user data access, compliance evidence, and enforcement. - [EU Digital Markets Act requirements for gatekeepers](/artifacts/eu/digital-markets-act/requirements.md): DMA requirements for designated gatekeepers: core platform service scope, Articles 5, 6 and 7 obligations, Article 11 reporting, anti-circumvention, evidence, remedies, and fines. - [EU Digital Markets Act Timeline and Key Milestones: practical obligations and evidence guide](/artifacts/eu/digital-markets-act/timeline-and-key-milestones.md): Practical EU Digital Markets Act guide to Timeline and Key Milestones: scope, owners, evidence, edge cases, checklist steps, and external source-linked citations. - [EU DMA Applicability Test: gatekeeper thresholds, core platform services, and evidence](/artifacts/eu/digital-markets-act/applicability-test.md): Test whether the EU Digital Markets Act may apply to a platform service using the DMA gatekeeper criteria, core platform service categories, EU user thresholds, notification steps, and evidence records. - [EU DMA Article 11 Compliance Reporting Guide](/artifacts/eu/digital-markets-act/article-11-reporting.md): Source-grounded guide to EU Digital Markets Act Article 11 compliance reports: report purpose, template evidence, non-confidential summaries, annual updates, and submission steps. - [EU DMA do's and don'ts for product teams](/artifacts/eu/digital-markets-act/dos-and-donts-for-product-teams.md): Product release checks for designated DMA gatekeepers: Article 5, 6 and 7 obligations, anti-circumvention review, data access, interoperability, self-preferencing and Article 11 evidence. - [What do DMA Articles 5, 6, and 7 require from gatekeepers?](/artifacts/eu/digital-markets-act/faq/articles-5-6-and-7-obligations.md): FAQ explaining how EU Digital Markets Act Articles 5, 6, and 7 group gatekeeper obligations, what product evidence they require, and how Article 11 reporting connects. --- [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/digital-markets-act/dma-vs-data-act