Data Act: questions to assess your obligations
Applicability: 12.9.2025 (main provisions; specific dates below)
Timeline
| Date | Scope |
|---|---|
| 12 September 2025 | Main applicability, including Chapter VI switching |
| After 12 September 2026 | Article 3(1) design/access duty for connected products and related services placed on the market after this date |
| 12 January 2027 | Article 29 prohibition of switching charges; distinct from ordinary service fees or separately applicable early-termination charges |
| From 12 September 2027 | Chapter IV also applies to contracts concluded on/before 12 September 2025 if indefinite or expiring at least 10 years from 11 January 2024 (Art. 50) |
There is no general “enhanced interoperability in September 2026 / full portability standardisation in September 2027” milestone. Technical duties follow Articles 30 and 35 and relevant standards/specifications.
Application overview
| Entity | Relevance | Priority |
|---|---|---|
| IoT manufacturers | HIGH | Ch. II-III |
| SaaS/Cloud providers | HIGH | Ch. VI |
| Cloud service customers | MEDIUM (rights) | Ch. VI |
| B2B data holders | MEDIUM | Ch. III-IV |
| Other organisations | Assess the specific role | Also check other chapters under Art. 1 |
Part A: IoT / Connected Products (Ch. II-III)
Distinguish manufacturers, sellers/rentors/lessors, related-service providers and data holders; Articles 3–5 allocate different duties. Check Article 2 definitions and Article 7 exceptions. The rows are review steps and technical examples; a particular API, UI or format is not universally prescribed.
| # | Activity | Reference | Phase | Description |
|---|---|---|---|---|
| A1 | Connected products inventory | Art. 2, 3 | Preparation | List all connected products in the portfolio |
| A1.1 | — Products generating data | Art. 2(5) | Preparation | Identify products with data |
| A1.2 | — Mapping data flows | Art. 3 | Preparation | What data, where, to whom available |
| A1.3 | — Related services | Art. 2(6) | Preparation | Software/services linked to products |
| A2 | Pre-purchase transparency | Art. 3(2) | Implementation | Pre-purchase information about data |
| A2.1 | — Data type and volume | Art. 3(2)(a) | Implementation | Documentation of generated data |
| A2.2 | — Real-time/continuous | Art. 3(2)(b) | Implementation | Info on continuous generation |
| A2.3 | — Data access | Art. 3(2)(d) | Implementation | How the user accesses data |
| A2.4 | — Prospective data holder’s use of data | Art. 3(3)(c) | Implementation | Information by related-service provider |
| A3 | Data access mechanism | Art. 4 | Implementation | Technical solution for access |
| A3.1 | — API/Interface | Art. 4(1) | Implementation | REST API or user interface |
| A3.2 | — User verification | Art. 4(5) | Implementation | Only necessary information; logs only as necessary |
| A3.3 | — Real-time streaming | Art. 4(1) | Implementation | Where relevant and technically feasible |
| A3.4 | — Machine-readable format | Art. 4(1) | Implementation | JSON, CSV, standard formats |
| A4 | Third-party data sharing | Art. 5 | Implementation | Process for sharing with third parties |
| A4.1 | — Request process | Art. 5(1) | Implementation | How the user requests sharing |
| A4.2 | — Data transfer | Art. 5(1) | Implementation | Technical data transfer |
| A4.3 | — Terms for recipients | Art. 6 | Implementation | Conditions for third parties |
| A5 | Data access by design | Art. 3(1) | Design | New products with built-in access |
| A5.1 | — Design review process | Art. 3(1) | Design | Review of new products |
| A5.2 | — Built-in UI/API | Art. 3(1) | Design | Access as part of the product |
| A6 | Contractual documentation | Art. 3(2)–(3), 4(6), 4(13), 5–6 | Legal | Separate information, data use, trade secrets and sharing |
| A6.1 | — Terms of Service update | Art. 4 | Legal | Update conditions |
| A6.2 | — Data-use contract with user | Art. 4(13) | Legal | Holder’s use of non-personal data only under a contract with the user |
Part B: Cloud Switching (Ch. VI)
For providers of data processing services under Art. 2(8) (IaaS, PaaS, SaaS); check Art. 31 exemptions
APIs, self-service UIs and JSON/CSV are implementation examples. Article 30(1) concerns functional equivalence for infrastructure services; paragraphs 2–4 cover other services, and paragraph 5 requires export where relevant specifications/standards have not been published. The maximum two-month notice is not the entire migration period or an automatic waiver of early-termination charges.
| # | Activity | Reference | Phase | Description |
|---|---|---|---|---|
| B1 | Customer contract audit | Art. 23-25 | Preparation | Review all contracts vs. Data Act |
| B1.1 | — Identify lock-in clauses | Art. 23 | Preparation | Problematic contractual terms |
| B1.2 | — Exit costs analysis | Art. 29 | Preparation | Current switching/exit fees |
| B1.3 | — Notice periods | Art. 25(2)(d) | Preparation | Notice periods vs. max 2 months |
| B2 | Contractual amendments | Art. 25 | Legal | Revision of Terms of Service |
| B2.1 | — Switching rights clause | Art. 25(2)(a) | Legal | Switching on request; notice and transition under Art. 25 |
| B2.2 | — Max notice period (2M) | Art. 25(2)(d) | Legal | Maximum notice period |
| B2.3 | — Switching process description | Art. 25(2)(a) | Legal | Documented process |
| B2.4 | — Transparent price list | Art. 29(4) | Legal | Switching costs in advance |
| B2.5 | — Early termination policy | Art. 25, 29(4) | Legal | Distinguish early-termination charges from switching fees; inform before contract |
| B3 | Data export function | Art. 23, 25, 30 | Implementation | Technical solution for export |
| B3.1 | — Export API | Art. 30 | Implementation | Programmatic data export |
| B3.2 | — Self-service UI | Art. 23, 25 | Implementation | Customer can export independently |
| B3.3 | — Export formats | Art. 30(5) | Implementation | JSON, CSV, SQL, standard |
| B3.4 | — Data completeness | Art. 2(38), 25(2)(e)–(f) | Implementation | Exportable data/digital assets within the statutory scope |
| B3.5 | — Metadata export | Art. 2(38), 25 | Implementation | Configuration, settings |
| B4 | Technical assistance | Art. 25(2)(a), 26 | Process | Support during switching |
| B4.1 | — Switching support process | Art. 25(2)(a) | Process | Assistance workflow |
| B4.2 | — Migration documentation | Art. 26, 27, 30 | Process | Technical guides |
| B4.3 | — SLA for switching | Art. 25(2)(a), 25(4)–(5) | Process | Notice max 2 months; transition normally max 30 calendar days, with Art. 25 exceptions |
| B5 | Interoperability | Art. 30, 35 | Implementation | Open standards, compatibility |
| B5.1 | — Open interfaces | Art. 30(2) | Implementation | Free of charge for customers and destination providers (services outside Art. 30(1)) |
| B5.2 | — Format standards | Art. 30, 35 | Implementation | Interoperable formats |
| B6 | Prohibition of switching fees | Art. 29 | Finance | Removal of charges |
| B6.1 | — Pricing update | Art. 29 | Finance | Price list update |
| B6.2 | — Contract amendments | Art. 29 | Legal | Contract modifications |
Part C: Unfair Contract Terms (Ch. IV)
Assess unilaterally imposed B2B terms on data access, use, liability and remedies under Article 13, including its exceptions and Article 50 transitions.
| # | Activity | Reference | Phase | Description |
|---|---|---|---|---|
| C1 | B2B contract audit | Art. 13 | Preparation | Review contracts for unfair terms |
| C1.1 | — Unilateral changes | Art. 13(3)–(5) | Preparation | Clauses allowing changes |
| C1.2 | — Exclusive interpretation and limits on own data | Art. 13(4)(c), 13(5)(c), (e) | Preparation | Exclusive right to interpret; preventing use/copy of provided data |
| C1.3 | — Disproportionate liability | Art. 13(4)–(5) | Preparation | Risk transfer |
| C2 | Revision of contractual terms | Art. 13, 50 | Legal | Removal of unfair terms |
| C2.1 | — New contracts | Art. 13 | Legal | Contracts concluded after 12.9.2025 |
| C2.2 | — Existing contracts | Art. 50 | Legal | From 12.9.2027 only for legacy contracts meeting Art. 50 duration criteria |
Part D: Cloud Service Customers (Rights)
For organisations using cloud/SaaS services. These are recommended customer actions, not a standalone Data Act duty to have an exit strategy; Article 25(2)(b) requires the provider to support it.
| # | Activity | Reference | Phase | Description |
|---|---|---|---|---|
| D1 | Vendor contract audit | Ch. VI | Preparation | Review contracts with cloud providers |
| D1.1 | — Switching rights | Art. 25 | Preparation | Do we have the right to switch? |
| D1.2 | — Exit costs | Art. 29 | Preparation | What are the exit costs? |
| D1.3 | — Data export | Art. 23, 25, 30 | Preparation | Is export available? |
| D2 | Vendor negotiation | Ch. VI | Action | Require Data Act compliance |
| D2.1 | — Contract amendments | Art. 25 | Action | Contract modifications |
| D2.2 | — Export testing | Art. 23, 25, 30 | Action | Test data export functions |
| D3 | Exit Strategy | Art. 25(2)(b) | Planning | Documented exit strategy |
| D3.1 | — Alternative vendors | - | Planning | Identify alternatives |
| D3.2 | — Migration plan | Art. 25–27 | Planning | Migration plan |
| D3.3 | — Cost estimate | Art. 29 | Planning | Cost estimate |
Critical path
Month ranges are illustrative planning stages, not new legal grace periods.
For IoT manufacturers
For Cloud/SaaS providers
For cloud service customers
Sources
Content reviewed: 6 September 2026. Primary sources: Data Act — Arts. 1–7, 13, 23–31, 35, 40, 50, Commission Data Act FAQ.