Skip to content
Technical note· 6 min read
Published: Updated:

If your app uses AI: Apple's Guideline 5.1.2(i) and the consent screen

App Review Guideline 5.1.2(i) requires you to clearly disclose, and get explicit permission, before sharing personal data with third parties, including third-party AI. The exact wording, who it covers and how to build the consent screen.

Short answer

Apple's App Review Guideline 5.1.2(i) requires you to clearly disclose where personal data will be shared with third parties, including third-party AI, and to obtain explicit permission before doing so. Apple added the words "third-party AI" as a clarification on November 13, 2025. In practice, that means showing a consent screen before the AI feature sends data for the first time.

Free toolApp Store review pre-check list

If your app sends text, photos or audio from users to an AI service from a provider such as OpenAI, Anthropic or Google, Apple requires you to disclose this clearly and get explicit permission first. The rule is in section 5.1.2(i) of the App Review Guidelines.

What exactly does the rule say?

The relevant sentence in item (i) of section 5.1.2 (Data Use and Sharing):

"You must clearly disclose where personal data will be shared with third parties, including with third-party AI, and obtain explicit permission before doing so."

So you must clearly disclose where personal data will be shared with third parties, third-party AI included, and get explicit permission before doing so. The first sentence of the same item prohibits using, transmitting or sharing someone's personal data without first obtaining their permission, unless otherwise permitted by law.

Apple added the words "third-party AI" in its November 13, 2025 guidelines update and described it as a clarification, not a new rule. The guidelines give no separate effective date.

One more section is relevant: 5.1.1(ii) requires an easily accessible and understandable way for users to withdraw consent.

Who does it cover?

Every app that sends personal data from users to a third-party AI service. Examples:

  • A chat feature that sends the user's question to a model such as ChatGPT, Claude or Gemini
  • A feature that uploads a photo to an AI API for image analysis
  • A feature that sends the user's text to an external service for summarizing or translation
  • A feature that sends voice recordings to an external service for transcription

If you run the model on your own servers, the data doesn't go to a third party, so the "third-party AI" sentence may not apply directly. But the first sentence of 5.1.2(i) and the permission requirement in 5.1.1(ii) still do.

Show a consent screen before the user first uses the AI feature, that is, before any data is sent. Our suggested content:

  1. Provider: name where the data goes, for example "OpenAI" or "Google". Just saying "AI" doesn't clearly disclose where the data is shared.
  2. Data type: concrete wording such as "the text you type" or "the photo you upload".
  3. Purpose: "to generate an answer to your question", "to summarize the text".
  4. The provider's privacy policy: so users can read it if they want.
  5. Two choices: "Accept" and "Decline". Explicit permission means the user actively agrees; don't use pre-ticked boxes.

Example text

About AI assistance. This feature uses OpenAI's service to answer your questions. Data sent: the text you type. Purpose: to generate an answer to your question. Do you want to continue? Decline / Accept and continue.
  • Save the choice; you don't need to ask on every use.
  • Offer a way to withdraw permission on the Settings screen (5.1.1(ii)).
  • If different features send data to different providers, get separate consent for each.
  • Ask again when you change the provider or the data you send.
  • Describe the same sharing in your app's privacy policy and in the App Store privacy information.

The KVKK side

For users in Turkey, KVKK's explicit consent principles also apply. Under the granular consent principle the Authority highlighted in its January 14, 2026 announcement on push notifications, users must be offered a separate, independent choice for each purpose.

If the AI provider's servers are outside Turkey, KVKK's rules on transfers abroad (Article 9) also apply. The Authority's "Use of Generative AI Tools in Workplaces" document, published on March 5, 2026, covers employees' use of such tools; it doesn't directly regulate in-app consent flows.

To design the consent flow and the data flow together in an app with AI features, see our React Native app development service. Before you submit, go through the other rejection reasons with the App Store review checklist tool.

Frequently asked questions

Is a consent screen mandatory? The guidelines require clear disclosure and explicit permission before sharing personal data with third-party AI. It doesn't have to be a screen, but a consent screen is the clearest way to ask for permission explicitly, separately and before sharing.

Did this rule start in November 2025? Apple added the words "third-party AI" to the guidelines on November 13, 2025 and described it as a clarification. The requirement to get permission before sharing personal data already existed in 5.1.2(i).

What if I don't send personal data? If you only send content that contains no personal data (for example, the app's own text), the sharing sentence in 5.1.2(i) may not apply. Text users type or photos they upload can often contain personal data, so asking for consent is the safer choice.

Do I need to label AI-generated content? We found no separate item in the App Review Guidelines about labeling AI output. Labeling it is good practice so users aren't misled, but we don't present it as an Apple requirement.

Sources

#güncel#yapay zeka#app store

Have a project in mind?

A short description is enough; if it isn't clear yet, we can think it through together. We'll write back within one business day.

With your consent, we use analytics cookies to improve the site and measure visits. Cookie policy