[null,null,["最后更新时间 (UTC):2025-07-26。"],[[["\u003cp\u003eARCore automatically collects user IDs, device IDs, performance & diagnostic data, and API usage data to support functionality, analytics, and improvements.\u003c/p\u003e\n"],["\u003cp\u003eARCore encrypts all user data collected on devices with Google Play Store using HTTPS.\u003c/p\u003e\n"],["\u003cp\u003eWhen using specific ARCore APIs like Geospatial API or Cloud Anchors, additional data such as location or video data may be collected, with specific handling and anonymization practices.\u003c/p\u003e\n"],["\u003cp\u003eAs the app developer, you are responsible for disclosing how your app uses ARCore and manages user data in the Google Play Data safety form.\u003c/p\u003e\n"],["\u003cp\u003eThis document only reflects data collection by the latest ARCore SDK, so using the latest version is crucial for accurate disclosures.\u003c/p\u003e\n"]]],[],null,["# Data safety form in Google Play Console\n\nApps in the Google Play Store must describe their data privacy and security\npractices. This information is shown on the app's Play Store listing to help\nusers understand how the app collects and shares user data.\n\nThis document provides information on how ARCore handles user data.\n\nARCore provides this information with the aim to be as transparent as possible.\n**However, we can't speak for you. As the app developer, you are solely\nresponsible for deciding how to respond to Google Play's Data safety form\nregarding your app's user data collection, sharing, and security practices.**\n| **Important:** This document lists the user data collected by only the [latest ARCore SDK](/ar/develop/downloads). To ensure that your app's disclosures are accurate, always use the latest ARCore SDK in your app.\n\nARCore data encryption\n----------------------\n\nAll user data collected by ARCore on devices that originally shipped with the\nGoogle Play Store is encrypted in transit using HTTPS.\n\nARCore data that is always collected\n------------------------------------\n\nARCore collects the following user data, regardless of which ARCore APIs your\napp uses:\n\n### User IDs\n\n- ARCore automatically collects Google account identifiers if the user is signed in to their Google account. Google does not share these identifiers with third parties.\n- This data collection is required, and data is stored by Google to produce analytics.\n- ARCore uses this data to determine user engagement, including AR usage by app.\n\n### Device IDs\n\n- ARCore automatically collects device-specific identifiers if the user is not signed in to a Google account. Google does not share these identifiers with third parties.\n- This data collection is required, and data is stored by Google to produce analytics.\n- ARCore uses this data to determine user engagement, including AR usage by app.\n\n### Performance and other diagnostic data\n\n- ARCore automatically collects performance and other diagnostic data about the app, the ARCore SDK, and the user's device; for example, battery life, loading time, latency, framerate, and other diagnostics. ARCore does not share this performance and other diagnostic data with third parties.\n- This data collection is required, and data is stored by Google to determine real-world ARCore performance, diagnose runtime behavior, and to help improve AR experiences for developers and users.\n\n### API usage and app activity\n\n- ARCore automatically collects data about the ARCore API calls that your app makes. ARCore does not share this ARCore API call data with third parties.\n- ARCore API call data collection is required, and data is stored by Google to produce analytics, ensure ARCore is operating correctly, and to help deliver high quality AR experiences for developers and users.\n\nARCore data that is conditionally collected\n-------------------------------------------\n\nARCore collects the following user data, only when your app uses certain ARCore\nAPIs as indicated:\n\n### Precise location\n\n- When **using the ARCore Geospatial API**, ARCore collects precise location data, which is required to provide API functionality. Google does not share this precise location data with third parties.\n- Google may store and analyze this precise location data in [anonymized](https://policies.google.com/technologies/anonymization) form for purposes including improvement of Google products and services; otherwise, this precise location data is stored temporarily and marked for automated deletion.\n\n### Video data\n\n- ARCore automatically collects video data while **hosting Cloud Anchors** , **resolving Cloud Anchors** , or when **using the ARCore Geospatial API** . Google does not share this collected video data with third parties.\n - When **hosting Cloud Anchors**, collected video data is stored temporarily. This video data is marked for automatic deletion after the Cloud Anchor hosting process has finished.\n - When **resolving Cloud Anchors**, collected video data is processed in real-time, in memory only. This video data is not retained after the Cloud Anchor resolving process has finished.\n - When **using the ARCore Geospatial API** , collected video data is stored temporarily, then marked for automatic deletion. [Anonymized](https://policies.google.com/technologies/anonymization) data extracted from the video may be collected, stored, and analyzed to improve Google products and services\n- When **hosting Cloud Anchors** , **resolving Cloud Anchors** , or **using the\n ARCore Geospatial API**, this data collection and processing is required to provide API functionality.\n\n### Cloud Anchor data\n\n- When **hosting Cloud Anchors**, ARCore automatically creates and stores user-generated Cloud Anchor data. Google does not share this user-generated Cloud Anchor data with third parties.\n- When **hosting Cloud Anchors**, this data collection is required to provide app functionality.\n- When **resolving Cloud Anchors**, Google collects user-generated Cloud Anchor data to resolve Cloud Anchor API requests.\n- When **resolving Cloud Anchors**, Google does not share user-generated Cloud Anchor data with third parties."]]