[[[Important]]] Prepare for Google Plays data disclosure requirements

Introduction

In May 2021, Google Play announced a new Data Security section, developer-provided disclosures about their apps' data collection, sharing, and security practices.

This page can help you complete your requirements for this disclosure of data regarding your use of the DFINERY (Adbrix) Android SDK.
On this page you can find information about whether and how the SDK processes end-user data, including applicable configurations that you can control as an app developer.

DFINERY aims to support our clients as transparently as possible. However, app developers are solely responsible for determining how their customers respond to forms in the Data Security section of Google Play regarding their apps end-user data collection, sharing, and security practices.

How we use information on this page

This page lists end-user data collected only from the latest version of each DFINERY (Adbrix) Android SDK.

If you are using an older version of DFINERY (Adbrix) Android SDK, we recommend updating to the latest version to ensure your app's disclosures are accurate.

Data collected items

DFINERY (Adbrix) SDK collects data on advertising identification values, device information, and app information.

Please refer to the items below for a detailed list.

Advertising identification value

• GAID (Android Advertising Identifier) ​​(optional)

device information

• Device model / OS / manufacturer / screen resolution / carrier / language / country / ssaid (Android ID) / location information (optional)
• platform
• Network used (LTE, Wifi)

App information

• package name
• API version
• App version
• Build ID
• installer

Items by data type

The table below explains whether DFINERY (AdBrix) SDK is collected by data type provided in the Google Play data security section. When linking DFINERY (AdBrix) SDK, if information for each data type is being passed through the SDK, this must be displayed in the Google Play data security section.

Data Type	DFINERY SDK Collection or not?	Note
location information Approximate location information precise location information	Note	When linking with DFINERY SDK, location information is not collected by default. However, if location information is passed through the setLocation API , the SDK can collect it.
Privacy name Email Address personal identifier address phone number race and ethnicity sexual orientation or gender identity Other personal information	Note	DFINERY SDK does not collect users personal information by default. However, the user's encrypted identifier and other personal information such as gender and age can be collected through the login / setUserProperties API .
financial information Purchase history credit information Credit card, debit card or bank account information Other financial information	Optional	DFINERY SDK collects purchase history through purchase API . In addition to purchase history, the SDK can collect other items if they are delivered through a custom event.
app activity App interaction Search history within the app installed apps Other user-generated content other tasks	Note	When integrating with the DFINERY SDK, lifecycle information about execution and termination within the app is collected. In addition, the SDK collects in-app activities, such as in-app search history, when they are delivered through Custom events.
Device or other ID	Optional	DFINERY SDK collects GAID (Google Advertiser ID) if the option is enabled on the user's device.
web navigation Web browsing history	Note	DFINERY SDK does not collect web browsing history by default. However, if your app is a hybrid app that uses WebView and the DFINERY Web SDK is installed in the web page, visit records of the web page are collected.
health and fitness health information fitness information	Note	DFINERY SDK does not collect your health and fitness information by default. However, if this is delivered through a Custom event, the SDK can collect it.
message email SMS or MMS Other pop-up messages	No	DFINERY SDK does not collect message information on your device.
photos and videos	No	DFINERY SDK does not collect photo and video information.
audio file Voice or sound recordings music files other audio files	No	DFINERY SDK does not collect audio file information.
files and documents	No	DFINERY SDK does not collect file and document information.
contact	No	DFINERY SDK does not collect contact information.
App information and performance Abnormal termination log Diagnosis Other app performance data	No	DFINERY SDK does not collect app information and performance information.

data sharing

“Data sharing” here means sharing selected data with a third-party company regardless of whether the user device is turned on or off.

Exceptions are permitted for some of the situations below.

• When DFINERY delivers data to the app developer according to the app developer's data request.
• When the data is passed on for legal purposes. (ex. government request for data provision)
• When passing data to end users in accordance with the app terms and conditions.
• Anonymous data sharing.

As a service provider, DFIENRY shares data only at the request, selection, and settings of the app developer. If you provide data to a third party for app marketing (e.g., extracting and sharing audience data for media postback settings, targeting, and retargeting), this is considered data sharing.

Data batch processing

“Temporary processing of data” here means temporarily processing collected data without storing it in memory. Data collected from DFINERY SDK is basically transmitted in real time, but is stored depending on the user's network situation and transmitted when the network is reactivated.

your choice

This means whether end users have choices about how their data can be used and shared. DFINERY SDK provides a GDPR API to allow users to refuse data collection.

Purpose of data collection and sharing

For each data type, the purpose of collecting and sharing the data must be provided to Google Play.

Purpose of data collection and sharing	Checked or not	Note
analytics	Yes	Check this because app usage information is collected through the DFINERY SDK.
Developer Communication	Optional	Check this when using the push and in-app message functions for new feature descriptions, app update information, etc. through the Growth Action of the DFINERY SDK.
advertising or marketing	Yes	Using the information collected from the DFINERY SDK, we check when advertising performance is provided to third-party media through targeting/retargeting advertisements and postbacks.
Fraud Prevention, Security, and Compliance	Yes	DFIENRY SDK checks this when running the app as it determines whether the execution is fraudulent.
Customization	Optional	Check if a personalized message is being sent to the user through push or in-app message through the Growth Action of the DFINERY SDK.
App features	No
Account Management	No

How to Fill Out the Google Play Data Security Section

Please refer to the guide below to fill out the Google Play data security section.

Reference: [Guide to creating Google Play data security section]