[null,null,["上次更新時間：2025-09-05 (世界標準時間)。"],[[["\u003cp\u003eThe Cast Android Sender SDK collects anonymized data about app interactions with Cast devices, including discovery events, session management, and device information, to improve the Casting experience and monitor SDK usage.\u003c/p\u003e\n"],["\u003cp\u003eThe Cast TV SDK collects anonymized data about media playback experiences on Android TV receiver apps that integrate Cast Connect, including session events, device information, and generic content attributes, to improve the Cast experience and evaluate media content usage.\u003c/p\u003e\n"],["\u003cp\u003eThe collected data is encrypted, aggregated, and retained for a short period; it is not used to model specific user behavior or shared with third parties.\u003c/p\u003e\n"],["\u003cp\u003eApp developers are responsible for disclosing data collection practices in their app's Google Play Data safety section, considering how their app uses the SDK and the information provided in this document.\u003c/p\u003e\n"],["\u003cp\u003eData collection by both SDKs is required, and neither app developers nor users can opt out of data collection or delete their data.\u003c/p\u003e\n"]]],["The Cast SDK, used by mobile apps to interact with Cast-enabled devices, automatically collects data related to its interactions with these devices, including discovery, session management, device information, and client app information. This data is logged anonymously and used to monitor SDK adoption, feature integration, and to improve the overall Casting experience. The Cast-TV SDK, for Android TV apps, collects anonymized data about media playback experiences. Neither SDK shares data with third parties, and encryption is used. Users and developers cannot opt-out of data collection.\n"],null,["# Cast SDK Google Play Data Safety Section\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),\na developer-provided disclosure of apps' user data collection, sharing, and\nsecurity practices.\n\nThis page can help you complete the requirements for this data disclosure\nwith respect to your usage of the Cast Android Sender SDK. On this page, you\ncan find information on whether and how our SDK handles end-user data,\nincluding any applicable configurations or invocations you can control\nas 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\nthe SDK.\n\nWe provide information about data *collected automatically* versus data\n*collected based on your usage*. Automatic collection means that the SDK\ncollects specific data without you invoking any specific method or class in\nyour app. However, in many cases, the data collected by the SDK depends on your\napp's specific usage of the product, meaning your app's configuration and how\nyou invoke the SDK.\n\nTo complete the data disclosure for your app, you can use Android's\n[data types guide](https://developer.android.com/guide/topics/data/collect-share)\nto help you determine which *data type* best describes the collected\ndata. In your data disclosure, make sure to also account for how your specific\napp shares and uses the collected data.\n| **Important:** To help you ensure that your app's disclosures are accurate, we recommend the following:\n|\n| - Always use the latest SDK versions in your app. This page only lists the data collected by the latest version of each SDK.\n| - Review this page whenever you update your app's SDK versions. Check that your data disclosures are accurate and up-to-date.\n\ncast and cast-framework\n-----------------------\n\n com.google.android.gms:play-services-cast\n com.google.android.gms:play-services-cast-framework\n\n### SDK data collection\n\nThe Cast SDK can be used by mobile apps to discover\nand communicate with Cast-enabled devices, such as Chromecast. The SDK\ncollects information about the SDK's interactions\n([App Activity](https://developer.android.com/guide/topics/data/collect-share#app-activity))\nwith Cast devices,\nand portions of that data are sent to a Google log collection server.\nInformation logged includes generic discovery events, session management\nevents, mobile device information, and client Cast app information.\n\nThe feature set metadata, SDK metadata, and client app metadata are used to\nmonitor the adoption rate of different SDK releases by different apps, and to\nunderstand which SDK features have been integrated into different mobile apps.\n\nThe SDK also collects non-user-specific data that allows Google to improve the\nCasting experience for users. This data is NOT used to model a specific user's\nbehavior. The analysis of the data results in product-wide decisions and\nchanges to the overall system, not in changes to a specific user's experience.\n\nThe SDK collects all data anonymously. Logs do not contain any identifiers\nthat can be traced back to a specific user. The collected data is only\nretained for a short period of time. Before deletion, the data is aggregated\nto obtain high-level product performance metrics, which are used to improve\nthe SDK.\n\nFor each data type listed:\n\n- Some features are user opt-in features. Analytics data for a specific\n feature are only collected if the Cast supports that feature, and the user\n has opted in. For both opt-in and required features, the user cannot opt out\n of data collection.\n\n - The SDK transmits encrypted analytics data off the device through\n a Google log collection server to Google's data analytics pipeline.\n\n - The collected data is used in aggregate form to improve the SDK:\n to monitor overall SDK usage and performance, and to detect\n software defects in the product.\n\n - The SDK does NOT transfer or share data with third parties,\n or with other apps on the user's device.\n\n### App-level notes\n\n- All data transmitted from the SDK is encrypted in transit.\n- Neither the app developer nor the users of the app utilizing this SDK can opt out of data collection or delete their data.\n\ncast-tv\n-------\n\n com.google.android.gms:play-services-cast-tv\n\n### SDK data collection\n\nThe SDK collects information about media playback experiences for Android TV\nreceiver apps that integrate Cast Connect. The collected analytics are\nanonymized before sending to a Google log collection server. The logged\ninformation includes session events, some device information, and application\nplayback information.\n\nThe SDK does not log any user information or content\nmetadata (for example, title, artist, content URL). Only generic attributes of\nthe content being played, such as content type, format, and\nduration, are logged. Data from these content-specific logs are only used\nin aggregate form.\n\nThe collected data is used to improve the Cast experience as follows:\n\n- To evaluate the usage of media content running on Cast devices.\n\n- To identify feature success, trends, and key usage in using Cast\n to drive product, business, and engineering decisions.\n\n- To tune performance and reduce latency of media startup, playback,\n and buffering.\n\nFor each data type listed:\n\n- All data collection is required.\n- The SDK transmits encrypted analytics data off the device through a Google log collection server to Google's data analytics pipeline.\n- This data is used to help Google determine performance impacts of new platform and SDK releases.\n- The SDK does NOT transfer or share data with third parties, or with other apps on the user's device.\n\n### App level notes\n\n- The logged data is encrypted in transit.\n- Neither the app developer nor the users of the app utilizing this SDK can opt out of data collection or delete their data."]]
