The Metrix library requires unique user identification to provide accurate attribution statistics for your application. To achieve this, it collects certain device identifiers that are accessible.

Although collecting this information does not require any additional permissions for your app, Google Play has specific sensitivities regarding some of these identifiers. Additionally, Google has stated in its documentation that apps must transparently disclose their data collection and sharing practices before a user downloads the app. Therefore, developers are required to complete the form provided in the Google Play Console and include the relevant link in their app’s policy page. It is important to note that this step is mandatory even for apps that do not collect the specified information.

Therefore, if you plan to publish your application on Google Play, to avoid potential warnings during the publication process, you must complete the following steps:

1. Disable the collection of sensitive identifiers within the Metrix SDK configuration.
2. Reference the Metrix Privacy Policy  within your application’s own Privacy Policy page.
3. Complete the Google Data Safety form accurately in the Google Play Console.

Disabling the Collection of Sensitive Identifiers

You can disable the collection of sensitive identifiers by adding the following lines to your application’s AndroidManifest.xml file.

<manifest>
 
  ...
 
  <application>
 
    ...
 
    <!-- Add the following lines -->
    <meta-data
        android:name="metrix_deviceId_collection_enabled"
        android:value="false" />
 
  </application>
</manifest>

Referencing Metrix’s Privacy Policy

Additionally, it is required that in the privacy policy of your application, which you submit when publishing the app on Google Play, you mention the use of the Metrix library and include a reference to the Metrix privacy policy  page.

The following text is a sample privacy policy that can be used for your application:

Completing the Google Data Safety Form in the Google Play Console

This section explains everything you need to complete this form.

Filling out this form requires having a Terms and Conditions or Privacy Policy page that explains how user data is protected.

The sections where you need to describe how Metrix operates within your application are outlined below.

Data Collection

In this section, you must answer general questions with yes or no.

1. Does your app collect or share any of the specified information?
2. Is all data collected by your app encrypted during transmission?
3. Have you provided users with the option to request deletion of their data?

To provide accurate attribution for advertising campaigns, Metrix requires a unique identifier for each user. For this purpose, it collects the Google Advertising ID and uses it as the unique identifier for each user. Please note that collecting this identifier does not require any sensitive access permissions. Additionally, Metrix encrypts all data transmitted through the SDK and allows its customers to delete data for a specific user.

Therefore, the answers to the first two questions will be “Yes”. The answer to the third question depends on your application type and the options you provide to users for requesting data deletion.

Type of Information

In this section, you must specify the types of data you collect. The required details are as follows:

1. Is this data shared?
2. Is the data processed ephemerally?
3. Is providing this data mandatory or optional for the user?
4. Purposes for data collection

As mentioned, one of the data points collected by Metrix is the Google Advertising ID, which must be specified under the Device or other IDs section.

Data Sharing

Data sharing refers to any transfer of your app’s user data by the app itself or the libraries it uses to a third-party platform. This transfer can occur directly from the application or via server-to-server transmission.

There are exceptions to this that must be considered:

1. Transferring data to service providers whose services are performed on your behalf and at your request.
2. Transferring data to fulfill legal or governmental purposes.
3. Sharing initiated by the user, where the user explicitly grants permission to access the data.

Based on this definition, the Metrix service does not share user data with third parties.

Ephemeral Processing

Ephemeral processing refers to processing data solely in RAM without any persistent storage. Given the nature of the Metrix service, data is not processed in this manner.

Data Collection Purposes

Metrix, as an attribution and analytics service, helps you understand how users interact with your application and their behavior within it. Therefore, the purpose that should be stated for data collection by Metrix is Analytics.

Summary

When using the Metrix service and integrating the Metrix library into your application, it is sufficient to consider the above points when completing the Data Safety form. Please also note that if you use other SDKs or collect any data based on your application’s specific type, you must have detailed information about their data collection practices to answer the form questions accurately.

Therefore, the correct answers to the form questions depend solely on your application’s data collection methods and functionality, and may vary across different SDKs and applications. The answers specified in this document are determined solely based on Metrix’s operational characteristics.