Per aiutarti a rispettare le
leggi statali sulla privacy negli Stati Uniti,
l'SDK Google Mobile Ads ti consente di utilizzare il parametro
trattamento dati limitato (RDP) di Google per
indicare se abilitare il trattamento dati limitato. Google supporta anche la
Global Privacy Platform
(GPP) per gli stati USA applicabili. Quando l'SDK Google Mobile Ads utilizza uno dei due
indicatori, l'SDK limita alcuni identificatori univoci e altri dati vengono trattati
nella fornitura di servizi.
Devi decidere in che modo il trattamento dati limitato può supportare i tuoi piani di conformità
e quando attivarlo. Determina se utilizzare direttamente il parametro RDP o segnalare il consenso e le scelte relative alla privacy con la specifica GPP.
Questa guida ti aiuta ad attivare RDP in base alle richieste di annuncio e a utilizzare l'indicatore GPP.
Attiva l'indicatore RDP
Per comunicare a Google di attivare l'indicatore RDP, scrivi la chiave gad_rdp con un valore
di 1 nell'archivio
SharedPreferences. L'SDK Google Mobile Ads legge la chiave gad_rdp durante il caricamento dell'annuncio:
Se raccogli le decisioni relative al consenso con una piattaforma di gestione del consenso o con messaggi personalizzati, l'SDK Google Mobile Ads rispetta gli indicatori GPP scritti nell'archivio locale. L'SDK User Messaging Platform (UMP) supporta la scrittura del
segnale GPP. Per raccogliere il consenso degli stati degli Stati Uniti, consulta
Assistenza IAB USA.
[null,null,["Ultimo aggiornamento 2025-08-31 UTC."],[[["\u003cp\u003eThis guide explains how to enable restricted data processing (RDP) in the Google Mobile Ads SDK for compliance with U.S. state privacy laws.\u003c/p\u003e\n"],["\u003cp\u003ePublishers can signal RDP using either Google's RDP signal or the IAB-defined \u003ccode\u003eIABUSPrivacy_String\u003c/code\u003e, both leading to non-personalized ads.\u003c/p\u003e\n"],["\u003cp\u003eEach signal can be passed via ad request extras or shared preferences; publishers should refer to code examples and documentation for implementation.\u003c/p\u003e\n"],["\u003cp\u003eFor mediation, publishers need to manage ad partners in Ad Manager, consider using the IAB signal for partner SDK compliance, and consult partner documentation for CPRA options.\u003c/p\u003e\n"]]],[],null,["# U.S. states privacy laws compliance\n\nSelect platform: [Android](/ad-manager/mobile-ads-sdk/android/privacy/us-states \"View this page for the Android platform docs.\") [iOS](/ad-manager/mobile-ads-sdk/ios/privacy/us-states \"View this page for the iOS platform docs.\") [Unity](/ad-manager/mobile-ads-sdk/unity/privacy/us-states \"View this page for the Unity platform docs.\") [Flutter](/ad-manager/mobile-ads-sdk/flutter/privacy/us-states \"View this page for the Flutter platform docs.\")\n\n\u003cbr /\u003e\n\n| **Important:** Verify that you have **Account Management** permission to complete the configuration for EU Consent and GDPR, US State regulations, and User Messaging Platform. See [Manage user access to your\n| account](//support.google.com/admob/answer/2784628) for details.\n\nTo help you comply with\n\n[U.S. states privacy laws](//support.google.com/admanager/answer/9561023),\n\nthe\n\nGoogle Mobile Ads SDK\n\nlets you use Google\n[restricted data processing](//business.safety.google/rdp/) (RDP) parameter to\nindicate whether to enable RDP. Google also supports the\n\n[Global Privacy Platform](//support.google.com/admanager/answer/14117049)\n\n(GPP) for applicable US states. When the\n\nGoogle Mobile Ads SDK\n\nuses either\nsignal, the SDK restricts certain unique identifiers and other data is processed\nin the provision of services to you.\n\nYou must decide how restricted data processing can support your compliance plans\nand when to enable. Determine whether to use the RDP parameter\ndirectly or signaling consent and privacy choices with the\n[GPP Specification](//github.com/InteractiveAdvertisingBureau/Global-Privacy-Platform).\n\nThis guide helps you enable RDP on a per-ad request basis and use the GPP\nsignal.\n\nEnable the RDP signal\n---------------------\n\nTo notify Google to enable the RDP signal, write the key `gad_rdp` with a value\nof `1` to\n[`SharedPreferences`](//developer.android.com/reference/android/content/SharedPreferences)\nstorage.\n\nGoogle Mobile Ads SDK\n\nreads the `gad_rdp` key during ad loading: \n\n### Java\n\n SharedPreferences sharedPref = PreferenceManager.getDefaultSharedPreferences(context);\n sharedPref.edit().putInt(\"gad_rdp\", 1).apply();\n\n### Kotlin\n\n val sharedPref = PreferenceManager.getDefaultSharedPreferences(context)\n sharedPref.edit().putInt(\"gad_rdp\", 1).apply()\n\n\u003cbr /\u003e\n\n| **Tip:** You can use [network tracing](/ad-manager/mobile-ads-sdk/android/network-tracing) or a proxy tool such as [Charles](/ad-manager/mobile-ads-sdk/android/charles) to capture your app's HTTPS traffic and inspect the ad requests for a `&rdp=` parameter.\n\nUse the IAB GPP Signal\n----------------------\n\nIf you collect consent decisions with a consent management platform or your own\ncustom messaging, the\n\nGoogle Mobile Ads SDK\n\nrespects GPP signals written to\nlocal storage. The User Messaging Platform (UMP) SDK supports writing the GPP\nsignal. To gather US state consent, see\n[US IAB Support](/ad-manager/mobile-ads-sdk/android/privacy/us-iab-support)."]]
