> For the complete documentation index, see [llms.txt](https://cmp.docs.sirdata.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cmp.docs.sirdata.net/en/advanced-features/cmp-display-management-for-ccpa-compliance.md). # CMP Display Management for CCPA Compliance ### Conditional Display Based on Geolocation Sirdata’s CMP automatically detects the user’s location and adjusts the display of the consent banner according to the applicable privacy laws. For the **California Consumer Privacy Act (CCPA)**, the specific CCPA banner is **only shown to users located in U.S. states where such disclosure is legally required**, such as California. > ✅ This behavior ensures a better user experience by limiting the CCPA banner display to only those users who are actually subject to the law. *** ### Option: Force Display Across All U.S. States Upon request, it is possible to **enable an option that displays the CCPA banner to all users in the United States**, regardless of which state they are in. > 🔧 This option is useful for companies that want to enforce a uniform policy or simplify their compliance strategy. *** ### “Do Not Sell My Personal Information” Button In compliance with the CCPA, a **“Do Not Sell My Personal Information”** link is displayed **at the bottom of the website (footer)** once the banner has been closed. This link allows users to reopen the banner and review or update their consent preferences. *** ### Option: Remove the Footer Button It is also possible to **disable the “Do Not Sell” button in the footer**. If this option is selected, it is recommended to provide an **alternative method** for users to reopen the CMP (e.g., via a link in the privacy policy, legal notice, or footer). > ⚠️ Important: To remain compliant with the CCPA, users must always be able to revisit and adjust their privacy choices at any time. *** ### Global Privacy Control (GPC) Signal The **Global Privacy Control** (GPC) is a signal that the visitor's browser sends to every website: it states that the visitor objects to the sale and sharing of their personal information. Some browsers send it on their own, others through an extension. Several U.S. states require businesses to honor this signal. Sirdata's CMP detects it and applies the opt-out for you. #### Turning GPC Support On or Off In the portal: **Advanced settings** > **Regulations**, CCPA section, option **Honor the Global Privacy Control (GPC) signal**. * The option is **enabled by default**. * It is only available when the CCPA is enabled for your site. > ⚠️ Attention: honoring the Global Privacy Control is legally required in twelve U.S. states since January 2026. By deactivating this option, you take responsibility for handling the signal yourself. #### Which Visitors Are Concerned The signal is honored for visitors located in a U.S. state where the CMP applies the CCPA, or in **any U.S. state** when the **Apply to all USA states** option is enabled. Elsewhere, the CMP does not apply it. #### On the CCPA Banner When the CMP honors the signal: * the opt-out of sale and sharing is recorded automatically, without asking the visitor anything; * on the **first page view** with the signal, the choices window opens once to confirm it: "Because your browser sent a Global Privacy Control signal, your opt-out has been applied automatically. You don't need to do anything." It does not reopen on its own on later pages; * as long as the signal is sent, the choices window shows this message instead of the opt-out switch: to withdraw their opt-out, visitors must turn off GPC in their browser; * the opt-out is passed on in the `usprivacy` string (3rd character `Y`) and in section 7 of the GPP (US National), which also reports that the signal is present. #### On the GDPR Banner, When the GDPR Applies to All Your Visitors If you apply the GDPR to all your visitors (**Advanced settings** > **Regulations** > **Apply the GDPR**: **To all users**), your U.S. visitors see the GDPR banner. The signal is honored there too, for the same visitors: * the banner is not displayed, and the CMP records a full refusal (all purposes and all partners, legitimate interest included); * a short notice is shown instead: "Because your browser sent a Global Privacy Control signal, your opt-out has been applied automatically. You don't need to do anything." It offers two links: * **Set your choices** opens the banner, where the visitor can accept if they wish; * **Close** dismisses the notice without changing anything; * consent given **before** the signal was sent no longer counts: the refusal replaces it; * a choice made **after** the notice, with the signal on, is kept on later pages. > ✅ This way, you keep GDPR prior consent for all your visitors while honoring the signal as U.S. laws require. #### Partner Modules Follow the Signal When the signal is honored, the enabled modules pass on the opt-out as soon as the page loads: | Module | CCPA banner | GDPR banner | | ------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------ | | [Google Consent Mode](/en/consent-transmission-standards/google-consent-mode.md) | advertising and measurement signals denied (`ad_storage`, `ad_user_data`, `ad_personalization`, `analytics_storage`) | advertising and measurement signals denied | | [Facebook Consent Mode](/en/consent-transmission-standards/facebook-consent-mode.md) | [Limited Data Use](/en/consent-transmission-standards/facebook-consent-mode/meta-limited-data-use-us.md): events are sent, Meta limits their use | pixel paused | | [OpenAI Consent Mode](/en/consent-transmission-standards/openai-consent-mode.md) | denied | denied | > 🔗 Learn more about the signal: [globalprivacycontrol.org](https://globalprivacycontrol.org/). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://cmp.docs.sirdata.net/en/advanced-features/cmp-display-management-for-ccpa-compliance.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.