Restrict data processing
When a publisher enables restricted data processing, on the publisher’s instruction Google will further limit how it uses data and begin serving non-personalized ads only. Non-personalized ads are not based on a user’s past behavior. They are targeted using contextual information, including coarse (such as city-level, but not ZIP/postal code) geo-targeting based on current location, and content on the current site or app or current query terms. Google disallows all interest-based audience targeting , including demographic targeting and user list targeting when in restricted data processing mode.
Partners who have implemented the Global Privacy Control or other universal opt-out mechanisms may choose to enable restricted data processing when they receive a GPC opt-out signal.
Some U.S. states' provisions require that Global Privacy Control (GPC) signals opt the user out of Ad Targeting, Sale, or Share of data. For users in applicable states, Google will receive GPC signals directly and trigger RDP mode for those ad requests.
Restricted data processing for third-party demand
When restricted data processing mode is enabled, a restricted data processing signal is passed via the SDK and the following happens for bidding and mediation for mobile apps:
- Restricted data processing ad requests are sent to third-party RTB bidders. Refer to this article for more detail.
- Mediation is not disabled. *
