Google Play Console - Data Safety
Understand the impact of the new Data Safety section in Google Play Console
Overview
Developers will now have a transparent way to show users if and how they collect, share, and protect user data before installing an app.
Google has introduced a new Data safety section in the Play Console. Any data shared with a third party must be declared on the Google Play Console using the newly-introduced data safety section.
This data will be displayed on the Google Play Store by late April 2022 and help the users make a more informed choice before installing an application.
For more information about the new declaration required in the Data safety section of the Play Console, refer to Google Play's Data safety help.
Note
This document is not legal advice. It is provided for your information and convenience. We strongly recommend that you must work closely with legal and other professional advisors to determine how you can comply with Google Play Console - Data Safety guidelines.
Data Safety
A user data type is any sensitive or personal information that can identify a user. Google will require app owners to display information about all the user data types collected in the app. You can pass the data types to CleverTap as either User Profile properties or Events.
After you log in to Google Play Console, go to App Content > Data Safety and answer questions about your data sharing. These questions are categorized into three sub-sections as follows:
Data Collection and Security
This section contains questions about data collection, security, and handling practices.
Question | Developer Response |
---|---|
Does your app collect or share any of the required user data types? |
|
Is all of the user data collected by your app encrypted in transit? |
|
Do you provide a way for users to request that their data is deleted? |
|
Third-party Data Share
CleverTap does not share data with any third parties.
Data Types
Through this section, the app owner can declare all the data types collected by the app.
Data Shared with CleverTap
CleverTap does not collect any of the data types by default. However, you can configure your app to share data types with CleverTap.
The following table will help you with privacy declaration for data types:
Category | Data Type | Description | Is Shared with CleverTap by Default? | Is Optional Sharing Possible with CleverTap? |
---|---|---|---|---|
Location | Approximate location | User or device physical location accurate to within an area greater than or equal to three square kilometers, such as the city a user is in, or location provided by Androidβs ACCESS_COARSE_LOCATION permission. | No | Yes. If you have configured to transmit this data type, respond accordingly. CleverTap Android SDK starting v3.1.9 and above (released in May 2018) has stopped tracking approximate location by default. Approximate location is captured only if the Device Network Information Reporting is enabled. |
Precise location | User or device physical location accurate to within an area less than three square kilometers, such as location provided by Androidβs ACCESS_FINE_LOCATION permission. | No | Yes.Precise Location is captured only if the user integrates the CleverTap GeoFencing SDK. | |
Personal info | Name | The way users refer to themselves, such as their first or last name, or nickname. | No | Yes. If you have configured to transmit this data to CleverTap, respond accordingly. |
Email address | The userβs email address. | No | Yes. If you have configured to transmit this data to CleverTap, respond accordingly. | |
User IDs | Identifiers that relate to an identifiable person. For example, an account ID, account number, or account name. | No | Yes. If you have configured to transmit this data to CleverTap, respond accordingly. | |
Address | The userβs address, such as a mailing or home address. | No | Yes. If you have configured to transmit this data to CleverTap, respond accordingly. | |
Phone number | The userβs phone number. | No | Yes. If you have configured to transmit this data to CleverTap, respond accordingly. | |
Race and ethnicity | Information about the userβs race or ethnicity. | No | Yes. If you have configured to transmit this data to CleverTap, respond accordingly. | |
Political or religious beliefs | Information about the userβs political or religious beliefs. | No | Yes. If you have configured to transmit this data to CleverTap, respond accordingly. | |
Sexual orientation | Information about the userβs sexual orientation. | No | Yes. If you have configured to transmit this data to CleverTap, respond accordingly. | |
Other info | Any other personal information, such as date of birth, gender identity, veteran status, and so on. | No | Yes. If you have configured to transmit this data to CleverTap, respond accordingly. | |
Financial info | User payment info | Information about the userβs financial accounts, such as credit card number. | No | Yes. If you have configured to transmit this data to CleverTap, respond accordingly. |
Purchase history | Information about purchases or transactions a user has made. | No | Yes.If you have configured to transmit this data to CleverTap, respond accordingly. | |
Credit score | Information about the userβs credit score. | No | Yes. If you have configured to transmit this data to CleverTap, respond accordingly. | |
Other financial info | Any other financial information such as user salary or debts. | No | Yes. If you have configured to transmit this data to CleverTap, respond accordingly. | |
Health and fitness | Health info | Information about the user's health, such as medical records or symptoms. | No | Yes. If you have configured to transmit this data to CleverTap, respond accordingly. |
Fitness info | Information about the user's fitness, such as exercise or other physical activity. | No | Yes. If you have configured to transmit this data to CleverTap, respond accordingly. | |
Messages | Emails | The userβs emails, including the email subject line, sender, recipients, and the content of the email. | No | Yes. If you have configured to transmit this data to CleverTap, respond accordingly. |
SMS or MMS | The userβs text messages including the sender, recipients, and the content of the message. | No | Yes. If you have configured to transmit this data to CleverTap, respond accordingly. | |
Other in-app messages | Any other types of messages. For example, in instant messages or chat content. | No | Yes. If you have configured to transmit this data to CleverTap, respond accordingly. | |
Photos or videos | Photos | The userβs photos. | No | No. |
Videos | The userβs videos. | No | No. | |
Audio files | Voice or sound recordings | The userβs voice such as a voicemail or a sound recording. | No | No. |
Music files | The userβs music files. | No | No. | |
Other audio files | Any other user-created or user-provided audio files. | No | No. | |
Files and docs | Files and docs | The userβs files or documents, or information about their files or documents such as file names. | No | Yes. If you have configured to transmit this data to CleverTap, respond accordingly. |
Calendar | Calendar events | Information from a userβs calendar such as events, event notes, and attendees. | No | Yes. If you have configured to transmit this data to CleverTap, respond accordingly. |
Contacts | Contacts | Information about the userβs contacts such as contact names, message history, and social graph information such as usernames, contact recency, contact frequency, interaction duration, and call history. | No | Yes. If you have configured to transmit this data to CleverTap, respond accordingly. |
App activity | App interactions | Information about how users interact with the app. For example, the number of times they visit a page or the sections that they tap on. | No | Yes. If you have configured to transmit this data to CleverTap, respond accordingly. |
In-app search history | Information search performed by the user in your app. | No | Yes. If you have configured to transmit this data to CleverTap, respond accordingly. | |
Installed apps | Information about the apps installed on the user's device. | No | Yes. If you have configured to transmit this data to CleverTap, respond accordingly. | |
Other user-generated content | Any other user-generated content not listed here, or in any other section. For example, user bios, notes, or open-ended responses. | No | Yes. If you have configured to transmit this data to CleverTap, respond accordingly. | |
Other actions | Any other user activity or actions in-app not listed here such as gameplay, likes, and dialog options. | No | Yes. If you have configured to transmit this data to CleverTap, respond accordingly. | |
Web browsing | Web browsing history | Information about the websites that a user has visited. | No | Yes. If you have configured to transmit this data to CleverTap, respond accordingly. |
App info and performance | Crash logs | Crash log data from user's app. For example, the number of times your app has crashed, stack traces, or other information directly related to a crash. | No | Yes. If you have configured to transmit this data to CleverTap, respond accordingly. |
Diagnostics | Information about the performance of your app. For example battery life, loading time, latency, framerate, or any technical diagnostics. | No | Yes. If you have configured to transmit this data to CleverTap, respond accordingly. | |
Other app performance data | Any other app performance data not listed here. | No | Yes. If you have configured to transmit this data to CleverTap, respond accordingly. | |
Device or other IDs | Device or other IDs | Identifiers that relate to an individual device, browser, or an app. For example, an IMEI number, MAC address, Widevine Device ID, Firebase installation ID, or advertising identifier. | No | Yes. If you have configured to transmit this data to CleverTap, respond accordingly. |
Data Usage and Handling
Data types collected by an application may or may not be shared. Any data transmitted to CleverTap or any other third party by the app will be considered shared data. For example, if a user adds a phone number to the app and records this information, this is collected data. However, if the app shares the phone number with CleverTap or any other third party, then the phone number is considered collected and shared data.
For every selected data type, declare if it is collected, shared, or both.
If your app collects data, declare the following:
- Purpose of collecting the data type - Select the appropriate reasons for collecting this data, such as App functionality, Analytics, Developer Communications, and so on.
- Is the collected data type ephemeral - Is the data processed temporarily, or if it resides in the app permanently?
- User Permission - If the user can allow or disallow data collection.
If your app shares data with a third party, declare the purpose of sharing this data. Select the appropriate reasons for sharing this data.
If your app collects data and also shares data with a third party, declare the purpose of collecting and sharing this data.
After completion
Until July 20, 2022, you can temporarily publish app updates regardless of whether Google finds issues with the information you have disclosed. If there are no issues, your app will be approved, and you need not do anything. If there are issues, revert your Data safety form's status to Draft in Play Console to publish your app update. Google will also send the developer account owner an email and an inbox message in Play Console and show this information on the Policy status (Policy > Policy status) page.
After July 20, 2022, all apps will be required to have completed the Data safety form accurately to disclose their data collection and sharing practices (including apps that do not collect any user data).
If you still need further information, please create a support ticket from the CleverTap dashboard. We would be happy to help you with any other queries.
Privacy Links
For more information about privacy links, refer to CleverTap's Privacy Policy.
FAQs
Q. What information does CleverTap Android SDK collect automatically?
CleverTap tracks the following information:
- Device model
- Cellular provider
- Network carrier
- Country code and timezone
- Wi-Fi and Bluetooth information
- Device width, height, and name
The CleverTap Android SDK is open-source, and all the device information captured is available in our Android Github Repository.
Updated about 1 year ago