Ad Tech Compliance

    EU Data Act for ad tech: requirements, cloud switching and connected-device data

    Published · Last updated
    Next scheduled review:

    The EU Data Act (Regulation (EU) 2023/2854) has applied since 12 September 2025. For ad tech it matters in three places. Cloud and SaaS contracts must allow switching, with switching and egress charges banned from 12 January 2027. Connected products such as smart TVs must give users their data. Recipients of that data face profiling limits (EUR-Lex).

    The Data Act is a horizontal law. Most of it was written for factories, cars and farm machinery, and the Commission's own examples follow that path. Two chapters reach ad tech directly: Chapter VI on switching between data processing services, and Chapter II on data from connected products and related services.

    Contents

    Key facts

    • Dates. In force 11 January 2024; applies from 12 September 2025; design duties for new connected products from 12 September 2026 (Article 50; Commission, Data Act page).
    • Egress fees end. "From 12 January 2027, providers of data processing services shall not impose any switching charges on the customer for the switching process" (Article 29(1)).
    • SaaS is in scope. The Commission's FAQ says Chapter VI covers IaaS, PaaS and SaaS and "does not make a distinction between different types of SaaS" (Commission FAQ v1.4, 22 January 2026, Q58a).
    • Smart TVs are named. The Commission lists "cars, smart TVs, and industrial machinery" as connected devices whose users gain control over data (Commission, Data Act page).
    • Content is out. Users cannot demand a film displayed on a smart TV. The same FAQ answer puts a camera's usage patterns, timestamps and event logs in scope (Commission FAQ v1.4, Q6).
    • Changes are pending. The Council's Digital Omnibus mandate of 21 October 2026 would ease switching duties for some older contracts but keep the charge ban (Council document 14756/26, pp. 79 to 80).
    Jump to the table

    Definition

    A data processing service, under Data Act Article 2(8), is a digital service that gives a customer on-demand network access to "a shared pool of configurable, scalable and elastic computing resources" (Regulation (EU) 2023/2854).

    The Commission reads this as the NIST definition of cloud computing (FAQ v1.4, Q58a). A self-serve DSP, a cloud data warehouse that hosts a clean room, and a customer data platform can each meet it, depending on how they are sold and run.

    EU Data Act timeline: the dates that matter

    8 of 8 rows

    Columns (3)

    22 Dec 2023

    Published in the Official Journal

    11 Jan 2024

    Entry into force; switching charges may only be reduced, cost-based charges

    12 Sep 2025

    General application, including Chapter II access rights and Chapter VI switching

    12 Sep 2025

    Member states notify their penalty rules to the Commission

    12 Sep 2026

    Access-by-design duty for connected products and related services placed on the market after this date

    12 Jan 2027

    No switching charges, including data egress for switching

    12 Sep 2027

    Unfair-terms rules (Chapter IV) extend to long-term contracts concluded on or before 12 Sep 2025

    Pending

    Digital Omnibus amendments; Council mandate agreed 21 Oct 2026

    22 Dec 2023

    What applies

    Published in the Official Journal

    Source

    EUR-Lex

    11 Jan 2024

    What applies

    Entry into force; switching charges may only be reduced, cost-based charges

    12 Sep 2025

    What applies

    General application, including Chapter II access rights and Chapter VI switching

    Source

    Article 50

    12 Sep 2025

    What applies

    Member states notify their penalty rules to the Commission

    12 Sep 2026

    What applies

    Access-by-design duty for connected products and related services placed on the market after this date

    Source

    Article 50

    12 Jan 2027

    What applies

    No switching charges, including data egress for switching

    12 Sep 2027

    What applies

    Unfair-terms rules (Chapter IV) extend to long-term contracts concluded on or before 12 Sep 2025

    Source

    Article 50

    Pending

    What applies

    Digital Omnibus amendments; Council mandate agreed 21 Oct 2026

    Download JSON

    Table by AdSovereign, CC BY 4.0.

    Our ad tech regulation calendar places these dates alongside the other 2027 deadlines.

    EU Data Act switching rules for cloud and SaaS

    The law. Providers of data processing services must remove "pre-commercial, commercial, technical, contractual and organisational obstacles" that stop customers from leaving. That covers terminating the contract, signing with a rival, and porting "exportable data and digital assets" to another provider or to on-premises infrastructure (Article 23). Exportable data means the input and output data, including metadata, generated by the customer's use of the service. It excludes the provider's own IP and trade secrets (Article 2(38)).

    The contract must say so in writing. Required terms include a notice period of no more than two months to start switching. A transition of at most 30 calendar days follows, during which the old provider keeps the service running and helps (Article 25(2)). Infrastructure providers must also take reasonable steps toward "functional equivalence" on the destination service (Article 30(1)).

    Charges. Since 11 January 2024 switching charges may not exceed the provider's costs directly linked to the switch. From 12 January 2027 they must be zero (Article 29). Providers must publish standard fees and early termination penalties before contract signature (Article 29(4) to (6)).

    What the Commission said. Parallel use is treated differently. Where a customer runs several clouds at once instead of switching, the provider "may still bill the customer for the costs incurred for data egress, even after 12 January 2027" (Commission FAQ v1.4, Q54). The Commission was due to recommend non-binding standard contractual clauses for cloud contracts (FAQ v1.4, Q58). Its Data Act page still links a draft recommendation on our check of 9 November 2026 (Commission, Data Act page).

    Exemptions. Three switching duties (Article 23(d), Article 29 and Article 30(1) and (3)) do not apply to services that are mostly custom-built for one customer and not sold from a broad catalogue. Test and evaluation versions are outside Chapter VI (Article 31).

    A worked scenario (our analysis). A retailer runs its retail media log-level data and clean room on a cloud data warehouse and wants to move both to another provider in 2027. The questions follow the articles. Is the warehouse a data processing service under Article 2(8)? Are the logs and audience tables "exportable data", or partly the provider's trade secrets? Does the contract give a notice period of two months or less and a 30-day transition? Is the retailer switching, so no charge applies, or adding a second cloud in parallel, where the FAQ allows egress billing?

    Our comparison of clean room architectures shows which designs keep the data in the customer's own account, and the analysis of the real cost of cloud DSPs covers data ownership in buying platforms.

    Interoperability rules

    The law. Open interoperability specifications and harmonised standards for data processing services must aim at interoperability between services of the same type, portability of digital assets, and functional equivalence, without harming security (Article 35(1)). Article 36 sets essential requirements for smart contracts that execute data sharing agreements.

    Pending change. The Commission proposed removing the essential requirements for smart contracts (COM(2025) 837), and the Council mandate deletes Article 36 (Council document 14756/26). For ad tech, the interoperability rules matter less than the switching rules today: they work through standards that do not yet exist for ad platforms.

    Connected products and CTV device data

    The law. A connected product is an item that "obtains, generates or collects data concerning its use or environment" and can communicate that product data (Article 2(5)). Products placed on the market after 12 September 2026 must be designed so that the user can reach product data and related service data by default. Access must be free of charge and in a machine-readable format (Articles 3(1) and 50). Where the user cannot reach the data directly, the data holder must make it available without undue delay (Article 4(1)).

    Two rules bind the data holder's own use. It may use readily available non-personal data only on the basis of a contract with the user. And it "shall not make available non-personal product data to third parties for commercial or non-commercial purposes other than the fulfilment of their contract with the user" (Article 4(13) and (14)). Personal data stays under the GDPR and the ePrivacy Directive, which prevail in a conflict (Article 1(5)).

    Third parties and gatekeepers. A user can ask for data to go to a third party. That third party may not use it "for the profiling" unless necessary for the service the user asked for, and may not pass it to a designated gatekeeper (Article 6(2)(b) and (d)). Gatekeepers under the Digital Markets Act are not eligible recipients at all (Article 5(3)).

    What is excluded. Recital 15 leaves out data "inferred or derived" through proprietary algorithms. Recital 16 leaves out content, and data generated "when the user records, transmits, displays or plays content" (Regulation (EU) 2023/2854). The Commission's FAQ adds that content means something "akin to copyrightable material" (FAQ v1.4, Q6).

    The table applies those rules to CTV data types. The first column is our classification; the last column names the open question.

    6 of 6 rows

    Columns (4)

    Power state, uptime, app launches, timestamps, error logs

    In scope as product or related service data

    FAQ Q6 examples of usage patterns, timestamps and event logs

    Whether "readily available" covers all log types

    The programme or film shown

    Out of scope

    Recital 16; FAQ Q6 smart TV example

    None for the content itself

    ACR data: fingerprints matched to programmes

    Unclear

    Recital 16 (data generated when displaying content) versus Article 2(15) (product data)

    Whether matching is "derived" data or data about use

    Audience segments and household inferences

    Out of scope as inferred or derived

    Recital 15

    Where raw ends and derived begins

    Ad impression logs from a TV's own ad platform

    Unclear

    Article 2(6) related service; recital 16

    Whether an ad service is a "related service" of the TV

    Any of the above that is personal data

    GDPR and ePrivacy apply as well, and prevail

    Article 1(5)

    Interaction with consent for ACR

    Power state, uptime, app launches, timestamps, error logs

    Likely status under Chapter II (our reading)

    In scope as product or related service data

    Basis

    FAQ Q6 examples of usage patterns, timestamps and event logs

    Open question

    Whether "readily available" covers all log types

    The programme or film shown

    Likely status under Chapter II (our reading)

    Out of scope

    Basis

    Recital 16; FAQ Q6 smart TV example

    Open question

    None for the content itself

    ACR data: fingerprints matched to programmes

    Likely status under Chapter II (our reading)

    Unclear

    Basis

    Recital 16 (data generated when displaying content) versus Article 2(15) (product data)

    Open question

    Whether matching is "derived" data or data about use

    Audience segments and household inferences

    Likely status under Chapter II (our reading)

    Out of scope as inferred or derived

    Basis

    Recital 15

    Open question

    Where raw ends and derived begins

    Ad impression logs from a TV's own ad platform

    Likely status under Chapter II (our reading)

    Unclear

    Basis

    Article 2(6) related service; recital 16

    Open question

    Whether an ad service is a "related service" of the TV

    Any of the above that is personal data

    Likely status under Chapter II (our reading)

    GDPR and ePrivacy apply as well, and prevail

    Basis

    Article 1(5)

    Open question

    Interaction with consent for ACR

    Download JSON

    Table by AdSovereign, CC BY 4.0.

    If a TV maker's ad business uses non-personal viewing or usage data, Article 4(13) ties that use to a contract with the user. Article 4(14) limits making non-personal product data available to third parties. Whether an aggregated audience report counts as product data or as derived data is the question that decides most CTV cases. Our guide to SSAI and CTV ad serving explains where these logs are produced.

    International access and data location

    The law. Cloud providers must take "adequate technical, organisational and legal measures, including contracts" to prevent third-country government access to non-personal data held in the EU where it would conflict with EU or national law (Article 32(1)). This sits beside the GDPR transfer rules for personal data.

    The Council mandate would also move the ban on unjustified data localisation from the Free Flow Regulation into the Data Act and repeal Regulation (EU) 2018/1807 (Council document 14756/26, recital 19). Country rules that do require local storage are tracked in our data residency requirements by country, and provider options in sovereign cloud providers compared.

    What the Digital Omnibus would change in the Data Act

    Nothing below is law. The Commission proposed the changes on 19 November 2025, the Council agreed its mandate on 21 October 2026, and Parliament has no position (EU Digital Omnibus tracker).

    6 of 6 rows

    Columns (4)

    Custom-made cloud services on contracts signed by 12 Sep 2025

    Full Chapter VI, except Article 31 custom-built carve-out

    Lighter regime for custom-made services (COM(2025) 837)

    Chapter VI and Article 34 disapplied except Article 29; clauses contrary to Article 29 void (new Article 31(1a), p. 79)

    SME and small mid-cap providers, non-IaaS, contracts by 12 Sep 2025

    Full Chapter VI

    Lighter regime (COM(2025) 837)

    Same carve-out, Article 29 kept (pp. 79 to 80)

    Early termination penalties in fixed-term contracts

    Must not obstruct switching

    Clarified as permitted for SME and small mid-cap providers

    Proportionate penalties permitted for non-IaaS services (p. 79)

    Trade secrets in Chapter II

    Refusal on serious economic damage

    New refusal ground for third-country risk

    Kept, with Commission guidelines (recitals 11 to 14a)

    Business-to-government requests

    "Exceptional need"

    Public emergencies only

    Public emergencies only (recital 15)

    Smart contracts, Article 36

    Essential requirements

    Essential requirements removed

    Article 36 deleted

    Custom-made cloud services on contracts signed by 12 Sep 2025

    Data Act today

    Full Chapter VI, except Article 31 custom-built carve-out

    Commission proposal, COM(2025) 837

    Lighter regime for custom-made services (COM(2025) 837)

    Council mandate, 14756/26

    Chapter VI and Article 34 disapplied except Article 29; clauses contrary to Article 29 void (new Article 31(1a), p. 79)

    SME and small mid-cap providers, non-IaaS, contracts by 12 Sep 2025

    Data Act today

    Full Chapter VI

    Commission proposal, COM(2025) 837

    Lighter regime (COM(2025) 837)

    Council mandate, 14756/26

    Same carve-out, Article 29 kept (pp. 79 to 80)

    Early termination penalties in fixed-term contracts

    Data Act today

    Must not obstruct switching

    Commission proposal, COM(2025) 837

    Clarified as permitted for SME and small mid-cap providers

    Council mandate, 14756/26

    Proportionate penalties permitted for non-IaaS services (p. 79)

    Trade secrets in Chapter II

    Data Act today

    Refusal on serious economic damage

    Commission proposal, COM(2025) 837

    New refusal ground for third-country risk

    Council mandate, 14756/26

    Kept, with Commission guidelines (recitals 11 to 14a)

    Business-to-government requests

    Data Act today

    "Exceptional need"

    Commission proposal, COM(2025) 837

    Public emergencies only

    Council mandate, 14756/26

    Public emergencies only (recital 15)

    Smart contracts, Article 36

    Data Act today

    Essential requirements

    Commission proposal, COM(2025) 837

    Essential requirements removed

    Council mandate, 14756/26

    Article 36 deleted

    Download JSON

    Table by AdSovereign, CC BY 4.0.

    The switching-charge ban survives in both texts. Every carve-out keeps Article 29, so the 12 January 2027 date stands on the texts we read (Council document 14756/26, pp. 79 to 80). The Council text amends Articles 4 and 5 only on trade secrets (paragraphs 6, 8, 9 and 11). We found no change to Articles 3, 4(13), 4(14), 5(3) or 6(2), the provisions that matter most for CTV.

    Penalties. Member states set penalties and had to notify them by 12 September 2025 (Article 40). Related frameworks are collected in our ad tech compliance hub.

    FAQ

    When does the EU Data Act apply?
    From 12 September 2025. Access by design for new connected products follows on 12 September 2026 and the end of switching charges on 12 January 2027. Older long-term contracts come under the unfair-terms chapter on 12 September 2027 (Articles 29 and 50).
    Does the Data Act ban cloud egress fees?
    For switching, yes, from 12 January 2027; until then, charges may only cover the provider's direct costs (Article 29). The Commission's FAQ says egress for parallel multi-cloud use can still be billed after that date (FAQ v1.4, Q54).
    Does the Data Act apply to SaaS ad platforms?
    It can. The Commission says Chapter VI covers SaaS that meets the definition of a data processing service, with no distinction between types of SaaS (FAQ v1.4, Q58a). Whether a given DSP, CDP or clean room qualifies depends on how it is provisioned and sold.
    Does the Data Act cover smart TV viewing data?
    Partly. Usage data such as timestamps and event logs can be in scope, while the content shown and data inferred through proprietary algorithms are out (recitals 15 and 16; FAQ v1.4, Q6). Automatic content recognition sits between the two and is unresolved.
    Does the Digital Omnibus change the EU Data Act?
    It would, if adopted. The Council text would exempt some custom-made and SME cloud contracts signed by 12 September 2025 from most switching duties, narrow government data requests and delete the smart contract article. It keeps the switching-charge ban (Council document 14756/26).

    How this works on owned infrastructure

    The switching chapter asks a simple question of every ad tech contract: can the customer take its logs, audiences and models elsewhere within 30 days, without a fee? The answer depends on the contract and on where the data physically sits. AdSovereign is an enterprise, on-premise RTB stack (DSP, SSP, exchange and clean room) designed to run inside the customer's own data centre or cloud account, so bid logs and audience tables stay in storage the customer already controls and an exit is a licence decision rather than a data migration. Whether a deployment is a "data processing service" under Article 2(8) is a separate legal question. The architecture page shows where data lives, and the TCO page compares running costs.

    Sources

    1. Regulation (EU) 2023/2854 (Data Act), OJ L, 22 December 2023: Articles 1, 2, 3, 4, 5, 6, 23, 25, 29, 30, 31, 32, 35, 36, 40, 50; recitals 15 and 16. EUR-Lex. https://eur-lex.europa.eu/eli/reg/2023/2854/oj/eng
    2. European Commission, Data Act policy page (checked 9 November 2026). https://digital-strategy.ec.europa.eu/en/policies/data-act
    3. European Commission, Frequently Asked Questions on the Data Act, version 1.4 (22 January 2026; library page updated 3 March 2026). https://ec.europa.eu/newsroom/dae/redirection/document/108144
    4. European Commission, "Commission publishes Frequently Asked Questions about the Data Act" (library page). https://digital-strategy.ec.europa.eu/en/library/commission-publishes-frequently-asked-questions-about-data-act
    5. European Commission, Proposal for a Regulation (Digital Omnibus), COM(2025) 837 final (19 November 2025), explanatory memorandum on Data Act changes. EUR-Lex. https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:52025PC0837
    6. Council of the European Union, document 14756/26, mandate for negotiations (22 October 2026; agreed by Coreper 21 October 2026), Data Act amendments at pp. 7 to 15 and 60 to 80. https://data.consilium.europa.eu/doc/document/ST-14756-2026-INIT/en/pdf
    Changelog
    • 9 November 2026: page created. Covers the Data Act as applied from 12 September 2025, FAQ v1.4 and the Council Omnibus mandate of 21 October 2026.