Data safety in Google Play
According to Google requirements, mobile app developers must inform Google Play about what data they collect through their apps. To do this, fill out the Data safety form on the App content page in Play Console.
The following Mobile Ads SDK guidance is designed to help developers in disclosing their app's data collection, sharing, and security practices specifically related to the Mobile Ads SDK's processing.
Alert
When using the Mobile Ads SDK, it's your responsibility to ensure that your app is compliant with the applicable privacy policy. If you collect and/or transmit any data, you have to make sure that the data is collected, secured, and managed properly.
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 user data collection, sharing, and security practices.
Mobile Ads SDK
Data collection
"Collect" means transmitting data from your app off a user’s device. Mobile Ads SDK in your app transmits user data off the device. The purposes for collection are listed in the Purposes section below.
Data sharing
"Sharing" refers to transferring user data collected from your app to a third party. User data collected from your app is transferred directly to a third party via the Mobile Ads SDK included in your app. The purposes for sharing are listed in the Purposes section below.
Data handling
You can also disclose whether each data type collected by your app is "optional" or "required." All data types collected in your app via Mobile Ads SDK and listed in the Data types section below are "optional" (users have control over its collection and can opt out of personalized ads).
Other data disclosures
This section is also an opportunity for you to showcase your app’s privacy and security practices to your users (e.g., encryption in transit, a deletion request mechanism). The Mobile Ads SDK encrypts all user data listed on this page in transit over HTTPS/TLS. The Mobile Ads SDK enables app developers to delete user data in a manner consistent with the functionality of the SDK.
Data types
Information about how each type of user data is collected and shared through the Mobile Ads SDK.
Please note that the following table assumes the Mobile Ads SDK default configurations. App developers are responsible for ensuring that they adapt accordingly in line with their specific configurations and uses.
|
Data type |
Description |
Collection and sharing of Mobile Ads SDK data (default configuration) |
|
Location |
||
|
Precise location |
User or device location in an area of less than 3 square kilometers, such as location provided by Android's |
No The app developer can optionally set up the transmission of this data by enabling the This means that only if developers allow 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 Mobile Ads SDK. The SDK does not collect or attempt to collect such information independently. |
|
Approximate location |
User or device location in an area greater than or equal to 3 square kilometers, such as the user's city or location provided by Android's |
No The app developer can optionally set up the transmission of this data by enabling the This means that only if developers allow 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 Mobile Ads SDK. The SDK does not collect or attempt to collect such information independently. |
|
Personal info |
||
|
Name |
How the user refers to themselves, such as their first or last name, or nickname. |
No |
|
Email address |
The user's email address. |
No |
|
User IDs |
User IDs, such as an account number, account ID, or account name. |
No |
|
Address |
The user's address, such as their mailing or home address. |
No |
|
Phone number |
The user's phone number. |
No |
|
Race and ethnicity |
Information about the user's race or ethnicity. |
No |
|
Political or religious beliefs |
Information about the user's political or religious beliefs. |
No |
|
Sexual orientation |
Information about the user's sexual orientation. |
No |
|
Other info |
Any other personal info, such as the user's date of birth, gender identity, or veteran status. |
No |
|
Financial info |
||
|
User payment info |
Information about the user's financial accounts, such as a credit card number. |
No |
|
Purchase history |
Information about the user's purchases and transactions. |
No |
|
Credit score |
Information about the user's credit. |
No |
|
Other financial info |
Any other financial info, such as the user's salary or debts. |
No |
|
Health and fitness |
||
|
Health info |
Information about the user's health, such as medical records or symptoms. |
No |
|
Fitness info |
Information about the user's physical activity, such as regular exercises. |
No |
|
Messages |
||
|
Emails |
The user’s emails including the subject line, senders, recipients, and message content. |
No |
|
SMS or MMS |
The user's text messages including information on senders, recipients, and message content. |
No |
|
Other in-app messages |
Any other types of messages, such as instant messages or chat content. |
No |
|
Photos and videos |
||
|
Photos |
The user's photos. |
No |
|
Videos |
The user's videos. |
No |
|
Audio files |
||
|
Voice or sound recordings |
The user's voice recordings, such as a voicemail or sound recording. |
No |
|
Music files |
The user's music files. |
No |
|
Other audio files |
Any other user-created or user-provided audio files. |
No |
|
Files and docs |
||
|
Files and docs |
The user's files and documents or information about their files and documents, such as file names. |
No |
|
Calendar |
||
|
Calendar events |
Information from the user's calendar such as events, event notes, and attendees. |
No |
|
Contacts |
||
|
Contacts |
Information about the user's contacts, such as contact names or message history, as well as their usernames, contact recency, contact frequency, interaction duration, and call history. |
No |
|
App activity |
||
|
App interactions |
Information about how the user interacts with the app. For example, the number of times they visit a page or sections they tap on. |
No |
|
In-app search history |
Information about the user's search queries in the app. |
No |
|
Installed apps |
Information about the apps installed on the user's device. |
No |
|
Other user-generated content |
Any other user-generated content not mentioned in any section, such as their bios, notes, or open-ended responses. |
No |
|
Other actions |
Any other user activity or in-app actions not listed here, such as their gameplay, likes, and dialog options. |
No |
|
Web browsing |
||
|
Web browsing history |
Information about the websites visited by the user. |
No |
|
App info and performance |
||
|
Crash logs |
Data from your app's crash log, such as the number of times the app has crashed, stack traces, or other info directly related to a crash. |
No |
|
Diagnostics |
Information about your app's performance, such as battery life, loading time, latency, frame rate, or any technical diagnostics. |
No |
|
Other app performance data |
Any other app performance data not mentioned here. |
No |
|
Device or other IDs |
||
|
Device or other IDs |
For example, advertising ID or any other device-related ID. |
Yes, if the respective permission is granted in the app. Learn more about how to use advertising IDs. |
Purposes
Information about data collection and sharing purposes specifically related to the Mobile Ads SDK's processing.
Please note that purposes of collection and sharing may depend on the particular use or implementation of Mobile Ads SDK by a given developer.
|
Data purpose |
Description |
Mobile Ads SDK data collection and sharing purposes |
|
App functionality |
Used for features that are available in the app. |
No |
|
Analytics |
Used to collect data about how users use the app or how it performs. |
No |
|
Developer communications |
Used to send news or notifications about the app or the developer. |
No |
|
Advertising or marketing |
Used to display or target ads or marketing communications, or measuring ad performance. |
Yes |
|
Fraud prevention, security, and compliance |
Used for fraud prevention, security, or compliance with laws. |
No |
|
Personalization |
Used to customize your app, such as showing recommended content or suggestions. |
No |
|
Account management |
Used for the setup or management of a user’s account with the developer. |
No |