privacy-by-design

Apply privacy-by-design principles to software architectures handling personal data.

1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/caobingsheng/skills --skill privacy-by-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: privacy-by-design
Source: https://github.com/caobingsheng/skills/tree/main/design/privacy-by-design
Command: npx skills add https://github.com/caobingsheng/skills --skill privacy-by-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Builds software that inherently protects user data by integrating privacy controls early, reducing risk and compliance overhead.

Core Features & Use Cases

  • Data minimization and purpose limitation during design
  • Consent management and user rights support (access, erasure, portability)
  • Encryption at rest/in transit, retention policies, and audit readiness
  • Applicable to databases, APIs, UI flows, and third-party integrations

Quick Start

Design and implement a data flow for a new feature with privacy-by-design from day one.

Frequently Asked Questions about privacy-by-design

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

FAQPage Schema
How do I apply privacy by design principles to database schemas handling personal data?

Apply privacy by design to database schemas by enforcing data minimization and explicit data-use purposes. This ensures personal data handling inherently protects users through access controls and purpose limitation from day one.

What is data minimization and how does it relate to GDPR Article 25 compliance?

Data minimization is the principle of collecting only necessary personal data. It directly satisfies GDPR Article 25 requirements by ensuring software architectures embed privacy controls early, reducing compliance overhead.

How do I design a consent management system for user data access and erasure?

Design a consent management system by integrating user rights support directly into APIs and UI flows. This enables explicit consent tracking and provides capabilities for user data access, erasure, and portability.

Can I use this approach for third-party integrations in mobile apps under CCPA and LGPD?

Yes, this approach applies to third-party integrations in mobile apps under CCPA and LGPD. It aligns software architectures with these regulations by enforcing encryption, retention policies, and explicit data-use purposes across integrations.

What's the best way to implement encryption and retention policies for audit readiness?

The best way to implement encryption and retention policies for audit readiness is to enforce encryption at rest and in transit across databases and APIs. This establishes clear retention limits and secure data flows.