Cross Jurisdiction Cookies logo

Cross Jurisdiction Cookies

Community
mukul975
cross-jurisdiction-cookies

Implementing cookie compliance across multiple jurisdictions including EU ePrivacy Directive, UK PECR, US California CCPA/CPRA opt-out model, and Brazil LGPD. Provides a requirements matrix and geolocation-based implementation approach.

Overview

Publishermukul975
RepositoryPrivacy-Data-Protection-Skills
Skill namecross-jurisdiction-cookies
Stars
279
Forks
59
Bundled files
4
LicenseApache-2.0
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 4 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by mukul975 on GitHub. Read the source before you install it.

Installation

Install the Cross Jurisdiction Cookies AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/mukul975/Privacy-Data-Protection-Skills.git /tmp/Privacy-Data-Protection-Skills
mkdir -p .claude/skills
cp -r /tmp/Privacy-Data-Protection-Skills/plugins/cookie-consent-skills/skills/cross-jurisdiction-cookies .claude/skills/cross-jurisdiction-cookies
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Cross Jurisdiction Cookies in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Cross Jurisdiction Cookies on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Cross Jurisdiction Cookies is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Cross-Jurisdiction Cookie Compliance

Overview

Organizations operating websites accessible to users in multiple jurisdictions face divergent cookie consent requirements. The EU ePrivacy Directive mandates prior opt-in consent for non-essential cookies. The UK's Privacy and Electronic Communications Regulations (PECR) mirrors this approach post-Brexit. California's CCPA/CPRA follows an opt-out model where cookies may be set by default but users must be able to opt out of "sale" or "sharing" of personal information. Brazil's LGPD requires a legal basis for processing but does not have a specific cookie regulation equivalent to ePrivacy. This skill provides a jurisdiction-by-jurisdiction requirements matrix and a unified implementation strategy for Pinnacle E-Commerce Ltd.

Jurisdiction Requirements Matrix

Cookie Consent Models by Jurisdiction

JurisdictionLegal FrameworkConsent ModelDefault StateKey Requirement
EU (27 member states)ePrivacy Directive 2002/58/EC + GDPROpt-inAll non-essential blockedPrior informed consent; no pre-ticked boxes (Planet49)
FranceePrivacy + Loi Informatique et Libertés + CNIL GuidelinesOpt-in (strict)All non-essential blockedEqual prominence accept/reject; 6-month reconsent; 13-month cookie max
GermanyTTDSG (Telekommunikation-Telemedien-Datenschutz-Gesetz) + GDPROpt-inAll non-essential blockedConsent required per Section 25 TTDSG; BGH Planet49 implementation
UKPECR (SI 2003/2426) + UK GDPROpt-inAll non-essential blockedSame as EU ePrivacy; ICO enforcement
California, USCCPA/CPRA (Cal. Civ. Code §1798.100 et seq.)Opt-outCookies may be set by default"Do Not Sell or Share My Personal Information" link; honor GPC signal
Colorado, USCPA (C.R.S. § 6-1-1301 et seq.)Opt-outCookies may be set by defaultUniversal opt-out mechanism recognized
Connecticut, USCTDPA (P.A. 22-15)Opt-outCookies may be set by defaultHonor universal opt-out signals
Virginia, USVCDPA (Va. Code § 59.1-575 et seq.)Opt-outCookies may be set by defaultOpt-out of targeted advertising and sale
BrazilLGPD (Lei 13.709/2018)Legal basis requiredDepends on legal basis claimedConsent or legitimate interest; ANPD guidance evolving
CanadaPIPEDA + proposed CPPA (Bill C-27)Implied consent (evolving)May be set with noticeMeaningful consent; implied consent may suffice for some cookies
South KoreaPIPA (amended 2023) + Act on Promotion of IT NetworkOpt-in for trackingNon-essential blockedConsent for tracking cookies; strict enforcement
JapanAPPI (amended 2022) + Cookie regulation (2023)Opt-in for third-party sharingVariesConsent if cookie data shared with third parties

Detailed Requirements Comparison

RequirementEU ePrivacyUK PECRCalifornia CCPA/CPRABrazil LGPD
Prior consent for analyticsYesYesNo (opt-out model)Depends on legal basis
Prior consent for advertisingYesYesNo (opt-out model)Yes (consent recommended)
Consent for strictly necessaryNo (exempt)No (exempt)Not applicableNot applicable
Cookie wall allowedNoNoNo (service cannot be denied)No
Equal prominence accept/rejectYes (CNIL, some DPAs)Recommended (ICO)N/A (opt-out model)Not specified
Must honor GPC/DNTNo legal requirement (but EDPB encourages)No legal requirementYes — GPC = valid opt-outNot specified
Consent record requiredYes (GDPR Art. 7(1))Yes (UK GDPR Art. 7(1))No (but recommended)Yes (LGPD Art. 8, §2)
Maximum cookie lifetime13 months (CNIL)Not specifiedNot specifiedNot specified
Reconsent frequency6 months (CNIL); varies by DPANot specifiedN/ANot specified
Opt-out link requiredNo (but withdrawal must be easy)NoYes — "Do Not Sell or Share"No
Privacy policy cookie sectionYesYesYesYes
Child-specific requirementsGDPR Art. 8 (age 16, or member state minimum 13)UK GDPR Art. 8 (age 13) + Age Appropriate Design CodeCCPA under-16 opt-in requiredLGPD Art. 14 (best interest of child)

Geolocation-Based Implementation

Architecture for Pinnacle E-Commerce Ltd

User Request
    ├── Determine user jurisdiction
    │   ├── Primary: IP geolocation (MaxMind GeoIP2 or similar)
    │   ├── Secondary: Accept-Language header
    │   ├── Tertiary: User account country setting
    │   └── Fallback: Most restrictive (EU opt-in)
    ├── Select consent configuration
    │   ├── EU/UK → Opt-in banner (full CNIL-style for FR)
    │   ├── US-CA → Opt-out with "Do Not Sell or Share" link
    │   ├── US-CO/CT/VA → Opt-out with universal opt-out support
    │   ├── US-other → Notice-only (monitor state law developments)
    │   ├── Brazil → Consent banner (LGPD legal basis)
    │   └── Other → Apply most restrictive applicable standard
    └── Load appropriate consent experience

Configuration by Jurisdiction

EU/EEA Configuration:

SettingValue
Banner typeOpt-in with equal accept/reject
Default cookie stateAll non-essential denied
Tags blocked before consentGA4, Meta Pixel, Hotjar, Google Ads, all advertising
Consent storageFirst-party cookie + server-side record
Reconsent interval6 months (CNIL standard; apply across EU for simplicity)
Cookie max lifetime13 months
GPC signal handlingTreat as opt-out of advertising/targeting

UK Configuration:

SettingValue
Banner typeOpt-in with clear accept/reject
Default cookie stateAll non-essential denied
Tags blocked before consentSame as EU
Legal framework referencePECR Regulation 6
ICO-specificLink to ICO cookie guidance in policy
Reconsent interval12 months (ICO does not specify; annual is prudent)

California Configuration:

SettingValue
Banner typeNotice banner with opt-out link
Default cookie stateAll cookies set by default
Required link"Do Not Sell or Share My Personal Information" in footer
GPC signalMust be honored as valid opt-out (Cal. Civ. Code §1798.135(e))
Opt-out scopeAdvertising cookies and any "sale" or "sharing" of PI
Financial incentive noticeRequired if offering loyalty program tied to data collection
Under-16 usersOpt-in required (no default setting of tracking cookies)

Brazil Configuration:

SettingValue
Banner typeConsent banner (opt-in recommended)
Default cookie stateNon-essential denied (conservative approach pending ANPD guidance)
Legal basis optionsConsent (Art. 7, I) or Legitimate Interest (Art. 7, IX)
Cookie policyMust be available in Portuguese
ANPD guidanceMonitor for specific cookie regulation (expected)
Data subject rightsAccess, correction, deletion, portability per LGPD

Consent State Storage by Jurisdiction

JurisdictionConsent Cookie NameContentDuration
EUpinnacle_consent_eu{version:"v3",analytics:false,advertising:false,functionality:false,timestamp:"2026-03-14T10:00:00Z"}6 months
UKpinnacle_consent_uk{version:"v3",analytics:false,advertising:false,functionality:false,timestamp:"2026-03-14T10:00:00Z"}12 months
US-CApinnacle_consent_ccpa{version:"v2",optout_sale:false,optout_sharing:false,gpc:false,timestamp:"2026-03-14T10:00:00Z"}12 months
Brazilpinnacle_consent_lgpd{version:"v2",analytics:false,advertising:false,timestamp:"2026-03-14T10:00:00Z"}12 months

Cross-Jurisdiction Cookie Policy

Policy Structure for Pinnacle E-Commerce Ltd

The cookie policy must address all jurisdictions served:

Section 1 — What Cookies We Use Universal section listing all cookies by category (same for all users).

Section 2 — Your Rights by Location

If You Are Located InYour Cookie Rights
European Economic AreaYou have the right to accept or reject non-essential cookies before they are set. We will not set analytics, advertising, or functionality cookies without your prior consent.
United KingdomUnder the Privacy and Electronic Communications Regulations (PECR), you have the right to accept or reject non-essential cookies before they are set.
California, USAYou have the right to opt out of the "sale" or "sharing" of your personal information collected through cookies. Click "Do Not Sell or Share My Personal Information" to exercise this right. We honor the Global Privacy Control (GPC) signal.
BrazilUnder the Lei Geral de Proteção de Dados (LGPD), we process cookie data based on your consent. You may withdraw consent at any time.
Other US StatesDepending on your state, you may have the right to opt out of targeted advertising. We honor universal opt-out mechanisms.

Section 3 — How to Manage Cookies Instructions for using the consent banner, browser settings, and GPC.

Section 4 — Updates to This Policy Version history and notification process for material changes.

Testing Cross-Jurisdiction Compliance

Verification Matrix

TestEUUKCaliforniaBrazil
Banner appears on first visitOpt-in bannerOpt-in bannerNotice with opt-out linkConsent banner
No non-essential cookies before interactionVerifyVerifyN/A (cookies allowed)Verify
Accept All sets all cookiesVerifyVerifyN/AVerify
Reject All blocks non-essentialVerifyVerifyN/AVerify
"Do Not Sell" link presentN/AN/AVerify in footerN/A
GPC signal honoredRecommendedRecommendedRequired — verifyRecommended
Consent persists across pagesVerifyVerifyVerifyVerify
Consent expires on schedule6 months12 months12 months12 months
Cookie policy accessibleVerifyVerifyVerifyVerify (Portuguese)

Key Legal References

  • ePrivacy Directive 2002/58/EC, Article 5(3) — EU cookie consent requirement
  • UK PECR (SI 2003/2426), Regulation 6 — UK cookie consent requirement
  • CCPA/CPRA (Cal. Civ. Code §1798.100 et seq.) — California opt-out model for sale/sharing
  • California AG Regulations, 11 CCR §7025 — GPC as valid opt-out mechanism
  • LGPD (Lei 13.709/2018), Articles 7-8 — Brazilian consent requirements
  • CJEU Case C-673/17 (Planet49) — Active consent; disclosure of duration and third-party access
  • TTDSG Section 25 — German implementation of ePrivacy cookie requirements
  • CNIL Deliberation No. 2020-091 — French cookie guidelines
  • UK ICO Guidance on Cookies and Similar Technologies (2023) — PECR compliance guidance
  • Colorado CPA Rules, 4 CCR 904-3, Rule 5.11 — Universal opt-out mechanism requirements

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Cross Jurisdiction Cookies AI skill do?

Implementing cookie compliance across multiple jurisdictions including EU ePrivacy Directive, UK PECR, US California CCPA/CPRA opt-out model, and Brazil LGPD. Provides a requirements matrix and geolocation-based implementation approach.

Why use Cross Jurisdiction Cookies on TypingMind?

Because you install it once and use it with any model. Cross Jurisdiction Cookies is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Cross Jurisdiction Cookies in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/mukul975/Privacy-Data-Protection-Skills/tree/main/plugins/cookie-consent-skills/skills/cross-jurisdiction-cookies. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Cross Jurisdiction Cookies?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Cross Jurisdiction Cookies?

As many as you like. As long as a model supports skills, you can use Cross Jurisdiction Cookies with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Cross Jurisdiction Cookies AI skill free?

Yes. It is published on GitHub by mukul975 under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇