Guide · 7 min read
AI Content Disclosure for Apps in 2026: What Google Play and Apple Now Require
Google Play's AI-generated content disclosure rules went live April 15, 2026, and the July 2026 policy clarification extended them to third-party AI integrations — meaning if your app calls any LLM API and returns output to the user, the label requirement now applies to you. Apple's updated guideline 5.1.2(i) covers the data side: explicit user consent before personal data reaches any external AI service. Together, they create a two-track compliance problem most indie devs didn't see coming. Here's what each platform requires and where developers most often get it wrong.
What Google Play's AI disclosure rule requires: a visible label in the UI, not a privacy policy footnote
Google Play's policy, effective April 15, 2026, requires a visible label on any user-facing content generated by a generative AI model — text, image, audio, or video. The label must appear in the app interface adjacent to the generated output itself; a disclosure buried in your privacy policy or Play Store listing description does not satisfy the requirement. Google's policy uses the phrase 'readily visible and accessible to users,' which enforcement has interpreted as contextual placement near the output — not in a settings screen, not in an onboarding disclaimer, and not in a section of the app users rarely visit.
The rule applies to content generated at runtime in response to user input or user data. A chatbot reply, an AI-generated image rendered inside the app, a synthetic voiceover, a video clip created on demand — all fall under the policy. The label itself does not need to be long: Google's own documentation shows simple inline tags like Generated by AI or AI-created positioned immediately below the output. What enforcement scrutinizes is proximity and readability. A sub-10px badge tucked into a corner will not satisfy review the same way a clearly readable inline tag does.
The July 15, 2026 policy update added one extension that changed the compliance scope for many apps: the labeling requirement now explicitly covers third-party AI integrations. If your app passes user input to an external LLM or image generation API and displays the result, your app must label that output — even when your code is a thin wrapper around another provider's model. The responsibility runs through you, not the API provider. Developers who assumed that using OpenAI, Gemini, or any other external AI service transferred compliance responsibility away from them need to revisit that assumption immediately.
The 4 AI output types that trigger labeling — and 2 common features that do not
Four content types trigger Google Play's disclosure requirement: generated text (chatbot replies, AI-written summaries, AI-composed email drafts), AI-generated images (images synthesized from text prompts or image-to-image transforms), AI-generated audio (synthetic voiceovers, voice cloning, music composition), and AI-generated video (clips produced by a generative model from any input). If your app produces any of these at runtime from user input or data, the label is required on every instance of that output.
Two categories that fall outside the labeling rule: recommendation systems and AI-assisted input features. An algorithm that ranks content, suggests products, or curates a feed based on user behavior does not require an AI-generated content label under the current policy. Autocorrect, predictive text, and grammar suggestions are also exempt. Google's policy draws the line at whether the model is generating new content versus assisting the user in composing or discovering content they control. When AI is producing something the user did not write — a generated reply, a synthesized image — it needs a label. When it is improving something the user wrote, it does not.
One edge case that regularly catches indie developers off guard: AI-generated static listing content. If you used a generative AI tool to write your Play Store description or to create your feature graphic, Google's separate policy for app store metadata expects disclosure in your listing itself. This is distinct from the runtime labeling requirement and enforced at submission review rather than post-launch monitoring. The practical rule: any static content in your listing that was generated by AI should be noted in your description using a brief human-readable acknowledgment. For Play Store asset specifications, see the Play Store feature graphic size and design guide — the graphic is the first asset reviewers evaluate for metadata policy compliance.
How to build a compliant AI label that does not hurt your UX
Compliant AI labels in well-designed apps look nothing like cookie banners. The pattern that works is an inline micro-tag — small, lower-contrast text reading Generated by AI placed immediately below the AI output, styled the same way a timestamp or source attribution would be styled. The label is discoverable by any user who looks, without dominating the UI or interrupting the reading flow. A chat card showing an AI-generated reply might display the reply at full contrast and the label at 60% opacity beneath it. That balance is exactly what 'readily visible and accessible' asks for.
For image-generating features, icon-based labeling is the common approach: a small AI badge overlaid on the image with an optional tap-to-expand explanation. The badge works for generated images, AI video thumbnails, and AI-composed cover art. The tap-to-expand panel is optional if the badge itself is legible and close to the content — it becomes most useful when you want to name the underlying model or offer a way to flag problematic outputs. Google requires in-app user reporting or flagging for AI-generated content, so users can report policy-violating outputs without leaving the app. Build that reporting flow into the same component that renders the content, not as a buried support link.
The compliance failure that most often triggers a Play Store warning: AI labels placed only in a settings screen or account profile page, rather than adjacent to the generated output itself. Google's reviewers test by using your AI features directly and looking for contextual labeling on the results. If your chatbot produces responses with no per-response label — even if a settings page discloses that AI powers the feature — you will receive a warning. The fix is architectural: build the label into the rendering component, not into a global disclosure panel. Once it is in the component, it shows up wherever that component renders, and you never have to think about it again.
Apple's guideline 5.1.2(i): explicit consent before personal data reaches any third-party AI
Apple's AI compliance requirement is structurally different from Google Play's. Rather than requiring labels on AI output, guideline 5.1.2(i) requires explicit user consent before any personal data is transmitted to a third-party AI service. The rule covers any API call that includes user-identifying data — name, location, health records, usage history, message content, or photos. If your app sends a user's journal entries to an external LLM to generate a summary, the user must explicitly consent to that data transfer before your first API call. Disclosure alone is not sufficient; consent must be affirmative and documented.
Three things the consent UI must cover: the AI provider by name (not 'a third-party service' — the actual provider), the specific purpose of the data transfer (not 'to improve your experience' — the actual operation), and an opt-out path that does not degrade the non-AI portions of your app. Apps that gate core functionality behind AI consent — where declining breaks features unrelated to AI — have been flagged during App Store review. The consent must be proportionate and genuinely voluntary. Apple's privacy nutrition labels are a separate but adjacent requirement; the App Store privacy labels guide covers which data type categories to declare and how declared data maps to the guideline 5.1.2(i) consent surface.
For most indie apps, this requirement means auditing every LLM API call and asking: does the prompt include any data derived from this specific user? Message history, health stats, location context, preferences, and behavioral data all qualify. The safest implementation is a consent gate at feature activation — the first time the user triggers an AI feature — rather than at onboarding, where blanket AI consent feels disconnected from the moment of actual data sharing. The App Store Connect submission process now asks whether your app integrates third-party AI; the App Store Connect guide for first-time submitters explains how these questions affect your review queue priority and what reviewers check during inspection.
Enforcement timeline: what April 15, July 15, and your next submission mean in practice
Google Play's AI content rules became enforceable April 15, 2026. Minor violations — typically missing labels or inadequate placement — result in a warning and 7 to 14 days to fix. Major violations — apps generating harmful, deceptive, or exploitative content without safeguards or moderation — proceed directly to suspension without a warning window. The July 15 update, which extended the rule to third-party integrations, is now an active enforcement priority. Apps that were compliant for their own AI features but added a third-party LLM integration after April without updating their labeling may now be in violation without knowing it. The audit question is not 'does my app have AI' but 'does every AI output surface have a visible label.'
Apple's enforcement mechanism for 5.1.2(i) is app review rejection at submission rather than post-launch suspension. Apps submitted with third-party AI integrations and no consent flow are rejected before going live, and resubmission requires demonstrating the consent UI during the review session itself — reviewers test it, not just look at screenshots of it. This makes the consent gate a hard launch blocker, not a deferred fix. The cost calculation is straightforward: building the consent flow correctly before submission takes hours; a rejected submission that delays a planned launch date costs days and — for apps tied to PR cycles, press embargoes, or promotional campaigns — significantly more.
If your app reaches users in the European Union, the EU AI Act adds a parallel compliance obligation for synthetic media. Any content generated by AI that could be mistaken for a real person (synthetic voice, deepfake video, AI-written text presented as authored by a human) must carry machine-readable disclosure metadata in addition to the visible label. Most consumer apps with standard LLM features fall into the general-purpose AI category with lighter obligations, but the synthetic media rule applies regardless of risk classification. For the broader context of how Google Play compliance obligations are expanding in 2026, the Google Play billing flexibility guide covers the other major policy shift this year — reduced commissions and third-party payment processor rules — that affects monetization decisions alongside disclosure requirements.
Audit your AI integration before the next Play Store review cycle
The practical checklist: map every place your app produces user-visible AI output (that is your Google Play label surface), then map every place your app sends user data to an external model (that is your Apple consent surface). Build the label and consent flows into the components that generate those outputs — not into a settings page, not into an onboarding modal, not into a privacy policy. Both platforms are testing for contextual, in-context disclosure; a global disclosure panel elsewhere in the app does not substitute for it.
Apps that get this right have a structural advantage: the compliance work is done once in the component layer and automatically propagates to every feature that uses AI output, including features added in future updates. Use the screenshot editor to update your listing screenshots if you are adding AI feature highlights — the disclosure architecture should be visible in your screenshots the same way it appears in the app.
Update your listing screenshots →
Frequently asked questions
does google play require ai labels for chatgpt api integrations
Yes. As of July 15, 2026, Google Play's AI content labeling requirement explicitly covers third-party AI integrations, including apps that pass user input to the ChatGPT, Gemini, Claude, or any other external LLM API and return the output to users. Your app must label each piece of generated output visible to users — regardless of which model produced it. The responsibility for compliance sits with the developer, not the API provider.
what does app store guideline 5.1.2i require for ai
Apple's guideline 5.1.2(i) requires explicit user consent before any personal data is transmitted to a third-party AI service. The consent UI must name the specific AI provider, explain the specific purpose of the data transfer, and offer a genuine opt-out that does not break non-AI features of your app. It applies to any LLM API call where the prompt includes user-identifying data — messages, health stats, location, usage history, photos, or any other personal data. Apps submitted without a compliant consent flow are rejected during App Store review.
do i need to label ai-generated images in my app
Yes — AI-generated images are one of the four content types explicitly covered by Google Play's AI disclosure policy. Each generated image displayed to users must carry a visible AI label adjacent to the image. Apple's guidelines do not have a separate image-labeling rule, but the EU AI Act requires machine-readable disclosure metadata on synthetic images that could be mistaken for real people, which applies if your app reaches European users.
does using a third-party ai api mean i need user consent on ios
It depends on whether your API calls include personal user data in the prompt. If you call an LLM API with a generic prompt that contains no user-identifying information, the consent requirement does not apply. If the prompt includes anything derived from that specific user — message history, health data, location, behavioral patterns, or photos — explicit consent is required before the first call. The distinction is whether the data shared is personal to the individual user, not whether the AI output is personalized.
what happens if my app fails google play ai content review
Minor violations — such as missing labels or labels placed in the wrong location — result in a warning with 7 to 14 days to fix the issue. Major violations — apps that generate harmful, deceptive, or policy-violating content without safeguards — go directly to suspension. Repeat violations after a warning can escalate to permanent removal. If your app generates content via AI features and fails review, the fix is typically adding contextual labels to the rendering component for each AI output surface and resubmitting; it does not require architectural changes to the AI features themselves.