cookie-policy-page-generator
cookie-policy-page-generator creates and optimizes cookie policy page content to meet transparency and legal compliance requirements, particularly under GDPR and CCPA regulations. Use this skill when a user requests a cookie policy, mentions cookie consent or cookie banners, or needs guidance on disclosing cookies like Google Analytics tracking, session tokens, or advertising pixels. The skill inventories actual site cookies, assesses consent requirements by jurisdiction, and generates policy language appropriate to the product category.
git clone --depth 1 https://github.com/kostja94/marketing-skills /tmp/cookie-policy-page-generator && cp -r /tmp/cookie-policy-page-generator/skills/pages/legal/cookie-policy ~/.claude/skills/cookie-policy-page-generatorSKILL.md
# Pages: Cookie Policy Guides cookie policy page content for transparency and regulatory compliance. Often presented as a standalone page or as part of the Privacy Policy. **When invoking**: On **first use**, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On **subsequent use** or when the user asks to skip, go directly to the main output. ## Initial Assessment Identify: 1. **Cookie inventory**: List every cookie the site actually sets — check `_ga`, `_ga_*`, session cookies, CSRF tokens, preference cookies, ad cookies 2. **Consent requirement**: Does the site need a notice or a consent banner? See §Notice vs Consent 3. **Jurisdiction**: GDPR/ePrivacy (EU), CCPA (California), other regions 4. **Product category**: Free anonymous, freemium, SaaS, e-commerce — affects which cookies exist --- ## Cookie Inventory: Common Patterns ### Google Analytics 4 (GA4) | Cookie | Type | Purpose | Duration | How to Opt Out | |--------|------|---------|----------|----------------| | `_ga` | Analytics | Distinguishes users; used for aggregate usage measurement | 2 years | [GA opt-out browser add-on](https://tools.google.com/dlpage/gaoptout), block third-party cookies, or enable Do Not Track | | `_ga_<container-id>` | Analytics | Persists session state; used with `_ga` for session-level metrics | 2 years | Same as `_ga` | **Disclosure requirement**: If the site uses Google Analytics, the cookie policy MUST list these cookies. GA ToS §7 requires posted privacy/cookie notice. ### Functional / Session Cookies | Cookie | Type | Purpose | Duration | How to Opt Out | |--------|------|---------|----------|----------------| | Session ID | Essential | Maintains user session across page loads | Session (deleted on browser close) | Required for service; cannot be disabled | | CSRF Token | Essential | Prevents cross-site request forgery attacks | Session | Required for security; cannot be disabled | | Fair-use quota | Functional | Counts daily usage for rate limiting | 24 hours | Clear browser data; resets on next visit | | Language preference | Functional | Remembers user's language choice | 30 days – 1 year | Clear browser data | | Dark mode / theme | Functional | Remembers display preference | 30 days – 1 year | Clear browser data | ### Advertising / Tracking Cookies (If Applicable) | Cookie | Type | Purpose | Duration | How to Opt Out | |--------|------|---------|----------|----------------| | `_fbp` | Marketing | Meta/Facebook pixel — tracks ad conversions | 90 days | [Meta ad preferences](https://www.facebook.com/ads/preferences) or block third-party cookies | | `_gcl_au` | Marketing | Google Ads conversion linker | 90 days | Block third-party cookies | | `_rdt_uuid` | Marketing | Reddit Ads conversion tracking | 90 days | Block third-party cookies | --- ## Notice vs Consent — Critical Distinction This is the most common compliance confusion. Determining which mechanism is needed depends on cookie type: ### Cookie Notice (Informational) **When to use**: Site uses only **strictly necessary** and **analytics** cookies (no advertising, no tracking, no third-party marketing cookies). **What it is**: A banner or page section stating "We use cookies for [analytics/functionality]. By continuing, you accept this." No accept/reject toggle needed. **Sufficient for**: GA4 analytics only, session cookies, CSRF tokens, functional preference cookies. ### Cookie Consent Banner (Interactive) **When to use**: Site uses **any** of: advertising cookies, third-party tracking cookies, social media pixels, or cookies that share data with ad networks. **What it is**: An interactive banner with accept/reject/customize options. Must allow granular consent by cookie category. Must be as easy to reject as to accept. Must not use dark patterns (pre-checked boxes, confusing language, "accept all" only). **Required for**: Meta pixel, Google Ads conversion tracking, retargeting cookies, any cross-site tracking. ### Do Not Track (DNT) State whether the site responds to browser DNT signals. Most sites do not, which is acceptable as long as disclosed. Example: "[Product] does not currently respond to Do Not Track signals because no uniform standard exists." --- ## Essential Elements ### 1. What Are Cookies Brief, plain-language explanation: "Cookies are small text files stored on your device by websites you visit. They help sites remember your preferences and understand how you use them." ### 2. Cookie Types Used Categorize by function: - **Essential / Strictly Necessary**: Required for the site to work (session, CSRF) - **Functional**: Remember preferences (language, theme, fair-use quota) - **Analytics / Performance**: Measure usage in aggregate (GA4) - **Marketing / Advertising**: Track ad effectiveness, retargeting (if applicable) ### 3. Full Cookie Table Table format for every cookie: | Cookie Name | Type | Purpose | Duration | How to Opt Out | |-------------|------|---------|----------|----------------| | [name] | [essential/functional/analytics/marketing] | [1-sentence purpose] | [duration] | [specific actionable instruction] | The **"How to Opt Out" column** is critical — don't just list cookies, tell users how to control them. This builds trust and satisfies regulatory expectations. ### 4. Third-Party Cookies - Which third parties set cookies through the site (GA4, Meta, Stripe, etc.) - Link to each third party's own privacy/cookie policy - Whether those third parties use cookies for their own purposes ### 5. How to Manage Cookies - Browser settings: link to instructions for Chrome, Firefox, Safari, Edge - GA4-specific: link to [GA opt-out browser add-on](https://tools.google.com/dlpage/gaoptout) - Mobile: how to manage cookies in iOS/Android settings - Effect of disabling: note that disabling essential cookies may break functionality ### 6. Updates - When the cookie policy was last updated - How users will be notified of changes --- ##
When the user wants to create, optimize, or audit About page content. Also use when the user mentions "about page," "about us," "company story," "our team," "about section," "company overview," "brand story," "team page," or "who we are." For sitewide page planning, use website-structure.
When the user wants to plan, implement, or optimize affiliate marketing strategy. Also use when the user mentions "affiliate marketing," "affiliate program strategy," "CPS model," "affiliate recruitment," "commission structure," "affiliate partners," "affiliate network," "affiliate tracking," "affiliate commission," or "partner marketing." For affiliate page, use affiliate-page-generator.
When the user wants to create, optimize, or audit affiliate program page content. Also use when the user mentions "affiliate program," "affiliate page," "partner program," "referral program page," "affiliate landing," "partner landing," "commission page," or "affiliate signup." For affiliate program strategy, use affiliate-marketing.
When the user wants to track AI search traffic in GA4 or GSC. Also use when the user mentions "AI traffic," "ChatGPT referral," "Perplexity traffic," "AI Overviews," "GA4 AI sources," "AI search analytics," "track AI referrals," "AI search traffic," "Claude traffic," or "how to track AI traffic." For AI SEO strategy, use generative-engine-optimization.
When the user wants to create, optimize, or audit alternatives or comparison content (page or blog article). Also use when the user mentions "alternatives page," "alternatives listicle," "X alternatives," "competitor comparison," "vs page," "compare page," "best alternatives to X," "switch from X," "competitor brand traffic," "brand keyword ads," or "intercept competitor search." For competitor research, use competitor-research.
When the user wants to set up, audit, or optimize analytics tracking (GA4, events, conversions). Also use when the user mentions "Google Analytics," "GA4," "event tracking," "conversions," "attribution model," "gtag," "data layer," "GA4 setup," "conversion tracking," "event setup," "User ID tracking," or "CTA attribution." For traffic insights, use traffic-analysis.
When the user wants to create, optimize, or audit the API introduction/overview page. Also use when the user mentions "API page," "API landing page," "/api page," "API overview," "developer landing," "API marketing," or "API for developers." Note: API documentation (endpoint reference) lives in docs; use docs-page-generator.
When the user wants to write, generate, or create article body content—blog post body, long-form content, how-to guide, listicle. Also use when the user mentions "write article," "article content," "blog post content," "article body," "long-form content creation," "generate article," "article draft," "how-to guide content," "listicle content," "information gain," or "content density." For single post page structure, schema, and SEO metadata, use article-page-generator. For blog index/listing page, use blog-page-generator. For short ad, landing, or email copy, use copywriting.