Agent skill · product strategy · sickn33

privacy-by-design

Use when building apps that collect user data. Ensures privacy protections are built in from the start—data minimization, consent, encryption.

Why this skill is useful

Provides specific guidelines and principles for integrating privacy protections into software design that the AI wouldn't reliably generate on its own.

What it needs

About 5k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.

What this skill does

Privacy by Design Overview Integrate privacy protections into software architecture from the beginning, not as an afterthought. This skill applies Privacy by Design principles (GDPR Article 25, Cavoukian's framework) when designing databases, APIs, and user flows. Protects real users' data and builds trust. When to Use This Skill Use when building apps that collect personal data (names, emails, locations, preferences) Use when designing database schemas, APIs, or authentication flows Use when the user mentions forms, user accounts, analytics, or third-party integrations Use when deploying to production—verify privacy controls before launch Legal Frameworks GDPR (EU) — Primary reference. Article 25 mandates "data protection by design and by default." Applies to EU users and often adopted globally. CCPA (California) — Right to know, delete, opt-out of sale. Similar principles: minimize, disclose, allow control. LGPD (Brazil) — Aligned with GDPR. Purpose limitation, necessity, transparency. Applies to Brazil users. Design for the strictest framework you target; it often satisfies others. --- Core Principles 1. Data Minimization Collect only what is strictly necessary. Every field needs a documented justification. Avoid "we might need it later." 2. Purpose Limitation Store the purpose of each data point. Do not reuse data for purposes the user did not consent to. 3. Storage Limitation Define retention periods. Implement automated deletion or anonymization when retention expires. Never keep data "forever" by default. 4. Privacy as Default Opt-in for optional collection, not opt-out. Sensitive settings (analytics, marketing) off by default. No pre-checked consent boxes. 5. End-to-End Security Encrypt at rest and in transit. Use RBAC. Log access to sensitive data for audit. 6. Transparency Document what is collected and why. Clear privacy policies. Easy access and deletion for users. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills sickn33/privacy-by-design

View the source on GitHub

Browse the @skills marketplace