Apple announced updates to its App Review Guidelines that explicitly bar apps from generating nudity or sexually explicit imagery of real people without consent. The changes also close off a common workaround in which developers submit an app that appears compliant during review and later activate disallowed features once it reaches users.
The prohibition on pornographic material has existed on the App Store for years. That rule already covered apps that produce nudity or sexually explicit imagery, including tools commonly called nudification apps. These applications take ordinary photos of individuals and output altered versions that depict them in intimate or sexual situations. The new language makes clear that such tools violate the rules when they operate without the consent of the people whose likenesses are used. Apps that allow user-generated content face separate obligations: they must automatically filter objectionable material, supply an in-app reporting mechanism for offensive posts, and give users the ability to block accounts that post abuse.
The updates focus on two related problems. First, they restate that apps containing hidden or undocumented features are not permitted. Second, they directly address the practice of submitting one version of an app for review and then enabling different, harmful capabilities after approval. Apple describes this pattern as a bait-and-switch tactic. In the specific case of nudification features, a developer might present an app as a harmless photo editor during the review process and only later reveal or activate the ability to create nonconsensual intimate images. The guidelines now treat this sequence as a violation of the existing rule against hidden functionality.
Developers who host user content must maintain the required filters, reporting paths, and blocking tools at all times. Any app that removes or weakens these controls after approval falls under the same prohibition on undisclosed changes. The announcement does not introduce new technical requirements beyond clearer wording; instead it signals that Apple intends to apply the existing standards more consistently to these categories of behavior.
No third-party reactions appear in the source material, and Apple did not publish separate statements from external developers or advocacy groups alongside the guideline update.
The changes reduce the room for interpretation that some developers have used to argue that their apps only became capable of disallowed actions after launch. Review teams now have explicit language to cite when rejecting submissions that generate nonconsensual imagery or that appear designed to evade detection during the initial review. For teams building image-generation tools or platforms that accept user uploads, the practical effect is earlier and more predictable rejection rather than a period of availability followed by removal. Users benefit from a clearer boundary: apps that rely on nonconsensual intimate imagery or that switch behavior after approval are treated as straightforward policy violations instead of ambiguous edge cases. Enforcement will still depend on Apple’s ongoing monitoring and on reports from users who encounter the features, but the updated text removes one line of defense developers previously invoked.
---
Sources:
No comments yet