Play Core 程式庫是應用程式與 Google Play 商店之間的執行階段介面。因此，在應用程式中使用 Play Core 時，Play 商店會執行自己的程序，包括依據《Google Play 服務條款》的規範處理資料。以下資訊說明 Play Core 程式庫如何處理資料，以處理應用程式的特定要求。
應用程式內更新
收集到資料的使用情況
裝置中繼資料 應用程式版本 已安裝的模組和資產包清單
資料收集目的
收集的資料會用於判斷是否有可用的更新及預期更新檔案大小。
資料加密
資料已加密。
資料分享
資料不會轉移給任何第三方。
資料刪除
過了固定的保留期限後，系統會刪除資料。
雖然我們力求盡可能維持公開透明，但您必須全權決定如何回覆 Google Play 的「資料安全性」專區表單，說明應用程式的使用者資料收集、分享和安全性做法。
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["缺少我需要的資訊","missingTheInformationINeed","thumb-down"],["過於複雜/步驟過多","tooComplicatedTooManySteps","thumb-down"],["過時","outOfDate","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["示例/程式碼問題","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-07-27 (世界標準時間)。"],[],[],null,["# In-app updates\n\nWhen your users keep your app up to date on their devices, they can try new\nfeatures, as well as benefit from performance improvements and bug fixes.\nAlthough some users enable background updates when their device is connected to\nan unmetered connection, other users might need to be reminded to install\nupdates. In-app updates is a Google Play Core libraries feature that prompts\nactive users to update your app.\n\nThe in-app updates feature is supported on devices running Android 5.0 (API\nlevel 21) or higher. Additionally, in-app updates are only supported for Android\nmobile devices, Android tablets, and ChromeOS devices.\n| **Note:** In-app updates are not compatible with apps that use APK expansion files (`.obb` files).\n\nUpdate flows\n------------\n\nYour app can use the Google Play Core libraries to support the following UX\nflows for in-app updates:\n\n### Flexible updates\n\nFlexible updates provide background download and installation with graceful\nstate monitoring. This UX flow is appropriate when it's acceptable for the user\nto use the app while downloading the update. For example, you might want to\nencourage users to try a new feature that's not critical to the core\nfunctionality of your app.\n\n\n**Figure 1.** An example of a flexible update flow.\n\n\u003cbr /\u003e\n\n### Immediate updates\n\nImmediate updates are fullscreen UX flows that require the user to update and\nrestart the app in order to continue using it. This UX flow is best for cases\nwhere an update is critical to the core functionality of your app. After a user\naccepts an immediate update, Google Play handles the update installation and app\nrestart.\n\n\n**Figure 2.** An example of an immediate update flow.\n\n\u003cbr /\u003e\n\nSupport in-app updates in your app\n----------------------------------\n\nLearn how to support in-app updates in your app, depending on your development\nenvironment:\n\n- [Kotlin or Java](/guide/playcore/in-app-updates/kotlin-java)\n- [Native (C/C++)](/guide/playcore/in-app-updates/native)\n- [Unity](/guide/playcore/in-app-updates/unity)\n- [Unreal Engine](/guide/playcore/in-app-updates/unreal-engine)\n\nTerms of service\n----------------\n\nBy accessing or using the Play In-App Updates Library, you agree to the [Play\nCore Software Development Kit Terms of Service](/guide/playcore#license). Read and understand all\napplicable terms and policies before accessing the library.\n\nData Safety\n-----------\n\nThe Play Core libraries are your app's runtime interface with the Google Play\nStore. As such, when you use Play Core in your app, the Play Store runs its own\nprocesses, which include handling data as governed by the [Google Play Terms of\nService](https://play.google.com/about/play-terms/index.html). The following information describes how the Play Core\nlibraries handle data to process specific requests from your app.\n\n### In-app Updates\n\n|----------------------------|----------------------------------------------------------------------------------------------------------------------|\n| Data collected on usage | Device metadata Application version List of modules and asset packs installed |\n| Purpose of data collection | The data collected is used to determine if an update is available and what the size of the update is expected to be. |\n| Data encryption | Data is encrypted. |\n| Data sharing | Data is not transferred to any third parties. |\n| Data deletion | Data is deleted following a fixed retention period. |\n\nWhile we aim to be as transparent as possible, you are solely responsible for\ndeciding how to respond to Google Play's data safety section form regarding your\napp's user data collection, sharing, and security practices."]]
