legal-policy
Legal & Policy Pages
Create clear, compliant legal pages (Privacy Policy, Terms of Service, Cookie Policy) that protect the business legally while remaining accessible and transparent to users.
Core Objectives
- Ensure legal compliance (GDPR, CCPA, CAN-SPAM, etc.)
- Protect business interests with clear terms
- Maintain transparency and user trust
- Balance legal protection with readability
- Reduce legal risk through proper disclosures
Mandatory Elements
1. Privacy Policy
- Data Collection: What data is collected and how
- Data Usage: How collected data is used
- Data Sharing: Third-party sharing and partnerships
- User Rights: Access, deletion, opt-out rights (GDPR/CCPA)
- Cookies: Cookie usage and management options
- Contact: How to exercise rights or ask questions
2. Terms of Service
- Acceptance: What constitutes acceptance of terms
- Service Description: What the service/product provides
- User Obligations: What users must and must not do
- Limitation of Liability: Legal protections for the business
- Dispute Resolution: How disputes are handled
- Changes: How terms can be modified
3. Cookie Policy (if applicable)
- Cookie Types: Essential, analytics, marketing cookies
- Purpose: Why each cookie type is used
- Management: How users can control cookies
- Third-Party Cookies: External services using cookies
Structure & Frameworks
The "Clear & Compliant" Framework
- Plain Language: Use simple terms where legally possible
- Organized Sections: Clear headings and table of contents
- Legal Accuracy: Ensure compliance with applicable laws
- User-Friendly: Make it easy to find specific information
Legal Page Structure
- Last Updated Date: Prominent date of last revision
- Table of Contents: Quick navigation to sections
- Main Content: Organized sections with clear headings
- Contact Information: How to reach for legal questions
- Acceptance Mechanism: Checkbox or "I Agree" button (for ToS)
Voice & Tone Guidelines
- Professional & Clear: Legal accuracy without unnecessary jargon
- Transparent: Honest about data practices and limitations
- Accessible: Use plain language where legally possible
- Formatting: Use clear headings, bullet points, and sections
Concrete Examples
Privacy Policy Data Collection Section
"We collect the following types of information:
• **Personal Information:** Name, email address, phone number
(collected when you sign up or contact us)
• **Usage Data:** Pages visited, time spent, clicks (collected
via cookies and analytics tools)
• **Payment Information:** Processed securely through [Payment
Processor] (we do not store full card details)"
Terms of Service User Obligations
"By using our service, you agree to:
• Provide accurate information when creating an account
• Not share your account credentials with others
• Not use the service for illegal or unauthorized purposes
• Respect intellectual property rights of others"
Quality Checklist
For every legal page, ask:
- Is it compliant with applicable laws (GDPR, CCPA, etc.)?
- Are data practices clearly and honestly explained?
- Is the language as clear as legally possible?
- Is there a clear "last updated" date?
- Would a user understand their rights and obligations?
More from mikefilsaime-groove/clickcampaigns-for-claude-code-in-cursor
crm-setup
This skill should be used when the user asks to "set up CRM", "configure CRM", "CRM implementation", "CRM objects and fields", or mentions HubSpot, Salesforce, Pipedrive, or CRM platforms. Creates technical implementation plans for CRM configuration and data architecture.
19frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
16saas-dev-marketing
This skill should be used when the user asks to "create SaaS marketing", "developer documentation", "product onboarding", "feature announcements", "API docs", or mentions SaaS marketing, developer content, or product-led growth. Creates strategic SaaS and developer marketing that drives adoption.
13design-branding
This skill should be used when the user asks to "create brand identity", "build brand kit", "logo design", "brand guidelines", "visual identity", or mentions branding, design systems, or creative assets. Creates professional brand identity and design systems that establish authority.
13book-writing
This skill should be used when the user asks to "write a book", "create book content", "book chapters", "book manuscript", "MVB", "authority book", or mentions writing a book from scratch. Creates complete book manuscripts from concept to final chapters.
13pdf
Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.
12