humanityco/cookie-compliance-agent-manual / site/skills/configure-regions
configure-regions
VerifiedSet which privacy regulations apply to a Cookie Compliance banner and how it treats visitors differently by region (GDPR in the EU, CCPA in California, and so on). Use when asked to set up region rules, turn on geolocation-based consent, configure GDPR/CCPA/other regulations, or "make the banner behave differently by country."
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.7 KB |
| index.html | other | 17.6 KB |
index.html
View on GitHub<!doctype html>
<!-- Generated by scripts/build-pages.mjs from skills/configure-regions/SKILL.md. Do not edit by hand. -->
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1, viewport-fit=cover">
<title>Configure region and regulation rules — Cookie Compliance Agent Manual</title>
<meta name="description" content="Set which privacy regulations a Cookie Compliance banner applies, such as GDPR in the EU and CCPA in California, and how it treats visitors by region.">
<link rel="canonical" href="https://manual.hu-manity.co/skills/configure-regions/">
<link rel="alternate" type="text/markdown" href="/skills/configure-regions/SKILL.md" title="Raw markdown (for agents)">
<meta property="og:title" content="Configure region and regulation rules">
<meta property="og:description" content="Set which privacy regulations a Cookie Compliance banner applies, such as GDPR in the EU and CCPA in California, and how it treats visitors by region.">
<meta property="og:type" content="article">
<meta property="og:url" content="https://manual.hu-manity.co/skills/configure-regions/">
<meta property="og:site_name" content="Cookie Compliance Agent Manual">
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@graph": [
{
"@type": [
"TechArticle",
"Article"
],
"headline": "Configure region and regulation rules",
"description": "Set which privacy regulations a Cookie Compliance banner applies, such as GDPR in the EU and CCPA in California, and how it treats visitors by region.",
"url": "https://manual.hu-manity.co/skills/configure-regions/",
"inLanguage": "en",
"publisher": {
"@type": "Organization",
"@id": "https://manual.hu-manity.co/#organization",
"name": "Hu-manity.co",
"url": "https://hu-manity.co/"
}
},
{
"@type": "BreadcrumbList",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://manual.hu-manity.co/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Configure region and regulation rules",
"item": "https://manual.hu-manity.co/skills/configure-regions/"
}
]
}
]
}
</script>
<link rel="stylesheet" href="/assets/site.css">
<script src="/assets/site.js" defer></script>
</head>
<body>
<a class="skip" href="#content">Skip to content</a>
<header class="site-header">
<div class="bar">
<a class="brand" href="/">Cookie Compliance <span>Agent Manual</span></a>
<nav aria-label="Main">
<ul>
<li><a href="/start/">Start</a></li>
<li><a href="/connect/">Connect</a></li>
<li><a href="/#skills" aria-current="true">Skills</a></li>
<li><a href="/#cookbooks">Cookbooks</a></li>
<li><a href="/gallery/">Gallery</a></li>
<li><a href="/llms.txt">For agents <span class="nav-note">(llms.txt)</span></a></li>
<li><a href="https://github.com/humanityco/cookie-compliance-agent-manual">GitHub</a></li>
</ul>
</nav>
</div>
</header>
<div class="layout">
<details class="sidebar" open>
<summary>All pages and this page's sections</summary>
<nav aria-label="Manual pages">
<h2>Get started</h2>
<ul>
<li><a href="/start/">Start here</a></li>
<li><a href="/connect/">Connect your AI assistant</a></li>
<li><a href="/prompts/">Prompts</a></li>
<li><a href="/platforms/">Platforms</a></li>
</ul>
<h2>Skills</h2>
<ul>
<li><a href="/skills/install-banner/">install-banner</a></li>
<li><a href="/skills/verify-install/">verify-install</a></li>
<li><a href="/skills/match-site-design/">match-site-design</a></li>
<li><a href="/skills/configure-regions/" aria-current="page">configure-regions</a>
<ul class="toc" aria-label="On this page">
<li><a href="#gdpr-starter">GDPR starter</a></li>
<li><a href="#1-two-separate-decisions--dont-conflate-them">1. Two separate decisions — don't conflate them</a></li>
<li><a href="#2-declaring-applicable-regulations--safe-to-merge">2. Declaring applicable regulations — safe to merge</a></li>
<li><a href="#3-per-region-behavior--geolocationrules-and-its-one-real-hazard">3. Per-region behavior — geolocationRules, and its one real hazard</a></li>
<li><a href="#4-geolocationmethod-automatic-silently-discards-your-custom-rules">4. geolocationMethod: "automatic" silently discards your custom rules</a></li>
<li><a href="#5-the-legacy-fallback-and-why-it-matters-even-if-you-never-touch-it">5. The legacy fallback, and why it matters even if you never touch it</a></li>
<li><a href="#verified">Verified</a></li>
</ul></li>
</ul>
<h2>Cookbooks</h2>
<ul>
<li><a href="/cookbooks/plain-html/">plain-html</a></li>
<li><a href="/cookbooks/wordpress/">wordpress</a></li>
<li><a href="/cookbooks/nextjs/">nextjs</a></li>
<li><a href="/cookbooks/nuxt/">nuxt</a></li>
<li><a href="/cookbooks/astro/">astro</a></li>
<li><a href="/cookbooks/angular/">angular</a></li>
<li><a href="/cookbooks/vite/">vite</a></li>
<li><a href="/cookbooks/sveltekit/">sveltekit</a></li>
<li><a href="/cookbooks/gtm/">gtm</a></li>
<li><a href="/cookbooks/shopify/">shopify</a></li>
<li><a href="/cookbooks/hugo/">hugo</a></li>
<li><a href="/cookbooks/gatsby/">gatsby</a></li>
<li><a href="/cookbooks/docusaurus/">docusaurus</a></li>
<li><a href="/cookbooks/laravel/">laravel</a></li>
<li><a href="/cookbooks/django/">django</a></li>
<li><a href="/cookbooks/rails/">rails</a></li>
<li><a href="/cookbooks/drupal/">drupal</a></li>
<li><a href="/cookbooks/joomla/">joomla</a></li>
<li><a href="/cookbooks/ghost/">ghost</a></li>
<li><a href="/cookbooks/prestashop/">prestashop</a></li>
<li><a href="/cookbooks/magento/">magento</a></li>
<li><a href="/cookbooks/wix/">wix</a></li>
<li><a href="/cookbooks/squarespace/">squarespace</a></li>
<li><a href="/cookbooks/webflow/">webflow</a></li>
<li><a href="/cookbooks/framer/">framer</a></li>
<li><a href="/cookbooks/trackers/">trackers</a></li>
</ul>
<h2>Design gallery</h2>
<ul>
<li><a href="/gallery/">v1 banner designs</a></li>
<li><a href="/gallery/v2/">v2 banner designs</a></li>
</ul>
</nav>
</details>
<main id="content" class="doc">
<h1 id="configure-region-and-regulation-rules">Configure region and regulation rules</h1>
<p class="page-meta">Skill <span aria-hidden="true">·</span> <a href="/skills/configure-regions/SKILL.md">View raw markdown (for agents)</a></p>
<p>MCP tool names below are written <code>account.previewComplianceChange</code>; some clients list them as <code>account_previewComplianceChange</code>.</p>
<h2 id="gdpr-starter">GDPR starter <a class="anchor" href="#gdpr-starter" aria-label="Link to this section">#</a></h2>
<p>A new app declares GDPR and leaves region detection, Consent Mode and Global Privacy Control off. Ask the site owner once whether to turn the starter on. Apply it only after they accept. An earlier request to "make the site compliant" is not that answer.</p>
<p>Read <code>subscriptionType</code> from <code>account.createApp</code> or from <code>account.getDesign</code> (<code>meta.subscriptionType</code>).</p>
<p>On <strong>Pro</strong>, preview then commit exactly:</p>
<div class="code"><pre tabindex="0"><code class="language-json">{"geolocation": true, "googleConsentMode": true, "facebookConsentMode": true, "microsoftConsentMode": true, "gpcSupportMode": true}
</code></pre></div>
<p>Leave <code>geolocationMethod</code> unset. It is already <code>automatic</code>, so the platform's region matrix applies. Do not send <code>geolocationRules</code>.</p>
<p>On <strong>Free</strong> (<code>Basic</code>, or any value other than <code>Pro</code>), the live banner keeps region detection off and keeps Meta and Microsoft Consent Mode off. Apply only:</p>
<div class="code"><pre tabindex="0"><code class="language-json">{"googleConsentMode": true, "gpcSupportMode": true}
</code></pre></div>
<p>Say, in the same question, that region detection and the Meta and Microsoft signals stay off on the Free plan. Do not change <code>regulations</code> or any consent-mode map. GDPR stays the only declared law. This does not make the site legally compliant.</p>
<p>The preview is the write. If it reports a deletion or a warning the owner did not accept, stop and show it.</p>
<h2 id="1-two-separate-decisions--dont-conflate-them">1. Two separate decisions — don't conflate them <a class="anchor" href="#1-two-separate-decisions--dont-conflate-them" aria-label="Link to this section">#</a></h2>
<div class="table-wrap" role="region" aria-label="Table" tabindex="0">
<table>
<thead>
<tr>
<th>Decision</th>
<th>Setting</th>
<th>What it does</th>
</tr>
</thead>
<tbody><tr>
<td>Which laws apply to this site at all</td>
<td><code>config.regulations.<key></code> — <code>gdpr</code>, <code>ccpa</code>, <code>otherus</code>, <code>ukpecr</code>, <code>lgpd</code>, <code>pipeda</code>, <code>popia</code> (all boolean)</td>
<td>A site-wide declaration. Not visitor-specific by itself.</td>
</tr>
<tr>
<td>Whether visitors get different treatment depending on where they are</td>
<td><code>config.geolocation</code> (boolean) + <code>config.geolocationMethod</code> (<code>automatic</code>|<code>manual</code>) + <code>config.geolocationRules[]</code></td>
<td>Turns on visitor-location-based branching and defines what each region gets.</td>
</tr>
</tbody></table>
</div>
<p>Read the app's current values first with <code>account.getDesign</code> before changing either — both live under <code>config.*</code>, and step 3 below depends on it.</p>
<h2 id="2-declaring-applicable-regulations--safe-to-merge">2. Declaring applicable regulations — safe to merge <a class="anchor" href="#2-declaring-applicable-regulations--safe-to-merge" aria-label="Link to this section">#</a></h2>
<p><code>account.previewComplianceChange</code> then <code>account.updateComplianceConfig</code> with, for example, <code>{"regulations": {"gdpr": true, "ccpa": true}}</code>. This <strong>merges</strong> against whatever the app already has stored: setting <code>lgpd</code> in a later call does not erase <code>gdpr</code>/<code>ccpa</code>. See Verified below.</p>
<h2 id="3-per-region-behavior--geolocationrules-and-its-one-real-hazard">3. Per-region behavior — <code>geolocationRules</code>, and its one real hazard <a class="anchor" href="#3-per-region-behavior--geolocationrules-and-its-one-real-hazard" aria-label="Link to this section">#</a></h2>
<p>To actually treat an EU visitor differently from a California visitor, turn on <code>geolocation: true</code>, set <code>geolocationMethod: "manual"</code> (see step 4 for why), and send the <strong>full</strong> <code>geolocationRules</code> array — one entry per regulation name, each with its own <code>display</code> / <code>revoke</code> / <code>blocking</code> / <code>privacy</code> / <code>doNotSell</code> booleans:</p>
<div class="code"><pre tabindex="0"><code class="language-json">{
"geolocation": true,
"geolocationMethod": "manual",
"geolocationRules": [
{"name": "gdpr", "display": true, "revoke": true, "blocking": true, "privacy": true, "doNotSell": false},
{"name": "ccpa", "display": true, "revoke": true, "blocking": false, "privacy": false, "doNotSell": true}
]
}
</code></pre></div>
<p><code>privacy</code> and <code>doNotSell</code> show or hide the privacy-policy link and the Do Not Sell link for that region's visitors, and a rule's flag wins over the app's <strong>Privacy Policy Link</strong> or <strong>Do Not Sell Link</strong> switch in the dashboard. Where no rule applies (for example geolocation is off, or the visitor matches no rule; see below), the switch alone decides. Make sure each link has a URL and link text. Send both flags on every entry: the two banner engines treat a missing flag differently.</p>
<p><strong>On the New banner, region rules shape the banner whether or not the script blocking engine is on.</strong> When the engine is off, the matching rule's <code>display</code>, <code>revoke</code>, <code>privacy</code> and <code>doNotSell</code> flags still decide what the banner shows. The engine is off on a WordPress site with the plugin's <strong>Script blocking engine</strong> setting off and on every page a logged-in WordPress administrator views. So an administrator sees the same banner as visitors. What the engine controls is blocking: with it off nothing is held and a rule's own <code>blocking</code> flag is ignored, and <code>display: false</code> hides the banner. The WordPress plugin's <strong>Autoblocking</strong> setting, and a rule's own <code>blocking: false</code>, do not switch region rules off. A Free plan site past its visit limit is also engine-off, but the live banner keeps region detection off on the Free plan on both engines (see the GDPR starter above) and new visitors have no country, so a rule applies there only to a visitor whose country is already known.</p>
<p><strong>This array replaces wholesale — it is never merged.</strong> Sending only the <code>gdpr</code> entry silently deletes every other region's rules. <code>account.previewComplianceChange</code> warns about this at preview time, but nothing warns you at commit time, so read the preview. Always fetch the app's current <code>geolocationRules</code> with <code>account.getDesign</code> first, edit only the one entry you mean to change, and send the <strong>whole list</strong> back.</p>
<p>Valid <code>name</code>s are the same seven keys as <code>regulations.*</code> above, plus <code>other</code>: the rule for visitors who match no other enabled rule. US visitors are the exception: outside California they match <code>otherus</code> only when it is enabled, and otherwise get no rule at all, so <code>other</code> does not cover them. <code>other</code> is kept whatever <code>regulations</code> says, so keep it in the list.</p>
<h2 id="4-geolocationmethod-automatic-silently-discards-your-custom-rules">4. <code>geolocationMethod: "automatic"</code> silently discards your custom rules <a class="anchor" href="#4-geolocationmethod-automatic-silently-discards-your-custom-rules" aria-label="Link to this section">#</a></h2>
<p><code>automatic</code> is the default. In automatic mode, the Cookie Compliance server overwrites whatever <code>geolocationRules</code> you last stored with its own built-in default matrix on every live read — your custom per-region rules never reach a visitor. <strong>Set <code>geolocationMethod: "manual"</code> in the same change</strong> if you want the array in step 3 to actually take effect.</p>
<h2 id="5-the-legacy-fallback-and-why-it-matters-even-if-you-never-touch-it">5. The legacy fallback, and why it matters even if you never touch it <a class="anchor" href="#5-the-legacy-fallback-and-why-it-matters-even-if-you-never-touch-it" aria-label="Link to this section">#</a></h2>
<p><strong>On the Classic banner only</strong>, if <code>geolocationRules</code> or <code>regulations</code> is empty, the widget falls back to three flat buckets instead — <code>geolocationEUblocking</code> / <code>geolocationUSblocking</code> / <code>geolocationORblocking</code> (plus matching <code>*display</code> / <code>*dontsell</code> / <code>*privacy</code> / <code>*revoke</code> keys) — and in that fallback, <strong>CCPA and "other US" visitors get the exact same treatment</strong>. The New banner ignores these flat keys, so with <code>geolocationMethod: "manual"</code> a config that carries only them gives it no region rules: send <code>geolocationRules</code> there. (In automatic mode the server supplies the default matrix, as in step 4.) If a site owner wants California treated differently from the rest of the US, <code>geolocationRules</code> (step 3) is the only way; the legacy booleans can't express it.</p>
<h2 id="verified">Verified <a class="anchor" href="#verified" aria-label="Link to this section">#</a></h2>
<p>Verified on a real test site on 2026-09-29, with every result confirmed against the stored configuration, not just the tool's response:</p>
<ul>
<li><code>regulations.gdpr</code>/<code>ccpa</code> written, then <code>regulations.lgpd</code> written alone: the stored draft ends up with all three set. Writes to <code>regulations.*</code> merge.</li>
<li><code>geolocationRules</code> written with 2 entries, then with a 1-entry list: the dropped entry is gone from the stored draft. Writes to <code>geolocationRules</code> replace the whole list.</li>
</ul>
<p>Steps 4 and 5, and the link-flag and New-banner notes in step 3, describe the documented behaviour of the server and the banner and were not part of that test. Re-check them if either changes.</p>
</main>
</div>
<footer class="site-footer">
<p>Cookie Compliance is a product of <a href="https://hu-manity.co">Hu-manity.co</a>.
Product: <a href="https://cookie-compliance.co/">Cookie Compliance</a> · <a href="https://cookie-compliance.co/mcp/">MCP server</a>.
Source and contributions: <a href="https://github.com/humanityco/cookie-compliance-agent-manual">github.com/humanityco/cookie-compliance-agent-manual</a>.</p>
</footer>
</body>
</html>
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| slack-gif-creatoranthropics/skillsKnowledge and utilities for creating animated GIFs optimized for Slack. Provides constraints, validation tools, and animation concepts. Use when users request animated GIFs for Slack like "make me a GIF of X doing Y for Slack." | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| ponytailDietrichGebert/ponytailLazy senior dev mode for any coding task: the smallest change that fully solves it, and a reply a busy human understands in one read. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-debtDietrichGebert/ponytailList every `shortcut:` comment (and older `ponytail:` ones) as a debt ledger. One-shot report, changes nothing. Use for "ponytail debt", "what did ponytail defer", "list the shortcuts", /ponytail-debt. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |