![]() ![]() You may not use the advertising identifier for creating user profiles forĪdvertising purposes or for targeting users with personalized advertising.Īllowed activities include contextual advertising, frequency capping, conversion 'Opt out of Ads Personalization' setting. ".you must abide by a user's 'Opt out of interest-based advertising' or Method to ensure that you aren't circumventing your users' wishes. Advertising IDs areĬonfigurable in that users can limit the amount of tracking associated with the ![]() Identifier without the explicit consent of the user."Īlways respect the associated Personalized Ads flag. Previous advertising identifier or data derived from a previous advertising ".if reset, a new advertising identifier must not be connected to a Subsequent Advertising IDs together without There are some key points to bear in mind, however, when you use thisĪlways respect the user's intention in resetting the advertising ID.ĭon't bridge user resets by using another identifier or fingerprint to link The Advertising ID is a user-resettable identifier and is appropriate for ads The remaining sections of this guide elaborate on these rules in the context of Is genuine without incurring privacy risk. The SafetyNet APIs are the easiest way to determine whether a device Use APIs that are appropriate for your use case to minimize privacyĬontent protection and the SafetyNet APIs for abuse For the vast majority of non-ads use cases, an FID or GUID Possible for all other use cases, except for payment fraud prevention and Use a Firebase installation ID (FID) or a privately stored GUID whenever Must connect the advertising identifier to personally-identifiable information, Using an Advertising ID, always respect users' selections regarding ad Only use an Advertising ID for user profiling or ads use cases. The READ_PRIVILEGED_PHONE_STATE privileged permission in order to access Which include both IMEI and serial number. (IMEI), without limiting required functionality.Īndroid 10 (API level 29) adds restrictions for non-resettable identifiers, Using hardware identifiers, such as International Mobile Equipment Identity Your app canĪchieve most of its use cases even when it uses identifiers other thanĪvoid using hardware identifiers. Choose user-resettable identifiers whenever possible.In particular, follow these best practices: To protect the privacy of your users, use the most restrictive identifier that satisfies your app's use case. Practices for working with Android permissions, see App permissions bestīest practices for working with Android identifiers ![]() This document provides guidance for selecting appropriate identifiers for yourįor a general look at Android permissions, see Permissions ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |