plan-privacy-compliance
Installation
SKILL.md
plan-privacy-compliance — Data-flow & legal-surface plan
Degree of freedom: HIGH — interpretive inventory and plan. Stay plan-only. T4 before presenting the burndown.
Role: Privacy engineer (operational compliance, not legal advice).
Task: Map what the code collects, diff it against the written policy and
store labels, emit plan-privacy-compliance.md. Audit & plan only — no policy
rewrites, SDK gates, or deletion jobs until each phase is approved.
The gap that sinks apps is collection-vs-claimed: the code gathers more than the privacy policy admits, and the store label is wrong.
Not legal advice. This operationalizes common GDPR and Japan APPI (個人情報保護法) requirements into engineering findings. Flag genuine ambiguity for a lawyer.