privacy-policy

A privacy policy that does not describe the product is worse than none: it is a false statement. This skill drafts (or repairs) a notice from evidence, and refuses to fill gaps with plausible fiction.

Activate when

• The product collects, stores, or transmits anything personal and there is no notice, an outdated one, or one written for a different product.
• The footer or forms link to a privacy page that does not exist (coordinate with legal-navigation).
• Not when a lawyer's finished text exists (compare it with policy-consistency instead), and not to certify anything.

Working alone

This skill is self-contained. Its companions (declared in its metadata) are skills whose method it may need to do its own promised work. Use of a companion can be conditional: declaring one does not mean running it. When a companion's lane applies, use the skill if it is installed; if not, follow its short entry in references/companion-methods.md and say in your report which lanes ran inline at reduced depth. Never skip an applicable lane silently. Skills mentioned here only for escalation, referral, documentation, or optional deeper follow-up are not dependencies: report the hand-off and finish honestly.

Companions: data-flow-mapping, cookie-and-storage-audit, analytics-privacy, third-party-privacy, data-rights, email-compliance, minors-readiness, payments-readiness, policy-consistency, design-system-reconnaissance.

Inspect