To help you comply with
U.S. states privacy laws,
the Google Mobile Ads SDK lets you use Google
restricted data processing (RDP) parameter to
indicate whether to enable RDP. Google also supports the
Global Privacy Platform
(GPP) for applicable US states. When the Google Mobile Ads SDK uses either
signal, the SDK restricts certain unique identifiers and other data is processed
in the provision of services to you.
You must decide how restricted data processing can support your compliance plans
and when to enable. Determine whether to use the RDP parameter
directly or signaling consent and privacy choices with the
GPP Specification.
This guide helps you enable RDP on a per-ad request basis and use the GPP
signal.
Enable the RDP signal
To notify Google to enable the RDP signal, write the key gad_rdp with a value
of true to UserDefaults storage:
If you collect consent decisions with a consent management platform or your own
custom messaging, the Google Mobile Ads SDK respects GPP signals written to
local storage. The User Messaging Platform (UMP) SDK supports writing the GPP
signal. To gather US state consent, see
US IAB Support.
[null,null,["Last updated 2025-06-20 UTC."],[[["The Google Mobile Ads SDK enables publishers to comply with U.S. state privacy laws using Google's RDP signal or the IAB-defined `IABUSPrivacy_String` to restrict data processing for non-personalized ads."],["Publishers can set Restricted Data Processing (RDP) at the ad request level using either Google's RDP signal (`gad_rdp` key in `UserDefaults`) or the IAB's `IABUSPrivacy_String`."],["When using mediation, publishers should add their mediation partners to the CPRA ad partners list in Ad Manager, potentially utilize the IAB signal for compliant partners, and consult each partner's documentation for CPRA compliance options."]]],[]]