服务条款和数据安全
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
在使用或访问 Play Integrity API 之前，请执行以下操作：
- 阅读 Play Integrity API 服务条款。
- 了解 API 如何处理数据。
服务条款
上次修改日期：2024 年 5 月 20 日
- 使用 Play Integrity API 即表示您同意遵守
《Google API 服务条款》
（简称《API 服务条款》）及这些条款。Play Integrity API 旨在保护应用安全
防范滥用、欺诈和未经授权的访问。
- 通过使用 Play Integrity API，您的应用或 SDK 将有权访问特定功能，并根据
Play Integrity API
文档中描述的资格条件获得有限制的配额。资格条件可能会变更。
- 如果您的应用或 SDK 不符合或不再符合相关资格条件，Google Play
保留撤销功能访问权限及减少配额的权利。
- 如果 Google Play 批准您使用更多功能或增加配额，相关授权不可转让
且仅适用于指定的应用或 SDK。
- 您不得使用 Play Integrity API 来识别或跟踪个人用户或设备。
- Google 可能随时更改这些条款。如有变更，Google 会向您发出通知
同时您也可以选择不继续使用 Play Integrity API。Google
会通过以下网址发布条款修改通知：
https://developer.android.com/google/play/integrity/terms#tos。
变更不具有追溯效力。
数据安全
Google Play 有一个
“数据安全”部分，
供开发者披露其应用的数据收集、分享和安全做法。为了满足“数据安全”部分的要求，
您可以参考以下信息，了解 Play Integrity API 是如何处理数据的。
Play Integrity API 是 Google Play 商店的运行时接口。因此，当您在应用中使用
Play Integrity 时，Play 商店会运行自己的进程，其中包括处理受
Google Play 服务条款
约束的数据。以下信息说明了 Play Integrity API
如何通过处理数据来处理从您的应用发来的特定请求。
收集的使用情况数据 |
始终收集：
- 请求中由应用提供的信息，包括
requestHash 和
nonce 字段
- 应用元数据，包括软件包名称、版本号和签名证书
- 设备上已登录用户帐号的应用
Google
Play 许可状态
- 设备信息，包括由 Google Play 服务生成的密钥认证证书和设备认证令牌
仅在发出请求的应用选择接收
环境详情
时收集：
- 应用活动信息，用于确定是否正在运行、可截屏或控制设备的应用
- 用于确定 Google Play 保护机制状态的设备信息
|
数据收集目的 |
我们会利用收集的数据来验证应用完整性、许可状态、环境详情和设备完整性。 |
数据加密 |
数据会加密。 |
数据分享 |
我们不会将收集的数据发送给任何第三方。 |
数据删除 |
我们会在固定保留期限过后删除收集的数据。 |
虽然我们力求做到尽可能公开透明，但对于
Google Play 的“数据安全”部分
针对您的应用的用户数据收集、分享和安全做法提供的表单，您需自行负责决定如何回应。
本页面上的内容和代码示例受内容许可部分所述许可的限制。Java 和 OpenJDK 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC)：2024-05-25。
[null,null,["最后更新时间 (UTC)：2024-05-25。"],[],[],null,["# Terms of Service and data safety\n\nBefore you use or access the Play Integrity API, do the following:\n\n1. Read the [Play Integrity API Terms of Service](#tos).\n2. Understand [how the API handles data](#data-safety).\n\nTerms of Service\n----------------\n\nLast modified: May 20, 2024\n\n1. By using the Play Integrity API, you agree to these terms in addition to the [Google APIs Terms of Service](https://developers.google.com/terms) (\"API ToS\"). The Play Integrity API is provided to protect app security and to mitigate abuse, fraud, and unauthorized access.\n2. By using the Play Integrity API, your app or SDK will have access to certain features and be granted quota limits based on the eligibility criteria described in the [Play Integrity API\n documentation](http://g.co/play/integrityapi). Eligibility criteria are subject to change.\n 1. Google Play reserves the right to remove feature access and reduce quota if your app or SDK does not meet, or stops meeting, the eligibility criteria.\n 2. The approval of additional features or increased quota is non-transferable and will only apply to the specified app or SDK.\n3. You may not use the Play Integrity API to fingerprint or track individual users or devices.\n4. Google may make changes to these terms at any time with notice and the opportunity to decline further use of the Play Integrity API. Google will post notice of modifications to the terms at `https://developer.android.com/google/play/integrity/terms#tos`. Changes will not be retroactive.\n\nData safety\n-----------\n\nGoogle Play has a [data safety\nsection](https://support.google.com/googleplay/answer/11416267) for developers\nto disclose their apps' data collection, sharing, and security practices. To\nhelp you complete the data safety section requirements, you can use the\ninformation below on how the Play Integrity API handles data.\n\nThe Play Integrity API is a runtime interface with the Google Play Store. As\nsuch, when you use Play Integrity 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/intl/en-US_us/about/play-terms/index.html). The\ninformation below describes how the Play Integrity API handles data to process\nspecific requests from your app.\n\n|----------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Data collected on usage | Always collected: - App-provided information in the request including the `requestHash` and `nonce` fields - App metadata including package name, version number, and signing certificate - The app's [Google Play license status](/google/play/integrity/verdicts#account-details-field) for the signed in user accounts on the device - Device information including a key attestation certificate and a device attestation token generated by Google Play services Only collected when the requesting app is opted in to receiving [environment details](/google/play/integrity/verdicts#environment-details-field): - App activity information used to determine if apps are running that can capture the screen or control the device - Device information used to determine the status of Google Play Protect |\n| Purpose of data collection | The data collected is used to verify the application integrity, the licensing status, environment details, and the device integrity. |\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\n[Google Play's data safety section form](https://support.google.com/googleplay/android-developer/answer/10787469)\nregarding your app's user data collection, sharing, and security practices."]]
