Skip to content

EU Digital Fairness Act: what the proposal means for apps

Filip LuchianencoUpdated 7 min read

Last updated: 2026-11-17

On November 11, 2026, the European Commission proposed the Digital Fairness Act (DFA), COM(2026) 1100 final, procedure 2026/0356(COD): a regulation that would replace the Unfair Commercial Practices Directive 2005/29/EC and add rules on dark patterns, addictive design, in-app currencies, loot boxes and personalised ads. Under Article 3(11), an "online interface" is any software "including a mobile application" operated by or on behalf of a trader.

The Digital Services Act bans profiling-based ads to known minors on online platforms only. Article 12 of the DFA would apply that ban to every trader, including providers of advertising services (recital 59). The DFA is a proposal; Parliament and Council have to agree on a text before any of it binds an app.

What is the status of the Digital Fairness Act, and when would it apply?

On November 17, 2026, the stage in the European Parliament's Legislative Observatory file for 2026/0356(COD) was "Preparatory phase in Parliament", and the committee responsible was "Pending final decision on the referral". One meeting with an interest representative is recorded in the file's transparency section: Kim van Sparrentak, an IMCO shadow rapporteur, met Supercell Oy on November 10, 2026. From the Commission press release: "The proposals will now be discussed by the European Parliament and Council."

Under Article 40, the regulation would enter into force 20 days after publication in the Official Journal and apply 12 months later, directly in every Member State. The DFA proposal and a Simplification Directive are on the Commission's Digital Fairness Act page. On the same day, the Commission adopted a separate proposal to replace the Consumer Protection Cooperation (CPC) Regulation; under it, the Commission would have direct investigation and fining powers, as described in the press release.

What does Article 12 change for ads shown to minors in apps?

Article 12 of the proposal:

Traders shall not target advertisements to a consumer based on profiling as defined in Article 4, point (4) of Regulation (EU) 2016/679: (a) by using personal data of the consumer where the trader is aware with reasonable certainty that the consumer is a minor; (b) by using special categories of personal data of the consumer referred to in Article 9(1) of Regulation (EU) 2016/679.

A minor is anyone under 18 (Article 3(16)). Under the same article, compliance "shall not oblige traders to process additional personal data to assess whether the consumer is a minor". Online platforms already covered by Section 3 of Chapter III of the Digital Services Act are excluded; for them, the same minors ban is in DSA Article 28(2), and the special-categories ban in Article 26(3). In the Commission's questions and answers: "The DFA will extend these bans to all websites and apps."

The ban would apply beyond the app developer. From recital 59:

these prohibitions should apply to all traders, including providers of advertising services, that target or facilitate the targeting of advertising, such as by selecting the advertising content, selecting the targeting and ad-delivery criteria, providing the data used for the targeting and delivery of an advertisement, providing the targeting techniques and ad-delivery techniques, and delivering and disseminating an advertisement.

On that wording, the functions of an ad network, a supply-side platform and an ad mediation SDK inside an app are all on the list. Under recital 59, the ban would also apply to "personalised content suggestions, product rankings and recommendations", "including in natural language systems".

The ban turns on knowledge: whether the trader is "aware with reasonable certainty". One test for that knowledge is in recital 62, on virtual currencies: where a product is accessed through a customer account "that allows the trader directly or indirectly to establish that it belongs to a minor", the trader "should be considered to be aware with reasonable certainty". An app that collects a birth date at sign-up has the user's age on record. Whether an ad SDK that receives no birth date is "aware with reasonable certainty" that the user is a minor is an open question under the draft text.

Which in-app purchases and game mechanics does the proposal restrict?

The minors rules in Articles 14(2), 15(3) and 16 apply where a trader's products "are directed at minors" or the trader "is aware with reasonable certainty that the product is used by minors". The first test is in recital 62: a product with an age rating, "such as" PEGI or an app store rating under the EU KIDS Act, "that indicates that the product's use is appropriate for persons under the age of 18". On that wording, a game rated PEGI 12 is directed at minors.

Article Mechanic All consumers Minors
12 Profiling-based ads Special-category data banned Banned where the trader knows with reasonable certainty
13 Personalised prices from profiling Banned where the trader knows with reasonable certainty that the consumer is vulnerable and harm is likely Banned where the trader knows with reasonable certainty and harm is likely
14 Paid virtual currencies Price shown in real money Off by default; on only with parent or guardian approval
15 Paid loot boxes ("variable reward systems") Odds and item types disclosed; a tool to disable them Banned
16 Pay-to-progress and pay-to-win Applies to minors only Banned
17 Addictive design features A tool to disable each one, or all at once Same tools; traders under KIDS Act Articles 9, 14 and 15 excluded for minors

Source: proposal, Articles 12 to 17.

Under Article 3(18), a paid-for variable reward system is a virtual item "offering random rewards or variable odds" bought with money or paid virtual currency; recital 63 gives "loot boxes, wheels of fortune, or collectible card packs" as examples. Under Article 3(19), pay-to-win covers in-game or in-app purchases "that are necessary or are presented as necessary for in-game or in-app progress or success". Social networks, video-sharing platforms, AI companions and general chatbots are excluded from the loot box ban for minors in Article 15(3); they fall under Article 13(2) of the EU KIDS Act proposal.

What counts as addictive design under Article 17?

Under Article 17(1), a trader whose product is "intended, or can reasonably be foreseen to encourage compulsive or excessive use" would have to give consumers tools to switch off, one by one or all at once, these features:

    1. autoplay and "uninterrupted content consumption" without regular breaks;
    1. notifications not triggered by, or not directly related to, the consumer's own activity;
    1. features rewarding engagement "at regular times or with greater frequency, including through penalties or loss of benefits for failing to engage regularly";
    1. "features and system behaviours that encourage continued use by simulating interpersonal relations, such as persistent prompts to continue engaging with an automated system".

From recital 66: "video games may incentivise engagement by penalising the consumer if they do not engage; AI companions and general conversational chatbots, in turn, may simulate interpersonal relations to incentivise prolonged use." Chatbot disclosure under the AI Act is covered in our post on Article 50. Two groups are excluded from Article 17: traders subject to KIDS Act Articles 9, 14 and 15 "for practices concerning minors", and traders providing services in KIDS Act Article 2(4) points (c) and (e). Under Article 17(2), the Commission can add features to the list by delegated act.

Two of the ten dark patterns in Part III of Annex I, which Article 10(2) regards as unfair "in all circumstances", are point 58, "Persistently requesting that consumers make a choice or change their choice where that choice has already been made" and point 62, refusal or withdrawal steps "disproportionately more numerous, complex or time-consuming than is reasonably necessary". Point 58 has one exception, a repeated request "necessary for the trader to comply with legal requirements". From iOS 27.2 in the EU, Apple's App Tracking Transparency sheet is shown again one year after the user's last answer, a denial included, unless the user has turned off the Settings switch for tracking requests.

Who enforces the DFA, and what are the fines?

National consumer authorities and courts enforce the regulation under Article 30. For traders within the KIDS Act, the authorities designated under that act enforce Articles 14(2), 15(3) and 16; for online platforms and AI systems, the Digital Services Act and AI Act authorities enforce Article 17(1) (Article 30(5)).

Under Article 35, Member States would have to set the maximum fine in coordinated cross-border cases at "at least 4% of the trader's annual turnover in the Member State or Member States concerned", or at least €2 million where turnover data is unavailable. The Commission "may impose fines not exceeding 6% of the trader's worldwide annual turnover" in cases it investigates under the revised CPC Regulation. Per the Commission's Q&A, it can act directly "when a breach is likely to affect consumers in at least two-thirds of EU Member States, representing at least two-thirds of the EU population", against a company that is not an SME.

Under Article 34, a claimant who has "presented facts and evidence sufficient to support the likelihood" of an unfair online practice can ask a national court or administrative authority to order the trader to disclose evidence on "the design, operation and impact on the behaviour of consumers" of that practice; under Article 34(5), a failure to disclose may be considered "a relevant element in establishing the unfairness" of the practice. Under Article 36, a trader held liable because of an act of a business partner "shall be entitled to pursue remedies against that person"; on that wording, an app held liable for targeting done by its ad SDK provider would have a claim against that provider.

What does a CITT scan and capture show for the Digital Fairness Act?

The CITT rules behind the findings below are drawn from laws in force (the engagement-reward rule from Nebraska LB 504 and the UK Age Appropriate Design Code). The DFA is a draft, so any reading of these findings against it compares a current build with a proposed text. When I scan an Android build with CanITrustThat (CITT), the static report contains the ad and attribution SDKs in the build, each with the file it was found in; the Play content rating and child-directed signals of the listing, recorded with the scan; the Play Billing permission in an app that appears directed to children; engagement-reward text such as "daily reward", "keep your streak" or "spin the wheel" in the resources of such an app; the Play Age Signals library beside an ad or attribution SDK; and an LLM API host in the same build as an ad SDK. That is presence in the build; whether the code runs is established on a device.

In a traffic capture on a test device, each request is logged with its host, its body and whether it was sent before or after consent, so the advertising ID, device attributes and any child-directed or under-age flag sent to an ad host are in that log. The "reasonable certainty" test turns on what the trader knows about a user's age, which is outside the build; where an app or SDK sends an age or birth date to an ad host during a session, that request is in the capture log. Loot box odds screens, pay-to-win prompts and streak penalties are recorded in the screen video of a device session when they appear during that session. See what a scan checks and the limits of a scan.

A related post covers Italy's Garante fine against Meta over Facebook's camera roll access, a decision under Italy's transposition of the ePrivacy Directive's consent requirement for access to information stored on a phone, in that case photos and videos.

I run these investigations for lawyers and for researchers working with lawyers, on one app or a list of apps in bulk. Sign up for a CanITrustThat account to run your own research, let us run an investigation for you, or read the teardowns.

App privacy law, applied to real apps.

Posts on new laws, fines and studies, and teardowns of the apps those laws apply to.

How we use your address: privacy notice. Prefer a feed reader? Use the RSS feed.