Play Core 库是您的应用与 Google Play 商店的运行时接口。因此,当您在应用中使用 Play Core 时,Play 商店会运行自己的进程,其中包括处理受 Google Play 服务条款约束的数据。以下信息说明了 Play Core 库如何通过处理数据来处理从您的应用发来的特定请求。
应用内更新
收集的使用情况数据
设备元数据
应用版本
已安装模块和资源包的列表
数据收集目的
我们会利用收集的数据来确定是否有可用的更新,以及更新的预计大小。
数据加密
数据会加密。
数据分享
我们不会将收集的数据发送给任何第三方。
数据删除
我们会在固定保留期限过后删除收集的数据。
虽然我们力求做到尽可能公开透明,但对于 Google Play 的“数据安全”部分针对您的应用的用户数据收集、分享和安全做法提供的表单,您需自行负责决定如何回应。
[null,null,["最后更新时间 (UTC):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."]]