Agent skill · Design & Presentation

privacy-policy-malik-taiar

Guide for drafting privacy policies compliant with GDPR. Includes CNIL 2020 recommendations, a reference template, and best practices. Use when drafting or revising a privacy policy for a website or application.

lawve-aigithub.com/lawve-aiGitHub ↗
claude-codeNOASSERTION
Install
npx skills add lawve-ai/awesome-legal-skills --skill privacy-policy-generator-malik-taiar --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 16
SKILL.md size: 17 KB
Bundled scripts: none
Version: 2025.12.24
Declared author: Malik Taiar
Path: skills/privacy-policy-generator-malik-taiar/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 618
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Privacy Policy Guide - GDPR ## Overview The privacy policy is the main document for informing data subjects under Articles 13 and 14 of the GDPR. It must be clear, accessible, and comprehensive. ### Policy Objectives | Objective | GDPR Requirement | |-----------|------------------| | **Transparency** | Clearly inform about data processing (Art. 12) | | **Information** | Provide all mandatory disclosures (Art. 13-14) | | **Rights** | Enable exercise of data subject rights (Art. 15-22) | | **Trust** | Reassure users about data protection | --- ## Reference Resources ### Templates | Template | Description | |----------|-------------| | `assets/sample_template_politique_confidentialite.docx` | Default template to use if no private template is provided | | Internal template provided by lawyer | Use if the lawyer has a more suitable private template | > **IMPORTANT**: The default template `sample_template_politique_confidentialite` is designed for a **brochure website without user accounts**. If the request concerns an **application or platform with users**, additional data categories will need to be added, such as: > - User account management (creation, authentication, profile) > - Lo

What's inside
Steps it walks through
  1. Overview
  2. Policy Objectives
  3. Reference Resources
  4. Templates
  5. CNIL Documentation
  6. Knowledge Base
  7. Information to Collect from Client
  8. 1. Data Controller Information
  9. 2. Nature of the Site/Application
  10. 3. Data Collected
  11. 4. Legal Bases for Processing
  12. 5. Recipients and Processors
  13. 6. Cookies and Trackers
  14. 7. Retention Periods
Ships with 15 files
  • LICENSE.txt
  • README.md
  • SKILL.fr.md
  • assets/CNIL_droits_personnes.pdf
  • assets/CNIL_durees_conservation.pdf
  • assets/CNIL_finalites.pdf
  • assets/CNIL_principes_rgpd.pdf
  • assets/CNIL_transparence.pdf
  • assets/RGPD_texte_officiel.pdf
  • assets/sample_template_politique_confidentialite.docx
  • assets/sample_template_politique_confidentialite.pdf
  • references/BASES_LEGALES.md
  • references/COOKIES.md
  • references/DROITS_PERSONNES.md
  • references/DUREES_CONSERVATION.md
More from awesome-legal-skills
All skills →
About this skill
What does the privacy-policy-malik-taiar skill do?

Guide for drafting privacy policies compliant with GDPR. Includes CNIL 2020 recommendations, a reference template, and best practices. Use when drafting or revising a privacy policy for a website or application.

How do I install it?

Run `npx skills add lawve-ai/awesome-legal-skills --skill privacy-policy-generator-malik-taiar --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From lawve-ai/awesome-legal-skills, a repository with 618 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going