> 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/introduction.md). # Introduction A regulation is a configuration of data collection practices by your organization which includes aspects such as vendors and purposes used, applicable regions, industry and legislative frameworks, etc... ### Overview The regulation is used in conjunction with a widget when publishing a privacy flow to your website or application.
While the widget determines much of what the end-user sees and experiences on your property, the regulation controls the compliance logic and how their choices are recorded and passed to vendors. ### Data Collection Scope When your organization creates a new regulation in Didomi you will need to define the data collection scope for the regulation. The data collection scope refers to the entity that determines the entity that is determining the processing rules for the collection of end-user data. See the table below for more information on each option.
Data Collection ScopeDescription
By vendor

For each vendor, your organization sets/confirms the processing rule for every purpose within the regulation using a vendor x purpose matrix.

This option gives your organization vendor-by-vendor control over what and how end-user data is processed and is tailored for
the General Data Protection Regulation (GDPR), the IAB Trasparency and Consent Framework (TCF), and other EU-style markets.

Note: By default, the regulation will have the IAB TCF and Google Consent Mode v2 frameworks enabled.

By country or region

The processing rule for a given purpose is defined based on the end-user's location and all vendors will follow the same rule in the country/region/state. This enables your organization to set different processing rules for the same purpose across multiple jurisdictions using a territory x purpose matrix.

This option is tailored for U.S. state privacy laws (e.g. CPRA) or anywhere the law itself sets the rule for everyone.

Note: By default, the regulation will have the Google Consent Mode v2 enabled.

--- # 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/introduction.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.