gdpr-compliant

Apply GDPR-compliant engineering practices to software design and API development.

3|1|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/Cogni-AI-OU/cogni-ai-agent-skills --skill gdpr-compliant-cogni-ai-ou
Or copy as Structured Prompt for Agentā–¼
Please help me install this Agent Skill.
Skill: gdpr-compliant
Source: https://github.com/Cogni-AI-OU/cogni-ai-agent-skills/tree/main/gdpr-compliant
Command: npx skills add https://github.com/Cogni-AI-OU/cogni-ai-agent-skills --skill gdpr-compliant-cogni-ai-ou

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps engineers prevent GDPR non-compliance by turning privacy requirements into concrete engineering rules for APIs, data models, security, logging, retention, and pull request reviews.

Core Features & Use Cases

  • GDPR engineering checklist: Applies Articles 5 and common GDPR engineering obligations such as minimization, retention limits, integrity/confidentiality, and accountability.
  • Privacy by Design/Default guidance: Defines practical defaults (e.g., opt-in for optional data collection), DPIA/RoPA/DPA expectations, and what to avoid when shipping features.
  • API, logging, encryption, and retention rules: Covers preventing PII in URLs, anonymizing IPs, using safe error handling, enforcing TLS/encryption standards, Argon2id password hashing guidance, and structured retention/erasure practices.
  • Pull Request review framework: Provides a PR checklist spanning data model, API behavior, logging, infrastructure, secrets/CI/CD, retention enforcement, and user-rights governance.

Quick Start

Use gdpr-compliant whenever you are designing an API or data model that handles personal data and then revise the design and PR changes until the rules on minimization, retention, logging, and encryption are satisfied.

Frequently Asked Questions about gdpr-compliant

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

FAQPage Schema
How do I prevent PII from leaking into API URLs and query strings?ā–¼

To prevent PII exposure in API URLs and queries, pass personal data exclusively in request headers or bodies. This keeps sensitive information out of server access logs and browser history.

What is a GDPR engineering checklist for data model design?ā–¼

A GDPR engineering checklist for data models enforces data minimization, sets defined retention TTLs, and documents purpose limitation via RoPA. It ensures accountability and integrity from day one.

How do I review a pull request for GDPR compliance?ā–¼

Review a pull request for GDPR compliance by checking the data model, API behavior, logging, and retention enforcement against privacy by design rules. Verify no PII is logged and TTLs are applied.

What does privacy by design require for API development?ā–¼

Privacy by design for API development requires opt-in defaults for optional data collection, anonymizing IP addresses, safe error handling, and TLS encryption. It mandates purpose limitation documentation via RoPA.

Can I use this to enforce data retention and erasure workflows?ā–¼

Yes, you can enforce data retention and erasure workflows by applying structured retention TTLs and safety-oriented error handling. This ensures personal data is automatically deleted when it expires.

What encryption standards should I use for GDPR-compliant systems?ā–¼

GDPR-compliant systems require TLS for data in transit and secure encryption standards for data at rest. For passwords, use Argon2id hashing to ensure integrity and confidentiality of personal data.