Para ajudar você a obedecer às leis de privacidade dos estados dos EUA, o SDK dos anúncios para dispositivos móveis do Google permite usar o parâmetro de tratamento de dados restrito (RDP) do Google para indicar se o RDP deve ser ativado. O Google também oferece suporte à Plataforma de Privacidade Global (GPP) para os estados aplicáveis dos EUA. Quando o SDK dos anúncios para dispositivos móveis do Google usa um dos
sinais, ele restringe determinados identificadores exclusivos e outros dados são tratados
na prestação de serviços a você.
Você precisa decidir como o tratamento de dados restrito pode ajudar seus planos de compliance e quando ativar esse recurso. Determine se você vai usar o parâmetro RDP diretamente ou sinalizar as opções de consentimento e privacidade com a especificação da GPP.
Este guia ajuda você a ativar o RDP por solicitação de anúncio e usar o
indicador da GPP.
Ativar o indicador RDP
Para notificar o Google e ativar o indicador RDP, grave a chave gad_rdp com um valor 1 no armazenamento SharedPreferences. O SDK dos anúncios para dispositivos móveis do Google lê a chave gad_rdp durante o carregamento do anúncio:
Se você coletar decisões de consentimento com uma plataforma de gestão de consentimento ou suas próprias mensagens personalizadas, o SDK dos anúncios para dispositivos móveis do Google vai respeitar os indicadores da GPP gravados no armazenamento local. O SDK da plataforma de mensagens para usuários (UMP) oferece suporte à gravação do
indicador da GPP. Para coletar consentimento dos estados dos EUA, consulte
Suporte da IAB nos EUA.
[null,null,["Última atualização 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)."]]