Apple Has Rewritten App Review Around Features That Were Not in the Binary. The Penalty Now Lands on the Developer Account

Apple revised its App Review Guidelines on 16 October and announced it the way it announces most guideline revisions: a dated entry in Apple Developer News with a seven-line changelog and no press release. Two of those lines are aimed at the same problem, and it is a problem App Review was never built to catch — an app whose harmful capability is not present in the binary a reviewer approved.

What Apple says it changed

Guideline 1.2 now opens by naming the harms it covers and the apps it covers:

Apps that enable users to create, generate, upload, share, or otherwise contribute content present particular challenges, including intellectual property infringement, nonconsensual intimate imagery, and anonymous bullying. This includes social media, user-generated content platforms, and AI content creation apps.

According to 9to5Mac, "nonconsensual intimate imagery" and the sentence below are the additions in this revision:

Developers who fail to implement appropriate safeguards or fail to remediate identified violations after notice may be considered in violation of the Developer Code of Conduct.

The new Guideline 2.5.19 reads in full:

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.

Review inspects a build; these apps moved the feature

The nudification problem was never that Apple's reviewers wave through apps advertising nudification. It is that the apps do not advertise it. The Tech Transparency Project identified dozens of AI "nudify" apps on the App Store in January, and a follow-up in April reported that App Store search suggestions and ads were steering users toward them. In July, San Francisco officials ordered Apple to remove eight apps capable of generating nonconsensual intimate imagery.

The same mechanism showed up in a different category. A 9to5Mac investigation in July found dozens of App Store apps presenting as games or utilities that revealed hidden betting platforms when opened from Brazilian IP addresses, many of them available to children. In both cases the capability is gated behind a server-side flag or buried in an obfuscated binary. A static review of a submitted build cannot see either, and no amount of reviewer headcount changes that.

So 2.5.19 is not a new detection tool. It is a cleaner basis for a penalty after the fact, and the penalty it names is account-level: removal of the app and termination of the developer account. Apple is explicit that the underlying policy is long-standing and previously lived in 2.3.1. What is new is that it now has its own clause, names code obfuscation, and says what happens to the developer rather than the submission.

Guideline 1.2 does the same on the content side. Routing failure-to-remediate into the Developer Code of Conduct moves the consequence from "this app comes down" to "this developer may not be in the program." For an operator who can ship the same binary under a new shell company next week, that is the only penalty with any weight.

The line worth watching is in Section 5

The most consequential clarification is the quietest. Section 5's introduction now states that in extreme cases — apps facilitating human trafficking or the exploitation of children — authorities will be notified and the apps "will be removed from the App Store and blocked from alternative distribution."

Guideline 2.5.19 carries Apple's notarization key, meaning it applies to apps distributed outside the App Store on iOS and iPadOS as well. Under the Digital Markets Act, Apple had to open iOS in the EU to other marketplaces and web distribution, but it kept the notarization step. These two edits are Apple writing its guidelines to operate on channels it does not own, through the gate the DMA left it. Whether that survives contact with the Commission is a separate question; the intent is now in the text.

Grok is the unnamed precedent

In April, Apple privately told xAI that Grok faced removal if it continued to allow nude deepfakes; xAI added safeguards and Apple approved an updated version. Neither MacRumors nor 9to5Mac reports Apple saying this revision was written for any particular app, and 1.2 now names "AI content creation apps" as a category rather than a company.

The honest read is that none of this is enforcement. It is the paperwork that enforcement needs. Apple has spent a year dealing with apps that lied at review time, and has responded by making the lie itself the violation. The test is how many developer accounts are actually terminated under 2.5.19 — a number Apple has never published. Translations of the updated guidelines are due within a month.

Sources: Apple Developer News: Updated App Review Guidelines are now available · Apple: App Review Guidelines · 9to5Mac: Apple's new App Store rules crack down on AI nudification and 'bait-and-switch' apps · MacRumors: New App Store Rules Target AI Deepfakes and Nudify Apps