Google Play Guidelines Update

The core rule prohibiting apps from changing device settings without user knowledge and consent is unchanged. Google has added a section number (2.1) to this clause as part of a broader policy restructuring. This is a formatting change only — no new requirements or restrictions have been introduced. Developers already complying with this rule are unaffected.

The prohibition on apps that modify device settings in ways that are not easily reversible — even with user consent — has been renumbered to 2.2 and 2.2.1. The rule itself is substantively unchanged. This is part of a structural reorganization of the policy document. No new obligations are introduced for developers.

The rule barring apps and ads from modifying device settings as a service to third parties or for advertising purposes has been assigned the number 2.2.2. The underlying requirement is unchanged. This is a structural renumbering with no change to what is or isn't permitted. Developers are unaffected in terms of compliance obligations.

The rule preventing apps from misleading users into removing or disabling third-party apps or altering device settings has been renumbered to 2.2.3. No substantive content has changed. This is purely a structural reorganization. Developers should continue to ensure their app never deceives users into acting against other installed apps.

The clause prohibiting apps from encouraging or incentivizing users to remove or disable third-party apps or change device settings (with an exception for verifiable security services) has been renumbered to 2.2.4. The substantive rule and its exception remain identical. No new compliance action is required.

The core prohibition on apps that help users mislead others — including generating fake IDs, passports, credit cards, and similar documents — has been renumbered to 3.1. The rule content is unchanged. This is a structural reorganization only. Developers building any document-generation or identity-related features should continue to ensure compliance with the existing prohibition.

The requirement that additional downloadable resources (such as game assets) may only be fetched if genuinely necessary for app functionality has been renumbered to 3.2. The rule itself is unchanged. Developers should already be ensuring that any on-demand downloads are justified by user-facing app needs.

The clause clarifying that labeling an app as a 'prank' or 'for entertainment purposes' does not exempt it from policy enforcement has been renumbered to 3.3. No change to the underlying requirement exists. Developers of novelty or joke apps should already understand that all standard policies still apply regardless of how the app is marketed.

The rule prohibiting apps that promote or help create false or misleading content through imagery, audio, video, or text has been renumbered to 4.1. The substantive policy is unchanged. This is a structural reorganization. Developers working with media generation or editing tools should continue to comply with the existing prohibition.

The list of exceptions to the Manipulated Media rule — covering public interest content, clearly artificial images, watermarked media, and obvious satire or parody — has been renumbered to 4.2. The exceptions themselves are unchanged. Developers relying on these carve-outs should continue to apply appropriate disclaimers or watermarks as previously required.

Previously, the manipulated media compliance requirement appeared as an unnumbered statement within the Developer Program Policy. It now carries the explicit identifier '4.3', formally anchoring it within the policy's numbered structure. The underlying requirement itself — that manipulated media must comply with existing Google Play policies and restricted content rules — is unchanged. Developers don't need to alter their apps, but should note this section number when referencing or responding to policy enforcement communications.