Apple Updates App Store Rules to Ban AI Nudify Apps and Hidden Bait-and-Switch Features


 

Apple is tightening its grip on the App Store's worst offenders. On October 16, 2026, the company updated its App Review Guidelines with new rules that explicitly target AI "nudify" apps generating nonconsensual intimate images, and ban apps that hide harmful features until after they pass review, as reported by 9to5Mac.

The update arrives after a year of investigations exposed dozens of predatory apps on the store — and it gives Apple's review team written rules to point at when removing them. Here's what changed and why it matters for every iPhone user.

Rule 1.2: Developers Must Now Proactively Remove AI Deepfakes

The revised Guideline 1.2, which covers user-generated content, now names nonconsensual intimate imagery as one of the core risks for apps that let people "create, generate, upload, share, or otherwise contribute content." Crucially, it explicitly lists AI content creation apps alongside social media and user-generated content platforms.

Developers are now required to proactively prevent and remove nonconsensual, sexual images — including those made with AI tools — as part of content moderation. Apps that fail to implement adequate safeguards, or fail to fix violations after Apple gives notice, can now be treated as violating the Developer Code of Conduct and removed from the App Store.


New Guideline 2.5.19: No Hidden or Dormant Features

The standout addition is the brand-new Guideline 2.5.19, which bans hidden, dormant, or undocumented features outright. In Apple's words:

"Don't include any hidden, dormant, or undocumented features in your app; your app's functionality should be clear to end users and App Review. Attempting to hide undocumented features in your app binary, such as through code obfuscation or other methods, is grounds for removal of your app from the App Store and termination of your developer account."

This targets "bait-and-switch" apps — ones that look clean and harmless during review, then unlock different capabilities once live. Apple explicitly names nudification as one such feature that has appeared only after approval. The ban on hidden features previously lived under Guideline 2.3.1; the new wording calls out tricks like code obfuscation directly, with removal and developer-account termination as the penalty.


Section 5: Tougher Stance on Exploitation

Section 5, covering legal matters, was also strengthened. Apps found to facilitate human trafficking or the sexual exploitation of children will now be removed from the App Store and blocked from alternative distribution — extending the ban past Apple's first-party store into the sideloading channels it was forced to open in some regions.

Why Apple Acted Now

The policy updates follow a trail of reporting and enforcement earlier this year:

  • January 2026: the Tech Transparency Project flagged AI "nudify" apps operating on the App Store
  • July 2026: an investigation surfaced gambling apps disguised to target children in Brazil
  • 2026: Apple privately warned xAI over Grok's capacity to generate nonconsensual imagery — xAI later added safeguards and received approval for an updated version
  • 2026: local removal orders in San Francisco targeted offending apps

The new rules formalize those enforcement actions, making content filters, reporting tools, and remediation plans a condition of staying listed — pushing user-generated-content and AI app makers to build safeguards or risk removal.






What It Means for Users

For everyday iPhone users, the change should mean fewer predatory apps slipping through review disguised as something innocent. For developers, it raises the bar: safeguards against AI-generated nonconsensual imagery are no longer optional, and anything the app can do must be visible at review time. The open question is enforcement — regulators and researchers will be watching how strictly Apple applies the new rules and whether bad actors simply shift tactics or platforms.

Disclaimer: App Store policies may be updated again; check Apple's developer guidelines for the current rules.




Post a Comment

Previous Post Next Post