为满足 Google Play 的数据披露要求做准备
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
2021 年 5 月，Google Play 宣布推出全新的“数据安全”部分，这是由开发者提供的关于应用数据的收集、共享和安全做法的披露声明。
本页面可帮助您符合与使用 Play 游戏服务 Android 和/或 C++ SDK 相关的此类数据披露要求。在本页面中，您可以了解 SDK 是否处理最终用户数据以及如何处理，包括您作为应用开发者可以控制的适用配置或调用的示例。
我们的目标是尽可能透明地为您提供支持。但是，作为应用开发者，您有责任自行决定如何回答 Google Play“数据安全”部分的表单中关于应用的最终用户数据收集、共享和安全做法的问题。
如何使用本页面上的信息
本页面仅列出了最新版本的 Play 游戏服务 SDK 收集的最终用户数据。
我们提供自动收集的数据的相关信息以及根据您的使用情况收集的数据的相关信息。自动收集意味着由 SDK 自动收集特定数据，您无需在应用中调用任何特定方法或类。不过在许多情况下，SDK 收集的数据取决于应用对产品的具体使用情况，即应用的配置和您调用 SDK 的方式。
如需完成数据披露，您可以使用 Android 的数据类型指南来确定哪些数据类型能准确描述所收集的数据。在数据披露中，另请务必明确说明您的特定应用将如何共享和使用所收集的数据。
Play 游戏服务 SDK 的数据加密、数据共享和数据删除概览
| 数据加密 |
对于本页中列出的已收集的最终用户数据，Play 游戏服务会使用 HTTPS 对传输中的数据进行加密。
|
| 数据分享 |
游戏服务数据通过第三方 API 公开。已启用 Play 游戏服务的游戏只能读取/写入该游戏的已登录玩家在这款游戏中的数据，而无法访问用户玩的其他游戏的数据。当用户使用 Play 游戏服务登录您的游戏时，其玩家身份会与已启用 Play 游戏服务的游戏共享。
用户可以选择将其资料的公开范围设为“仅限好友”“所有人”或“仅限您自己”。当用户选择“仅限好友”的公开范围时，只有添加为好友的用户才能看到此用户资料的游戏数据。如果设为公开，则所有其他用户都可以查看此用户资料的游戏数据。
如果设置为不公开，则其他用户只能看到使用中的显示名称，而无法看到任何游戏/游戏内容数据。
用户还可以选择已启用 Play 游戏服务的游戏是可以自动访问其好友列表（仅包含显示名称，而不包含电子邮件地址），还是仅在收到游戏提示时才能访问。
|
| 数据删除 |
用户可以通过其 Play 游戏玩家资料或 Google MyAccount 删除其账号以及 Google 收集的所有关联游戏数据。
如果 Google 收集某款游戏的 Play 游戏服务数据，用户可以通过其 Play 游戏玩家资料删除这些数据。
|
Play 游戏服务 SDK
自动收集的数据
Play 游戏服务 SDK 会自动收集以下数据。
| 数据 |
默认行为 |
|---|
| 游戏服务 |
在用户创建和更新其游戏账号时收集以下游戏账号数据：
|
| 分析 |
收集分析数据以提高 SDK 的稳定性并改进产品。
|
| 诊断 |
收集诊断数据以提高 SDK 的稳定性并改进产品。
|
根据您的使用情况收集的数据
根据您配置或调用 Play 游戏服务 SDK 和产品功能的情况，您的应用可能会收集需要包含在您的数据披露声明中的最终用户数据。下表列出了根据您的使用情况可能会收集的最终用户数据示例，但请务必指出根据您的具体使用情况收集的所有数据。
| 数据 |
详细信息 |
|---|
| 游戏服务 |
用户在游戏过程中生成并存储在 Google 服务器上用于游戏分析的累积数据。要收集的玩家数据由您的应用定义。这可能包括一些指标，例如用户执行以下操作的频率（仅列举一些示例）：
|
| 游戏服务 |
用户在玩游戏过程中产生的服务数据。例如：
- 达成的成就
- 游戏得分
- 互动度和支出统计信息
- 社交关系（好友联系、请求、好友昵称）
|
| 元游戏数据 |
用户在玩游戏过程中产生的元游戏。例如：
- 职位
- 等级
- 经验值
- 经验值历史记录
- 每个类别的经验值
|
| 游戏存档 |
用户在玩游戏过程中产生的游戏存档数据。
|
本页面上的内容和代码示例受内容许可部分所述许可的限制。Java 和 OpenJDK 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC)：2025-07-26。
[null,null,["最后更新时间 (UTC)：2025-07-26。"],[],[],null,["# Prepare for Google Play's data disclosure requirements\n\nIn May 2021, Google Play\n[announced the new Data safety section](https://android-developers.googleblog.com/2021/05/new-safety-section-in-google-play-will.html),\nwhich is a developer-provided disclosure for an app's data collection, sharing,\nand security practices.\n\nThis page can help you complete the requirements for this data disclosure in\nregards to your usage of the Play Games Services Android and/or C++ SDKs. On\nthis page, you can find information on whether and how our SDKs handle end-user\ndata, including examples of applicable configurations or invocations you can\ncontrol as the app developer.\n\nWe aim to be as transparent as possible in supporting you. However, as the app\ndeveloper, you are solely responsible for deciding how to respond to Google\nPlay's Data safety section form regarding your app's end-user data collection,\nsharing, and security practices.\n\nHow to use the information on this page\n---------------------------------------\n\nThis page lists the end-user data collected by only the latest version of the\n[Play Games Services SDKs](/games/pgs/downloads).\n\nWe provide information about data collected automatically and data collected\ndepending on your usage. Automatic collection means that the SDK collects\nspecific data without you invoking any specific method or class in your app.\nHowever, in many cases, the data collected by the SDK depends on your app's\nspecific usage of the product, meaning your app's configuration and how you\ninvoke the SDK.\n\nTo complete your data disclosure, you can use Android's\n[guide about data types](https://developers.android.com/guide/topics/data/collect-share) to help you determine\nwhich data type best describes the collected data. In your data disclosure, make\nsure to also account for how your specific app shares and uses the collected\ndata.\n\nOverview of data encryption, data sharing, and data deletion for Play Games Services SDKs\n-----------------------------------------------------------------------------------------\n\n|---------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| **Data encryption** | For the collected end-user data listed on this page, Play Games Services encrypts the data in transit using HTTPS. |\n| **Data sharing** | Game Services data is exposed using a 3rd-party API. Your Play Games Services enabled game can only read/write the signed in player's data for that game. It cannot access games service data for another game a user plays. When a user logs into your game using Play Games Services, their gamer identity is shared with your Play Games Services enabled game. Users choose whether their profile is for \"Friends only,\" for \"Everyone,\" or \"Only you.\" When users choose the \"Friends only\" visibility, only users added as friends can see game data for the profile. If public, all other users can see game data for the profile. If private, other users can only see that the display name is in use, but not any game/gameplay data. Users can also choose whether Play Games Services enabled games can access their friends lists (includes only the display name, not the email address) automatically or only when prompted by a game. |\n| **Data deletion** | Users can delete their account and all associated games data collected by Google through their [Play Games profile](https://play.google.com/games/profile) or [Google MyAccount](https://myaccount.google.com). If Google collects Play Games Services data for an individual game, users can delete the data through their [Play Games profile](https://play.google.com/games/profile). |\n\nPlay Games Services SDKs\n------------------------\n\n### Data collected automatically\n\nThe Play Games Services SDKs collect the following data automatically.\n\n| Data | Default behavior |\n|--------------|------------------------------------------------------------------------------------------------------------------------------------|\n| Game Service | Collects the following Games account data when a user creates and updates their games account: - Gamer Identity (Gamertag, avatar) |\n| Analytics | Collects analytics data to improve the stability of our SDKs and make product improvements. |\n| Diagnostics | Collects diagnostics data to improve the stability of our SDKs and make product improvements. |\n\n### Data collected depending on your usage\n\nDepending on how you configure or invoke the Play Games Services SDKs and the\nproduct's features, your app may collect end-user data that needs to be included\nin your data disclosure. The following table lists examples of end-user data\nthat can be collected depending on your usage, but make sure to account for any\ndata collected by your specific usage.\n\n| Data | Details |\n|---------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|\n| Game Service | Cumulative data generated by users during gameplay and stored on Google's servers for game analytics. The player data to collect is defined by your app. This might include metrics such as how often users do the following (examples only): - Use a particular item - Reach a certain level - Perform a specific game action |\n| Game Service | Service data when a user progresses through a game. For example: - Unlocked achievements - Games scores - Engagement and spend statistics - Social connections (Friend connections, requests, nicknames for friends) |\n| Metagame data | Metagame data when a user progresses through a game. For example: - Title - Level - Experience points - Experience points history - Experience points per category |\n| Saved Games | Save game data when a user progresses through a game: - Saved game progress - Saved game screenshot |"]]
