What changed
On October 16, 2026 Apple revised its App Review Guidelines. Rule 1.2 now expressly includes apps that let users create or generate content, including AI content creation apps, and names nonconsensual intimate imagery among the material that must be prevented or removed. Developers that fail to maintain safeguards or respond to notices may violate the Developer Code of Conduct. Apple separated the longstanding ban on hidden, dormant or undocumented functionality into new rule 2.5.19 and expressly names attempts to conceal binary features through obfuscation as grounds for app removal and developer-account termination. Section 5 says apps facilitating trafficking or child exploitation may also be blocked from alternative distribution. The same update revises external-purchase-link wording in 3.1.1(a) and adds rule 2.3.14 for promotional creative assets. Apple has not claimed the pre-existing ban on pornographic or undisclosed functionality is new.
Why it matters
For developers shipping AI image generators, community apps or content-creation tools on iOS, moderation is no longer plausibly confined to conventional social-media uploads: generated outputs are explicitly in scope. Builders need a documented process for filtering, reporting, blocking and responding to violations, not just terms of service. Release engineers should ensure review notes, app behaviour and remotely enabled features agree, because a concealed capability can put the developer account at risk. The rules affect platform eligibility and operating cost, but they do not demonstrate that Apple has already increased enforcement or that any particular model provider is noncompliant.
AI-generated output is explicitly subject to moderation
Guideline 1.2 now covers apps that create, generate, upload or share user content, expressly including AI creation apps. It calls for filtering objectionable material, reporting mechanisms, user blocking and published contact details. It specifically identifies nonconsensual intimate imagery and makes failure to implement safeguards or remediate violations a potential Developer Code of Conduct breach. The exact implementation standard for generative-output filters is not prescribed in the text.
Hidden features now carry a clearer account-level risk
Guideline 2.5.19 prohibits hidden, dormant or undocumented features, including attempts to conceal functionality in the binary using obfuscation or other techniques. Apple can remove the app and terminate the developer account. The principle was previously covered under 2.3.1; the October change makes it a distinct rule and emphasizes enforcement. Legitimate code obfuscation is not automatically a violation; the stated target is concealment of undocumented features.
Alternative distribution and purchase links also change
Section 5 expressly extends certain serious exploitation-related removals to alternative distribution. Separately, 3.1.1(a) changes the language for permitted external-purchase-link destinations and consolidates music-streaming entitlement wording. Developers implementing regional alternative checkout should review the current entitlement and storefront rules rather than assuming all outbound links are permitted.
Operational checklist for builders
Review how an AI or community app handles generated and uploaded material; test reporting and blocking flows, moderation escalation and contact channels; keep the App Review demo account and release notes representative of production; document server-side feature flags and disclose changes that alter functionality. Review promotional assets under new rule 2.3.14. Track actual App Review decisions before treating the clarified text as evidence of changed approval rates.