行動垃圾軟體 (MUwS)
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
Google 深信,只要以使用者為中心,一切就會水到渠成。我們在《軟體規範》和《垃圾軟體政策》中提供了一般建議,說明何種條件的軟體可提供良好的使用者體驗。這項政策的製定依據為《Google 垃圾軟體政策》,其中大致歸納了 Android 生態系統和 Google Play 商店的原則。違反這些原則的軟體可能會對使用者體驗造成負面影響,而我們會採取適當措施保護使用者。
您也可以前往 android.com。
如垃圾軟體政策所述,我們發現大多數垃圾軟體都顯示了一或多項相同的基本特性:
- 說詞不實,承諾無法達到的價值主張。
- 試圖誘騙使用者安裝軟體,或將軟體挾帶在其他程式的安裝程式中。
- 但未向使用者提供所有主要和重要功能的相關資訊。
- 對使用者系統造成預期外的影響。
- 擅自收集或傳送使用者的私人資訊。
- 會以安全的方式收集或傳送私人資訊 (例如透過 HTTPS 傳輸)。
- 暗中挾帶其他軟體。
在行動裝置上,軟體是一種應用程式、二進位檔、架構修改等形式的程式碼。為避免軟體危害軟體生態系統或乾擾使用者體驗,我們將對違反這些原則的程式碼採取行動。
在本文件中,我們以《垃圾軟體政策》為基礎,將行動軟體適用範圍擴大。和這項政策一樣,我們會持續修訂
這項「行動垃圾軟體」政策,因應新型濫用行為。
確保行為公開透明並清楚揭露相關資訊
所有程式碼的行為都必須合乎對使用者所做的承諾。應用程式必須提供所標榜的所有功能,應用程式不應讓使用者產生混淆。
- 應用程式必須清楚說明其功能和用途。
- 向使用者明確說明應用程式會進行哪些系統變更,並允許使用者檢閱及核准所有重要安裝選項和變更。
- 軟體不得對使用者提供不實的裝置狀態,例如聲稱系統的安全性受到嚴重威脅或遭病毒感染。
- 請勿利用無效活動提高廣告流量和/或轉換次數。
- 我們禁止應用程式冒用他人身分 (例如假冒其他開發人員、公司或實體) 或模仿其他應用程式,藉此誤導使用者。請勿不實暗示您的應用程式與他人相關或已獲他人授權。
違規示例:
保護使用者資料和隱私權
請清楚公開揭露對於使用者個人和機密資料的存取、蒐集、使用及分享行為。使用者資料的使用方式必須遵循所有相關適用的使用者資料政策,並採取所有預防措施來保護資料。
- 在您開始透過裝置收集及傳送資料前,請先讓使用者有機會同意您蒐集他們的資料,包括第三方帳戶、電子郵件、電話號碼、已安裝的應用程式、檔案、位置,以及使用者不希望收集的其他個人和機密資料。
- 您必須以安全無虞的方式處理收集到的使用者個人和機密資料,包括使用新型密碼編譯法 (例如 HTTPS) 傳輸資料。
- 軟體 (包括行動應用程式) 只能基於應用程式的功能運作,將使用者的個人和機密資料傳輸至伺服器。
- 請勿要求或欺騙使用者關閉裝置安全性保護措施,例如 Google Play 安全防護。舉例來說,您無法向使用者提供其他應用程式功能或獎勵,藉此換取關閉 Google Play 安全防護。
違規示例:
- 資料蒐集 (另請參閱間諜軟體)
- 受限制權限的濫用行為
使用者資料政策範例:
不要損害行動裝置體驗
使用者體驗應直接明瞭,易於理解,並須由使用者明確做出選擇。應用程式應向使用者明確呈現價值主張,且不得乾擾廣告中標榜或理應的使用者體驗。
- 請勿以非預期方式向使用者顯示廣告,包括影響或乾擾裝置功能的可用性,或是在觸發的應用程式環境外顯示廣告,但未讓使用者輕易關閉並充分取得同意聲明和歸因。
- 應用程式不得乾擾裝置運作或其他應用程式。
- 解除安裝程序 (如適用) 應清楚明確。
- 行動軟體不得模仿裝置 OS 或其他應用程式的提示。
請勿隱藏其他應用程式或作業系統發出的快訊,特別是告知使用者 OS 變更的快訊。
違規示例:
如要進一步瞭解每個違規內容,請前往 Play 政策中心、GMS 規定和 Google Play 安全防護頁面。
行動垃圾軟體 (MUwS) 類別
資料收集與限制權限濫用行為
應用程式在未充分告知使用者或未徵得使用者同意的情況下,收集及傳輸使用者的個人和機密資料。這類資訊可能包括收集已安裝應用程式的清單、裝置電話號碼、電子郵件地址、位置資訊,或其他第三方帳戶 ID 或其他個人資訊。
社交工程
應用程式偽裝成其他應用程式,意圖誘騙使用者執行使用者為原始信任應用程式執行的動作。
幹擾性廣告
應用程式以非預期方式向使用者顯示廣告,包括影響或乾擾裝置功能的可用性,或是在未充分告知使用者並歸因的情況下,顯示在觸發的應用程式環境之外。
未經授權使用或仿製系統功能
模仿或乾擾系統功能 (例如通知或警告) 的應用程式或廣告。系統層級通知只能用於應用程式的重要功能。
廣告詐欺
我們嚴禁廣告詐欺行為。如果產生的廣告互動是用於欺騙廣告聯播網,讓廣告聯播網誤信這些無效流量確實是因使用者感興趣而產生,就屬於廣告詐欺行為,這屬於一種無效流量。廣告詐欺可能是開發人員以禁止方式導入廣告而產生,例如顯示隱藏廣告、自動點擊廣告、修改或修改資訊,以及利用非人為動作 (例如自動尋檢程式和漫遊器),或利用非人為操作來產生無效廣告流量。無效流量和廣告詐欺行為會對廣告客戶、開發人員和使用者造成傷害,且會導致長期以來對行動廣告生態系統失去信任。
以下列舉一些常見的違規情況:
- 應用程式顯示使用者看不到的廣告。
- 應用程式會在使用者無意間自動點擊廣告,或是產生對等的網路流量,以詐欺手法誘使點擊功勞。
- 應用程式傳送假的安裝歸因點擊以獲得收益,帶來的安裝並非來自傳送者的網路。
- 在使用者未操作應用程式介面時彈出廣告。
- 應用程式對廣告空間的陳述不實,例如應用程式告知廣告聯播網在 iOS 裝置上執行,但其實際上是在 Android 裝置上執行;應用程式謊稱用於營利的套件名稱。
這個頁面中的內容和程式碼範例均受《內容授權》中的授權所規範。Java 與 OpenJDK 是 Oracle 和/或其關係企業的商標或註冊商標。
上次更新時間:2025-07-26 (世界標準時間)。
[null,null,["上次更新時間: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."]]