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

Cac card mac