> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/regulations-manager/frameworks/global-privacy-protocol-gpp/multi-state-privacy-agreement-mspa.md). # Multi-State Privacy Agreement (MSPA) The Multi-State Privacy Agreement (MSPA) is a complementary legal framework to the Multi-State Privacy String (technical signal). It is a joint legal agreement across industry participants that dictates obligations of partners on how the framework should be used in practice so that all participants have confidence that the framework is being used appropriately and in the same way. In this article, we will cover the following related to the Multi-State Privacy Agreement (MSPA): * [U.S. National privacy section](#u.s.-national-privacy-section) * [MSPA ID](#mspa-id) * [MSPA modes](#mspa-modes) * [Technical signalling ](#technical-signalling) *** ### U.S. National privacy section Within the GPP String, each supported law or region has its own section which is essentially a sub-encoding within the overall GPP String that carries the signals relevant to that specific legal regime. The US National privacy section is the section built to represent consent/opt-out signals under U.S. state privacy laws **collectively**, rather than requiring a separate string per state. Rather than encoding, say, California's CCPA/CPRA rules in one string, Virginia's VCDPA in another, Colorado's CPA in a third, etc., the US National privacy section attempts to create one unified string that captures the applicable signals across (most) U.S. State privacy laws However, use of the U.S. National privacy section requires your organization to be signatories of the Multi-State Privacy Agreement (MSPA). This is because without being a MSPA signatory, an organization could technically read the string, ignore the opt-out, and there would be no contractual obligation forcing them to comply since the GPP string alone imposes no legal obligation.
GPP StringInforms your organization what the end-user selected
Multi-State Privacy Agreement (MSPA)Informs what your organization, as a recipient of that signal, are contractually obligated to do about it (e.g., not further disclose the data, not use it for purposes the user opted out of, flow the signal downstream unaltered, limit use of sensitive data categories, etc.)
While Didomi does not block the use of utilizing the U.S. National section for non-signatories, doing so introduces risk for your organization since the section would not have the legal backing of the agreement. ### MSPA ID An MSPA ID is the unique identifier assigned to an organization when it signs the Multi-State Privacy Agreement (MSPA). It is how the system tracks who is actually authorized to participate in the U.S. National GPP section. Organization's can input their MSPA ID when configuring the Global Privacy Protocol (GPP) framework for the regulation.
### MSPA modes When an organization signs the Multi-State Privacy Agreement (MSPA), it elects how it operates in regards to transactions covered by the agreement. See the table below for different modes that your organization can elect:
ModeDescription
Service Provider ModeFor first-parties who do not sell or share end-user personal information, and do not process personal information for targeted advertising
Opt-Out Option Mode

For first-parties who do one of the following:

  • sell or share end-user personal information
  • process information for targeted advertising
Organization's can select their MSPA mode when configuring the Global Privacy Protocol (GPP) framework for the regulation.
### Technical signalling Your organization's signatory status of the Multi-State Privacy Agreement (MSPA) is encoded in each section of the GPP Staring in the following fields:
FieldDescription
MspaCoveredTransactionPublisher or Advertiser, as applicable, is a signatory to the IAB Multi-state Service Provider Agreement (MSPA), as may be amended from time to time, and declares that the transaction is a “Covered Transaction” as defined in the MSPA.

1 Yes
2 No
MspaOptOutOptionModePublisher or Advertiser, as applicable, has enabled “Opt-Out Option Mode” for the “Covered Transaction,” as such terms are defined in the MSPA.

0 Not applicable.
1 Yes
2 No
MspaServiceProviderModePublisher or Advertiser, as applicable, has enabled “Service Provider Mode” for the “Covered Transaction,” as such terms are defined in the MSPA.

0 Not applicable.
1 Yes
2 No
{% code overflow="wrap" %} ``` {... "MspaCoveredTransaction": 1, "MspaOptOutOptionMode": 1, "MspaServiceProviderMode": 2, ...} ``` {% endcode %} --- # 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://docs.didomi.io/regulations-manager/frameworks/global-privacy-protocol-gpp/multi-state-privacy-agreement-mspa.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.