gdpr-privacy-notice-eu-oliver-schmidt-prietz
Draft GDPR/DSGVO-compliant privacy notices as .docx for any EU/EEA jurisdiction and audience. Use when user asks to create a privacy policy/notice, mentions "Datenschutzerklärung", "politique de confidentialité", "privacy notice", needs Art. 13/14 disclosures, AI Act transparency, cookie policy, or notices for applicants ("Bewerber-Datenschutz"), employees ("Beschäftigten-Datenschutz"), B2B partners, or B2C customers. Covers DE (DSGVO+BDSG+TDDDG), FR (RGPD+LIL+LCEN), AT, IT, ES, NL, BE, IE, UK GDPR. Five notice types: Website/App, Applicant, Employee, Business Partner, B2C Customer.
npx skills add lawve-ai/awesome-legal-skills --skill privacy-notice-generator-oliver-schmidt-prietz --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Generates jurisdiction-aware, GDPR-compliant privacy notices as professional .docx documents. It guides the user through selecting notice type, jurisdiction, and template, then collects controller, data, purposes, recipients, and transfers information, and finally drafts a structured .docx privacy notice with sections tailored to the chosen type and jurisdiction.
How it works
- Scope, Notice Type & Template Selection: Determine the notice type from a predefined list (Website/App, Applicant/Recruiting, Employee, Business Partner, B2C Customer, Combined); determine target jurisdictions; choose a base template or generate from references/templates.md if no user template is provided. For multilingual needs, decide primary language and translations per scenario. Reference checks and multi-language verification steps are outlined.
- Information Intake: Collect controller identity, data inventory, purposes & legal bases, recipients/transfers, cookies, AI usage, and DPIA indicators. Use guided groups (A–G) to ensure all relevant categories are captured. Includes explicit handling rules for special category data and AI-related processing. Produce a structured summary for user confirmation before drafting.
- Draft the Notice: Use the selected notice type’s section map from references/NOTICE_TYPES.md to include only approved sections. Follow a standard structure with sections such as Who We Are, What Data We Collect, Why We Process, Who Receives Data, International Transfers, Retention, Rights, Cookies, AI/Automated Decisions, Data Security, Children’s Data, Changes, and Contact. Follow drafting rules for language, tone, legal bases, retention, and AI transparency when applicable.
- Verify & Deliver: (Not shown in the excerpt) Likely steps include compliance checks (Art. 13/14, AI Act, multi-language verification) and final .docx output via a docx skill.
When to use it
Use when a user asks to create a GDPR/DSGVO privacy notice for any EU/EEA jurisdiction or audience and when the service involves multiple audiences such as Website/App visitors, job applicants, employees, business partners, or B2C customers. Applicable to DE, FR, AT, IT, ES, NL, BE, IE, UK GDPR and supports pan-EU / multi-jurisdiction needs.
What it can touch
Noted tools include: claude-code. The workflow references data collection, intake, and drafting steps that imply touching documents (.docx) and reference materials. Specific touch points include: loading reference files (references/NOTICE_TYPES.md, references/templates.md), collecting controller data, data categories, and crafting a .docx output via a docx skill.
Caveats
License: AGPL-3.0. No explicit risk or refusal terms are stated here. The skill requires careful alignment with jurisdiction-specific templates and legal bases; it highlights that sections to include/skip depend on the chosen notice type. It also notes that if a DPIA is required, it should be separate and prepared prior to processing; the privacy notice can be drafted, but the DPIA is a separate exercise.
# Pan-EU GDPR Privacy Notice Generator Generate jurisdiction-aware, GDPR-compliant privacy notices as professional .docx documents. ## Workflow Overview ``` 1. SCOPE → Notice type, jurisdiction(s), template choice 2. INTAKE → Type-driven collection: controller info, data inventory, legal bases 3. DRAFT → Generate notice from template + type profile + collected info 4. VERIFY → Art. 13/14 compliance check + type-specific checks + AI Act check 5. DELIVER → .docx output via docx skill ``` ## Step 1: Scope, Notice Type & Template Selection ### Determine Notice Type (FIRST QUESTION) Before anything else, determine what type of privacy notice is needed. Load `references/NOTICE_TYPES.md` and ask: > "What type of privacy notice do you need?" | Type | Description | |---|---| | **Website / App** | For visitors, users, subscribers of a website, web app, or mobile app | | **Applicant / Recruiting** | For job applicants and candidates (Bewerber, candidats) | | **Employee** | For employees, contractors, interns (Beschäftigte, salariés) | | **Business Partner (B2B)** | For contact persons at vendors, suppliers, clients, partners | | **B2C Customer** | For end consumers in a customer/purchase rela
- Workflow Overview
- Step 1: Scope, Notice Type & Template Selection
- Determine Notice Type (FIRST QUESTION)
- Determine Jurisdiction
- Template Selection
- Multi-Language Decision Tree
- Platform Sub-Type (Website/App type only)
- Step 2: Information Intake
- Group A — Controller Identity
- Group B — Data Inventory
- Group C — Purposes & Legal Bases
- Group D — Recipients & Transfers
- Group E — Cookies & Tracking
- Group F — AI & Automated Processing
What does the gdpr-privacy-notice-eu-oliver-schmidt-prietz skill do?
Draft GDPR/DSGVO-compliant privacy notices as .docx for any EU/EEA jurisdiction and audience. Use when user asks to create a privacy policy/notice, mentions "Datenschutzerklärung", "politique de confidentialité", "privacy notice", needs Art. 13/14 disclosures, AI Act transparency, cookie policy, or notices for applicants ("Bewerber-Datenschutz"), employees ("Beschäftigten-Datenschutz"), B2B partners, or B2C customers. Covers DE (DSGVO+BDSG+TDDDG), FR (RGPD+LIL+LCEN), AT, IT, ES, NL, BE, IE, UK GDPR. Five notice types: Website/App, Applicant, Employee, Business Partner, B2C Customer.
How do I install it?
Run `npx skills add lawve-ai/awesome-legal-skills --skill privacy-notice-generator-oliver-schmidt-prietz --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.