---
metadata:
  - name: generator
    content: Diplodoc Platform v5.50.6
alternate:
  - https://appmetrica.yandex.com/docs/en/data-security/google-data-safety.md
  - https://appmetrica.yandex.com/docs/ru/data-security/google-data-safety.md
---
> **Documentation Index:** Fetch the complete configuration index at https://appmetrica.yandex.com/docs/en/llms.txt

# Data safety in Google Play

According to [Google requirements](https://support.google.com/googleplay/android-developer/answer/10787469), mobile app developers must inform Google Play about what data they collect through their apps. This includes data collected and handled through any third-party libraries or SDKs used in their apps. To do this, fill out the **Data safety** form on the [App content](https://play.google.comconsole/app/app-content/summary) page in Play Console.

The following AppMetrica SDK guidance is designed to help developers in disclosing their app's data collection, sharing, and security practices **specifically related to the AppMetrica SDK's processing.**

{% note info "" %}

When using the AppMetrica SDK, it's your responsibility to ensure that your app is compliant with the applicable privacy policy. If you collect and/or transmit any data, you have to make sure that the data is collected, secured, and managed properly.

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 user data collection, sharing, and security practices.

{% endnote %}

## AppMetrica SDK {#sdk}

### Data collection {#data-collection}

"Collect" means transmitting data from your app off a user's device.

AppMetrica SDK in your app transmits user data off the device. The purposes for collection are listed in the [Purposes](#purposes) section below.

### Data sharing {#data-sharing}

"Sharing" refers to transferring user data collected from your app to a third party.

User data collected from your app is transferred directly to a third party via the AppMetrica SDK included in your app. The purposes for sharing are listed in the [Purposes](#purposes) section below.

### Data handling {#data-handling}

You can also disclose whether each data type collected by your app is "optional" or "required".

All data types collected in your app via the AppMetrica SDK and listed in the [Data types](#data-types) section below are "optional" (the developers can [initialize the SDK with disabled statistics sending](https://appmetrica.yandex.com/docs/en/data-security/notification.md) before getting consent).

### Other data disclosures {#disclosures}

This section is also an opportunity for you to showcase your app's privacy and security practices to your users (e.g., encryption in transit, a deletion request mechanism).

The AppMetrica SDK encrypts all user data listed on this page in transit using AES-128.

The AppMetrica SDK enables app developers to delete user data in a manner consistent with the functionality of the SDK.

## Data types {#data-types}

Information about how user data of each type is collected and shared through the AppMetrica SDK.

Please note that the following table assumes the AppMetrica SDK default configurations. App developers are responsible for ensuring that they adapt accordingly in line with their specific configurations and uses.

#|
|| **Data type** | **Description** | **AppMetrica SDK data collection and sharing (default configuration)** ||
|| **Location** | > | > ||
|| **Precise location** | The location of the user or device within an area of less than three square kilometers, such as a location obtained using Android's `ACCESS_FINE_LOCATION` permission. | No<br><br>Collection of this data is disabled by default in all SDK versions starting from 5.0.0.<br><br>The app developer can configure the transmission of this data by enabling the `Location tracking` parameter in the SDK settings.<br><br>This means that only if developers allow its app to collect location data from users after obtaining user's explicit consent to such data collection, then such data is also collected via the AppMetrica SDK. The SDK **does not** collect or attempt to collect such information independently. ||
|| **Approximate location** | The location of the user or device within an area of at least three square kilometers, such as the city the user is in or a location obtained using Android's `ACCESS_COARSE_LOCATION` permission. | No<br><br>Collection of this data is disabled by default in all SDK versions starting from 5.0.0.<br><br>The app developer can configure the transmission of this data by enabling the `Location tracking` parameter in the SDK settings.<br><br>This means that only if developers allow its app to collect location data from users after obtaining user's explicit consent to such data collection, then such data is also collected via the AppMetrica SDK. The SDK **does not** collect or attempt to collect such information independently. ||
|| **Personal info** | > | > ||
|| **Name** | The user's preferred name, such as their first name, last name, or nickname. | No<br><br>The app developer can configure how that data is transmitted if necessary. ||
|| **Email address** | The user's email address. | No<br><br>The app developer can configure how that data is transmitted if necessary. ||
|| **User IDs** | The user's identifiers, such as their account number, ID, or name. | No<br><br>The app developer can configure how that data is transmitted if necessary. ||
|| **Address** | The user's address, such as their postal or home address. | No<br><br>The app developer can configure how that data is transmitted if necessary. ||
|| **Phone number** | The user's phone number. | No<br><br>The app developer can configure how that data is transmitted if necessary. ||
|| **Race and ethnicity** | Information about the user's race or ethnicity. | No<br><br>The app developer can configure how that data is transmitted if necessary. ||
|| **Political or religious beliefs** | Information about the user's political or religious beliefs. | No<br><br>The app developer can configure how that data is transmitted if necessary. ||
|| **Sexual orientation** | Information about the user's sexual orientation. | No<br><br>The app developer can configure how that data is transmitted if necessary. ||
|| **Other info** | Any other personal information, such as date of birth, gender identity, or veteran status. | No<br><br>The app developer can configure how that data is transmitted if necessary. ||
|| **Financial info** | > | > ||
|| **User payment info** | Information about the user's financial accounts, such as their credit card number. | No<br><br>The app developer can configure how that data is transmitted if necessary.<br><br>Starting from SDK version 4.0, automatic collection is available for in-app purchase data. You can enable and disable it using the `withRevenueAutoTracking Enabled` method. ||
|| **Purchase history** | Information about the user's purchases and transactions. | No<br><br>The app developer can configure how that data is transmitted if necessary.<br><br>Starting from SDK version 4.0, automatic collection is available for in-app purchase data. You can enable and disable it using the `withRevenueAutoTracking Enabled` method. ||
|| **Credit score** | Information about the user's credit rating. | No<br><br>The app developer can configure how that data is transmitted if necessary.<br><br>Starting from SDK version 4.0, automatic collection is available for in-app purchase data. You can enable and disable it using the `withRevenueAutoTracking Enabled` method. ||
|| **Other financial info** | Other financial information, such as the user's salary or debts. | No<br><br>The app developer can configure how that data is transmitted if necessary.<br><br>Starting from SDK version 4.0, automatic collection is available for in-app purchase data. You can enable and disable it using the `withRevenueAutoTracking Enabled` method. ||
|| **Health and fitness** | > | > ||
|| **Health info** | Information about the user's health, such as medical records or symptoms. | No ||
|| **Fitness info** | Information about the user's physical activity, such as workouts. | No ||
|| **Messages** | > | > ||
|| **Emails** | Content, subject line, and information about the sender and recipients of the user's emails. | No ||
|| **SMS or MMS** | Content and information about the sender and recipients of the user's messages. | No ||
|| **Other in-app messages** | Other types of messages, such as instant messages or chat content. | No ||
|| **Photos or videos** | > | > ||
|| **Photos** | The user's photos. | No ||
|| **Videos** | The user's videos. | No ||
|| **Audio files** | > | > ||
|| **Voice or sound recordings** | Audio recordings and recordings of the user's voice, such as voice messages. | No ||
|| **Music files** | The user's music files. | No ||
|| **Other audio files** | Other audio files created or provided by the user. | No ||
|| **Files and docs** | > | > ||
|| **Files and docs** | The user's documents and other files or any information about them, such as file names. | No ||
|| **Calendar** | > | > ||
|| **Calendar events** | Information from the user's calendar, such as events, event notes, and attendees. | No ||
|| **Contacts** | > | > ||
|| **Contacts** | Information about the user's contacts, such as contact names or message history, and information like usernames, call history, contact recency, contact frequency, and interaction duration. | No ||
|| **App activity** | > | > ||
|| **App interactions** | Information about how the user interacts with the app, such as the number of times they visited a page or the sections they tapped. | No<br><br>The app developer can configure the transmission of this data using custom events. ||
|| **In-app search history** | Information about what the user has searched for in your app. | No<br><br>The app developer can configure transmission for this data using custom events. ||
|| **Installed apps** | Information about the apps installed on the user's device. | No<br><br>The app developer can configure transmission for this data using custom events. ||
|| **Other user-generated content** | Other user-generated content not mentioned in any section, such as user bios, notes, or open-ended responses. | No<br><br>The app developer can configure transmission for this data using custom events. ||
|| **Other actions** | Other in-app user actions not mentioned in any section, such as gameplay, likes, and selected dialog options. | No<br><br>The app developer can configure transmission for this data using custom events. ||
|| **Web browsing** | > | > ||
|| **Web browsing history** | Information about the sites visited by the user. | No ||
|| **App info and performance** | > | > ||
|| **Crash reports** | Data from your app's crash log, such as the number of crashes and stack traces or other information directly related to crashes. | Yes ||
|| **Diagnostics** | Information about the app's performance, such as battery life, loading time, latency, frame rate, or technical diagnostics. | Yes<br><br>AppMetrica SDK can collect battery level data for crash analytics. ||
|| **Other app performance data** | Other app performance data not mentioned here. | Yes<br><br>AppMetrica SDK can collect additional data. For example, technical information about the device, including the OS version and screen type. ||
|| **Device or other IDs** | > | > ||
|| **Device or other IDs** | Device, browser, or app IDs, such as the IMEI number, MAC address, Widevine device ID, Firebase installation ID, or advertising ID. | Yes, if the developer obtained the user's permission.<br><br>Collection of this data can be disabled in SDK version 5.0.0 or higher. ||
|#

## Purposes {#purposes}

Information about data collection and sharing purposes specifically related to the AppMetrica SDK's processing.

Please note that purposes of collection and sharing may depend on the particular use or implementation of the AppMetrica SDK by a given developer.

#|
|| **Data purpose** | **Description** | **AppMetrica SDK data collection and sharing purposes** ||
|| **App functionality** | Used for features that are available in the app | No ||
|| **Analytics** | Used to collect data about how users use the app or how it performs | Yes ||
|| **Developer communications** | Used to send news or notifications about the app or the developer | Yes ||
|| **Advertising or marketing** | Used to display or target ads or marketing communications, or measuring ad performance | Yes ||
|| **Fraud prevention, security, and compliance** | Used for fraud prevention, security, or compliance with laws | No ||
|| **Personalization** | Used to customize your app, such as showing recommended content or suggestions | No ||
|| **Account management** | Used for the setup or management of a user's account with the developer | No ||
|#

<!-- source: en/_includes/feedback-button.md -->
If you didn't find the answer you were looking for, you can use the feedback form to submit your question. Please describe the problem in as much detail as possible. Attach a screenshot if possible.

<a href="../troubleshooting/feedback-new">
  <span class="button">Contact support</span>
</a>

<a href="../troubleshooting/feedback-docs">
  <span class="button">Suggest an improvement for documentation</span>
</a>
<!-- endsource: en/_includes/feedback-button.md -->