移动垃圾软件 (MUwS)
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
在 Google,我们坚信以用户为中心,其他一切自然水到渠成。在软件准则和垃圾软件政策中,我们针对可提供良好用户体验的软件提供了一般性建议。此政策以 Google 垃圾软件政策为基础,概述了 Android 生态系统和 Google Play 商店的相关原则。违反这些原则的软件可能会给用户体验造成负面影响,我们将采取措施保护用户免受此类软件的影响。android.com 上也提供了此信息。
如垃圾软件政策中所述,我们发现大多数垃圾软件都具有一个或多个相同的基本特征:
- 具有欺骗性,承诺其无法实现的价值主张。
- 试图诱骗用户进行安装,或在其他程序安装时搭载安装。
- 不向用户告知其所有主要功能和重要功能。
- 以非预期方式影响用户的系统。
- 在用户不知情的情况下收集或传输隐私信息。
- 它会在没有安全处理的情况下收集或传输私密信息(例如,通过 HTTPS 传输)。
- 与其他软件捆绑在一起,但并未将这一情况告知用户。
在移动设备上,软件是指代码形式为应用、二进制文件和框架修改。为了防止软件对软件生态系统造成危害或对用户体验造成干扰,我们将对违反这些原则的代码采取措施。
本文档以《垃圾软件政策》为基础,将其适用范围扩展至移动软件。与该政策一样,我们将继续优化此“移动垃圾软件”政策,以解决新的滥用行为类型。
公开行为和明确披露信息
所有代码都应兑现对用户的承诺。应用应提供所有已宣传的功能。应用不应使用户感到困惑。
- 应用应明确功能和目标。
- 向用户清楚明确地说明应用将进行哪些系统更改。允许用户审核和批准所有重要的安装选项和更改。
- 软件不得向用户虚假陈述用户设备的状态,例如声称系统存在严重的安全问题或受到病毒感染。
- 请勿利用旨在增加广告流量和/或转化次数的无效活动。
- 我们不允许任何应用通过假冒他人(例如其他开发者、公司、实体)或其他应用来误导用户。请勿不实暗示您的应用与其他人有关或已获得其授权。
违规行为示例:
保护用户数据和隐私
对个人数据和敏感用户数据的访问、使用、收集和分享应保持透明。对用户数据的使用必须遵守所有相关的用户数据政策(如适用),并采取所有预防措施来保护数据。
- 在您开始从设备收集和发送他们的数据之前,请向用户提供一个机会,让他们同意收集他们的数据,包括关于第三方帐号、电子邮件地址、电话号码、已安装的应用、文件、位置的数据,以及用户不会希望收集的任何其他个人和敏感数据的数据。
- 应以安全的方式处理收集的个人数据和敏感用户数据,包括使用新型加密技术(例如通过 HTTPS)传输此类数据。
- 软件(包括移动应用)只能将个人数据和敏感用户数据传输到服务器,因为此类数据与应用的功能相关。
- 不得要求或欺骗用户关闭 Google Play 保护机制等设备安全保护功能。例如,您不能通过提供额外的应用功能或奖励来换取用户关闭 Google Play 保护机制。
违规行为示例:
用户数据政策示例:
不得破坏移动体验
用户体验应简单明了、易于理解,并且以用户做出的明确选择为基础。应向用户传达明确的价值主张,并且不得破坏所宣传的或预期的用户体验。
- 不得以意想不到的方式向用户展示广告,包括影响或干扰设备功能的易用性,或者展示在无法轻松关闭且未充分征得用户同意和提供方说明的情况下,在触发型应用环境之外展示。
- 应用不得干扰其他应用或设备的易用性。
- 请明确卸载(如适用)。
- 移动软件不得模拟设备操作系统或其他应用的提示。
请勿禁止其他应用或操作系统向用户发出提醒,尤其是那些告知用户操作系统发生变化的提醒。
违规行为示例:
如需详细了解每项内容违规行为,请查看 Play 政策中心、GMS 要求和 Google Play 保护机制中的政策要求。
移动垃圾软件 (MUwS) 类别
数据收集和受限权限滥用
应用在未经充分通知或未征得用户同意的情况下,收集和传输个人数据和敏感用户数据。这可能包括收集已安装应用的列表、设备电话号码、电子邮件地址、位置或其他第三方帐号 ID,或其他个人信息。
社会工程行为
应用冒充其他应用,企图诱骗用户执行用户想对原始可信应用执行的操作。
干扰性广告
应用以意想不到的方式向用户展示广告,包括影响或干扰设备功能的易用性,或者在未充分征得用户同意和注明提供方的情况下,在触发式应用环境之外展示广告。
未经授权使用或模仿系统功能
模仿或干扰系统功能(例如通知或警告)的应用或广告。系统级通知只能用于应用的基本功能。
广告欺诈
我们严禁广告欺诈行为。广告欺诈是指以诱使广告联盟相信流量源自用户的真实兴趣为目的而生成的广告互动,属于无效流量。广告欺诈可能是开发者以禁止的方式投放广告的副产物,例如展示隐藏广告、自动点击广告、更改或修改信息以及以其他方式利用非人为操作(例如“蜘蛛”程序和漫游器)或旨在产生无效广告流量的人为活动。无效流量和广告欺诈行为会损害广告主、开发者和用户,并导致移动广告生态系统长期失去信任。
下面是常见违规行为的一些示例:
- 应用呈现用户看不到的广告。
- 应用会在用户无意的情况下自动生成广告点击,或产生同等的网络流量来以欺诈手段获得点击功劳。
- 应用发送虚假安装归因点击,以通过并非来自发送者网络的安装来获得收入。
- 应用在用户未进入应用界面时弹出广告。
- 应用对广告资源进行虚假陈述。例如,当在 Android 设备上运行时,应用与在 iOS 设备上运行的广告网络进行通信;应用虚假陈述用于变现的软件包名称。
本页面上的内容和代码示例受内容许可部分所述许可的限制。Java 和 OpenJDK 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC):2025-07-26。
[null,null,["最后更新时间 (UTC):2025-07-26。"],[[["\u003cp\u003eThis policy outlines principles for software on the Android ecosystem and Google Play Store to protect users from harmful or disruptive experiences.\u003c/p\u003e\n"],["\u003cp\u003eGoogle will take action on code that violates these principles, such as software that is deceptive, hides functionality, or collects private information without consent.\u003c/p\u003e\n"],["\u003cp\u003eSoftware must be transparent about its behavior, protect user data and privacy, and not harm the mobile experience by displaying disruptive ads or imitating system functions.\u003c/p\u003e\n"],["\u003cp\u003eMobile Unwanted Software (MUwS) categories include: Data collection and permissions abuse, social engineering, disruptive ads, unauthorized system functionality use, and ad fraud.\u003c/p\u003e\n"],["\u003cp\u003eDevelopers should review the Play Policy Center, GMS requirements, and Google Play Protect for more details on policy violations and requirements.\u003c/p\u003e\n"]]],["Google's mobile software policy extends its Unwanted Software Policy to the Android ecosystem and Google Play Store. The policy aims to protect users from harmful software by outlining principles that prioritize transparency, user data privacy, and a positive mobile experience. Key actions include prohibiting deceptive practices, unauthorized data collection, disruptive ads, ad fraud, and impersonation. Apps must be clear about functionality, system changes, and data usage, and avoid interfering with device usability or mimicking system prompts. Violations are classified, and actions will be taken against offending code.\n"],null,["# Mobile Unwanted Software (MUwS)\n\nAt Google, we believe that if we focus on the user, all else will follow. In\nour [Software\nPrinciples](https://www.google.com/about/software-principles.html) and the [Unwanted\nSoftware Policy](https://www.google.com/about/unwanted-software-policy.html), we provide general recommendations for software that\ndelivers a great user experience. This policy builds on the Google Unwanted\nSoftware Policy by outlining principles for the Android ecosystem and the Google\nPlay Store. Software that violates these principles is potentially harmful to\nthe user experience, and we will take steps to protect users from it.\nThis information is also available on [android.com](https://www.android.com/mobile-unwanted-software-policy/).\n\nAs mentioned in the [Unwanted\nSoftware Policy](https://www.google.com/about/unwanted-software-policy.html), we've found that most unwanted software displays one or\nmore of the same basic characteristics:\n\n- It is deceptive, promising a value proposition that it does not meet.\n- It tries to trick users into installing it or it piggybacks on the installation of another program.\n- It doesn't tell the user about all of its principal and significant functions.\n- It affects the user's system in unexpected ways.\n- It collects or transmits private information without users' knowledge.\n- It collects or transmits private information without a secure handling (for example, transmission over HTTPS).\n- It is bundled with other software and its presence is not disclosed.\n\nOn mobile devices, software is code in the form of an app, binary, framework\nmodification. In order to prevent software that is harmful to the software\necosystem or disruptive to the user experience we will take action on code that\nviolates these principles.\n\nIn this document, we build on the Unwanted Software Policy to extend its applicability\nto mobile software. As with that policy, we will continue to refine this Mobile\nUnwanted Software policy to address new types of abuse.\n\n### Transparent behavior and clear disclosures\n\nAll code should deliver on promises made to the user. Apps should\nprovide all communicated functionality. Apps shouldn't confuse users.\n\n- Apps should be clear about the functionality and objectives.\n- Explicitly and clearly explain to the user what system changes will be made by the app. Allow users to review and approve all significant installation options and changes.\n- Software should't misrepresent the state of the user's device to the user, for example by claiming the system is in a critical security state or infected with viruses.\n- Don't utilize invalid activity designed to increase ad traffic and/or conversions.\n- We don't allow apps that mislead users by impersonating someone else (for example, another developer, company, entity) or another app. Don't imply that your app is related to or authorized by someone that it isn't.\n\nExample violations:\n\n- Ad fraud\n- Impersonation\n\n### Protect user data and privacy\n\nBe clear and transparent about the access, use, collection, and sharing\nof personal and sensitive user data. Uses of user data must adhere to all\nrelevant User Data Policies, where applicable, and take all precautions to\nprotect the data.\n\n- Provide users an opportunity to agree to the collection of their data before you start collecting and sending it from the device, including data about third-party accounts, email, phone number, installed apps, files, location, and any other personal and sensitive data that the user wouldn't expect to be collected.\n- Personal and sensitive user data collected should be handled securely, including being transmitted using modern cryptography (for example, over HTTPS).\n- Software, including mobile apps, must only transmit personal and sensitive user data to servers as it is related to the functionality of the app.\n- Don't request or deceive users into turning off device security protections such as Google Play Protect. For example, you can't offer additional app features or rewards to users in exchange for turning off Google Play Protect.\n\nExample violations:\n\n- Data Collection (cf [Spyware](https://developers.google.com/android/play-protect/phacategories#spyware))\n- Restricted Permissions abuse\n\nExample User Data Policies:\n\n- [Google\n Play User Data Policy](https://play.google.com/about/privacy-security-deception/user-data/)\n- [GMS\n Requirements User Data Policy](https://support.google.com/androidpartners_gms/answer/7351400)\n- [Google\n API Service User Data Policy](https://developers.google.com/terms/api-services-user-data-policy)\n\n### Do not harm the mobile experience\n\nThe user experience should be straightforward, easy-to-understand, and\nbased on clear choices made by the user. It should present a clear value\nproposition to the user and not disrupt the advertised or desired user\nexperience.\n\n- Don't show ads that are displayed to users in unexpected ways including impairing or interfering with the usability of device functions, or displaying outside the triggering app's environment without being easily dismissable and adequate consent and attribution.\n- Apps should not interfere with other apps or the usability of the device.\n- Uninstall, where applicable, should be clear.\n- Mobile software should not mimic prompts from the device OS or other apps. Do not suppress alerts to the user from other apps or from the operating system, notably those which inform the user of changes to their OS.\n\nExample violations:\n\n- Disruptive ads\n- Unauthorized Use or Imitation of System Functionality\n\nFor more details about each content violation, review policy requirements on\nthe [Play\nPolicy Center](https://play.google.com/about/developer-content-policy/), [GMS\nrequirements](https://docs.partner.android.com/gms/policies/overview/gms-requirements#mba-impersonation), and [Google\nPlay Protect](https://developers.google.com/android/play-protect/phacategories).\n\n### Mobile Unwanted Software (MUwS) categories\n\n#### Data collection and restricted permissions abuse\n\nAn app that collects and transmits personal and sensitive user data without\nadequate notice or consent. This may include collecting the list of installed\napps, the device phone number, email addresses, location, or other third-party\naccount IDs, or other personal information.\n\n#### Social Engineering\n\nAn app that pretends to be another app with the intention of deceiving users\ninto performing actions that the user intended for the original trusted app.\n\n#### Disruptive ads\n\nAn app that shows ads that are displayed to users in unexpected ways\nincluding impairing or interfering with the usability of device\nfunctions, or displaying outside the triggering app's environment\nwithout adequate consent and attribution.\n\n#### Unauthorized Use or Imitation of System Functionality\n\nApps or ads that mimic or interfere with system functionality, such as\nnotifications or warnings. System level notifications may only be used\nfor an app's integral features.\n\n#### Ad fraud\n\nAd fraud is strictly prohibited. Ad interactions generated for the purpose of\ntricking an ad network into believing traffic is from authentic user interest is\nad fraud, which is a form of [invalid\ntraffic](https://support.google.com/admob/answer/3342054?ref_topic=2745287). Ad fraud may be the byproduct of developers implementing ads in\ndisallowed ways, such as showing hidden ads, automatically clicking ads,\naltering or modifying information and otherwise leveraging non-human actions\n(such as spiders and bots) or human activity designed to produce invalid ad traffic.\nInvalid traffic and ad fraud is harmful to advertisers, developers, and users,\nand leads to long-term loss of trust in the mobile Ads ecosystem.\n\n#### Here are some examples of common violations:\n\n- An app that renders ads that are not visible to the user.\n- An app that automatically generates clicks on ads without the user's intention or that produces equivalent network traffic to fraudulently give click credits.\n- An app sending fake installation attribution clicks to get paid for installations that did not originate from the sender's network.\n- An app that pops up ads when the user is not within the app interface.\n- False representations of the ad inventory by an app, for example, an app that communicates to ad networks that it is running on an iOS device when it is in fact running on an Android device; an app that misrepresents the package name that is being monetized."]]