EU specifics — one or the other, and the fee stack | Faceless AI - Dataspheres AI

Design the EU build separately The EU is not just the US rules with a different flag. Under the DMA you may communicate and promote offers freely and link ...

Design the EU build separately The EU is not just the US rules with a different flag. Under the DMA you may communicate and promote offers freely and link users anywhere, but you must decide, per storefront, between Apple's in-app purchase and your own external payment — you cannot run both in the same EU app. Model the real cost External EU purchases carry the fee stack from Route C: an acquisition fee, a store-services fee, and a Core Technology Commission around 5%. For a low-priced subscription with high volume, that stack can approach or exceed the reduced in-app rate, so run the numbers for your actual price and mix before assuming external is cheaper. The exact figures were still being negotiated with the European Commission in mid-2026, so re-check them at build time. Storefront targeting Because the US, EU, and rest-of-world rules diverge, a serious build detects the user's storefront and shows the right flow: Route A in the US, Route C in the EU, in-app purchase where nothing better is allowed. Treat "which route runs here" as a configuration value, not a hard-coded assumption. Educational material, not legal or tax advice. App-store rules and the underlying court cases are changing month to month in 2026 — always confirm the current terms in Apple's and Google's own developer documentation before you ship, and get professional advice for your jurisdiction.