[null,null,["上次更新時間：2025-08-25 (世界標準時間)。"],[[["\u003cp\u003eGoogle Mobile Ads SDK allows publishers to enable restricted data processing (RDP) for US privacy law compliance using Google's RDP signal or the IAB-defined \u003ccode\u003eIABUSPrivacy_String\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eWhen RDP is enabled, Google restricts the use of certain data and serves non-personalized ads, overriding UI settings.\u003c/p\u003e\n"],["\u003cp\u003ePublishers can notify Google to enable RDP by inserting \u003ccode\u003erdp\u003c/code\u003e with a value of \u003ccode\u003e1\u003c/code\u003e or \u003ccode\u003eIABUSPrivacy_String\u003c/code\u003e with a compliant value as extra parameters in ad requests.\u003c/p\u003e\n"],["\u003cp\u003eFor mediation, publishers should add CPRA partners in AdMob UI, potentially use \u003ccode\u003eUserDefaults\u003c/code\u003e for IAB signal sharing with compliant partners, and consult each partner's documentation for CPRA compliance options.\u003c/p\u003e\n"]]],["Publishers can use Google Mobile Ads SDK to enable restricted data processing (RDP) for compliance with U.S. privacy laws. This is achieved by setting RDP at the ad request level, using either Google's `rdp` signal with a value of `1` or the IAB-defined `IABUSPrivacy_String` signal. Both methods restrict data usage, resulting in non-personalized ads. Mediation users should add partners to the CPRA ad partners list and use `UserDefaults` to write the IAB signal, so partners can read it.\n"],null,["# U.S. states privacy laws compliance\n\nSelect platform: [Android](/admob/android/privacy/us-states \"View this page for the Android platform docs.\") [iOS](/admob/ios/privacy/us-states \"View this page for the iOS platform docs.\") [Unity](/admob/unity/privacy/us-states \"View this page for the Unity platform docs.\") [Flutter](/admob/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/admob/answer/9561022),\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/admob/answer/14126918)\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 that RDP must be enabled using Google's RDP signal, insert\nthe key `rdp` as an extra parameter with a value of `1`. \n\n final request = AdRequest(extras: {'rdp': '1'});\n\n\n| **Tip:** You can use network tracing or a proxy tool such as [Charles](//www.charlesproxy.com/) 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](/admob/flutter/privacy/us-iab-support)."]]
