개발자 가이드
User GuideDeveloper GuideAPI Guide🏠
English
English
  • 홈
  • 공통
    • Unified ID Linkage Scenario
    • Constant
    • FAQ
  • 플랫폼 별 가이드
    • Android
      • Link up
      • Event
      • Set User Identification Information
      • User Profile Settings
      • Action
        • Push
        • In-app messages
        • Notification Talk
        • Message
      • Privacy Policy
        • Support for Privacy Protection
        • Preparing for data disclosure requirements on Google Play
      • Release Notes
    • iOS
      • Link up
      • Event
      • Set user identification information
      • User Profile Settings
      • Action
        • Push
        • In-app messages
        • Notification Talk
        • message
      • Release Notes
    • HybridApp
      • Link up
    • Web
      • Link up
      • Event
      • Set user identification information
      • User Profile Settings
      • Action
        • In-app messages
        • Notification Talk
        • Message
      • Advanced use cases
        • Additional Settings
      • Release Notes
Powered by GitBook
On this page
  • Items by data type
  • Location
  • Personal information
  • Financial Information
  • Health and Fitness
  • Photos and Videos
  • Audio file
  • Files and Documents
  • Calendar
  • Contact
  • App Activity
  • Web Browsing
  • App information and performance
  • Device or other ID
  • Data Collection and Security
  • Purpose of data collection and sharing
  1. 플랫폼 별 가이드
  2. Android
  3. Privacy Policy

Preparing for data disclosure requirements on Google Play

PreviousSupport for Privacy ProtectionNextRelease Notes

Last updated 3 months ago

As of April 2022, Android developers will be required to complete to disclose their privacy and security practices . This guide provides instructions on how to complete this new form with information about how DFINERY handles your app data.

This document provides information about the data processed by the DFINERY SDK in connection with the Google Safety Section questionnaire. This document does not constitute legal advice and you should consult with your legal team before submitting any information to Google.

Items by data type

The data that DFINERY collects depends on your specific integration and the user data you choose to collect.

Location

Data Type
Whether or not to collect DFINERY

Approximate location

Not collected

Exact location

Not collected

Personal information

Data Type
Whether or not to collect DFINERY

Name

Basically not collected

Email address

Basically not collected

User ID

Basically not collected

Address

Not collected

Phone number

Basically not collected

Race and Ethnicity

Not collected

Political or religious beliefs

Not collected

Sexual orientation

Basically not collected

Other information

Basically not collected

Financial Information

Data Type
Whether or not to collect DFINERY

User Payment Information

Basically not collected

Purchase History

Basically not collected

Credit Score

Not collected

Other financial information

Not collected

Health and Fitness

Data Type
Whether or not to collect DFINERY

Health Information

Not collected

Fitness Information

Not collected

Message

Data Type
Whether or not to collect DFINERY

Email

Not collected

SMS or MMS

Not collected

Other in-app messages

When you send in-app messages or push notifications through DFINERY, we collect information about when users open or read these messages.

Photos and Videos

Data Type
Whether or not to collect DFINERY

Picture

Not collected

Video

Not collected

Audio file

Data Type
Whether or not to collect DFINERY

Record voice or sound

Not collected

Music file

Not collected

Other audio files

Not collected

Files and Documents

Data Type
Whether or not to collect DFINERY

Files and Documents

Not collected

Calendar

Data Type
Whether or not to collect DFINERY

Calendar Events

Not collected

Contact

Data Type
Whether or not to collect DFINERY

Contact

Not collected

App Activity

Data Type
Whether or not to collect DFINERY

App Interaction

DFINERY collects session activity data by default. All other interactions and activities are determined by the user's settings in the app.

In-app search history

Not collected

Installed Apps

Not collected

Other User Generated Content

Not collected

Other activities

Not collected

Web Browsing

Data Type
Whether or not to collect DFINERY

Web Browsing History

Not collected

App information and performance

Data Type
Whether or not to collect DFINERY

Crash Log

Not collected

Diagnosis

Not collected

Other app performance data

Not collected

Device or other ID

Data Type
Whether or not to collect DFINERY

Device or other ID

DFINERY collects App Set Id and if you set an advertising ID, the advertising ID may also be collected.

Data Collection and Security

Question
Answer for DFINERY SDK

Does the SDK transmit that data off the device?

Yes

Does the SDK transfer data to third parties, such as other apps on the user's device?

No

Does the SDK encrypt data in transit?

Yes

Can app developers and users request deletion of collected user data?

Yes

Purpose of data collection and sharing

For each Data Type, you must provide Google Play with the purpose of collecting and sharing the data.

Purpose of data collection and sharing
Check or not
Reference

Analytics

✅

We collect app usage information through the DFINERY SDK, so please check this.

Developer Communication

🤔

Check this when using the push and in-app message functions for new feature descriptions, app update notifications, etc. through the Action of the DFINERY SDK.

Advertising or Marketing

❎

Fraud Prevention, Security, and Compliance

✅

DFIENRY SDK checks for fraud when running an app, so it determines whether the execution is fraudulent.

Customization

🤔

Check this if you are sending personalized messages to users via push and in-app messages through Action of DFINERY SDK

App Features

❎

Account Management

❎

Google Play’s Data Safety Form