What problem does it solve? Engineering teams often collect, log, or share personal data without a clear map of where it flows or how long it is kept, creating privacy and regulatory exposure. This Skill provides structured privacy engineering guidance to audit data collection, minimization, retention, deletion, and vendor sharing before problems ship. ## Core Features & Use Cases - PII Inventory and Flow Mapping: Guides scripted sweeps for PII fields, full-payload logging, and third-party data flows so privacy posture is auditable in the repo. - Lifecycle Checks: Covers retention defaults, deletion/export tests across storage, logs, caches, backups, and vendors. - Decision Rubric and Review Checklist: Structured questions on what data is collected, why, where it flows, who accesses it, and whether lower-data alternatives exist. - Use Case: Before launching a feature that adds analytics tracking, use this Skill to map what data each vendor receives, verify retention defaults are explicit, and confirm deletion workflows actually remove data everywhere. ## Quick Start Review this feature's personal data collection, logging, retention, and third-party sharing for privacy risks and suggest lower-data alternatives.
