Mobile Unwanted Software - Play Console Help (original) (raw)

Disclaimer: Policy summaries and Key Considerations are overviews only; always refer to the full policy for compliance. The full policy takes precedence in case of conflict.

Mobile Unwanted Software

Policy Summary

To ensure a safe and great user experience, this policy builds on the Google Unwanted Software Policy by outlining principles for the Android ecosystem and the Google Play Store. Apps that violate these principles are potentially harmful to the user experience and we will take actions to protect users from them. Your app must deliver its promised value, be transparent about its functions and clearly disclose any bundled software. It must not misrepresent the device’s state, impersonate others or generate fake ad traffic. You must handle all user data securely and in compliance with our User Data policies. Apps that interfere with device usability, show disruptive ads or mimic system prompts are prohibited. Please review the full policy to ensure compliance.

Full Policy

At Google, we believe that if we focus on the user, all else will follow. In our Software Principles and the Unwanted Software policy, we provide general recommendations for software that delivers a great user experience. This policy builds on the Google Unwanted Software policy by outlining principles for the Android ecosystem and the Google Play store. Software that violates these principles is potentially harmful to the user experience, and we will take steps to protect users from it.

As mentioned in the Unwanted Software policy, we’ve found that most unwanted software displays one or more of the same basic characteristics:

On mobile devices, software is code in the form of an app, binary, framework modification, etc. In order to prevent software that is harmful to the software ecosystem or disruptive to the user experience we will take action on code that violates these principles.

Below, we build on the Unwanted Software policy to extend its applicability to mobile software. As with that policy, we will continue to refine this Mobile Unwanted Software policy to address new types of abuse.

Transparent behavior and clear disclosures

All code should deliver on promises made to the user. Apps should provide all communicated functionality. Apps should not confuse users.

Example violations:

Protect user data and privacy

Be clear and transparent about the access, use, collection, and sharing of personal and sensitive user data. Uses of user data must adhere to all relevant User Data policies, where applicable, and take all precautions to protect the data.

All apps must comply with all Google Play Developer Program Policies, including user and device data policies such as User Data, Permissions and APIs that Access Sensitive Information, Spyware, and SDK Requirements.

Do not harm the mobile experience

The user experience should be straightforward, easy-to-understand, and based on clear choices made by the user. It should present a clear value proposition to the user and not disrupt the advertised or desired user experience.

Example violations:

Key Considerations

Do Don't
Be transparent with users about your app's functionality and present a clear value proposition that your app delivers on. Don’t trick users into installing your app or disabling device security protections, such as, Google Play Protect.
Handle personal and sensitive user data securely and ensure compliance with User Data policies. Don’t disrupt or interfere with other apps on the user's device or the device's normal functions.
Ensure the uninstall process is simple, clear and straightforward. Don't display disruptive or unexpected advertisements.
Disclose all bundled software and explicitly explain any system changes and allow user review and approval. Don’t misrepresent the device's state with fake security or virus alerts and don’t mimic system-level notifications or other app prompts.
Ensure ads are easily dismissible and don't disrupt device use. Don’t mislead users or impersonate other apps, developers or entities.

Was this helpful?

How can we improve it?