Policy Insights · App Store

Apple's EU tracking prompt is optional in 22 countries and mandatory in five — and the new one-year re-prompt works both ways

Apple announced this on 16 September 2026 in Updates to App Tracking Transparency in the European Union. The change comes "as part of agreements with select European competition authorities" and begins with iOS 27.2 and iPadOS 27.2. Apple's Software Releases page listed iOS 27.2.1 on 9 November 2026, so 27.2 is already on devices; the exact 27.2 release date is not shown on that page today ([verify]).

Policy Insights ~6 min read
KEY TAKEAWAY

From iOS 27.2 the EU gets a second ATT system prompt, with different formatting and wording and an optional "Additional Information" button. It is optional across the EU but the only prompt available for apps distributed in Germany, France, Italy, Poland and Romania. EU users can be re-prompted one year after their previous ATT choice, whether that choice was accept or reject (unless they turned off the setting in Settings). What doesn't change: you still may not touch the IDFA or tracking data before the user grants permission in that prompt.

Optional in most of the EU, the only option in five countries

Apple's wording: developers "will have the option to use an alternative version of the App Tracking Transparency system prompt in the EU," but "due to legal requirements, only the alternative version of the system prompt is available for apps distributed in Germany, France, Italy, Poland, and Romania." The EU has 27 member states; the other 22 keep a choice. Apple has not named any other mandatory country. Do not write "the whole EU must switch," and do not write "the whole EU can ignore it."

What actually changes on screen

The alternative prompt has "modified formatting and language." The new API, requestTrackingAuthorization(preferExpandedInterface:additionalInformationAction:completionHandler:) (iOS / iPadOS 27.2), can show a full-page sheet instead of the usual alert, uses Markdown text from a new Info.plist key, NSUserTrackingMarkdownUsageDescription, and adds an "Additional Information" button only if you pass an action. Apple's documentation splits the behaviour by region:

  • France, Germany, Italy, Poland and Romania: the system shows your Markdown text in a full-page sheet *regardless* of what you set for preferExpandedInterface, plus the Additional Information button if you supply an action.
  • Rest of the EU: the system displays the Markdown text from NSUserTrackingMarkdownUsageDescription if you supply it. The full-page sheet appears if you set preferExpandedInterface to true, and includes the Additional Information button if you supply an action.
  • Outside the EU: the system ignores both parameters and shows the original alert with NSUserTrackingUsageDescription.

The Markdown key is optional; without it the system falls back to NSUserTrackingUsageDescription. The regional behaviour depends on the device being in the relevant EU country *and* signed in with an Apple Account set to that country or region. What happens in the five countries if an app still calls only the older requestTrackingAuthorization(completionHandler:) is not spelled out on the pages we read ([verify] on a device in one of those countries before shipping).

The one-year re-prompt is symmetric

On Apple's User Privacy and Data Use page: for users in the EU, "you can reprompt a user … one year after the user's previous choice … regardless of whether that choice was to accept or reject." The API documentation adds the mechanics: once a person answers, the system notes the date and will not show the prompt again until a year passes. The one exception: a user cannot be re-prompted if they turned off "Allow Apps to Request to Track" — renamed in the EU to "Allow Apps to Request to Link Your Activity Across Companies" — in Settings > Privacy & Security > Tracking. So a year-old *yes* can be asked again too. Plan for that in your consent records, not only for re-asking people who said no.

The Additional Information button is yours to fill — and yours to answer for. It can lead to more information and more granular consent controls, for example to meet ePrivacy or GDPR. Apple's FAQ says that content is "entirely your responsibility." Tapping the button dismisses the sheet *without* recording an answer: your completion handler receives notDetermined, your action runs, and you show your own screen. You may then send the user back to the ATT prompt so the choice is recorded — but Apple says you "should not redirect users to your ATT prompt if they have opted out of all relevant legal consent choices in the screen or page surfaced." The button is optional; it is not a ready-made GDPR consent tool and does not replace your own consent management.

What does not change

"The requirements for when you must seek permission to track users will remain the same." Until the user grants permission *in that prompt*, you cannot read the advertising identifier or otherwise collect and use the data the prompt describes. App Review Guideline 5.1.2(i) still applies: you must get explicit permission through the App Tracking Transparency APIs to track, and the app may not require tracking to access features, content, or "monetary or other compensation." Apple's FAQ answers "Can I gate functionality … or incentivize users to agree?" with a plain "No."

What to do

  1. List where your EU builds are distributed. If the app reaches Germany, France, Italy, Poland or Romania, treat the alternative prompt as required there: adopt the new API, write NSUserTrackingMarkdownUsageDescription, and test on a device signed in to an account set to one of those countries.
  2. For the other 22 EU countries, decide on purpose whether to request the expanded sheet (preferExpandedInterface). Apple’s page says the Markdown text is shown if you supply it, and the full-page sheet appears when that flag is true.
  3. Before adding the Additional Information button, write down what the screen behind it shows, and the rule for when you send the user back to ATT: never after they have opted out of all relevant consents on that screen.
  4. Add the one-year re-prompt to your consent calendar for both earlier answers, yes and no. Never re-prompt a user who has turned off the request setting in Settings.
  5. Check that no feature, content, coin, or reward depends on tapping Allow (5.1.2(i)).

What this article is not

It is not about EU payments or commission; that is a separate article: Apple's new EU business terms: commission and external payment. It is not a reread of the 16 October 2026 App Review Guidelines update. It is not a loosening of tracking rules, and it does not predict opt-in rates; Apple has published none. It is not legal advice on GDPR or ePrivacy.

Not legal advice. Wording is quoted or paraphrased from Apple's public news post, the User Privacy and Data Use page, the App Tracking Transparency developer documentation, and the App Review Guidelines. Follow the current pages and test on real devices before you ship.