Artifact GuideEU

EU Data Act Deadlines and Compliance Calendar

Deadline tracker and compliance calendar page for upcoming milestones and reporting dates.

Use official sources to map obligations to owners, evidence, and staged deadlines.

Back to main artifact Review sources

Author

Sorena AI

Published

Feb 23, 2026

Updated

Feb 23, 2026

Sections

Structured answer sets in this page tree.

Primary sources

Cited legal and guidance references.

Publication metadata

Sorena AI

Published Feb 23, 2026

Updated Feb 23, 2026

Overview

The EU Data Act is phased. Treat each legal date as a release gate: scope decisions, role mapping (user/data holder/data recipient), contract updates, API/data-access workflows, and evidence. This page turns the Data Act's application and transitional rules into a calendar you can run with owners and deliverables.

Section 1

The dates that drive your roadmap (Article 50 + cloud switching pricing)

The general application date is 12 September 2025, but several obligations have their own triggers (notably the connected-product design duty and the legacy unfair-terms extension). Cloud switching pricing rules also have fixed milestones.

Plan the earliest gate you cannot miss: if you provide data processing services, switching charges phase out on a hard date (12 January 2027).

11 January 2024 - entered into force (baseline for certain transitional provisions)
12 September 2025 - Regulation applies (most obligations become enforceable)
12 September 2026 - Article 3(1) design duty applies for connected products/related services placed after this date
12 September 2027 - Chapter IV legacy extension applies for certain long-running pre-2025 contracts
12 January 2027 - switching charges banned (Article 29)

Section 2

By 12 September 2025 - core readiness (scope, roles, contracts, interfaces)

By the application date, you need a defensible scope boundary and a working access workflow. Most implementation failures come from unclear definitions (product vs related service data, readily available data) and unclear role mapping (who is data holder).

Treat this gate as "operational readiness": request intake, identity verification, data delivery mechanisms, trade secret safeguards, and contract templates.

Scope memo per product line: product data, related service data, readily available data, and exclusions (inferred/derived)
Role mapping: user vs data holder vs data recipient; outsource/related service provider data holder cases
User access + sharing workflow: direct access vs portal requests, authentication/authorization, audit logs
Trade secrets safeguards: confidentiality measures + escalation path ("handbrake" process)
B2B contract baseline: FRAND terms, compensation approach, liability/remedies, termination, security requirements

Section 3

By 12 September 2026 - connected-product design duty (Article 3(1)) for new products

Article 3(1) has a forward-looking trigger: it applies to connected products and related services placed on the market after 12 September 2026. In practice, you need a product architecture pattern that can expose data access safely and consistently.

Build a reference implementation so new product lines inherit compliant design by default.

Design patterns: data capture layer, event schema, export formats, and "readily available" extraction path
Security and privacy controls: access control, encryption, logging, and GDPR coordination for personal data
Developer experience: internal APIs/SDKs, documentation, and test harnesses for portability and sharing requests
Evidence: architecture diagrams, interface specs, and test evidence for data access workflows

Section 4

By 12 September 2027 - legacy unfair-terms exposure (Chapter IV extension)

Chapter IV applies to contracts concluded after 12 September 2025. From 12 September 2027 it also applies to certain earlier contracts (indefinite duration or expiring at least 10 years from 11 January 2024).

This is a commercial/legal gate: you need a contract inventory and a remediation plan for "take-it-or-leave-it" clauses covering data access and use, and related liability/remedy terms.

Contract inventory: identify data-sharing-related terms in pre-2025 B2B contracts that may fall into the extension criteria
Remediation plan: clause library, negotiation playbook, and fallbacks if a clause is voided as unfair
Governance: sales/legal enablement and a change-control process for standard terms

Section 5

Cloud switching pricing milestones (Article 29) - hard dates

If you provide data processing services, Article 29 sets a clear pricing ramp-down for switching charges. Reduced switching charges are allowed only during a fixed window; from 12 January 2027, switching charges are prohibited.

This is a product + finance change: pricing, billing systems, and contract templates must match the legal timeline.

11 Jan 2024 -> 12 Jan 2027: reduced switching charges allowed (capped at directly linked costs)
From 12 Jan 2027: no switching charges
Customer disclosures: pre-contract clarity on fees, early termination penalties, and switching charges during the reduced-charge window

Recommended next step

Turn EU Data Act Deadlines and Compliance Calendar into an operational assessment

Assessment Autopilot can take EU Data Act Deadlines and Compliance Calendar from planning deadlines, owners, and milestones from this page to a reusable workflow inside Sorena. Teams working on EU Data Act can keep owners, evidence, and next steps aligned without copying this guide into separate documents.

Assessment workflow

Open Assessment Autopilot for EU Data Act Deadlines and Compliance Calendar

Start from EU Data Act Deadlines and Compliance Calendar and turn the guidance into owned tasks, evidence requests, and review checkpoints.

Explore next step

Talk to Sorena

Talk through EU Data Act

Review your current process, evidence gaps, and next steps for EU Data Act Deadlines and Compliance Calendar.

Explore next step

Primary sources