| **Caution:** As of October 17, 2025, Privacy Sandbox on Android is deprecated.

The [Privacy Sandbox on
Android](https://developer.android.com/design-for-safety/privacy-sandbox/introduction)
introduces new technologies to improve user privacy and enable effective,
personalized advertising experiences for mobile apps. The Privacy Sandbox
includes [Privacy-Preserving
APIs](https://developer.android.com/design-for-safety/privacy-sandbox/introduction#privacy-preserving-apis),
each of which requires an Ad Services `normal` permission in order to support
core advertising use cases without reliance on cross-app identifiers.

Learn more about [Android's Privacy Sandbox initiative and
AdMob](https://support.google.com/admob/answer/13635519).

## Topics API

The [Topics
API](https://developer.android.com/design-for-safety/privacy-sandbox/topics)
is part of the Privacy Sandbox designed to infer coarse-grained interest signals
on-device based on a user's app usage. These signals or "topics" are
recognizable categories that are inferred based on the apps they used.

Apps and advertising platforms can use topics to decide what ads are relevant.
Topics support interest-based advertising (IBA) use cases without requiring
tracking of individual users across mobile apps.

Google Mobile Ads SDK
22.4.0 accesses the
Topics API and declares the following permission by default:  

    <!-- Topics API permission. -->
    <uses-permission android:name="android.permission.ACCESS_ADSERVICES_TOPICS" />

If you want to opt out of AdMob testing of Android's Topics API,
see how to prevent the merging of permissions in
[Android's instructions](https://developer.android.com/design-for-safety/privacy-sandbox/setup-api-access#declare-adservices).

## Attribution Reporting API (with debug reports)

The [Attribution Reporting
API](https://developer.android.com/design-for-safety/privacy-sandbox/attribution)
is part of the Privacy Sandbox and is designed to provide improved user privacy
by removing reliance on cross-party user identifiers and to support key use
cases for attribution and conversion measurement across mobile apps.

Google Mobile Ads SDK 22.4.0 accesses the Attribution Reporting API with
[debugging reports](https://developer.android.com/design-for-safety/privacy-sandbox/attribution#extended-debugging-reports) and declares the
following permissions by default:  

    <!-- Attribution Reporting API (with debug reports) permissions. -->
    <uses-permission android:name="android.permission.ACCESS_ADSERVICES_ATTRIBUTION" />
    <uses-permission android:name="android.permission.ACCESS_ADSERVICES_AD_ID" />

If you want to opt out of AdMob testing of Android's Attribution
Reporting API, see how to prevent the merging of permissions in
[Android's instructions](https://developer.android.com/design-for-safety/privacy-sandbox/setup-api-access#declare-adservices).