Google Play data safety section for deltaDNA
Starting April 2022, Android developers publishing on the Google Play store must define what data their apps collect, including the data collected by integrated third-party SDKs such as deltaDNA. For your convenience, deltaDNA provides information on its data collection practices below.
For more information on Google’s data safety disclosure policies, including terminology definitions, please see the Google documentation.
Data collection survey
Does the SDK collect or share any of the required user data types? | Yes* |
Is all of the data collected by the SDK encrypted in transit? | Yes** |
Does the SDK provide a way for users to request that their data is deleted? | Yes |
*deltaDNA provides an SDK for developers to integrate in their games, as well as APIs for developers to submit data from their own servers. On that basis, we collect this data. Developers can send events with any user-related contents – we are not the data controller in this circumstance.
**SSL/HTTPS.
Data types
Location | Collected | Shared | Ephemeral | Required | Purpose |
Does the SDK collect the user’s approximate location? | Yes | Not applicable (N/A) | No | Yes | App functionality |
Does the SDK collect the user’s precise location? | Yes* | N/A | No | Yes** | Up to developer |
*If developer sends it in event contents.
**Up to developer implementation – we cannot influence this.
Personal information | Collected | Shared | Ephemeral | Required | Purpose |
Does the SDK collect the user’s name? | Yes* | N/A | No | Yes** | Up to developer |
Does the SDK collect the user’s email address? | Yes* | N/A | No | Yes** | Up to developer |
Does the SDK collect the user’s personal identifiers? | Yes*** | N/A | No | Yes | App functionality |
Does the SDK collect the user’s address? | Yes* | N/A | No | Yes** | Up to developer |
Does the SDK collect the user’s phone number? | Yes* | N/A | No | Yes** | Up to developer |
Does the SDK collect the user’s race and ethnicity? | Yes* | N/A | No | Yes** | Up to developer |
Does the SDK collect the user’s political or religious beliefs? | Yes* | N/A | No | Yes** | Up to developer |
Does the SDK collect the user’s sexual orientation or gender identity? | Yes* | N/A | No | Yes** | Up to developer |
Does the SDK collect any of the user’s other personal information? | Yes* | N/A | No | Yes** | Up to developer |
*Developers can record whatever data they desire, we are not the data controller in this circumstance.
**Up to developer implementation – we cannot influence this.
***Collected. Randomly-generated GUID per install (or developer-provided) ID.
Financial info | Collected | Shared | Ephemeral | Required | Purpose |
Does the SDK collect the user’s purchase history? | Yes* | N/A | No | Yes** | Up to developer |
Does the SDK collect the user’s credit info? | Yes* | N/A | No | Yes** | Up to developer |
Does the SDK collect the user’s credit card, debit card, or bank account number? | Yes* | N/A | No | Yes** | Up to developer |
Does the SDK collect any of the user’s other financial info? | Yes* | N/A | No | Yes** | Up to developer |
*Developers can record whatever data they desire, we are not the data controller in this circumstance.
**Up to developer implementation – we cannot influence this.
Health and fitness | Collected | Shared | Ephemeral | Required | Purpose |
Does the SDK collect the user’s health information? | Yes* | N/A | No | Yes** | Up to developer |
Does the SDK collect the user’s fitness information? | Yes* | N/A | No | Yes** | Up to developer |
*Developers can record whatever data they desire, we are not the data controller in this circumstance.
**Up to developer implementation – we cannot influence this.
Messages | Collected | Shared | Ephemeral | Required | Purpose |
Does the SDK collect the user’s emails? | Yes* | N/A | No | Yes** | Up to developer |
Does the SDK collect the user’s SMS or MMS messages? | Yes* | N/A | No | Yes** | Up to developer |
Does the SDK collect any of the user’s other in-app messages? | Yes* | N/A | No | Yes** | Up to developer |
*Developers can record whatever data they desire, we are not the data controller in this circumstance.
**Up to developer implementation – we cannot influence this.
Photos and videos | Collected | Shared | Ephemeral | Required | Purpose |
Does the SDK collect the user’s photos? | Yes* | N/A | No | Yes** | Up to developer |
Does the SDK collect the user’s videos? | Yes* | N/A | No | Yes** | Up to developer |
*Developers can record whatever data they desire, we are not the data controller in this circumstance.
**Up to developer implementation – we cannot influence this.
Audio files | Collected | Shared | Ephemeral | Required | Purpose |
Does the SDK collect the user’s voice or sound recordings? | Yes* | N/A | No | Yes** | Up to developer |
Does the SDK collect the user’s music files? | Yes* | N/A | No | Yes** | Up to developer |
Does the SDK collect any of the user’s other audio files? | Yes* | N/A | No | Yes** | Up to developer |
*Developers can record whatever data they desire, we are not the data controller in this circumstance.
**Up to developer implementation – we cannot influence this.
Files and docs | Collected | Shared | Ephemeral | Required | Purpose |
Does the SDK collect the user’s files and or documents? | Yes* | N/A | No | Yes** | Up to developer |
*Developers can record whatever data they desire, we are not the data controller in this circumstance.
**Up to developer implementation – we cannot influence this.
Calendar | Collected | Shared | Ephemeral | Required | Purpose |
Does the SDK collect the user’s calendar events? | Yes* | N/A | No | Yes** | Up to developer |
*Developers can record whatever data they desire, we are not the data controller in this circumstance.
**Up to developer implementation – we cannot influence this.
Contacts | Collected | Shared | Ephemeral | Required | Purpose |
Does the SDK collect the user’s contacts? | Yes* | N/A | No | Yes** | Up to developer |
*Developers can record whatever data they desire, we are not the data controller in this circumstance.
**Up to developer implementation – we cannot influence this.
App activity | Collected | Shared | Ephemeral | Required | Purpose |
Does the SDK collect data on page views and taps in the app? | Yes* | N/A | No | Yes** | Up to developer |
Does the SDK collect in-app search history? | Yes* | N/A | No | Yes** | Up to developer |
Does the SDK collect data on installed apps? | Yes* | N/A | No | Yes** | Up to developer |
Does the SDK collect data on any other user-generated content? | Yes* | N/A | No | Yes** | Up to developer |
Does the SDK collect data on any other app activity? | Yes*** | N/A | No | Yes | Analytics |
*Developers can record whatever data they desire, we are not the data controller in this circumstance.
**Up to developer implementation – we cannot influence this.
Web browsing | Collected | Shared | Ephemeral | Required | Purpose |
Does the SDK collect data on the user’s web browsing history? | Yes* | N/A | No | Yes** | Up to developer |
*Developers can record whatever data they desire, we are not the data controller in this circumstance.
**Up to developer implementation – we cannot influence this.
App info and performance | Collected | Shared | Ephemeral | Required | Purpose |
Does the SDK collect crash logs? | No | N/A | N/A | N/A | N/A |
Does the SDK collect app diagnostics? | Yes* | N/A | No | Yes** | Up to developer |
Does the SDK collect any other app performance data? | Yes* | N/A | No | Yes** | Up to developer |
*Developers can record whatever data they desire, we are not the data controller in this circumstance.
**Up to developer implementation – we cannot influence this.
Device or other identifiers | Collected | Shared | Ephemeral | Required | Purpose |
Does the SDK collect data on the user’s device or other identifiers? | Yes* | Yes | No | Yes** | Up to developer |
*Developers can record whatever data they desire, we are not the data controller in this circumstance.
**Up to developer implementation – we cannot influence this.