Skip to content

humanityco/cookie-compliance-agent-manual / site/skills/configure-regions

configure-regions

Verified

Set 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."

Configure region and regulation rules

MCP tool names below are written account.previewComplianceChange; some clients list them as account_previewComplianceChange.

GDPR starter

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.

Read subscriptionType from account.createApp or from account.getDesign (meta.subscriptionType).

On Pro, preview then commit exactly:

{"geolocation": true, "googleConsentMode": true, "facebookConsentMode": true, "microsoftConsentMode": true, "gpcSupportMode": true}

Leave geolocationMethod unset. It is already automatic, so the platform's region matrix applies. Do not send geolocationRules.

On Free (Basic, or any value other than Pro), the live banner keeps region detection off and keeps Meta and Microsoft Consent Mode off. Apply only:

{"googleConsentMode": true, "gpcSupportMode": true}

Say, in the same question, that region detection and the Meta and Microsoft signals stay off on the Free plan. Do not change regulations or any consent-mode map. GDPR stays the only declared law. This does not make the site legally compliant.

The preview is the write. If it reports a deletion or a warning the owner did not accept, stop and show it.

1. Two separate decisions — don't conflate them

DecisionSettingWhat it does
Which laws apply to this site at allconfig.regulations.<key> — gdpr, ccpa, otherus, ukpecr, lgpd, pipeda, popia (all boolean)A site-wide declaration. Not visitor-specific by itself.
Whether visitors get different treatment depending on where they areconfig.geolocation (boolean) + config.geolocationMethod (automatic|manual) + config.geolocationRules[]Turns on visitor-location-based branching and defines what each region gets.

Read the app's current values first with account.getDesign before changing either — both live under config.*, and step 3 below depends on it.

2. Declaring applicable regulations — safe to merge

account.previewComplianceChange then account.updateComplianceConfig with, for example, {"regulations": {"gdpr": true, "ccpa": true}}. This merges against whatever the app already has stored: setting lgpd in a later call does not erase gdpr/ccpa. See Verified below.

3. Per-region behavior — geolocationRules, and its one real hazard

To actually treat an EU visitor differently from a California visitor, turn on geolocation: true, set geolocationMethod: "manual" (see step 4 for why), and send the full geolocationRules array — one entry per regulation name, each with its own display / revoke / blocking / privacy / doNotSell booleans:

{
  "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}
  ]
}

privacy and doNotSell 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 Privacy Policy Link or Do Not Sell Link 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.

On the New banner, region rules shape the banner whether or not the script blocking engine is on. When the engine is off, the matching rule's display, revoke, privacy and doNotSell flags still decide what the banner shows. The engine is off on a WordPress site with the plugin's Script blocking engine 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 blocking flag is ignored, and display: false hides the banner. The WordPress plugin's Autoblocking setting, and a rule's own blocking: false, 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.

This array replaces wholesale — it is never merged. Sending only the gdpr entry silently deletes every other region's rules. account.previewComplianceChange warns about this at preview time, but nothing warns you at commit time, so read the preview. Always fetch the app's current geolocationRules with account.getDesign first, edit only the one entry you mean to change, and send the whole list back.

Valid names are the same seven keys as regulations.* above, plus other: the rule for visitors who match no other enabled rule. US visitors are the exception: outside California they match otherus only when it is enabled, and otherwise get no rule at all, so other does not cover them. other is kept whatever regulations says, so keep it in the list.

4. geolocationMethod: "automatic" silently discards your custom rules

automatic is the default. In automatic mode, the Cookie Compliance server overwrites whatever geolocationRules you last stored with its own built-in default matrix on every live read — your custom per-region rules never reach a visitor. Set geolocationMethod: "manual" in the same change if you want the array in step 3 to actually take effect.

5. The legacy fallback, and why it matters even if you never touch it

On the Classic banner only, if geolocationRules or regulations is empty, the widget falls back to three flat buckets instead — geolocationEUblocking / geolocationUSblocking / geolocationORblocking (plus matching *display / *dontsell / *privacy / *revoke keys) — and in that fallback, CCPA and "other US" visitors get the exact same treatment. The New banner ignores these flat keys, so with geolocationMethod: "manual" a config that carries only them gives it no region rules: send geolocationRules 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, geolocationRules (step 3) is the only way; the legacy booleans can't express it.

Verified

Verified on a real test site on 2026-09-29, with every result confirmed against the stored configuration, not just the tool's response:

  • regulations.gdpr/ccpa written, then regulations.lgpd written alone: the stored draft ends up with all three set. Writes to regulations.* merge.
  • geolocationRules written with 2 entries, then with a 1-entry list: the dropped entry is gone from the stored draft. Writes to geolocationRules replace the whole list.

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.

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: 198kUpdated Claude CodeCodexVerifiedInstall
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: 194kUpdated Claude CodeCodexVerifiedInstall
ponytail-debtDietrichGebert/ponytailHarvest every shortcut: comment into one debt ledger, so deferrals get tracked instead of forgotten. One-shot report.Stars: 194kUpdated Claude CodeCodexVerifiedInstall
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: 194kUpdated Claude CodeCodexVerifiedInstall