Verve's data processing practices for Google Play Console's Data Safety form
Prepare for Google Play’s Data Disclosure Requirements
In May 2021, Google Play announced the new Data safety section, which is a developer-provided disclosure for an app’s data collection, sharing, and security practices.
This page can help you complete the requirements for this data disclosure in regards to your usage of Verve’s HyBid Android SDK. On this page, you can find information on whether and how our SDKs handle end-user data.
We aim to be as transparent as possible in supporting you; however, as the app developer, you are solely responsible for deciding how to respond to Google Play’s Data safety section form regarding your app’s end-user data collection, sharing, and security practices.
How To Use the Information on This Page
This page lists the end-user data collected by only the latest version of Verve’s HyBid Android SDK.
We provide information about data collected automatically versus data collected depending on your usage. Automatic collection means that the SDK collects specific data without you invoking any specific method or class in your app. However, in many cases, the data collected by the SDK depends on your app’s specific usage of the product, meaning your app’s configuration and how you invoke the SDK.
To complete your data disclosure, you can use Android’s guide about data types to help you determine which data type best describes the collected data. In your data disclosure, make sure to also account for how your specific app shares and uses the collected data.
Important:
To help you ensure that your app’s disclosures are accurate, we recommend the following:
- Always use the latest SDK versions in your app. This page lists the data collected by only the latest version of Verve’s HyBid Android SDK.
- Review this page whenever you update your app’s SDK versions. Check that your data disclosures are accurate and up-to-date.
Overview of Data Encryption, Data Sharing, and Data Deletion for Verve’s HyBid Android SDKs
| Data Encryption | For the collected end-user data listed on this page, HyBid Android SDK encrypts the data in transit using HTTPS. |
| Data sharing | For the collected end-user data listed on this page, Verve does not transfer this data to third-parties except: To third-party subprocessors that assist us in providing Verve services. In accordance with your instructions (for example, if you choose to link Verve to other non-Verve services). |
| Data deletion | Verve enables developers to delete end-user data in a manner consistent with the functionality of the Verve services. |
Data Collected and Shared Automatically
| Data Type Category | Data Type | Collection Purposes | Relevance to HyBid Android SDK’s Data Collection Policies |
|---|---|---|---|
| Identifiers | Device ID | Advertising or marketing Fraud prevention, security and compliance | HyBid Android SDK collects Ad ID (Identifier for Advertisers) when made available by the user per the device settings. |
| Usage Data | Advertising Data | Advertising or marketing Fraud prevention, security and compliance | HyBid Android SDK collects information related to the ads served to users of the app via the Verve services (e.g. impressions, advertiser name, clicks, completions). |
Data Collected and Shared Depending On Your Usage
| Data Type Category | Data Type | Collection Purposes | Relevance to HyBid Android SDK’s Data Collection Policies |
|---|---|---|---|
| Location | Precise Location | Advertising or marketing | It is optional for publishers to share “precise location” and allow HyBid Android SDK to collect it. This means that only if the publishers allows its app to collect location data from users after obtaining user’s explicit consent to such data collection, then such data is also collected via the HyBid Android SDK. HyBid Android SDK does not collect or attempt to collect such information independently. |
| Location | Coarse Location | Advertising or marketing | It is optional for publishers to share “coarse location” and allow HyBid Android SDK to collect it. This means that only if the publishers allows its app to collect location data from users after obtaining user’s explicit consent to such data collection, then such data is also collected via the HyBid Android SDK. HyBid Android SDK does not collect or attempt to collect such information independently. |
Data Handling
Android Ad ID is collected by default. The Ad ID can be reset by users using Ad ID control. As the app developer, you can prevent the collection of Ad Ids by updating the app’s manifest file.
Certain other features in Verve’s HyBid Android SDK, such as the limit ad tracking feature, may also disable transmission of the Ad ID and other data.
Upload to Google Play Console
To simplify the process of gathering the information in a standardized manner, we have put together a .csv file based on the official Google template, containing all of Verve’s data handling practices for our HyBid Android SDK. You can utilize this .csv file to merge it with your app’s and other vendors’ data handling practices and convert it into a master file, which can be uploaded directly to the Data Safety section of your app in the Google Play Console.