Privacy Page Generator
Draft and structure a Privacy Policy page with GDPR/CCPA-oriented sections before you ship a site or app that collects user data.
Overview
Privacy Page Generator is an agent skill for the Ship phase that structures Privacy Policy page content and sections for GDPR- and CCPA-aware solo launches.
Install
npx skills add https://github.com/kostja94/marketing-skills --skill privacy-page-generatorWhat is this skill?
- Initial assessment for jurisdiction (GDPR, CCPA), business model, data types, and noindex guidance for legal URLs
- Required sections table: collection, purposes, use, retention, rights, cookies, third parties, contact
- Triggers on privacy policy, data protection, GDPR, CCPA, cookie policy, and personal data phrases
- Pairs with legal-page-generator for broader legal hub pages when needed
- Optional friendly intro on first use; direct structured output on repeat invocations
- Skill metadata version 1.0.1
- Eight core required sections in the best-practices table
Adoption & trust: 849 installs on skills.sh; 586 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are about to ship but only have a blank legal route and no checklist of privacy sections regulators and users expect.
Who is it for?
Indie founders launching a data-collecting SaaS, store, or content site who need a sensible first privacy page fast.
Skip if: Enterprise DPIAs, regulated health or finance attestations, or teams that already have counsel-approved static legal PDFs.
When should I use this skill?
User mentions privacy policy, privacy page, data protection, GDPR compliance, privacy notice, data privacy, CCPA, cookie policy, or personal data.
What do I get? / Deliverables
You leave with a sectioned privacy policy draft aligned to your data practices, retention, cookies, third parties, and rights contact paths—ready for counsel review and publish.
- Structured Privacy Policy page content with standard sections
- Indexing/noindex recommendation for legal URL
Recommended Skills
Journey fit
Launch prep under Ship is where legal-facing pages block release; the skill targets pre-ship compliance copy, not early idea validation. Launch subphase covers distribution-ready site artifacts—privacy notice alongside go-live—not ongoing grow/support macros.
How it compares
Focused privacy-policy generator—use legal-page-generator when you need a broader legal landing index, not this skill alone.
Common Questions / FAQ
Who is privacy-page-generator for?
Solo builders and small marketing-led teams shipping web products that collect emails, usage, cookies, or payments and need structured privacy copy.
When should I use privacy-page-generator?
During Ship launch prep when adding or rewriting /privacy before go-live, or when rebranding and your data flows changed.
Is privacy-page-generator safe to install?
It is editorial guidance only; verify accuracy with qualified legal advice for your jurisdiction and review the Security Audits panel on this Prism page.
SKILL.md
READMESKILL.md - Privacy Page Generator
# 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