Privacy page generator
Skill bg-szy/TOP-SKILLS/skills/superskills/privacy-page-generator
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.From its SKILL.md
npx -y skills add bg-szy/TOP-SKILLS --skill privacy-page-generatorAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 5 stars5 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.4 KB, 493 tokens by cl100k_base, as published. Nobody here has run it
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
- 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
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.