{"release":{"id":"7a41a2cc5aaf78412593b2d310cf279f6d209fcbf373aa170d236de8b21d8f21","published":"2026-11-17T06:41:06Z","pinned":false},"limits":{"coverage":{"history":"current_only","held_since":"2024-09-06","gaps":[],"covered":["FAQ version 1.4 — Q&A — Data Act [in force] L3"],"not_covered":["national guidance","court decisions"]},"freshness":{"release_id":"7a41a2cc5aaf78412593b2d310cf279f6d209fcbf373aa170d236de8b21d8f21","release_published":"2026-11-17T06:41:06Z","checked_at":"2026-11-16","checked_against":"the Commission publication"},"truncation":null,"failures":[],"incomplete":[]},"page":{"path":"/data-act/level-3/q-and-a/commission/commission-data-act-faq","url":"https://www.headlesslaw.com/data-act/level-3/q-and-a/commission/commission-data-act-faq","title":"FAQ version 1.4 — Q&A — Data Act [in force]","family":"l3","work_id":"spaces/dataact/level-3/q-and-a/commission/commission-data-act-faq","status":"in_force","force_status":"in_force","date_state":"current","requested_date":null,"as_of":"2026-11-18","applies_from":null,"application":null,"version_label":"Commission publication, 6 September 2024","check":{"against":"the Commission publication","on":"2026-11-16"},"check_result":"matched","official_url":"https://digital-strategy.ec.europa.eu/en/library/commission-publishes-frequently-asked-questions-about-data-act","valid_from":"2024-09-06","valid_until":null,"revision":1,"content_id":"a733b4ac4f2b734a","change_date":null,"nearest_versions":["2024-09-06"],"first_text_date":"2024-09-06","correction_applies":false,"versions":["2024-09-06"],"version_url":"https://www.headlesslaw.com/data-act/level-3/q-and-a/commission/commission-data-act-faq/versions/2024-09-06","revision_url":"https://www.headlesslaw.com/data-act/level-3/q-and-a/commission/commission-data-act-faq/versions/2024-09-06/rev/a733b4ac4f2b734a","versions_url":"https://www.headlesslaw.com/data-act/level-3/q-and-a/commission/commission-data-act-faq/versions","relations_url":"https://www.headlesslaw.com/data-act/level-3/q-and-a/commission/commission-data-act-faq/relations","source_line":"Answer by the European Commission · not legislation · dated 22 Jan 2026 [in force]","attribution":{"prepared_by":"European Commission","published_by":"European Commission","published_in":null,"document_type":"qa_answer","legal_nature":"not_legislation","addressees":"not stated in the document","dates":{"document_date":"2026-01-22","locators":{"document_date":"PDF page 1: \"22 January 2026\""}},"adoption":null}},"provenance":{"official_url":"https://digital-strategy.ec.europa.eu/en/library/commission-publishes-frequently-asked-questions-about-data-act","check":{"result":"matched","checked_at":"2026-11-16","against":"the Commission publication"},"repo_path":null,"body_sha256":"0c837b343aebb798df1ea2a1afff6fd31220a61b5bfbc7b7ff76b887390483c5","markdown_sha256":"3e611f768ab0bffe25dabbe6eb2002b1614da0d66f79dcbc33f6053c5ce62d31"},"units":[],"markdown":"**Answer by the European Commission · not legislation · dated 22 Jan 2026 [in force]**\n\n*In force · Commission publication, 6 September 2024 · Verified 16 Nov 2026 · [Official source](https://digital-strategy.ec.europa.eu/en/library/commission-publishes-frequently-asked-questions-about-data-act)*\n\n| | |\n|---|---|\n| **Full title** | FAQ version 1.4 — Q&A — Data Act \\[in force\\] |\n| **Prepared by** | European Commission |\n| **Published by** | European Commission |\n| **Reference** | FAQ version 1.4 |\n| **Document type** | Q&A |\n| **Legal nature** | Not legislation |\n| **Addressees** | Not stated in the document |\n| **Dates** | Dated 22 January 2026 |\n| **Legal basis** | Regulation (EU) 2023/2854 |\n| **Related instruments** | Documents: [FAQ PDF](https://ec.europa.eu/newsroom/dae/redirection/document/108144) |\n| **Text on this page** | Word for word — the full text of the Commission publication; its 3 tables cell by cell, rows and columns as in the PDF |\n\n## Frequently Asked Questions\n\n## Data Act\n\n## 22 January 2026 Version 1.4\n\nThe Data Act (Regulation (EU) 2023/2584) establishes harmonised, horizontal rules to ensure fairness in the allocation of value generated from data across market actors, while safeguarding the interests of those who invest in data-generation technologies.\n\nFor an introduction to the Data Act, we invite you to consult the “Data Act Explained” fact page.\n\nThis set of more technical Frequently Asked Questions (FAQs), published approximately a year before the entry into application of the Data Act, is designed to assist stakeholders in the implementation of the legal provisions. The FAQs are the product of extensive stakeholder interactions, and this is intended to be a ‘living document’ that will be updated as and when necessary. The version history can be found at the end of the document.\n\nThis document should not be considered as representative of the European Commission’s official position. The replies to the FAQs do not extend in any way the rights and obligations deriving from applicable legislation nor introduce any additional requirement. The expressed views are not authoritative and cannot prejudge any future actions the European Commission may take, including potential positions before the Court of Justice of the European Union.\n\nPlease contact us if you have a question that is not covered here and we will try to get back to you as quickly as possible. For any complaints related to the Data Act’s implementation, please consider contacting the data coordinator in your Member State.\n\n<!-- table: t01 -->\n<!-- lint: table-cell-ok — verbatim table of the official text, rendered from its table file -->\n| FAQ Version | Date |\n| --- | --- |\n| 1.0 | 06/09/2024 |\n| 1.1 | 13/09/2024 |\n| 1.2 | 03/02/2025 |\n| 1.3 | 12/09/2025 |\n| 1.4 | 22/1/2026 |\n<!-- /table -->\n\n### © European Union, 2024\n\nThe reuse policy of European Commission documents is implemented by Commission Decision 2011/833/EU of 12 December 2011 on the reuse of Commission documents (OJ L 330, 14.12.2011, p. 39). Unless otherwise noted, the reuse of this document is authorised under a Creative Commons Attribution 4.0 International (CC BY 4.0) licence (https://creativecommons.org/licenses/by/4.0/). This means that reuse is allowed provided appropriate credit is given and any changes are indicated.\n\n### Interaction with other EU law\n\n## 1. How does the Data Act interact with the General Data Protection Regulation?\n\nThe General Data Protection Regulation (GDPR) is fully applicable to all personal data processing activities under the Data Act. The Data Act does not regulate as such the protection of personal data. Instead, the Data Act enhances data sharing and enables a fair distribution of the value of data by establishing clear rules related to the access and use of data within the EU’s data economy.\n\nIn some cases, the Data Act specifies and complements the GDPR (e.g. real-time portability of data from Internet-of-Things (IoT) objects). In other cases, the Data Act restricts the re-use of data by third parties (e.g. Article 6 of the Data Act). In the event of a conflict between the GDPR and the Data Act, the GDPR rules on the protection of personal data prevail (cf. Article 1(5) of the Data Act).\n\n## 2. How does the relationship between the Data Act and the GDPR affect the enforcement and protection of personal data?\n\nThe Data Act respects the competence of the data protection authorities (DPAs) to enforce rules on personal data protection. The Data Act provides a coherent enforcement and cooperation mechanism between DPAs and other competent authorities.\n\nArticle 1(5) of the Data Act establishes that the GDPR applies to the processing of personal data in the framework of the Data Act. In this context, it recalls that the DPAs are competent to enforce the obligations stemming directly from the GDPR.\n\nArticle 37(3) of the Data Act provides that, insofar as the protection of personal data is concerned, the DPAs are responsible for monitoring the application of the Data Act and can rely on the tasks and powers laid down in the GDPR. This is also stated in recital 107 of the Data Act. The protection of personal data captures, for example, the power to assess: (i) whether a user who is a data subject has received or has been allowed to port all personal data it requests; (ii) whether the data holder correctly qualifies which data should be considered personal data; and (iii) whether a valid legal basis under the GDPR exists for a user who is not a data subject to request and port personal data. Article 37(3) of the Data Act also ensures that data subjects are not required to go to two different authorities in cases where the rights of access and porting would apply under both the Data Act and the GDPR or where there could be any other grievance relating to the protection of their personal data in the application of the Data Act.\n\nMore generally, the Commission strives to promote a strong working relationship between the authorities that enforce data legislation in the EU, including through the membership of the European Data Protection Supervisor (EDPS) and the European Data Protection Board (EDPB) in the European Data Innovation Board.\n\n## 3. How does the Data Act interact with data-sharing obligations under other EU legislation?\n\nThe Data Act is a horizontal piece of legislation that aims to significantly enhance fair access to and use of data across all sectors of the economy. Chapter III, in particular, establishes a framework regarding the conditions, compensation, and technical protection measures for whenever a data holder is obliged under EU or national law to share data with a data recipient.\n\nMore concretely, Article 44 of the Data Act addresses two key dimensions that structure the interaction between the Data Act and other EU legislation that include rules on data access and use: time of entry into force (Article 44(1)) and sectoral specificities (Article 44(2)).\n\nAccording to Article 44(1), data-sharing obligations contained in Union legal acts that entered into force on or before 11 January 2024 (the Data Act’s entry into force) remain unaffected, meaning that previous legal obligations (including those laid down in delegated or implementing acts) prevail. If EU legal acts introduce rules on data between 11 January 2024 and 12 September 2025 (the Data Act’s entry into application), best efforts should be made to ensure alignment, but there is no legal obligation to do so.\n\nThe Data Act sets horizontal rules for data access, sharing and use. However, Article 44(2) allows the Data Act to be complemented by sector-specific legislation, where necessary, with practical and technical modalities (e.g. safety, standardisation, or technical matters) and with specific limits on data holders’ access rights or actions. However, the development of such sectoral rules should be approached cautiously and be consistent with the principles laid down in the Data Act to the greatest extent possible, thus avoiding unnecessary complexity. The principles of the Data Act apply for all matters related to ‘access to data’ that are not specifically regulated in such sectoral rules.\n\n### Access to and use of data in the Internet-of-Things context\n\nAn example of Chapter II in practice\n\n## Section on data in scope\n\n## 4. Which data are in scope?\n\nSeveral factors determine which data are covered by the data access rights provided for in Articles 3, 4 and 5 of the Data Act. Generally speaking, raw and pre-processed data (simply put, ‘raw but usable’ data) that are readily available to a data holder as a result of the manufacturer’s technical design are subject to mandatory data-sharing obligations that are regulated by Chapter II.\n\n### Access and use of IoT data – Chapter II of the Data Act\n\n<!-- table: t02 -->\n<!-- lint: table-cell-ok — verbatim table of the official text, rendered from its table file -->\n| Factor | Explanation | Reference in the legal text |\n| --- | --- | --- |\n| Product data | Data obtained, generated, or collected by a connected product and which relates to its performance, use or environment. Purely descriptive data that accompanies the connected product (e.g. in user manuals or on the packaging) is not product data. The only situation in which information ‘about’ the connected product is relevant is the pre-contractual transparency obligation under Article 3. | Article 2(15), Recital 15 |\n| Related service data | Data representing user action, inaction and events related to the connected product during the provision of a related service. | Article 2(16), Recitals 15 and 17 |\n| Readily available data | Product data and related service data that a data holder can obtain without disproportionate effort going beyond a simple operation. The definition of 'readily available data' does not include a reference to the time of their generation or collection. Only data generated/collected after the entry into application of the Data Act should be considered as falling within the scope of Chapter II. | Article 2(17), Recitals 20 and 21 |\n| Level of enrichment of the data | In scope: raw data and pre-processed data, accompanied by the necessary metadata to make it understandable and usable. For example, data collected from a single sensor or a connected group of sensors for the purpose of making the collected data comprehensible for wider use-cases by determining a physical quantity or quality or a change in a physical quantity (e.g. temperature, pressure, flow rate, audio, pH value, liquid level, position, acceleration, or speed). Out of scope: highly enriched data, meaning inferred or derived data or data that result from additional investments (including by way of proprietary, complex algorithms). In addition, content that is often covered by intellectual property rights (e.g. textual, audio, or audiovisual content). | Recital 15 |\n<!-- /table -->\n\n<!-- table: t03 -->\n<table>\n<tbody>\n<tr><td>Personal vs non-personal data</td><td>Users are entitled to access all data generated by the connected product or related service, whether personal or non-personal. However, personal data processing is governed by GDPR rules, so the user’s rights provided by the Data Act have to be exercised in compliance with the GDPR. Users that are not data subjects or data holders must have a valid legal basis under Article 6 of the GDPR for processing personal data. Question 26 examines in further detail non-personal data access, use and sharing.</td><td>Recitals 25 and 35</td></tr>\n<tr><td>Trade secrets</td><td>The Data Act does not modify the relevant legal protections for protection of trade secrets. The 2016 Trade Secrets Directive, for example, continues to apply. The Data Act establishes a new mechanism to protect trade secrets. This mechanism is known as the ‘trade secrets handbrake’ and is explored further in Question 20.</td><td>Articles 4(6) and 5(9), Recital 31</td></tr>\n</tbody>\n</table>\n<!-- /table -->\n\n## 5. What level of enrichment transforms raw and pre-processed data into inferred or derived data, excluding it from Chapter II?\n\nChapter II of the Data Act considers the level of enrichment of the data as one of the key factors in the effort to achieve a balanced and fair allocation of data value.\n\nUsers have the right to receive, use, and port data that they have (co-)generated . This right applies to raw and pre-processed data, as well as accompanying metadata. “Metadata” is relevant to understand the conditions (e.g. time, weather, location) under which the data was collected or generated.\n\nAt the same time, the Data Act seeks to preserve incentives to invest in data technologies that, for instance, transform the data, give additional insights, or allow processes to take actions autonomously. To distinguish between raw and pre-processed data on the one hand, and derived or inferred data on the other, Recital 15 mentions notions such as “substantial modification”, “substantial investments in cleaning and transforming the data”, and “proprietary and complex algorithms”.\n\nAs explained in Recital 15, the data in scope – raw and pre-processed data – include measurements of a “physical quantity or quality”. Considering the Data Act’s objective to enable processing of data by a wide array of actors in the data economy, such data should be ‘easily’ usable and understandable by entities other than those who generated it. While all sensor measurements require some level of interpretation before they can be communicated in a digital format, additional investments may be necessary to make the data useable and understandable, such as cleaning, transforming, or reformatting. However, this does not translate into an obligation on the data holder to make substantial investments in these processes. Users, or third parties chosen by the user, are expected to have a reasonable level of technical capability to interpret the data.\n\nAs explained in question 13, processing that is designed to preserve the privacy of the information such as anonymisation or pseudonymisation or processes of encryption should not be considered sufficient for the data to be excluded from scope of Chapter II.\n\n### 5a) How does Chapter II apply to IoT data processed at the edge?\n\n“Edge processing” involves processing data locally on the connected product itself, rather than on a remote server or cloud infrastructure. This approach is typically used for efficiency, reducing latency, and it is often a key feature of privacy-by-design architectures intended to minimise unnecessary data exposure. It is important to emphasise that the Data Act does not seek to override or weaken data protection or privacy-focused design principles. Chapter II of the Data Act requires data holders to make available all “readily available” data \\[i.e. raw or pre-processed data that is stored (even if temporarily), retrievable, or transmitted externally\\] from connected products and related services. If the design of a connected product inherently prevents external data storage or transmission, such data is not considered “readily available” (Recital 20). It is important to ensure that the effects of the Data Act enable users and third parties to benefit from data processed at the edge, where appropriate. By promoting transparency and fairness, the Data Act seeks to avoid situations where data holders retain exclusive benefits from derived insights while limiting user or third-party access to the underlying co-generated data. Obligations apply if raw or pre-processed data was at any point accessible or externally transmittable. If the connected product processes data exclusively locally without any external transmission, Chapter II obligations are in principle not triggered. Where connected products have the technical capacity for data storage or transmission (which may be evidenced by the ability to send processed or derived data via a SIM card or similar communication module to the data holder’s backend server), data holders should consider proportionate, technically feasible, and cost-effective mechanisms to ensure user or third-party access to the raw or pre-processed data. Possible solutions include dual data flows (simultaneous user access/transmission and internal processing), secure temporary buffering, encrypted local storage accessible by users, or time-limited retention period. Recital 22 acknowledges that connected products may be designed to enable data processing by the user or a third party on the connected product itself, on the manufacturer’s system, or within an ICT environment of the user’s or third party’s choice. Chapter II aims to ensure balanced sharing practices without imposing unreasonable technical or economic burdens. Compliance should realistically align with intended connected product design, legal obligations, and the broader objective of promoting a fair and competitive data economy.\n\n6\\. What does the exclusion of “content” from the scope of data under Chapter II mean?\n\nRecital 16 contains two elements that help with the interpretation of “content”. First, it explains that “content” is of textual, audio, or audiovisual nature and often covered by intellectual property rights. Second, it explains that one should distinguish between markets for connected products and related services and markets for unrelated software and content. This suggests that “content” needs to be something akin to copyrightable material, i.e. the result of a creative process (even if the minimum threshold for copyright protection is not met) and typically destined for human appreciation or consumption. The reference to distinct markets indicates that the Data Act does not aim to replace existing legal protections and trading mechanisms for data that represent content. It rather seeks to open up markets for other types of data, such as measurements and non-creative output.\n\nFor example, data holders of digital cameras capable of recording, transmitting, or displaying photographs or video are required to share readily available data, such as usage patterns, battery charging levels, timestamps, location, light levels, and event logs. They are in principle not obliged to share the audiovisual content itself. Similarly, users do not have the right to request access to and use of a motion picture/film displayed on a smart TV. However certain cameras, in combination with the appropriate software, can also act as sophisticated sensors, capable of interpreting pixels in view of recommending action. For instance, cameras in connected vehicles support collision warning and emergency braking systems, and cameras in agricultural machinery assess plant health and provide automated advice for fertilizer or pesticide use. The imagery generated by such cameras is not destined for human consumption and lacks creative elements. As such, this imagery should fall in scope of Chapter II of the Data Act.\n\n7\\. What is a ‘connected product’?\n\nConnected products are items that can generate, obtain, or collect data about their use, performance, or environment and that can communicate this data via a cable-based or wireless connection. This includes communication of data outside the product on an ad hoc basis (e.g. during maintenance operations). Connected products can be found in all areas of the economy and society. They include smart home appliances, consumer electronics, industrial machinery, medical devices, smartphones, and TVs (cf. Recital\n\n14). Products which primarily fulfil the function of storing, processing, or transmitting data (e.g. servers and routers) are outside the scope of the mandatory data-sharing obligations under Chapter II of the Data Act, unless they are owned, rented, or leased by the user. Similarly, the fact that a connected product (e.g. a wagon, airplane, or vehicle) must use certain infrastructure (e.g. railways, airports, or highways) to function does not entitle the user of that connected product to access data generated by, for instance, sensors that are part of that infrastructure. Access would only be granted if the user has received ownership or contractual rights over the sensors embedded in the infrastructure. As an example, if a vehicle receives data from smart infrastructure (e.g. roadside sensors, traffic lights) or records data on road conditions (e.g. fog, ice) and the vehicle data holder has access to the data, then it must be made available to the vehicle user in accordance with the Data Act. The mere fact that a vehicle user is driving on the road does not make them a “user” of the road infrastructure and sensors. Rather, the Data Act ensures user access to data that the vehicle itself receives and processes, not the entire dataset managed by the infrastructure operator. Finally, the Data Act specifies that prototypes are out of scope, as their manufacturing stage has not been completed.\n\n8\\. What determines whether a connected product falls in scope of the Data Act?\n\nA connected product falls within the scope of the Data Act if it has been ‘placed on the Union market’ (Article 2(22)). ‘Placing on the market’ concerns the transfer of ownership, possession, or any other property right between two economic actors that occurs after the manufacturing stage. A connected product is ‘placed on the market’ only once. All subsequent operations are considered as ‘making available on the market’ (Article 2(21)). The concept of placing on the market refers to each individual product, not to a type of product. The requirements laid out in the Data Act are therefore applicable only to individual products that have been placed on the EU market, and not to all products of that type.\n\nThe Commission notes that ’The “Blue Guide” on the implementation of EU product rules’ (2022) served as inspiration for the Data Act’s rules on products and provides comprehensive guidance on this topic. For instance, the Blue Guide identifies situations where a product is not considered to be ‘placed on the market’. These include situations where (i) the product is purchased by a consumer in a third country while they are physically present in that third country and brought by that consumer into the EU for their personal use, and (ii) when the product is manufactured in a Member State with a view to exporting it to a third country.\n\nThe Blue Guide also clarifies that a product brought into the EU is considered to have been placed on the market only if it has been released for free circulation, i.e. when it has the customs status of Union goods. This could for example be relevant for maritime vessels.\n\n## 9. What happens if a connected product that is placed on the EU market generates data when it is used abroad?\n\nIf a connected product is placed on the market in the EU and then used outside the EU, the data generated by that connected product both inside and outside the EU should be made available to the user in accordance with the Data Act.\n\nAs explained in the answer to Question 6, a connected product falls within the scope of the Data Act if it has been placed on the market in the EU. This means that ‘mobile’ connected products (e.g. ships, airplanes, trains, and cars) should be treated in the same manner as other connected products. The mere circulation of a ship, airplane, train, or car on EU territory or in EU waters is not sufficient for a connected product to be considered as having been ‘placed on the EU market’ because there has been no transfer of ownership.\n\nThe rules of the Data Act build on civil law relations of ownership and lease between a person or entity and an object. The fact that connected products such as cars, rail vehicles or planes are registered in a Member State is an indicator that the connected product in question was placed on the EU market.\n\n## 10. What is a ‘related service’?\n\nA related service is a digital service that can be linked to the operation of a connected product and that affects the functionality of this connected product, for instance by transmitting data or commands to it (e.g. an app to adjust the brightness of lights, or to regulate the temperature of a fridge).\n\nTwo basic conditions must be satisfied for a digital service to be considered as a related service:\n\n* there must be a two-way/bidirectional exchange of data between the connected product and the service provider; and\n* the service must affect the connected product’s functions, behaviour, or operation.\n\nDetermining the ’functions’ of a connected product is an ongoing and evolving task. Practice and courts’ interpretation will play an essential role in further delineating whether a digital service is a related service. The following elements could be useful in further narrowing down whether a digital service is a related service:\n\n* user expectations for that product category;\n* marketing accompanying the connected product and/or the digital service;\n* contractual negotiations;\n* the replaceability of the digital service;\n* pre-installation of the digital service on the connected product.\n\nMost but not all digital services that interact with connected products will fall under the category of related services. The following digital services cannot be considered as related services: connectivity, power supply and aftermarket services (e.g. auxiliary consulting, analytics and financial services, and regular repair and maintenance) (cf. Recital 17).\n\nTo offer a related service, a provider must first receive product data. Once a contractual relationship is established between the user and the provider and a related service is rendered that leads to the creation of data, the provider becomes a data holder.\n\n## 11. What happens if a connected product is resold (‘second-hand connected products’)?\n\nWhen it comes to the user’s right to access data generated by the use of a connected product, the Data Act does not distinguish between ‘first-hand’ and ‘second-hand’ connected products.\n\nIf a connected product is being (re)sold, the seller must comply with the ‘transparency obligation’ outlined in Article 3. This requires the seller to provide the necessary information for the future owner to exercise their new data access rights under the Data Act. As a result, the future owner will be informed as to who the data holders are as well as the modalities to accessing and using the generated data. Other sections of this FAQ address related issues, such as how data holders can identify legitimate users.\n\n## 12. How do the obligations under Chapter II of the Data Act relate to mechanisms of conformity assessment or type approval?\n\nThe Data Act applies to all connected products, including those that are subject to specific type approval or conformity assessment regimes (e.g. motor vehicles, aircraft, and medical devices).\n\nThe Data Act does not have specific provisions with respect to mechanisms of conformity assessment, but Data Act obligations apply. As a general rule, therefore, a connected product can only be placed on the market if it complies with all applicable Data Act provisions and if a conformity assessment has been carried out in accordance with applicable legislation. In other words, the specific need for a connected product to undergo a conformity assessment procedure is determined by requirements set in legislation other than the Data Act.\n\n## 13. Does applying privacy-enhancing technologies to achieve anonymisation or pseudonymisation result in derived or inferred data?\n\nNo. As explained in Recital 8, pseudonymisation and encryption play an important role in the implementation of the Data Act. Pseudonymisation or anonymisation of personal data can be achieved by applying privacy enhancing technologies (PETs). It cannot be concluded that data resulting from applying PETs should be treated as inferred or derived data solely due to the application of these technologies. As made clear in Recital 15, the protection to data holders’ inferred or derived data is intended to safeguard “additional investments into assigning values or insights from the data”. PETs are investments that are made for the purpose of being able to analyse data while protecting privacy and not to assign values or derive insights.\n\nAnonymisation or pseudonymisation can be relevant, for instance, when the data holder must respond to a request under Article 4 or 5, and the requesting user is not the data subject, or there are several data subjects who may all be users of the same connected product (e.g. a rented car). In such situations, applying PETs can assist with ensuing compliance with the GDPR.\n\n### 13a) How does anonymisation or severing the link between stored data and its connected product impact compliance with the Data Act?\n\nThe Data Act ensures reasonable, clear and predictable access to data for both users and data holders. While data holders are not required to store data indefinitely (Recital 24), they may be legally required to retain certain data (e.g. for regulatory oversight or product safety). In such cases, PETs can mitigate certain risks, including those related to personal data protection or protection of trade secrets.\n\nHowever, applying PETs should not be used to circumvent data sharing obligations (see Question 13). Applying anonymisation, encryption, or storage techniques does not automatically exempt data holders from their data sharing obligations.\n\nThis means, firstly, that in situations where data are being transferred from the device to the data holder’s backend server, users and third parties of their choice should be given a reasonable chance (see Question 5a, Recital 24) to obtain a copy of the data generated by a connected product before data are anonymised or encrypted.\n\nSecondly, wherever there are reasonable means to relink data to a specific user or connected product without substantial system changes or costs, the data remain ‘readily available’ to be requested under Articles 4 and 5.\n\n## Section on users\n\n## 14. What are ‘users’?\n\nThe general principle in Article 2(12) of the Data Act is that a ‘user’ is a natural or legal person that owns a connected product or to whom temporary rights to use that connected product have been contractually transferred, or that receives a related service.\n\nThis implies the user has to have a stable right on the connected product (e.g. ownership, or a right from a rent or lease contract) that pertains to the object. Such a user has a legal right under the Data Act over the data being generated by the connected product.\n\nWhere the use of a connected product (e.g. use of an airplane as a passenger) is included in a service contract (plane ticket) that does not transfer property-type of rights on the object itself, the person using the connected product (plane passenger) is not a ‘user’ according to the Data Act.\n\n## 15. Does the Data Act apply to users established outside the EU?\n\nAccording to Article 1(3)(b) of the Data Act, a user must be established in the EU. A user may request access to data on the basis of the Data Act, irrespective of whether the data are stored inside or outside the EU.\n\n## 16. Can there be multiple users for a single connected product, and how should their access be governed?\n\nVarious actors may have a legal right based on the contractual arrangements related to the use of a connected product. It is therefore entirely possible for multiple persons to be users of the same connected product. In such a situation, data holders should have mechanisms in place to ensure that each user can access the data to which they are entitled. Users might also conclude separate agreements (e.g. a user-to-user sub-lease of a connected product).\n\nThe following example illustrates, in a non-exhaustive manner, how access to data in a multiple-user scenario could be organised. Other data-sharing arrangements and mechanisms are possible. The Commission’s upcoming model contractual clauses will provide further guidance (cf. Question 71).\n\n### Example:\n\nSara goes on holiday to Portugal for 2 weeks and needs to rent a car. The rental agency, Sunny Wheels, owns a fleet of cars bought from Omni Motors, a large car manufacturer. Keen to exercise her rights under the Data Act, Sara asks Sunny Wheels to provide her with a ‘connected car’.\n\nSunny Wheels has a contract with Omni Motors that ensures that Sunny Wheels and its clients can access the data generated by the car. Omni Motors has put in place a data management system that can simultaneously handle data access requests from the thousands of users of their cars.\n\nSara’s rental agreement contains detailed information on the data generated by the car, including how to access it. The following are two possible ways of organising access to data generated by Sara’s rented car.\n\n* ‘Corporate accounts’: Sunny Wheels has a corporate account with Omni Motors. Sunny Wheels provides Sara with the details needed to log in to Omni Motors’ website and access the rented car’s data.\n* ‘Individual accounts’: Sunny Wheels informs Sara that she has to set up her own account and enter into a separate data-sharing contract with Omni Motors. Sunny Wheels notifies Omni Motors that Sara will be using the car for 2 weeks.\n\nIn both cases, Omni Motors is the data holder; Sunny Wheels is a user because it owns the rented car and can access the data; and Sara is also a user because she has, by virtue of the rental agreement with Sunny Wheels, received temporary rights over the rented car.\n\n## 17. How can I, as a user, access my data?\n\nArticle 3(2) and 3(3) of the Data Act oblige sellers, rentors, lessors, or prospective providers of related services, as the case may be, to provide users with information on the data that their connected product or related service generates. This is known as the ‘transparency obligation’.\n\nAs part of the transparency obligation, users must be informed about how to access the generated data. Data can be made available ‘directly’ (Article 3(1)) or ‘indirectly’ (Article 4(1)). Different configurations are possible (for instance, part of the data could be made available directly, and the rest could be made available indirectly).\n\nDirect access means that the user has the technical means to access, stream or download the data in question without having to request the data holder to do so. For instance, a connected product has a digital interface where the user has control over the access mechanism, controlling the interface and workflows, and where the user can directly extract data from the connected product.\n\nIndirect access means that the connected product or related service is designed in such a way that the user is required to ask the data holder for access (i.e. an approval process). An example would be a web portal where the user can submit a request to access data.\n\nArticle 3 of the Data Act leaves some flexibility (‘where relevant and technically feasible’) to a manufacturer to decide whether or not to design for direct access. This is because not all products (and not all data) are designed in such a way as to make data directly accessible to users. There may be situations where data holders prefer to offer indirect access to the data. The Data Act incentivises data holders to put in place solutions that work best for them when they have to comply with the obligation of making data available to the user.\n\n## 18. How does the Data Act complement the GDPR’s data portability rights?\n\nArticle 1(5) of the Data Act clarifies the relationship between the Data Act and the GDPR, namely that Articles 4 and 5 of the Data Act (right to access and share data from IoT devices) complements Articles 15 and 20 of the GDPR (right to access and port personal data). Recital 35 of the Data Act further clarifies this interaction.\n\nThe Data Act complements the data portability right established under Article 20 of the GDPR. Under the GDPR, only data subjects can exercise such a right and only when the personal data are processed under certain legal bases (consent or contract) and where technically feasible. The Data Act creates an enhanced portability right specifically for the IoT context. Thanks to the Data Act, users (e.g. data subjects and businesses) can access and port any data (both personal and non-personal) generated by the use of a connected product or related service. They can do so independently of the legal basis and, where applicable, in real time. Data subjects are therefore able to move their personal data between controllers (e.g. entities offering repair and maintenance services) more easily.\n\n## 19. In which situations can users monetise their non-personal data?\n\nUsers are free to conclude agreements both with data holders and with third parties. They may compensate the user for gaining access to and using their non-personal data, including for commercial purposes. Recital 25 of the Data Act explains that, in business-to-business relations, an arrangement between the data holder and the user may even include a waiver of the user’s right to use or share data further, provided that such a limitation of the user’s rights is properly compensated.\n\n## 20. What are the options for users, especially consumers, if the right to access and use data is not properly exercised?\n\nThe Data Act ensures a high level of consumer protection. Article 1(9) states that the Data Act complements and is without prejudice to EU consumer legislation, particularly to the Unfair Contract Terms Directive (Directive 93/13/EEC), the Unfair Commercial Practices Directive (2005/29/EC) and the Consumer Rights Directive (2011/83/EU).\n\nSeveral options are therefore available for those who seek to enforce their rights under the Data Act:\n\n* Users (including consumers) can lodge a complaint with the relevant competent authority. If they are unsure about which competent authority to address in their specific case, they should first contact the data coordinator in their Member State (the Commission will make their names and contact details publicly available online.) See Question 64 for more details.\n* Users (including consumers) can initiate legal proceedings.\n* Users who are consumers can use the instruments available to them under EU consumer protection legislation. They can in particular lodge a complaint with the European Consumer Centres Network in\n* the event that the data holder is established in a Member State other than that in which the consumer resides.\n* Users who are data subjects can contact the relevant DPA regarding all issues concerning the processing of personal data.\n\n## Section on data holders\n\n## 21. Is a manufacturer always a data holder?\n\nEven though manufacturers will typically be data holders, this is not always the case. The Data Act allows an entity to ’outsource’ the role of ‘data holder’. For example, a manufacturer may contract out to another entity the role of ‘data holder’ for all or part of the manufacturer’s connected products.\n\nIn addition, a data holder who is not a manufacturer might be a company that provides a related service linked to a connected product. This means that the business offering the related service might be a data holder and be different from the company that actually made the connected product.\n\nDetermining who the data holder is does not depend on who produced the hardware or software, but on who controls access to the readily available data. See the flowchart below for an example of role distribution.\n\nThe flowchart illustrates a situation where a user enters into two contracts (e.g. for the sale of the connected product and for the provision of the related service) that establish a legal relationship (in red) between the user and three separate data holders (circled in blue). The user must always be informed of the identity of the data holder(s) before signing such contracts.\n\n1\\. The manufacturer is interested in receiving and using the data, and therefore establishes itself as a data holder in the sales contract, in line with Articles 3(2) and 4(13) of the Data Act.\n\n2\\. Both component supplier A and component supplier B deliver data-generating components. However, only supplier A receives data directly from the component via an embedded SIM card and is identified as a data holder in the pre-contractual information given in accordance with article 3(2) of the Data Act. If supplier A desires to use that data, this needs to happen on the basis of an agreement with the user in accordance with Article 4(13). At the point of sale/rent/lease, the manufacturer or distributor facilitates this agreement from which supplier A is notified of the identity of the user.\n\nSupplier B receives its component data from the manufacturer in accordance with their individual agreement which is subject to the user’s approval. In this scenario, supplier A is a data holder and supplier B is a third party.\n\n3\\. Whenever a user also acquires a related service linked to the connected product, the related service provider must necessarily enter into a contract with the user, in line with Articles 3(3) and 4(13) of the Data Act. The related service provider therefore becomes a data holder.\n\nIn order for there to be an obligation on a data holder under Chapter II of the Data Act, there must always be a user. It is nevertheless possible under the Data Act for a person to be a user without there being a data holder. This situation could occur, for example, if a user acquires a connected product where the data are stored directly on the device or transferred from the device to the user’s computer, and the manufacturer does not have access to any of the data. In this scenario there is no data holder, since only the user has access to the data.\n\n## 22. Does Article 3(1) oblige manufacturers of connected products to design or redesign their connected products so that users can access the data directly?\n\nNo. Article 3(1) of the Data Act does not oblige manufacturers to grant direct access to data in all situations and for all connected products. Data should be ‘directly accessible’ to the user ’where relevant and technically feasible’.\n\nThe formulation ‘where relevant and technically feasible’ is meant to reinforce the manufacturers’ discretion to decide whether to design a connected product in a way that provides users with ‘uncontrolled’ access (i.e. without any intervention by any other party) or in a way that provides access with additional controls (typically via a remote server). For this purpose, a manufacturer may assess, for example, whether direct access is technically possible; the costs of potential technical modifications; and the difficulty of protecting trade secrets or IP, or of ensuring the connected product’s security. One could also consider whether direct access is relevant in a specific scenario from the perspective of the connected product, user, or data holder. Based on this assessment, manufacturers may choose to design the connected product in such a way that all or part of the product data is directly accessible or may enable only indirect access. If agreed upon, data holders can also access product data made directly accessible to a user.\n\nData are ‘directly accessible’ when:\n\n* The user is able to access the data without the intervention of any other party, notably the data holder (this is an alternative to making requests under Articles 4 and 5, which do require data holder intervention).\n* The user has the technical means to stream or download the data as a result of the design of the connected product. Recital 22 explains that the location where the data are stored is irrelevant: data can be ‘directly accessible’ from a storage point on the device itself or from a remote server under the control of the manufacturer or a data holder.\n\nPut simply, for data to be ‘directly accessible’, the user must therefore be able to access them without the involvement of the data holder, regardless of where the data are stored. Even if there is direct access and a remote server, the data holder is obliged to provide the means (i.e. appropriate interfaces, such as an API) to allow the user to easily access the relevant data (cf. Recital 35 of the Data Act, which compares Article 3(1) of the Data Act with Article 20 of the GDPR).\n\nBy the date of entry into application of the Data Act (12 September 2025), products already on the market and new products (when placed on the market) must allow for data to be accessed by the user. By this date, manufacturers have to decide whether such access will be made directly or indirectly (cf. Article 4(1)) of the Data Act. Companies will find practical ways to incentivise the use of the solution that works best for them. Sectoral legislation can be more specific.\n\n### 22a) What technical and practical requirements must data holders meet concerning criteria such as data format, quality and latency?\n\nThe Data Act creates strong incentives and requirements for greater and better data availability in the EU. To comply with Articles 3(1), 4(1), and 5(1) of the Data Act, data holders must meet several technical and practical requirements, including:\n\n* Format: Data holders must make data available “in a comprehensive, structured, commonly used and machine-readable format” to ensure interoperability and facilitate reuse. Modelled after GDPR Art 20 (Data portability), this requirement establishes the minimum conditions for data portability. Data holders, as the entities responsible for the design of the data at the source, must provide data in an interoperable format (e.g. XML, JSON, CSV). Formats subject to licensing constraints are not considered “commonly used”. While industry is encouraged to develop common formats for certain data, no obligation to develop those flows from the Data Act.\n* Quality: The data holder is required to share data “of the same quality”, i.e. as accurate, complete, reliable, relevant and up-to-date (cf. Recital 30, as it makes available to itself. This implies that the data should be shared in a format and quality consistent with how it would be shared with another subsidiary within the same corporate group or in a manner that aligns with industry standards or practices within a specific industry.\n* Timeliness: Articles 4(1) and 5(1) require data holders to provide data “without undue delay” upon user or third-party request. This means data should be made available in a prompt, timely and responsive manner. Data holders must proactively implement solutions such as automation, streamlined and structured request procedures, self-service portals, and clear organisation policies to minimise administrative bottlenecks and reduce reliance on manual intervention (c.f. Recital 21). Delays can be justified based on security, technical, or legal constraints, and must remain proportionate to the request.\n* Latency: The requirement to provide data “where relevant and technically feasible, continuously and in real-time” applies to scenarios where low latency is beneficial, such as IoT systems, connected mobility, and industrial monitoring. Unlike Article 20 GDPR, the Data Act ensures that access is not hindered by technical obstacles (c.f. Recital 35). Feasibility must therefore be assessed objectively, based on industry standards and best practices. Data holders should proactively implement solutions such as APIs (automated data retrieval) and event architectures (software design that trigger data updates) to ensure real-time or near instantaneous access wherever feasible.\n* Convenience: Data holders must grant access to data “easily”. This requires implementing mechanisms that streamline and simplify data sharing and avoid unnecessary complexities or barriers. Where access is limited to on-site or specific tools are required, it must not involve unreasonable complications for users or third parties, such as restrictive locations, time slots, or disproportionate costs.\n* Security: Data must be made available “securely”, ensuring protection against unauthorised access or use. Such mechanisms should align with industry standards and relevant legal frameworks, such as those related to cybersecurity.\n\n## 23. Does the new data access right affect the protection of trade secrets?\n\nThe Data Act provides a framework that balances data sharing with the need to preserve the protected nature of the data (including with respect to the protection of trade secrets, whose confidentiality continues to be ensured). The Data Act does not modify the applicable legal protections (including the 2016 Trade Secrets Directive, which already provides a legal framework for the protection of trade secrets).\n\nHowever, a data holder can unilaterally determine which data are trade secrets, so the claim that certain data are trade secrets is not enough to prevent the exercise of the data access rights provided by the Data Act. This does not mean that the Data Act leads to the forfeiture of trade secret protection. Rather, it carefully balances the need to prevent illegitimate restrictions on the user’s new data access rights against the need to uphold the legal protection provided to trade secrets.\n\nThe data holder therefore has the right, prior to disclosure, to require users and third parties to preserve the confidentiality and secrecy of the trade secret encumbered data by agreeing to and implementing safeguards necessary to that end. As an additional layer of protection, the Data Act introduces a new mechanism (commonly known as the ‘trade secrets handbrake’) that frames the conditions under which a data holder can withhold, suspend or, exceptionally, refuse to share data.\n\nHow can data holders handle trade secrets and activate the ‘trade secrets handbrake’?\n\nWhen a data holder receives a request to access data, it must identify the trade secrets that need to be shared and agree with the user/third party on the necessary measures to preserve their confidentiality (Articles 4(6) and 5(7) of the Data Act). These safeguards need to be in place prior to the sharing of data. Possible measures could include model contractual terms, confidentiality agreements, strict access protocols, technical standards and the application of codes of conduct.\n\nThe data holder may withhold or suspend the sharing of trade secrets if there is no agreement, if the user or third party does not implement the agreed measures, or if the confidentiality of the trade secrets is undermined (Articles 4(7) and 5(10) of the Data Act).\n\nIn exceptional circumstances, the data holder may refuse to share trade secrets if it can demonstrate, on the basis of objective evidence, that it is highly likely that serious economic damage would result from the disclosure of trade secrets (Articles 4(8) and 5(11) of the Data Act). ‘Serious economic damage’ means serious and irreparable economic loss. Such decisions need to be made on a case-by-case basis.\n\nIf the data holder considers that it must withhold, suspend, or refuse to share data, it must notify the competent authority of the respective Member State, and communicate the reasoning behind the decision to the user or third party without undue delay.\n\nThe user or third party can seek redress and challenge the data holder’s decision before a court or tribunal of a Member State or agree with the data holder to refer the matter to a dispute settlement body. The user or third party can also lodge a complaint with the competent authority. The competent authority should, without undue delay, decide whether and under which conditions data sharing should start or resume (Articles 4(9) and 5(12) of the Data Act).\n\n## 24. Can the protections that Article 4, 5 and 6 provide for also apply in relation to data made directly available in the sense of Article 3(1)?\n\nDifferent from the rights under Article 4 and 5, Article 3 does not provide for any statutory law protections of the manufacturer when making data directly available from the connected product. The Data Act allows manufacturers to choose, when designing a connected product (or a related service), whether readily available data can be made accessible by the user directly, indirectly or a combination of both (see Question 14). When making this choice, the protection of trade secrets or the security of the connected product can be a consideration, especially since, in a direct access situation, the manufacturer will be less involved (or not at all) than in an indirect access situation in how a user will exercise their access rights.\n\nHowever, direct access does not mean that it has to be unconditional and can be made subject to contractual conditions that preserve the interests of the manufacturer or the data holder. The manufacturer could e.g. contractually oblige the user to protect certain data that are made directly accessible, in order to ensure the protection of trade secrets, or prohibit certain use cases such as manufacturing of a competing product. Disabling direct access with the Data Act coming into effect based on the considerations in Articles 4(7), 4(8), 5(10) and 5(11) (referred to as the ‘trade secrets handbrake') is not prohibited by the Data Act but is a matter to be negotiated on a contractual basis. Any such contractual conditions cannot undermine the user’s rights, as per Article 7(2) of the Data Act.\n\n## 25. Does a data holder have to share data if there are safety/security concerns?\n\nPursuant to Article 4(2) of the Data Act, users and data holders can agree to restrict or refuse to share data if there is a risk that the security requirements of the connected product could be undermined, resulting in serious adverse effects to the health, safety or security of people. Such requirements must be laid down in EU or national law. Sectoral authorities may provide users and data holders with technical expertise in order to determine whether restrictions are necessary or warranted.\n\nThis mechanism (i.e. the possibility of restricting or prohibiting data access on the basis of safety or security considerations), is referred to as the ‘safety and security handbrake’.\n\nIf, under the conditions explained above, the data holder intends to activate this handbrake, it must notify the competent authority of the respective Member State. Moreover, users may challenge the data holder’s refusal to share data before the competent authorities, courts, or a dispute settlement body.\n\n### 25a) What GDPR legal bases could the data holder rely on when replying to a request for data?\n\nDifferent scenarios and different processing operations need to be distinguished.\n\n* The user is the data subject in relation to the data in question\n\nArticle 1(5) specifies that Data Act complements the rights of access by data subjects and rights to data portability under Articles 15 and 20 of Regulation (EU) 2016/679. This means that where the user is the data subject and requests the data under Article 4 of the Data Act for themselves, the situation is comparable to a data subject access request under Article 15 GDPR. Where the user asks data to be ported to a third party under Article 5 of the Data Act, the situation is comparable with Article 20 of the GDPR. The fact that the request to port the data is received via another actor does not change that assessment.\n\n* The user is not the data subject in relation to the data in question\n\nAs specified in Recital 7, where the user is not the data subject, the Data Act was not intended as a legal basis for providing access or for making personal data available to a third party in the sense of Article 6(1) GDPR, including 6(1)(c). The intention was to protect data subjects in multi-user situations (either multiple users at the same level – co-ownership of a connected product – or layered user situations with owners and lessees).\n\nThis means that the data holder will have to make an assessment on an appropriate legal basis for providing access or for making personal data available – or alternatively it will have to provide anonymised data. Depending on the circumstances of the request, the controller could explore whether providing the data is necessary for the performance of the contract with the data subject or service legitimate interest of data holder or a third party.\n\n### 25b) Should the data holder verify that the user or third party has a valid legal basis under the GDPR before transmitting the data?\n\nIn situation when data is shared between two controllers, each controllers must be able to demonstrate their own compliance with the GDPR in accordance with principle of accountability. Each controller must ensure that they have sufficient information to do so. The controller should cooperate to share strictly necessary information to allow to demonstrate the compliance by each of them.\n\n## 26. A non-compete clause for connected products has been introduced. Does this also apply to related services?\n\nNo. As explained in its Recital 32, a key objective of the Data Act is to allow service providers to have access to new data and compete on an equal footing with comparable services offered by manufacturers. The prohibition on developing competing related services could have a discouraging effect on innovation and the provision of other services (not necessarily ‘related services’).\n\nAs a result of the limitation of the non-compete clause to connected products only, businesses and consumers will see a reduction in the cost of switching to alternative services. They will also benefit from more competition for value-added services (e.g. predictive maintenance), which depend on access to such data; and be able to make more informed consumer decisions (e.g. buying more sustainable products and services).\n\n## 27. How are the interests of data holders protected?\n\nThe interests of data holders are protected in various ways. The following are four examples.\n\ni. The Data Act limits the scope of data which is subject to mandatory sharing obligations under Chapter II to raw and pre-processed data. This minimises adverse effects on data-related investments and on the protection of trade secrets or IPR.\n\nii. Specific provisions address the situation where data requested by the user are considered trade secrets by the data holder/trade secrets holder or where the use of data is linked to considerable safety risks.\n\niii. Data access from connected products under the Data Act cannot be used to develop a competing product.\n\niv. The data holder is able to request compensation from third parties (when prompted by the user to share data), or from data recipients (when there is a legal data-sharing obligation).\n\n## 28. Does the Data Act apply to manufacturers of connected products and providers of related services that are established outside the EU?\n\nYes. The Data Act does not require the manufacturer or related service provider to be established in the EU. The Data Act establishes a right for users in the EU to access, use and share the readily available data they are entitled to. All connected products and related services placed in the EU must therefore be designed in such a way that this right can be exercised.\n\nAll legal requirements must be met when the connected product is placed on the EU market or when the related service is offered. The related service is linked to the connected product’s functioning, so the place of establishment of the provider of the related service is not a factor in determining whether they fall within the scope of the Data Act.\n\n## 29. Are there any limitations on the data holder’s use of the data generated by the user?\n\nWhile the GDPR governs processing of personal data, Article 4(13) and (14) of the Data Act cover the use of non-personal data by the data holder.\n\nArticle 4(13) states that the data holder can use the non-personal data for any purpose, provided that (i) this is agreed with the user; and (ii) the data holder does not derive insights about the economic situation, assets and production methods of the user in any other manner that could undermine the commercial position of that user on the markets on which the user is active.\n\nRecital 25 further explains that any contractual term regarding the data holder’s intended use of data should be transparent to the user. Possible purposes of data usage by the data holder include the improving of the functioning of the connected product or related service or making aggregated data available to a third party, provided that these data do not allow identification of granular data. The user is the sole source of access to granular non-personal data from the connected product or related service.\n\nArticle 4(14) addresses the specific aspect of data usage by the data holder that involves the sharing of non-personal data with third parties, which should only take place if contractually agreed with the user (in line with Article 4(13)).\n\n## 30. How would a data holder be able to verify a legitimate user?\n\nArticle 4(5) of the Data Act states that, for the purpose of verifying a person as a possible user, ‘a data holder shall not require that person to provide any information beyond what is necessary’. Recital 29 explains that ‘Data holders may require appropriate user identification to verify a user’s entitlement to access the data.’\n\nThe ‘information’ that a user may be requested to provide must therefore conclusively demonstrate that a person is a user (i.e. someone who ‘owns a connected product or to whom temporary rights to use that connected product have been contractually transferred, or that receives related services’ (Article 2(12) of the Data Act). Given users’ vested interest in accessing the data, it is reasonable to expect that they will try to properly identify themselves.\n\nRecital 21 provides guidance on how a data holder can verify users. According to this recital, access should be granted to the user:\n\non the basis of simple request mechanism granting automatic execution and not requiring examination or clearance by the manufacturer or data holder. (...) Where automated execution of the data access request is not possible, for example via a user account or accompanying mobile application provided with the connected product or related service, the manufacturer should inform the user as to how the data may be accessed.\n\nData holders are therefore free to set up the specific process to identify users but must still comply with Article 4(4) and (5) of the Data Act. Data holders can assess, for instance, (i) what best fits the type of product; (ii) the type of user (consumer vs industrial); (iii) the number of likely users (single owner of an elevator vs multiple users in car rental); (iv) the expected frequency of data access requests; (v) presence of specific mechanisms of demonstrating ownership (e.g. car holder registration); (vi) the cost of setting up differentiated user accounts; and (vii) the ease of use of such accounts for the actual consumers. Where applicable, solutions such as the EU Digital Identity Wallet could be envisaged.\n\nWith respect to personal data, Recital 34 of the Data Act explains that ‘Personal data may only be requested by a controller or a data subject (...) Where the user is not the data subject but an enterprise, including a sole trader, and not in cases of shared household use of the connected product, the user is considered to be a controller.’\n\nRecital 34 recalls that users that are data subjects can always access personal data concerning themselves. It also clarifies that users who are not data subjects are controllers under the GDPR and must comply with their obligations under the GDPR when requesting personal data from IoT devices.\n\n## 31. Does a data holder still need to share data with a third party upon request of the user where it has granted direct access to the user?\n\nYes. Users also have a right under Article 5 of the Data Act to request the data holder to transfer data to a third party when the user has direct access to the data in the sense of Article 3(1). This pre-supposes that there is a data holder with data readily available to them. Article 5 is not conditional upon the type of access that the user has.\n\n## 32. Can users request access to historical data that a data holder might be storing (e.g. when buying a second-hand sensor/machine)?\n\nThe Data Act can be read as giving users the right to access and port readily available data generated by the use of a connected object, including data generated by other users before them. Such subsequent users might have a legitimate interest in such data (e.g. in respect of updates or incidents), while keeping in mind the ‘reasonable retention policy’ referred to in Recital 24 of the Data Act.\n\nHowever, the rights of previous users and other applicable law (e.g. with respect to their personal data or commercially confidential information, including their request for data to be deleted) would have to be respected. In that sense, the granularity or scope of ‘historical data’ would be limited in order to preserve the rights and interests of others.\n\n## 33. Can users request that data holders delete their non-personal data before selling a product to another user?\n\nThe Data Act does not establish a ‘right to erasure’ for non-personal data, similar to the GDPR.\n\nThe possibility to erase data may be contractually agreed upon. Such data are referred to as ‘user’s removable data’ in the Model Contractual Terms (MCTs) to be recommended by the Commission. For other types of data, the data holder may decide that erasure is not permitted, particularly where retaining historical data serves the interests of future users (e.g. for servicing and repair purposes; see Question 32). These are referred to in the MCTs as ‘residual data’, that is other data than user’s removable or always removable data. Product-specific legislation may also provide differently and prohibit the erasure of certain data (for example, when a certain type of data is meant to ‘follow’ the product for safety reasons).\n\nIf there is a contractual agreement for users to erase data, information on how data can be erased is one of the requirements pursuant to Article 3(2)(d) of the Data Act. Recital 21 gives guidance on account solutions in the case of multiple usership, where users should be allowed to delete the non-personal data related to their account.\n\nAdditionally, two subsequent users could contractually agree on the erasure or non-erasure of (certain) data before the handover of a connected product.\n\n## 34. Can a company be both a user and a data holder at the same time?\n\nA company can be both a user and a data holder with respect to different connected products or related services. For example, a manufacturing company can be both a ‘user’ of the robots used in its factory, and a ‘data holder’ for the connected products it manufactures.\n\nA company cannot simultaneously be a user and a data holder for the same data, and, a user sharing data with a third party should not be considered a data holder for that third party.\n\nThe specific exception referred to in Recital 34 of the Data Act refers to a possible multi-user scenario where two companies (a data holder and the initial user who is not a data subject) decide to act as joint controllers for additional users (who are the data subjects). This allocation of responsibilities could result in the initial user becoming a data holder for those additional users.\n\n### 34a) After the Data Act enters into application, can data holders continue to use data generated by connected products placed on the market before the application date?\n\nAs stated in Article 4(13), data holders will need to have a contract in place with users to use readily available data from 12 September 2025. This obligation applies to connected products placed on the market both before and after 12 September 2025.\n\nData holders who can identify the users of their connected products placed on the market before 12 September 2025 therefore need to either:\n\n* conclude a contract that secures the user’s agreement to their use of the data, if they were doing so without a contractual basis, or\n* check if an existing contract (e.g. a sales contract, a contract for the provision of related services or any other contract) needs to be adapted to include the user’s agreement to their use of the data.\n\nThere will, however, be data holders that cannot identify the user of their connected product despite having made reasonable efforts (e.g. a notice published on the website of the data holder/manufacturer) and the Data Act does not provide any express provisions for these situations. Such data holders should still be able to continue using the data generated by the product after 12 September 2025, since they designed and sold the product with a legitimate expectation of being able to collect and use this data. Furthermore, without being able to identify the user, this data holder would not be in a situation where they could use the data to derive insights about the user’s economic situation, assets and production methods, as prohibited by Article 4(13).\n\nHowever, should such data holders become aware of any users at some point (for example following a user’s request for access to their data), they must conclude a contract with the users to obtain their agreement to the continued use of the data by the data holder.\n\n## Section on third parties\n\n## 35. What can a third party do with the data they receive from a user/data holder in the context of Chapter II?\n\nThe general principle, according to Article 6(1) of the Data Act, is that a third party can use the data for purposes that were agreed with the user (usually in the context of providing a service to the user). Article 6(2) includes a closed list of actions which are prohibited for the third party. This list includes using data to develop a competing product and sharing the data with a gatekeeper (as defined under the Digital Markets Act).\n\n## 36. Can users oblige data holders to share data with Digital Markets Act gatekeepers?\n\nNo. DMA gatekeepers, which are defined as undertakings that provide core platform services under the Digital Markets Act (DMA), typically have no difficulties in gaining access to large amounts of data. Data already tend to gravitate towards these large undertakings due to their gateway position, control over platform ecosystems and superior bargaining power. Requiring mandatory data sharing for IoT data with DMA gatekeepers would therefore be unfair to those who must comply, and unnecessary given the goals of the Data Act. DMA gatekeepers cannot therefore be third parties in the sense of the new IoT data access right established under the Data Act.\n\nThis does not mean that DMA gatekeepers are entirely excluded from the IoT (data) market. DMA gatekeepers are prohibited from relying on the specific mandatory data sharing mechanisms created by Articles 4 and 5 of the Data Act but all other mechanisms (including regarding voluntary data sharing arrangements) remain unaffected.\n\n## 37. Can someone established in a third country receive data on the basis of the data-sharing obligations under Chapter II?\n\nNo. The scope of the Chapter II data-sharing obligation on data holders is limited to entities and persons, including consumers, in the Union (cf. Articles 1(3)(b), 1(3)(d) and 2(14) of the Data Act). Giving data access to operators that do not have a presence in the EU cannot be justified based on the Data Act.\n\nIrrespective of its place of establishment, a data holder has a legal obligation to share data with an EU-based entity or person at the request of an EU user. A user may ask a data holder to share data with an entity or person that is not established in the EU, but the data holder is not obliged to grant that access.\n\n### Fair, reasonable, and non-discriminatory (FRAND) conditions, compensation and dispute resolution\n\n## 38. Is it possible to differentiate between the data recipients and apply different licensing conditions?\n\nArticle 8(3) of the Data Act implements the general principle that it is not admissible to differentiate between entities that are in the same situation (non-discrimination). Analysing whether two recipients are in a comparable category must be done on a case-by-case basis.\n\n## 39. Is there an upper limit to reasonable compensation?\n\nNo. There is no upper (nor lower) limit to compensation as such. Rather, the Data Act imposes certain transparency requirements in order to ensure that calculation of compensation is based on certain objective criteria (e.g. costs incurred, or the volume of data being made available). Reasonable compensation cannot include a profit margin if the recipient is an SME or a non-profit research organisation.\n\n## 40. Who can rely on the dispute settlement mechanism established by the Data Act and under which conditions?\n\nUsers, data holders and data recipients can refer their disputes to the dispute settlement bodies designated by Member States in accordance with the Data Act, which can help them to conclude a contract on data sharing or settle disputes arising after the conclusion of the contract. These dispute settlement bodies will be competent (i) for disputes relating to the ‘safety and security handbrake’ and to the ‘trade secrets handbrake’ (see Questions 20, 21 and 22) in business-to-consumers and in business-to-business relations, (ii) for disputes relating to the fair, reasonable and non-discriminatory terms and conditions for, and transparent manner of, making data available in business-to-business relations, where the data holder is legally obliged to make data available (including in accordance with the Data Act) and (iii) for dispute relating to the fairness of contractual terms related to data access and use in business-to-business relations.\n\nThe rules on dispute settlement are applicable to disputes relating to the fair, reasonable and non-discriminatory terms and conditions for (and transparent manner of) making data available in business-to-business relations, where the obligation to share data is enshrined in law (including the Data Act itself). The dispute settlement rules can also be used by customers and providers of data processing services to settle disputes relating to breaches of the provisions of the Data Act dealing with such services.\n\nA decision to have recourse to a dispute settlement body is voluntary and should be agreed by both parties to the dispute. In addition, a decision of a dispute settlement body binds the parties only if they have explicitly consented to its binding nature prior to the start of the dispute settlement proceedings. A dispute settlement body may not be tasked with resolving a dispute if it has already been brought before another dispute settlement body or before a court or tribunal of a Member State.\n\n### Unfairness in business-to-business data-sharing contracts\n\n## 41. What special provisions exist to help SMEs, given that they are often in a weaker negotiating position?\n\nChapter IV of the Data Act does not specifically address SMEs, but the prohibition on unfair contractual terms is expected to benefit businesses upon which a contractual term was unilaterally imposed. Given that SMEs often have limited market power and weaker negotiating positions, Chapter IV will therefore provide particular support to them, especially when they seek access to data held by larger companies. If an SME needs to submit a complaint or raise a concern, it can, for instance, contact the data coordinator in its Member State (see the answer to Question 64).\n\nThe European Commission will recommend model contractual terms for data sharing that reflect the rights and obligations of the Data Act and that will be intended to help SMEs negotiate better. These models will be voluntary. The Commission should have adopted them by the time the Data Act starts to apply.\n\n## 42. I think that the data-sharing contractual terms in my contract are unfair. What can I do?\n\nFirstly, it should be ascertained that the terms in question are covered by Article 13 of the Data Act:\n\na) they concern access to and the use of data or liability and remedies for the breach or termination of data-related obligations;\n\nb) they do not reflect mandatory provisions of EU law, or provisions of EU law that would apply if the contractual terms did not regulate the matter;\n\nc) they are unilaterally imposed; and\n\nd) both parties to the contract are enterprises.\n\nSecondly, it should be assessed whether the terms grossly deviate from good commercial practice in data access and use, contrary to good faith and fair dealing. A non-exclusive list of such terms is provided in Article 13(4) of the Data Act. Such terms should always be considered unfair.\n\nThirdly, the terms in question might fall into a different category: terms which are only presumed to be unfair. The party imposing them can rebut such a presumption by presenting evidence to the contrary. Such terms are listed in Article 13(5).\n\nIf the conclusion of the above assessment confirms that a term in a contract is unfair or presumed to be unfair, the party imposing such a term should be asked to withdraw it from the contract. In any case, a term found to be unfair will not be binding on the party on which it is imposed. The remaining contract terms will continue to be binding if the unfair term can be separated from them (i.e. it is sufficiently stand-alone). If the imposing party disputes the outcome of the assessment and does not withdraw the term, the matter can be brought in front of a competent authority, the courts or (if the other party agrees) a dispute settlement body.\n\n42a) To which extent does the unfairness control in Article 13 of the Data Act apply to agreements or contracts that are primarily on another subject, but which contain provisions on data sharing?\n\nArticle 13 (1), Chapter IV on unfair contractual terms applies to any contractual term ‘concerning access to and the use of data or liability and remedies for the breach of data related obligations’ in contracts concluded between enterprises. Recital 60 of the Data Act clarifies that ‘the rules on unfair contractual terms should apply only to those elements of a contract that are related to making data available, that is contractual terms concerning access to and use of the data as well as liability or remedies for breach or termination of data related obligations. Other parts of the same contract, unrelated to making data available,’ should not be subject to Chapter IV. The Data Act therefore does not require that data be the main or unique subject of the contract where the term is stipulated, for such term to be covered by the unfairness control. As a consequence, where a single contract between the same parties includes elements related to data and other elements, the unfairness control would only apply to the terms that concern either a) data access and use or b) liability and remedies for the breach of data related obligations. Such contractual terms could be, for example, about data access modalities, purposes for its use, how the data is protected, as well as remedies and liability for breaches of such terms.\n\nSuch terms can be commonly found in contracts about, for example, sale of a connected product, logistics, advertising, loans, investment consulting, management advice, cloud computing services etc. For example, in a contract for a bank loan to a business, where data sharing is needed for the fulfilment of the agreement, Chapter IV of the Data Act applies to the clauses related to the sharing of the client’s data with the bank.\n\nThis means that Chapter IV does not apply to contractual terms that have another purpose, for instance the terms that deal with product guarantees, the characteristics or technicalities of the provision of cloud services, the insurance conditions, etc.\n\nSometimes though, there are parts of the agreement (such as a general section on remedies or the terms dealing with the duration of the contract) that apply to all contractual obligations. Chapter IV of the Data Act applies to such clauses to the extent that data access and use or data-related obligations are concerned. For example, the unfairness control would apply to the general terms and conditions about liability and remedies, if these cover breach of data related obligations. However, the unfairness control provided by Article 13 would not apply to the clauses regulating the terms for the bank loan, as explained above.\n\n### 42b) Does Chapter IV of the Data Act apply to contracts concluded before the Data Act started to apply?\n\nAs a general rule, the Data Act applies from 12 September 2025. In accordance with the exception in Article 50, the unfairness control (Chapter IV Article 13) only applies:\n\n* to contracts concluded after 12 September 2025, and\n* starting from 12 September 2027 to contracts concluded on or before 12 September 2025, if these contracts are of indefinite duration or these contracts are due to expire at least 10 years from 11 January 2024.\n\nThe second situation is meant to give time to the parties to renegotiate such contracts and remove any provisions that might be considered unfair under Article 13.\n\n### Business-to-government data access\n\n## 43. What qualifies as ‘mitigation of or recovery from’ a public emergency?\n\nThe Data Act does not clarify these concepts, but Article 15 clearly distinguishes them from ‘public emergency response’ (Article 15(1)(a)), which suggests that they are distinct from the actual occurrence of a public emergency, in particular in terms of timing. The factors to be considered when identifying an activity as ‘mitigation or recovery from a public emergency’ are likely to be laid down in national law, because mitigation or recovery from a public emergency must be designated as a “specific task carried out in the public interest, that has been explicitly provided for by law” in order to be relevant for Chapter V requests.\n\n## 44. What does the term ‘equivalent conditions’ mean in the context of Article 15(1)(a)?\n\n‘Under equivalent conditions’ could be read in the context of this Article as a rule requiring a public sector body wishing to use its rights under Chapter V of the Data Act to first verify whether the same data could not be obtained elsewhere, while at the same time requiring a comparable amount of effort. The last sentence of Recital 64 provides some examples in this regard.\n\n## 45. Could the new rights under the Data Act endanger data holders’ existing business models because a public sector body could request the data instead of purchasing it?\n\nThere is little risk of current business models being seriously affected. This is because - in all situations other than an exceptional need for data to directly respond to a public emergency, and where an option of purchasing non-personal data is available to the public body - the data will need to be purchased at the market price (note the exception in Article 15(3) of the Data Act). A public sector body can rely on the process outlined in Article 15(1)(b) only if it has been unable to obtain the non-personal data - either because the data cannot be purchased or because the public sector body made an unsuccessful attempt to buy it at the market rate (e.g. via procurement).\n\n## 46. How can a data holder verify that a Chapter V request is justified and lawful?\n\nData holders should verify the following:\n\n* Is the requesting entity a public sector body of a Member State or one of the EU-level entities listed in Article 17(1) of the Data Act?\n* Is there sufficient and clear justification regarding the choice of the data holder, the scope of specific data, the existence of an exceptional need, the duration of use, the nature of the public task and the purpose for requesting the data (as per Article 17(1)(a)-(j))?\n* Is the request proportionate (e.g. in terms of data scope and granularity) to the exceptional need described?\n* If personal data are requested – are the necessary conditions described in Articles - 17(1)(g) and 17(2)(e) fulfilled?\n* Have all the relevant authorities been notified (e.g. if the request is made by a public sector body from a different Member State)?\n* In the case of justified doubts as to the conditions listed above, the data holder should be able to ask for clarification and, ultimately, refuse the request or ask for its modification. In such a case, the requesting entity may ask the competent authority to settle the matter.\n\n47\\. Can a public body in one country request data from a data holder in a different country? Are the rights of the data holder fully protected in such a case?\n\nYes. The Data Act includes the right for a public sector body to request data from data holders (companies) located in a Member State that is not the Member State of the requesting public sector body. This right may be important in the case of cross-border emergencies (e.g. natural disasters).\n\nAs always, the request needs to fulfil all the requirements under Article 17 of the Data Act. This means that it must be formulated in clear, concise, and plain language that the data holder can understand.\n\nArticle 22 of the Data Act contains a specific procedure for cross-border requests to ensure the data holder’s protection. Such requests are always notified to the competent authority of the data holder’s Member State for ex ante examination.\n\n## 48. Once data are made available following a request, do they become public sector information? Can the public sector body use them in any way it sees fit?\n\nNo. The requested data do not become public sector information that has to be made openly re-usable under Directive (EU) 2019/1024 (the Open Data Directive). In principle, the data can only be used for the specific purpose set out in the request and only by the requesting body. However, the requesting body may require the involvement of another public sector body or third party in carrying out a public sector task for which the data were requested. If so, the relevant public body or third party should already be identified in the request - as per Article 17(1)(f) of the Data Act.\n\nArticle 21 describes two situations in which the requested data can be shared onwards: (i) for carrying out scientific research or analytics compatible with the purpose for which the data were requested and (ii) for the production of official statistics. The data holder should be notified if such a transfer takes place, so that they have the opportunity to lodge a complaint with the competent authority.\n\nData that are shared under the mechanism described in Article 21 must be deleted no later than 6 months after the fulfilment of the original purpose for which the data had been requested.\n\n## 49. Can a request under Chapter V be made repetitively or simultaneously by different public sector bodies?\n\nA data holder cannot be expected to respond to repetitive requests for the same data. Public sector bodies should first check if the data are already available within the public sector. The Data Act therefore empowers a data holder to refuse a request if (i) a similar request for the same purpose has been previously submitted by another public sector body or the Commission, the European Central Bank or another EU body and (ii) the data holder has not been notified of the erasure of the data pursuant to Article 19(1)(c) of the Data Act.\n\n## 50. Could Chapter V be used by governments in a way that puts citizens’ fundamental rights in danger?\n\nThe co-legislators have carefully drafted the text of Chapter V of the Data Act to limit the possibility for public sector bodies to put the rights of the citizens and companies at risk, even unintentionally. Specific provisions ensure that the need to request data justified by an exceptional need cannot in any way lower the protection of personal data or of trade secrets. These provisions primarily include Article 17 with a detailed list of requirements for a valid request, as well as Articles 18(4), 19(1)(b) and 19(3)-(4).\n\nAny alleged infringement of the provisions of Chapter V of the Data Act can be brought to the relevant courts or to the competent authority of the Member State in which the data holder is established.\n\n## 51. Can a public sector body be a ‘user’ of a connected product/related service under Chapter II?\n\nYes. Nothing prevents a public sector body (as a separate legal entity) from becoming a user in the sense of Chapter II of the Data Act (see Recital 18).\n\n### Switching between data processing services\n\n## 52. Which services are excluded from the scope of Chapter VI?\n\nArticles 23-32 and 34-35 of the Data Act apply to providers of data processing services. The definition of a data processing service is laid down in Article 2(8) and mirrors common definitions of cloud computing services. The concept is designed to cover the popular delivery models - Infrastructure as a Service (IaaS), Platform as a service (PaaS) and Software as a Service (SaaS) - while also remaining open to technological innovation.\n\nArticle 31 introduces a specific regime for (i) data processing services that are custom-built and not offered on a broad commercial scale and (ii) for data processing services that are provided as a testing/beta version. However, this does not mean that custom-built services are fully excluded from the scope of Chapter VI. The provisions not listed in Article 31(1) still apply. For example, providers of such services must make open interfaces available and ensure that data are exported in a structured, commonly used and machine-readable format.\n\n## 53. What is the difference between exportable data and digital assets? What do these concepts mean?\n\nAccording to Article 2(38) of the Data Act, the concept of “exportable data” covers input and output data. It also includes metadata directly or indirectly generated, or co-generated, by the customer’s use of the respective data processing service. These concepts exclude data protected as intellectual property and trade secrets of the provider or a third party.\n\n“Digital assets” are defined in Article 2(32). They are elements that the customer needs in order to be able to effectively use their data in the environment of a new service provider to which they have switched. Digital assets therefore cover other types of metadata, for example those related to the configuration of settings, security and access and control rights management. Applications as well as virtualisation technologies (e.g. virtual machines and containers) can also count as digital assets. As part of the switching process, digital assets can be ported from a source provider to a destination provider if the customer has the right to use these assets, independent from their contractual relationship with the provider of data processing service that the customer intends to switch from.\n\n## 54. What is the deadline for providers to reduce switching charges so that they are limited to the costs they incur?\n\nPursuant to Article 29(2) of the Data Act, providers of data processing services must reduce any switching charges (including egress charges) from 11 January 2024 onwards. Concretely, they must limit any switching charges to the costs that they incur in order to make the respective switching operation happen. From 12 January 2027 onwards, providers will no longer be allowed to charge for switching (including data egress).\n\nA special rule applies when a customer does not switch but instead asks a provider to provide services in parallel with other services, (e.g. in a multi-cloud deployment model). In such cases of in-parallel use, the provider may still bill the customer for the costs incurred for data egress, even after 12 January 2027. This is because a multi-cloud deployment may imply a constant data egress as opposed to the one-off data egress that can be expected for a switching operation.\n\n## 55. What does ‘free-tier offering’ mean?\n\nArticle 23(c) of the Data Act clarifies that customers who have benefited from a free-tier offering can also benefit from switching. A free-tier offering (sometimes referred to as cloud credits) is a free offer of data processing services from a provider to a customer. Free-tier offerings are intended to allow customers to test a data processing service or to assist start-up companies.\n\n## 56. How do the notice period and the transition period relate to one another?\n\nArticle 25 of the Data Act provides that the notice period begins once the customer notifies the provider of data processing services of their desire to switch to another provider or to an on-premises ICT infrastructure. Switching should be completed by the end of the transition period, which starts after the end of the notice period (maximum 2 months).\n\nDuring the transition period (maximum 30 calendar days), the provider must carry out the actions needed to enable the customer’s switching – in close cooperation with the customer themselves and, where applicable, with the customer’s new provider. The customer has the right to replace the 30-day transition period with a longer period. The provider can only extend the transition period if the provider can, within 14 days during the notice period, prove that a transition period of maximum 30 days would be technically unfeasible. In this case, the transition period can last a maximum of 7 months.\n\n## 57. How will the Commission create the common Union repository for the interoperability of data processing services?\n\nThe process is laid down in Article 35 of the Data Act.\n\nThe repository will take the form of an online platform. It will become a one-stop-shop for providers to see which harmonised standards or common specifications (on the basis of open interoperability specifications) apply to the type of service they offer. Providers must ensure that the interfaces that they make accessible to customers are compatible with the standards/specifications referenced in the repository. The aim is to ensure that cloud services are interoperable so that customers can benefit from switching without losing functionalities, and to make it easier for providers to support their customers in the switching process.\n\nAs a first step, the Commission will map existing harmonised standards and open interoperability specifications that qualify for recognition in the repository. Before the Commission can take a harmonised standard or a common specification up in the repository, it must adopt an implementing act. Following the mapping, the next step will be the preparation of the implementing act, which will be adopted in a comitology procedure.\n\nThe repository will be a living document and will be continuously updated with new relevant harmonised standards and common specifications per service type.\n\n## 58. What is the state of play regarding the standard contractual clauses for cloud computing contracts and what will they cover?\n\nAs per Article 41 of the Data Act, an Expert Group on B2B data sharing and cloud computing contracts, jointly managed by DG JUST and DG CNECT, is currently developing model contractual terms for data sharing and standard contractual clauses for cloud computing contracts.\n\nThe standard contractual clauses for cloud computing contracts are non-binding and can be adapted by the parties according to their contractual needs. Based on the Report of the Expert Group, the Commission will adopt a Recommendation. This is expected to happen before 12 September 2025.\n\nThe standard contractual clauses for cloud computing contracts will cover elements related to switching & exit, term & termination, non-dispersion, non-amendment, security & business continuity and to liability. These elements mirror the aspects covered by Chapter VI of the Data Act but also include other aspects that are relevant for fulfilling the objective of Art. 41, which is to assist parties in drafting and negotiating contracts with fair, reasonable, and non-discriminatory contractual rights and obligations.\n\n### 58a) Do the Data Act provisions on data processing services also apply to PaaS and SaaS?\n\nArticle (2)(8) of the Data Act defines “data processing services” as “a digital service that is provided to a customer and that enables ubiquitous and on-demand network access to a shared pool of configurable, scalable and elastic computing resources of a centralised, distributed or highly distributed nature that can be rapidly provisioned and released with minimal management effort or service provider interaction”. This definition builds on the widely and internationally accepted definition of cloud computing by the National Institute of Standards and Technology and covers IaaS, PaaS, and SaaS. This is confirmed by Recital 81 which lists IaaS, PaaS and SaaS as data processing service delivery models.\n\nChapter VI of the Data Act does not make a distinction between different types of SaaS, and thus applies to all SaaS types which display the characteristics listed in the definition of data processing services:\n\n* They enable access to computing resources, including networks, servers, storage, applications, and services;\n* They enable on-demand network access, meaning that a customer can unilaterally provision these computing resources which are available over the network and through standard mechanisms, for example via mobile phones, laptops, or workstations;\n* They can be rapidly provisioned and released with minimal management effort or service provider interaction, which implies that the unilateral provision can be done without significant intervention from the service provider and can be deployed quickly, allowing organisations to start using the resources almost immediately;\n* They are elastic and can be rapidly provisioned, meaning that the solutions can easily scale to accommodate changing needs and that customers can upgrade or downgrade demand based on their requirements.\n\nAnother relevant element of the definition of a ‘data processing service’ is that it must be provided to a customer. Article 2(30) defines ‘customer’ as “a natural or legal person that has entered into a contractual relationship with a provider of data processing services with the objective of using one or more data 40 processing services”. It is therefore important to consider whether the user is a customer and whether that customer uses a data processing service as such or makes use of a functionality enabled by a data processing service, such as listening to music or viewing videos.\n\nA provider whose service offering displays these characteristics must comply with the provisions of the Data Act to enable switching between data processing services. This includes, for example, bringing service contracts in line with Article 25, reducing and removing switching and egress charges pursuant to Article 29, and complying with the technical aspects of switching defined in Article 30. However, not all requirements placed on data processing services under Chapter VI of the Data Act apply to SaaS. Notably, the concept of functional equivalence laid down in Article 30(1) only applies to providers of IaaS, whereas Articles 30(2) and 30(3) apply to providers of PaaS and SaaS. These latter two provisions require providers of PaaS and SaaS to make open interfaces available and comply with open interoperability specifications and harmonised standards published in an EU repository.\n\nArticle 31(1) exempts providers of data processing services from certain obligations when the majority of the main features has been custom-built for a specific customer. In addition, Article 31(2) removes from the scope of Chapter VI data processing services provided for testing purposes and for a limited period of time. While neither of those two exemptions single out SaaS, it is possible that a specific SaaS solution meets these criteria and thus benefits from a lighter regime.\n\n### 58b) Is the source provider responsible for assisting the customer in rebuilding their service in the ecosystem of the destination provider?\n\nArticle 24 of the Data Act puts a clear limit on the scope of the source provider’s obligations to facilitate switching by stating that, “\\[t\\]he responsibilities of providers of data processing services laid down in Articles 23, 25, 29, 30 and 34 shall apply only to the services, contracts or commercial practices provided by the source provider of data processing services.” This provision limits the scope of a source provider’s technical obligations in facilitating switching (Art. 30) to the source provider’s own service environment.\n\nRecital 92 provides further clarification in explaining that “\\[t\\]his Regulation does not require providers of data processing services to develop new categories of data processing services, including within, or on the basis of, the ICT infrastructure of different providers of data processing services in order to guarantee functional equivalence in an environment other than their own systems. A source provider of data processing services does not have access to or insights into the environment of the destination provider of data processing services. Functional equivalence should not be understood to oblige the source provider of data processing services to rebuild the service in question within the infrastructure of the destination provider of data processing services. Instead, the source provider of data processing services should take all reasonable measures within its power to facilitate the process of achieving functional equivalence through the provision of capabilities, adequate information, documentation, technical support and, where appropriate, the necessary tools”.\n\nPursuant to Art. 30(1), the obligation to facilitate functional equivalence only applies to source providers of IaaS. Recital 92 explains that this obligation is limited to the source provider’s service environment. Article 30 obliges source providers of PaaS and SaaS to make open interfaces available, to export data in a structured, commonly used and machine-readable format, as well as the obligation to make their services compatible with harmonised standards or open interoperability specification if and when these are published in the common Union repository. The obligations placed on source providers of PaaS and SaaS fall short of the obligation to facilitate functional equivalence. The limits which recital 92 illustrates to the obligations of source providers of IaaS thus also apply to source providers of PaaS and SaaS.\n\nThe Data Act thus does not place a responsibility on any source provider to assist the customer in rebuilding their data processing service in the environment of the destination provider.\n\n### Unlawful access to and transfer of non-personal data held in the EU by third country authorities\n\n## 59. Does the Data Act create data localisation requirements?\n\nThe Data Act does not limit companies’ ability to transfer non-personal data internationally. It does not change the prohibition of national data localisation requirements as presented in the Free Flow of Non-personal Data Regulation.\n\nUsers of cloud services will continue to be free to choose a cloud provider of their liking and to decide where to store their data.\n\n## 60. What is the aim of Article 32?\n\nArticle 32 of the Data Act ensures that customers of cloud service providers that choose to store their non-personal data in the EU are protected from having their data unlawfully accessed by or transferred to non-EU governments. To this end, the cloud service provider must put in place all adequate technical, organisation and legal measures in order to prevent unlawful or illegitimate government access to or transfer of the customer’s data (cf. Article 28).\n\nAn unlawful access to or transfer of data may occur when such access or transfer would clash with obligations under EU or Member State law, such as regarding the protection of fundamental rights of the individual, or the protection of commercially sensitive data, including trade secrets and intellectual property rights (cf. Recital 101).\n\nIn case of access or transfer request made by a third country authority to a customer’s non-personal data, the cloud service provider is obliged to verify its lawfulness. Lawfulness exists, for instance, where the request is based on an international agreement such as a mutual legal assistance treaty. In the absence of an international agreement, the request must comply with certain procedural safeguards that are aligned with fundamental rules and norms in the EU legal order, such as proportionality of the request and judicial review.\n\nThe definition of ‘government’ or ‘public authority’ should not be too narrow when evaluating whether a particular body falls in that category.\n\n## 61. Does Article 32 cover international data transfers between or inside businesses?\n\nNo. Similar to Article 31 of the Data Governance Act, Article 32 of the Data Act covers only a very small and specific subset of international data flows – those which result from an unlawful access to or transfer of non-personal data by non-EU public authorities.\n\nThese Articles do not cover data transfers between private entities on both sides of the EU border. Rather, they prevent access to or transfers of non-personal data by non-EU public authorities that are contrary to EU or Member State law. International transfers of personal data are regulated under the GDPR.\n\n## 62. What measures should data processing service providers implement to prevent unlawful governmental access to or transfer of data?\n\nRecital 102 of the Data Act explains that data processing service providers “should take all reasonable measures to prevent access to systems on which non-personal data are stored, including, where relevant, through the encryption of data, frequent submission to audits, verified adherence to relevant security reassurance certification schemes, and by the modification of corporate policies.” The Commission encourages the development, deployment, and regular update of these measures.\n\nThe Commission may in the future decide to offer further guidance on this point to the competent authorities, following the advice of the European Data Innovation Board.\n\n## 63. Which bodies can a data processing service provider consult before deciding whether to grant access or transfer data following a request from third country authorities?\n\nTo identify the “relevant national body or authority competent for international cooperation in legal matters” under Chapter VII of the Data Act, a data processing service provider must check which administrative entity in their Member State is normally responsible for the implementation of Mutual Legal Assistance Treaties (MLATs). In the case of France, it could for example be the Bureau de l'entraide pénale internationale, which is a unit within the French Ministry of Justice. In Germany, the Bundesjustizamt acts as the central point of international collaboration.\n\nIn case of doubt, the addressee may also consult the Member State’s data coordinator.\n\n### Interoperability\n\n## 64. Can the Commission impose common specifications instead of standards?\n\nThe Data Act expresses a clear preference for standards to be developed by the EU standardisation bodies instead of imposing common specifications. Recital 103 confirms that “Common specifications should be adopted only as an exceptional fall-back solution to facilitate compliance with the essential requirements of this Regulation, or when the standardisation process is blocked, or when there are delays in the establishment of appropriate harmonised standards”.\n\nMoreover, the Commission can, taking into account the advice of the European Data Innovation Board, supplement the Data Act by adopting delegated acts which further specify those essential requirements laid down Article 33(1) that cannot produce the intended effect unless they are further specified by EU law.\n\nFor interoperability of data processing services (Article 35), the Data Act establishes the central Union standards repository for the interoperability of data processing services. References to both harmonised standards and common specifications can be published in the repository. Common specifications can be adopted based on open interoperability specifications if these comply with the requirements laid down in Article 35(1) and (2). In line with Article 30(1), providers of data processing services other than those of the Infrastructure as a Service delivery model must ensure compatibility with the common specifications and harmonised standards referenced in the repository, at least 12 months after the publication therein. See Question 54.\n\n## 65. Is the Commission intending to replace existing (e.g. sectoral) standards?\n\nNo. There is no such intention. Instead, the Data Act requires that sectoral specification should only be developed based on a careful assessment of those sectors’ specific needs. In addition, the Data Act should be without prejudice to more specific EU rules, such as in the context of the development of common European data spaces.\n\n## 66. Do the essential requirements in Article 36 affect national contract law?\n\nThe essential requirements applicable to smart contracts do not affect national contract law. The definition of ‘smart contract’ makes it clear that only computer programs used for executions of agreements - and not the agreements as such - are regulated by the Data Act.\n\n### Enforcement\n\n## 67. What bodies should Member States put in place to ensure that the Data Act is enforceable?\n\nThe Member States are required to designate at least one competent authority to deal with the enforcement of the Data Act and carry out the tasks listed in its Article 37(5). The competent authority may be newly created but it can also be an already existing public sector body. It is possible that Member States will appoint more than one such competent authority. If so, they will also have to designate from among them a ‘data coordinator’ - an additional competent authority whose role will be to facilitate cooperation between competent authorities and help entities wishing to have their rights under the Data Act enforced (as a ‘single point of contact’). In practice, the data coordinator will be expected to receive questions from companies or consumers and guide them to the authority which will be the right ‘competent authority’ in their specific case.\n\nIt is important to note that the DPAs remain responsible for monitoring the application of the Data Act insofar as the protection of personal data is concerned.\n\nMoreover, it is crucial that the Data Act is applied efficiently across all sectors. Competent authorities must therefore cooperate with sectoral authorities to ensure the Data Act is enforced consistently with other EU or national laws.\n\nThe Commission will work closely with these authorities, including through the European Data Innovation Board, to ensure the seamless and uniform application of the Data Act. This effort may include issuing sector-specific guidelines for the effective application of data access and use rules.\n\n## 68. Which public authority can help me if I consider that my rights under the Data Act are not respected?\n\nIf a Member State designates only one competent authority, this authority will oversee all matters relating to the application of the Data Act. In any event, the name of the competent authorities for each Member State along with the corresponding tasks and powers will be displayed on a publicly available register maintained by the Commission. In case of doubt, applicants can always direct their queries to the data coordinator in their Member State, because it should act as the single point of contact for all issues related to the application of the Data Act. In certain cases, the data coordinator may facilitate cooperation between competent authorities.\n\nNatural and legal persons should lodge complaints with the relevant competent authority in the Member State of their habitual residence, place of work or establishment, including with respect to cross-border matters. The competent authorities have a duty to cooperate and assist each other not only within the same Member State but also across borders.\n\n## 69. What is the role of the Commission in the enforcement of the Data Act?\n\nThe enforcement of the Data Act is primarily the responsibility of the Member States’ authorities, but the Commission plays a supportive role. It hosts the European Data Innovation Board (EDIB), an expert group which facilitates cooperation between competent authorities, promotes best practices and common approaches in enforcement. In addition, the Commission provides publicly available information on the competent authorities and on national legislation and measures in relation to penalties. To support market players in observing the rights and obligations introduced by the Data Act, the Commission will also recommend model contract terms for data sharing agreements and standard contractual clauses for cloud computing contracts that reflect the provisions of the Data Act.\n\n## 70. Are penalties harmonised across the EU?\n\nThe Member States are responsible for setting penalties and all the necessary measures relative to their application. However, to ensure high consistency across the EU, the EDIB will be used as a platform to evaluate, coordinate, and adopt recommendations on setting penalties for infringements of the Data Act.\n\nDPAs may within their scope of competence impose fines in accordance with the GDPR for the infringements of the obligations laid down in Chapter II, III and V of the Data Act. The EDPS may, within its scope of competence, impose administrative fines in accordance with Regulation (EU) 2018/1725 for infringements of the obligations laid down in Chapter V.\n\n## 71. When should a legal representative be designated? Is such a legal representative liable for non-compliance with the Data Act by companies outside the EU?\n\nThe legal representative's role is to facilitate compliance with the Data Act by entities that make their services (including, but not limited to, related services) or connected products available in the EU market but are established outside the EU. All such entities must designate an EU-based representative. The competent authorities can address such a representative in all matters related to the implementation of the Data Act instead of or in addition to the non-EU entity. However, their liability is limited to their obligations as representatives under the Data Act. The role and responsibilities of legal representatives under the Data Act is similar to that of legal representatives under the GDPR (cf. European Data Protection Board Guidelines 3/2018).\n\n### Next steps and future actions\n\n## 72. When will the Commission publish the guidance on reasonable compensation?\n\nIn line with Article 9(5) of the Data Act, the European Data Innovation Board must be consulted on the guidelines on calculating reasonable compensation for making data available before their adoption. The guidelines are expected to be adopted by Q2/Q3 2026.\n\n## 73. What are the next steps regarding interoperability?\n\nIn support of Article 33 of the Data Act on requirements related to interoperability in data spaces, the Commission has prepared a standardisation request called the “European Trusted Data Framework” (ETDF).\n\nThe ETDF request covers seven European standards/standardisation deliverables. These are closely aligned with the recommendations of the data interoperability workstream of the High-Level Forum on European Standardisation (published on 11 April 2024).\n\nThe request reflects input from consultations with the European standardisation organisations (CEN, Cenelec and ETSI), the EU stakeholder organisations representing consumers, environmental interests, trade unions and SMEs in standardisation (SBS, ETUC, ANEC and ECOS), and the European Data Innovation Board.\n\nIt is expected that the request will be formally adopted by the end of Q2 2025.\n\n## 74. What is the state of play of the model contractual terms for data sharing and the standard contractual clauses for cloud computing contracts?\n\nThe Commission has published Model Contractual Terms (MCTs) for data access and use and Standard Contractual Clauses (SCCs) for cloud computing contracts, based on a report by an Expert Group set up to assist the Commission with this task.\n\nThe MCTs cover contracts between data holders and users, data holders and data recipients, users and data recipients and between data sharers and data recipients.\n\nThe SCCs cover elements related to switching & exit, term & termination, non-dispersion, non-amendment, security & business continuity and to liability. These elements mirror the aspects covered by Chapter VI but also include other aspects that are relevant for fulfilling the objective of Article 41, which is to assist parties in drafting and negotiating contracts with fair, reasonable, and non-discriminatory contractual rights and obligations.\n\nThe contracts are non-binding and can be adapted by the parties according to their contractual needs.\n"}