compliance-gdpr

Review GDPR privacy obligations and engineering controls for EU/UK personal data processing.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/pnewsam/skills --skill compliance-gdpr-pnewsam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: compliance-gdpr
Source: https://github.com/pnewsam/skills/tree/main/archive/platform-compliance-evicted/compliance-gdpr
Command: npx skills add https://github.com/pnewsam/skills --skill compliance-gdpr-pnewsam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Engineering teams handling EU/UK personal data often miss GDPR obligations like lawful basis, data subject rights, retention limits, and breach notification because these requirements span data flows rather than individual code lines. This Skill provides structured guidance to audit data flows, build rights workflows, and preserve accountability evidence. ## Core Features & Use Cases - Data-Flow Audits: Scriptable sweeps to map personal-data fields, payload logging, and third-party SDKs, keeping the data map generated rather than stale. - Rights and Consent Workflows: Guidance for deletion/export tests across databases, logs, backups, and vendors, plus consent evidence and withdrawal verification. - Decision Rubric and Escalation: A rubric mapping GDPR concerns (Article 5 principles, lawful basis, DPIA triggers, breach) to engineering requirements, with clear handoff rules to legal/privacy owners. - Use Case: Before launching a feature that collects user analytics from EU customers, use this Skill to verify a lawful basis is identified, retention is bounded, and deletion propagates through all storage layers. ## Quick Start Review this feature's handling of EU user personal data against GDPR requirements and flag any gaps in lawful basis, retention, or deletion workflows.

Frequently Asked Questions about compliance-gdpr

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

FAQPage Schema
How do I check if my feature complies with GDPR?▼

Start with a data map identifying personal data fields, purposes, stores, vendors, and retention. Then verify a lawful basis is named by the product or legal owner, rights workflows exist for access and deletion, and retention is technically enforceable.

How to implement GDPR data deletion across the whole stack?▼

Build deletion tests that exercise forget-me requests through the database, logs, backups, vendors, and derived data, not just the API handler. Deleting the user row alone does not remove all personal data.

When is consent required versus another lawful basis under GDPR?▼

Consent is only one lawful basis and should not be assumed by default. The product or legal owner must identify the appropriate basis before collection or use changes; engineering records the decision for accountability.

Does pseudonymized data avoid GDPR obligations?▼

No, pseudonymized data is still personal data under GDPR and should not be treated as non-personal without review. Only properly anonymized data falls outside GDPR scope.

When should GDPR decisions be escalated to legal teams?▼

Escalate lawful basis selection, controller/processor status, international transfer mechanisms, DPIA decisions, and breach notification obligations to legal or privacy owners. This guidance covers engineering controls, not legal interpretation.