Design a privacy lifecycle across collection, purpose, consent, retention, access, and deletion. Use when mapping personal data or building consent, retention, or deletion controls. Do not use to fulfill one specific data-rights request, and not for legal advice.
Installs into .claude/skills of the current project.
Are you the author of Privacy Lifecycle?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/sylphxai-privacy-lifecycle)
---
name: privacy-lifecycle
description: "Design a privacy lifecycle across collection, purpose, consent, retention, access, and deletion. Use when mapping personal data or building consent, retention, or deletion controls. Do not use to fulfill one specific data-rights request, and not for legal advice."
---
# Privacy Lifecycle
Availability is not reuse authority. A toggle without enforceable propagation is not a control. A disabled capability creates no undeclared collection, permission, network, or retention cost.
Open [data inventory](references/data-inventory-purpose-and-controls.md) or [consent and retention](references/consent-retention-and-change.md) when the map or control machine needs depth. For a specific access, export, correction, deletion, restriction, or appeal request, use `data-rights-request`.
