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:
- Jurisdiction: GDPR, CCPA, other regional requirements
- Business model: SaaS, e-commerce, content, ads
- Data collected: Cookies, forms, analytics, third parties
- 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
- pages-legal: Privacy is a legal page type
- pages-terms: Often linked together
- pages-contact: Privacy link near forms
- seo-technical-indexing: noindex for privacy
1---2name: pages-privacy3description: When the user wants to create, optimize, or structure Privacy Policy page. Also use when the user mentions "privacy policy," "privacy page," "data protection," or "GDPR compliance."4---56# Pages: Privacy Policy78Guides Privacy Policy page content, structure, and compliance.910**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.1112## Initial Assessment1314Identify:151. **Jurisdiction**: GDPR, CCPA, other regional requirements162. **Business model**: SaaS, e-commerce, content, ads173. **Data collected**: Cookies, forms, analytics, third parties184. **Indexing**: Typically noindex for legal pages1920## Best Practices2122### Required Sections2324| Section | Content |25|---------|---------|26| **What we collect** | Types of data (name, email, usage, etc.) |27| **Why we collect** | Purposes (service, marketing, analytics) |28| **How we use** | Processing, storage, sharing |29| **How long we keep** | Retention periods |30| **Your rights** | Access, correction, deletion, opt-out |31| **Cookies** | Types, purposes, how to manage |32| **Third parties** | Who receives data (analytics, payment) |33| **Contact** | How to exercise rights, data protection contact |3435### Content Principles3637- **Clear language**: Plain English; avoid legalese where possible38- **Structure**: Headings, table of contents, scannable39- **Updates**: Date of last update; version if needed40- **Legal review**: Have lawyer review for compliance4142### Placement4344- **Footer**: Link on every page45- **Forms**: Link near signup, contact, checkout46- **Cookie banner**: Link to Privacy and Cookie policy4748### SEO4950- **Noindex**: Common for legal pages51- **Canonical**: If multiple versions (e.g., by region)5253## Output Format5455- **Outline** (sections)56- **Key points** per section57- **Cookie** disclosure approach58- **Rights** section (GDPR/CCPA)59- **Disclaimer**: Recommend legal review6061## Related Skills6263- **pages-legal**: Privacy is a legal page type64- **pages-terms**: Often linked together65- **pages-contact**: Privacy link near forms66- **seo-technical-indexing**: noindex for privacy
tools-only