EU AI Act, DSA & DMA: What They Actually Mean for Your App's ASO in 2026

Three different EU laws landed on app developers' desks in the same year, and most explainers blur them into one vague "EU compliance" panic. They're not one thing. Each targets a different part of your app, and only some of it is your job to fix.

If you sell an app in the European Union, you've probably seen three acronyms pile up in your inbox this year: the AI Act, the DSA (Digital Services Act), and the DMA (Digital Markets Act). Somewhere in the noise, someone told you this affects your App Store Optimization. That's true — but not in the way most summaries explain it, and not equally for every app.

This guide separates the three laws by what they actually regulate, tells you plainly which parts are your responsibility versus Apple's or Google's, and walks through one worked example so the abstract rules turn into an actual decision you can make this quarter.

The mental model: three laws, three different targets

The fastest way to stop confusing these three is to stop thinking of them as "EU tech law" and start thinking of them as regulating three separate layers of your app's existence:

• The AI Act regulates what your app says. If any part of your app uses AI to talk to users, generate content, or make decisions about them, this is about disclosure and labeling — not your store listing, your actual product behavior.
• The DSA regulates how your app is shown to people. This is mostly a burden on Apple and Google as platform operators (ad labeling, why-am-I-seeing-this explanations, recommender transparency) — but it changes what you'll see when you buy Apple Search Ads, and what your own in-app ads or referral programs need to disclose if you run them.
• The DMA regulates how your app is sold and distributed. This is the one with real strategic weight for ASO: new distribution channels, new payment options, and a completely restructured fee table that changes the math on where you should sell.

Only one of these three (the AI Act) asks something specific of your app's own code and content. The other two mostly reshape the environment your app sits in — but that environment now includes real new options and real new costs worth understanding before your next pricing or distribution decision.

The mechanics: what each law actually requires

AI Act — Article 50 transparency rules

The AI Act's transparency obligations (Article 50) began enforcement on 2 August 2026. They apply narrowly, to four specific situations, not to "having AI in your app" broadly:

• If users interact directly with an AI system (a chatbot, a voice assistant, an AI agent) and it isn't obvious they're talking to AI, you must disclose it.
• AI-generated or AI-altered content needs a machine-readable mark so it can be detected automatically.
• Deepfakes — AI-edited or generated images, video, or audio depicting real people or events — must be labeled as such to users.
• AI-generated text published on matters of public interest needs disclosure that it wasn't human-written.

Generative systems already on the market before the enforcement date get a grace period on the machine-readable marking piece specifically, until 2 December 2026. The EU's AI Office also published a voluntary Code of Practice on Transparency of AI-Generated Content; signing it earns a presumption of conformity and generally lighter enforcement scrutiny, though it's optional. Penalties for non-compliance run up to €15 million or 3% of global annual turnover, whichever is higher.

For most indie apps, this affects a narrower slice than the marketing panic suggests: a to-do app with zero AI features owes nothing here. A journaling app with an AI-powered "summarize my week" feature needs to disclose that the summary is AI-generated. A photo app with an AI background-removal tool is a closer judgment call — probably fine without a special disclosure since it's an obvious, expected tool behavior, not an attempt to represent something as real that isn't.

Sources: European Commission — Digital Strategy news, "Commission starts enforcing AI Act rules and new transparency requirements on 2 August"; European Commission — Quick Facts: Transparency rules for AI systems; EU Artificial Intelligence Act (artificialintelligenceact.eu) — Article 50 practical guide.

DMA — distribution and the new fee table

The Digital Markets Act designates Apple and Google as "gatekeepers" and forces them to open up distribution and payments that used to be locked to their own App Store or Play Store. As of 2026, EU users can install apps through alternative marketplaces (AltStore PAL is one officially notarized example), sideload apps directly, and developers can process payments outside Apple's own system or link out to an external checkout entirely.

The part that actually moves ASO strategy is the fee restructuring Apple rolled out to settle its dispute with EU regulators, effective 1 October 2026:

*Reduced rates generally apply to smaller developers/qualifying programs and, for subscriptions, after the first year — check Apple's current terms for your exact eligibility.

This replaces the old flat €0.50-per-install Core Technology Fee that used to kick in after a million EU installs a year — a structure a lot of growing indie apps were quietly dreading. Apps distributed fully outside the App Store now pay a flat 5% instead, a meaningfully different number to plan around.

Distributing outside the App Store also comes with a real cost most explainers skip: your app has to go through Apple's notarization process, a baseline security/malware check, before an alternative marketplace can offer it. This isn't onerous, but it's a real extra step, not a free lunch.

Sources: Apple Developer — "Changes for apps in the European Union"; Apple — "Complying with the Digital Markets Act" (PDF); gHacks — "Apple Replaces Per-Install EU Core Technology Fee With a Flat 5% Commission"; Tech Times — "Apple EU Settlement Locks In 5% App Store Rate With Notarization Still in Place".

DSA — mostly a platform burden, with one thing you should check

The Digital Services Act is the least developer-actionable of the three. Its recommender-system transparency rules (platforms must plainly explain the main factors behind what they show you) and its ad-transparency rules (every ad must be clearly labeled, show who paid, and explain why you were targeted) apply to Apple and Google as the platform operators — not to your app directly.

The one place this touches your own work: if you run Apple Search Ads or in-app advertising of your own, the ad labeling and "why am I seeing this" disclosure requirements mean the platform will show more context around your ads than it used to. That's a UI change happening around your campaigns, not a compliance task for you — but it's worth knowing your ad copy and targeting choices are more visible to end users than before, since the platform is now required to explain them.

Sources: Apple Legal — Digital Services Act (DSA) page; AlgorithmWatch — "A guide to the Digital Services Act".

Worked example: Aria's note-taking app

This example uses a made-up developer and illustrative numbers to show how the three laws actually interact for one real-shaped app — not to represent anyone's real business.

Aria ships a note-taking app with an optional "AI summarize this note" feature, sells a monthly subscription through Apple's in-app payment, and runs a small Apple Search Ads budget. About 40% of her subscribers are in the EU.

• AI Act: applies. The AI summarize feature generates content, so it needs a visible "AI-generated" label on summaries and — once the marking grace period ends in December — a machine-readable tag on that output. This is a product change, not an ASO one, but it's the one legally load-bearing item on her list.
• DSA: doesn't require anything new from Aria directly. Her Apple Search Ads will simply show more disclosure context to users than before; her ad copy and targeting don't need to change.
• DMA: this is where her actual decision lives. She's currently on the standard 26% App Store + Apple payment tier. The fee table above gives her three real alternatives worth modeling before renewing her annual plan.

At most realistic revenue levels, moving fully outside the App Store looks like the biggest fee win on paper — but Aria would lose App Store search visibility entirely, which is most of how she gets new subscribers today. For her, the link-out option is the more interesting middle path: she stays listed and discoverable in the App Store, and only pays the lower link-out rate on whoever actually converts through her own checkout page. The right answer depends entirely on how much of your growth is organic App Store search versus channels you already control — which is an ASO question, not just a finance one.

Decision framework: does this apply to you?

Your compliance checklist

Common mistakes

• Assuming this is only for "AI companies." The AI Act's disclosure rules apply to any app with an AI feature that generates or alters content, however small a part of the product it is.
• Ignoring the DMA fee changes because you're staying on the App Store. The new tiered structure applies whether or not you ever touch an alternative marketplace — it's worth re-checking your rate even if your distribution strategy doesn't change at all.
• Treating "notarization" as a formality. It's a real process with real turnaround time; budget for it before committing to an alternative-distribution launch date.
• Confusing DSA's platform-side obligations with a to-do list for your app. Most of the DSA's weight sits on Apple and Google, not on you — don't spend engineering time building disclosure UI the platform already handles.
• Treating the 2 December marking deadline as the real deadline. The core disclosure obligation started 2 August 2026; only the machine-readable marking piece has the later grace period.

TL;DR