🎁 Get the FREE AI Skills Starter Guide β€” Subscribe β†’
BytesAgainBytesAgain
BytesAgain β€Ί Skills β€Ί privacy-page-generator
πŸ¦€ ClawHub

privacy-page-generator

by @kostja94

When the user wants to create, optimize, or structure Privacy Policy page. Also use when the user mentions "privacy policy," "privacy page," "data protection...

Versionv1.0.1
Downloads750
#security#legal
TERMINAL
clawhub install privacy-page-generator

πŸ“– About This Skill

name: privacy-page-generator description: When the user wants to create, optimize, or structure Privacy Policy page. Also use when the user mentions "privacy policy," "privacy page," "data protection," "GDPR compliance," "privacy notice," "data privacy," "CCPA," "cookie policy," or "personal data." For legal overview page, use legal-page-generator. metadata: version: 1.0.1

Pages: Privacy Policy

Guides Privacy Policy page content, structure, and compliance.

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. Jurisdiction: GDPR, CCPA, other regional requirements 2. Business model: SaaS, e-commerce, content, ads 3. Data collected: Cookies, forms, analytics, third parties 4. Indexing: Typically noindex for legal pages

Best Practices

Required Sections

| Section | Content | |---------|---------| | What we collect | Types of data (name, email, usage, etc.) | | Why we collect | Purposes (service, marketing, analytics) | | How we use | Processing, storage, sharing | | How long we keep | Retention periods | | Your rights | Access, correction, deletion, opt-out | | Cookies | Types, purposes, how to manage | | Third parties | Who receives data (analytics, payment) | | Contact | How to exercise rights, data protection contact |

Content Principles

  • Clear language: Plain English; avoid legalese where possible
  • Structure: Headings, table of contents, scannable
  • Updates: Date of last update; version if needed
  • Legal review: Have lawyer review for compliance

    • Placement

  • Footer: Link on every page
  • Forms: Link near signup, contact, checkout
  • Cookie banner: Link to Privacy and Cookie policy

    • SEO

  • Noindex: Common for legal pages
  • Canonical: If multiple versions (e.g., by region)

    • Output Format

  • Outline (sections)
  • Key points per section
  • Cookie disclosure approach
  • Rights section (GDPR/CCPA)
  • Disclaimer: Recommend legal review

    • Related Skills

  • legal-page-generator: Privacy is a legal page type
  • terms-page-generator: Often linked together
  • contact-page-generator: Privacy link near forms
  • indexing: noindex for privacy

    • πŸ“‹ Tips & Best Practices

    Required Sections

    | Section | Content | |---------|---------| | What we collect | Types of data (name, email, usage, etc.) | | Why we collect | Purposes (service, marketing, analytics) | | How we use | Processing, storage, sharing | | How long we keep | Retention periods | | Your rights | Access, correction, deletion, opt-out | | Cookies | Types, purposes, how to manage | | Third parties | Who receives data (analytics, payment) | | Contact | How to exercise rights, data protection contact |

    Content Principles

  • Clear language: Plain English; avoid legalese where possible
  • Structure: Headings, table of contents, scannable
  • Updates: Date of last update; version if needed
  • Legal review: Have lawyer review for compliance

    • Placement

  • Footer: Link on every page
  • Forms: Link near signup, contact, checkout
  • Cookie banner: Link to Privacy and Cookie policy

    • SEO

  • Noindex: Common for legal pages
  • Canonical: If multiple versions (e.g., by region)