In May 2021, Google Play announced the new Data safety section , which is a developer-provided disclosure for an app's data collection, sharing, and security practices.
This page can help you complete the requirements for this data disclosure in regards to your usage of the Maps 3D SDK for Android. On this page, you can find information on how the Maps 3D SDK for Android handles end-user data, including any applicable configurations or invocations you can control as the app developer.
We aim to be as transparent as possible in supporting you; however, as the app developer, you are solely responsible for deciding how to respond to Google Play's Data safety section form regarding your app's end-user data collection, sharing, and security practices.
How to use the information on this page
This page lists the end-user data collected by only the latest version of the Maps 3D SDK for Android.
To complete your data disclosure, you can use Android's guide about data types to help you determine which data type best describes the collected data. In your data disclosure, make sure to also account for how your specific app shares and uses the collected data.
Data collected automatically
For example:
- Device metadata: OS version, name, model, brand, form factor.
- Maps 3D SDK for Android build and version information.
- Number of results returned.
- Internal Usage Attribution Identifier
Crash metrics
Data collected depending on your usage
| Data | Depending on your app's configuration and invocation, the Maps 3D SDK for Android... |
|---|---|
| Map interaction events | Collects interaction data, such as panning and zooming the map when the 3D map camera APIs are used, to improve Google services |
