[[[Important]]] Google Play data security settings instructions
1.Getting started
Google Play's data security policy has been updated in July 2021.Accordingly, by April 2022, all apps released on Google Play must disclose security-related information about data applied to the app to Google Play. When launching or updating after linking the DFINERY (Adbrix) SDK, you must update the data security settings as follows.
References: [Information courtesy of Google Play's Data Security section]
[[Quote: Risk: Moderate]] The survey below was prepared based on data collection through the DFINERY (Adbrix) SDK.
The guide says "No", but depending on how the app data is processed, you may need to answer "Yes".
2. Data Security Settings Section
Access the Google Play Console, select the [Data Security] section in the "Policy -> App Content" menu at the bottom left, and click the "Start" button.
After reading the instructions on defining data security and what needs to be disclosed, click the “Next” button.
3. Data Collection and Security
When linking the DFINERY (Adbrix) SDK, set the answers to the questions below and click the “Next” button.
| Does your app collect or share any types of required user data? | yes |
| Is all user data collected by the app encrypted and transmitted? | yes |
| How to create an account / How to request data deletion | Reply according to app policy |
If account and data deletion is provided within the app, you must enter a URL that provides instructions on how to do so.
3. data type
Set the type of data collected. You must set all information collected in addition to the information collected by the DFINERY (Adbrix) SDK.Here, we will mainly explain the information collected by the DFINERY (Adbrix) SDK.However, depending on the type of data your app processes, you may need to write your answer differently than the example answer.
1) Personal information (Optional)
Select when setting and delivering the user's personal information through the Login API and UserProperty API in the DFINERY (Adbrix) SDK.
- Personal Identifier: Select when passing User ID through the Login API of the DFINERY (Adbrix) SDK.
- Other personal information: Select when delivering personal information through setUserProperties API of DFINERY (Adbrix) SDK.
[[Quote:Warning:Medium]] The above is an example based on the basics of SDK integration. Depending on the data your app processes, you may need to choose a different answer.
2) Financial information (Optional)
When linking the Purchase API of the DFINERY (Adbrix) SDK, select Financial Information Purchase History.
- Purchase history: When linking the Purchase API of the DFINERY (Adbrix) SDK
- Other financial information: Select if the information is delivered through the Custom event of the DFINERY (Adbrix) SDK.
[[Quote:Warning:Medium]] The above is an example based on the basics of SDK integration. Depending on whether you are linking financial information to a custom event in the SDK or processing financial information in your app, you will need to choose a different answer.
3) App activity (Required)
Select if you want to collect the users in-app activity and pass on this data.In the case of “Page views and tabs in the app”, be sure to select it as it is collected by the SDK during basic integration.
- App interaction (required): Must be selected as information about app launch and termination is collected when basic integration with DFINERY (Adbrix) SDK is performed.
- Other app activities: Select if the relevant information is collected and delivered through the Custom event of the DFINERY (Adbrix) SDK, or processed in the app.
[[Quote:Warning:Medium]] The above is an example based on the basics of SDK integration. You must choose a different answer depending on the scope of SDK integration and the data processed by the app.
4) Device or other identifier (Required)
Select if you want to collect your device identifier. DFINERY (Adbrix) SDK collects Google advertising ID based on the users selection, so be sure to select it.
Device or other identifier (required): DFINERY (Adbrix) SDK collects Google advertising ID, so be sure to select this.
4. Data handling and processing
Set the purpose of data collection and sharing for each data selected in data type 3.
Set each data type as follows.
1) Whether data is collected/shared
Do you collect or share data? Or do you both collect and share?
Since data is collected and shared through DFINERY (Adbrix) SDK, select both “Collected” and “Shared.”
2) Whether data is temporarily processed
Is this data processed temporarily?
DFINERY (Adbrix) SDK processes events immediately when they are called, so select “Yes”.
3) Whether the user can refuse collection
Is this data required for the app? Or can users choose whether to collect it or not?
In DFINERY (Adbrix) SDK, users can temporarily suspend SDK operation and collection if desired through the GDPR API .
“Users can choose whether or not their data is collected.” Select .
[[Quote:Warning:Medium]] The above is an example based on the basics of SDK integration. If your app does not offer GDPR functionality, you will need to choose a different answer.
4) Reason for data collection
Why is this user data collected?
Data from DFINERY (Adbrix) SDK can be collected for various purposes.Basically, you can select the relevant item according to the functions provided by DFINERY.
| item | DFINERY function |
| analytics | Report displayed by default in the DFINERY console. |
| Developer Communication | Check to notify users of new app features and updates through DFINERY Growth Actions Push Message / in-app message. |
| advertising or marketing | Check this if you are running an advertising campaign through a tracking link. |
| Fraud Prevention, Security, and Compliance | DFINERY SDK basically collects data to prevent fraud. |
| Customization | Check if a personalized message is delivered to the user through DFINERY Growth Actions Push Message / in-app message. |
[[Quote:Warning:Medium]] The above is an example based on the basics of SDK integration. You will need to choose a different answer depending on how your app handles data.
5) Reasons for sharing data
Data from DFINERY (Adbrix) SDK can be collected for various purposes.Basically, you can select the relevant item according to the functions provided by DFINERY.
| item | DFINERY function |
| analytics | Report displayed by default in the DFINERY console. |
| Developer Communication | Check to notify users of new app features and updates through DFINERY Growth Actions Push Message / in-app message. |
| advertising or marketing | Check this if you are running an advertising campaign through a tracking link. |
| Fraud Prevention, Security, and Compliance | DFINERY SDK basically collects data to prevent fraud. |
| Customization | Check if a personalized message is delivered to the user through DFINERY Growth Actions Push Message / in-app message. |
[[Quote:Warning:Medium]] The above is an example based on the basics of SDK integration. You will need to choose a different answer depending on how your app handles data.
5. Preview and save data
Confirm the data security information set and click the “Save” button to finalize the section.
6. Contact support
If you have any questions or need support related to Google Play data security settings and DFINERY (Adbrix) SDK integration, please contact us by email below and we will provide active support.
support-tracker@adbrixsupport.zendesk.com