Fulfill one access, export, correction, deletion, restriction, or appeal request with proof and reconciliation. Use when a user asks to fulfill a data-rights request, a DSAR, a GDPR or CCPA request, or a specific access/delete ticket. Do not use to design the privacy lifecycle, and not for legal advice.
Installs into .claude/skills of the current project.
Are you the author of Data Rights Request?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/sylphxai-data-rights-request)
---
name: data-rights-request
description: "Fulfill one access, export, correction, deletion, restriction, or appeal request with proof and reconciliation. Use when a user asks to fulfill a data-rights request, a DSAR, a GDPR or CCPA request, or a specific access/delete ticket. Do not use to design the privacy lifecycle, and not for legal advice."
---
# Data Rights Request
One request ID through receive, acknowledge, identity and authority check, scope, plan, fulfill, reconcile, deliver, and close. Duplicate requests, missing information, holds, delivery failures, partial fulfillment, scope disputes, and reopened cases keep the same request ID and a clear customer status. Record the authority that controls each deadline. A download link without reconciliation is not fulfillment.
Open [request control and fulfillment](references/request-control-and-fulfillment.md) for identity, authorization, per-system fulfillment, and export quality. Open [edge cases and proof](references/rights-edge-cases-and-proof.md) for holds, shared workspaces, backups, and deletion invariants.
Use `privacy-lifecycle` to design the control system rather than fulfill one request.
