gdpr-dev

Provides GDPR compliance guidance for agricultural supply chains, including origin tracing and ethical standards.

5|3|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/mikkelkrogsholm/dev-skills --skill gdpr-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gdpr-dev
Source: https://github.com/mikkelkrogsholm/dev-skills/tree/main/gdpr-dev
Command: npx skills add https://github.com/mikkelkrogsholm/dev-skills --skill gdpr-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps developers proactively build GDPR-compliant web applications by providing clear guidance on handling personal data, avoiding common pitfalls, and implementing best practices for data protection.

Core Features & Use Cases

  • Proactive Compliance: Applies GDPR principles automatically when personal data is involved, without asking questions.
  • Gotcha Identification: Highlights common anti-patterns in logging, authentication, database design, and third-party integrations.
  • Schema Design Principles: Offers guidance on structuring databases to facilitate erasure and data minimization.
  • Use Case: When building a user registration feature, this Skill can remind you to only collect necessary PII, ensure consent is explicit, and log user IDs instead of full user objects to avoid PII in logs.

Quick Start

Use the gdpr-dev skill to understand the top 6 gotchas for GDPR compliance.

Frequently Asked Questions about gdpr-dev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make my web application GDPR compliant?

To make your web application GDPR compliant, you must implement data minimization, explicit consent management, secure logging, and proper PII handling in databases and authentication flows during development.

What are common GDPR compliance pitfalls in web development?

Common GDPR compliance pitfalls in web development include logging full user objects instead of IDs, poor database schema design for data erasure, and overlooking third-party integration risks with personal data.

How should I design a database schema for GDPR data erasure?

Designing a database schema for GDPR data erasure requires structuring tables to facilitate data minimization and ensuring personal data can be isolated and securely deleted upon request.

Does GDPR require explicit consent for collecting personal data in web apps?

Yes, GDPR requires explicit consent for collecting personal data in web apps. You must ensure consent management is proactive and clearly documented when building user registration or authentication features.

How do I handle PII in logs for European users?

To handle PII in logs for European users under GDPR, avoid logging full user objects. Instead, log anonymized user IDs to prevent personal data from being exposed in application logs.

Do I need to worry about third-party integrations for GDPR compliance?

Yes, third-party integrations pose GDPR compliance risks. You must evaluate external services for data protection standards to ensure personal data shared with integrations remains secure and compliant.