gdpr-data-handling
π―SkillA practical guide for building software that handles personal data of people in the EU under GDPR, the EU privacy law. It covers asking for permission, answering people's requests about their data, and building privacy in from the start.
Installation
npx skills add wshobson/agents --skill gdpr-data-handlingRun it in a terminal; it asks which AI coding tools to install it for (Claude Code, Codex, Cursor and more).
Uses skills.sh Β· Node.js 22.20+
After installing
Ask for related work and the agent uses it on its own, or call it yourself.
/gdpr-data-handlingInstall by hand
Copy the whole skill folder from GitHub to the place below. Copying only SKILL.md can leave out files the skill uses.
Open the skill folder β- This project
.claude/skills/gdpr-data-handling/ - All projects
~/.claude/skills/gdpr-data-handling/
These paths are for Claude Code. For other tools, the command above puts it in the right place.
What this skill does
Overview
This skill is a practical guide for following GDPR, the European Union's law on personal data. It helps when your app stores or uses information about people in the EU, such as names, emails or health details. It explains which data needs extra care and what rules apply.
Key Features
- Sort personal data into groups, such as basic, sensitive and children's data, and see how much protection each needs.
- Pick a valid legal reason for using data, such as user consent or a contract.
- Handle requests from people who want to see, fix, move or delete their data within the one-month deadline.
- Follow a clear list of do's and don'ts, like collecting only what you need and never pre-checking consent boxes.
- Find longer worked examples in the
references/details.mdfile.
Who is this for?
It suits developers building apps or websites used by people in the EU. It also helps teams checking whether an existing system follows the law. You do not need to be a legal expert to use it.
Summarized by AI from this skill's SKILL.md. Suggest a better one
SKILL.md
View on GitHub βImplement GDPR-compliant data handling with consent management, data subject rights, and privacy by design. Use when building systems that process EU personal data, implementing privacy controls, or conducting GDPR compliance reviews.
GDPR Data Handling
Practical implementation guide for GDPR-compliant data processing, consent management, and privacy controls.
When to Use This Skill
- Building systems that process EU personal data
- Implementing consent management
- Handling data subject requests (DSRs)
- Conducting GDPR compliance reviews
- Designing privacy-first architectures
- Creating data processing agreements
Core Concepts
1. Personal Data Categories
| Category | Examples | Protection Level |
|---|---|---|
| Basic | Name, email, phone | Standard |
| Sensitive (Art. 9) | Health, religion, ethnicity | Explicit consent |
| Criminal (Art. 10) | Convictions, offenses | Official authority |
| Children's | Under 16 data | Parental consent |
2. Legal Bases for Processing
Article 6 - Lawful Bases:
βββ Consent: Freely given, specific, informed
βββ Contract: Necessary for contract performance
βββ Legal Obligation: Required by law
βββ Vital Interests: Protecting someone's life
βββ Public Interest: Official functions
βββ Legitimate Interest: Balanced against rights
3. Data Subject Rights
Right to Access (Art. 15) ββ
Right to Rectification (Art. 16) β
Right to Erasure (Art. 17) β Must respond
Right to Restrict (Art. 18) β within 1 month
Right to Portability (Art. 20) β
Right to Object (Art. 21) ββ
Detailed worked examples and patterns
Detailed sections (starting with ## Implementation Patterns) live in references/details.md. Read that file when the navigation summary above is insufficient.
Best Practices
Do's
- Minimize data collection - Only collect what's needed
- Document everything - Processing activities, legal bases
- Encrypt PII - At rest and in transit
- Implement access controls - Need-to-know basis
- Regular audits - Verify compliance continuously
Don'ts
- Don't pre-check consent boxes - Must be opt-in
- Don't bundle consent - Separate purposes separately
- Don't retain indefinitely - Define and enforce retention
- Don't ignore DSARs - 30-day response required
- Don't transfer without safeguards - SCCs or adequacy decisions
More from this repository10
Helps you build a consistent look for your app with Tailwind CSS v4. It sets up shared colors, sizes, dark mode and reusable components so every screen matches.
A guide to TypeScript's advanced type features, which describe the shape of your data so mistakes are caught before the code runs. It covers reusable types, types that change based on rules, and built-in helper types, with short examples.
Guidance for building reliable server-side apps with Node.js, using Express or Fastify. It covers login, error handling, databases, API design and a list of proven best practices.
Intelligent automation and multi-agent orchestration for Claude Code
Claude Code plugin for AI-powered framework migration workflows, coordinating specialized agents to plan and execute transitions between technology stacks as part of the wshobson/agents marketplace.
A Claude Code plugin for payment system integration covering Stripe, PayPal, and billing platforms with checkout flows, subscription management, and webhook handling in the wshobson/agents ecosystem.
A Claude Code plugin bundling core development tools and agents for everyday tasks like debugging and code generation, part of the wshobson/agents marketplace with 73 focused plugins.
Claude Code plugin for observability and monitoring including logging, metrics, distributed tracing, and alerting, part of the wshobson/agents marketplace with 73 focused plugins.
A Claude Code plugin providing specialized AI agents for deployment strategy planning and execution, covering blue-green deployments, canary releases, rolling updates, and zero-downtime patterns.
Claude Code plugin for JVM language development including Java, Kotlin, and Scala with specialized agents for idiomatic patterns, build tools, and runtime optimization in the wshobson/agents marketplace.