What problem does it solve?
This Skill helps teams design software that protects personal data from the start instead of adding privacy controls after launch. It reduces compliance risk, limits unnecessary data collection, and makes consent, retention, and user rights part of the core design.
Core Features & Use Cases
- Data minimization: Identify only the fields and events that are truly necessary for the feature.
- Consent and purpose limitation: Ensure optional collection, analytics, and third-party sharing happen only with explicit permission.
- Security and retention: Apply encryption, access controls, logging hygiene, deletion policies, and backup-aware retention rules.
- User rights support: Plan for access, correction, export, and erasure workflows from the beginning.
- Use case: Review a signup flow, database schema, or analytics integration and rewrite it so the product collects less data, explains why it is collected, and provides a clear way to delete or export it.
Quick Start
Use the privacy-by-design skill to review this feature and tell me what personal data to remove, what consent is required, and how to add retention, deletion, and safe logging safeguards.
