Apple Introduces Alternative App Tracking Transparency Prompt for EU Developers

Apple will let developers use a different version of its App Tracking Transparency prompt in the European Union beginning with iOS 27.2 and iPadOS 27.2, while the underlying rules for when permission is required stay unchanged.

The news

Apple is updating its App Tracking Transparency framework in the European Union. The change stems from agreements with select European competition authorities. Starting in iOS 27.2 and iPadOS 27.2, developers gain the option to present an alternative system prompt when asking for tracking permission. The conditions that trigger the need for permission remain the same as before.

Context

Previously, the App Tracking Transparency prompt followed a single design across all regions where the requirement applied. The new arrangement creates a regional variation limited to the EU. In five specific countries—Germany, France, Italy, Poland, and Romania—only the alternative prompt may be used for apps distributed there. The update also adds a provision that allows developers to show the prompt again one year after a user’s prior choice.

Developers must still obtain permission before tracking users across apps and websites owned by other companies. The timing of when that permission must be sought does not shift. For users in Germany, France, Italy, Poland, and Romania the alternative version is the sole option presented by the system. Across the wider EU, developers may issue a fresh request through the App Tracking Transparency flow twelve months after the user last responded in that app.

The change applies at the operating-system level once iOS 27.2 and iPadOS 27.2 ship. No other regions receive the alternative prompt. The one-year reprompt window is stated as a new capability available for EU users and is tied directly to the App Tracking Transparency system prompt.

Details

The alternative prompt is available only inside the EU. Developers must still obtain permission before tracking users across apps and websites owned by other companies. The timing of when that permission must be sought does not shift. For users in Germany, France, Italy, Poland, and Romania the alternative version is the sole option presented by the system. Across the wider EU, developers may issue a fresh request through the App Tracking Transparency flow twelve months after the user last responded in that app.

The change applies at the operating-system level once iOS 27.2 and iPadOS 27.2 ship. No other regions receive the alternative prompt. The one-year reprompt window is stated as a new capability available for EU users and is tied directly to the App Tracking Transparency system prompt. Because the source material specifies these constraints without further technical description of the alternative prompt itself, the exact wording or layout differences remain unspecified beyond the fact that an option now exists.

Why it matters

The modification gives developers a second interface option inside the EU while preserving the same consent threshold that already exists. For teams that ship in Germany, France, Italy, Poland, or Romania the choice disappears and the alternative prompt becomes mandatory. The one-year reprompt rule creates a defined interval at which developers can again surface the request, something not previously available under the framework. Because the underlying permission requirement is unchanged, the practical effect is limited to the wording and layout of the dialog rather than the scope of tracking that needs consent.

Developers operating across the EU will need to test both prompt variants and adjust any custom flows that rely on the original presentation. The update reflects a narrow accommodation reached through regulatory agreements rather than a broad redesign of tracking controls. Teams maintaining apps in the listed countries face an immediate requirement to adopt the alternative prompt once the operating-system versions ship, while those active in the remaining EU member states retain flexibility but must handle the new reprompt timing in their consent logic. The result is incremental adjustment rather than wholesale revision of how tracking consent is collected.

---

Sources:

No comments yet