data-retention-policies

Define and enforce data retention policies across regulatory standards.

Updated Mar 29, 2026

Search Tags:#compliance #retention #audit-trails #data-lifecycle #legal-hold #data-purging

Ready to run

npx skills add https://github.com/marquesfelip/agents-and-skills --skill data-retention-policies-marquesfelip

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: data-retention-policies
Source: https://github.com/marquesfelip/agents-and-skills/tree/main/skills/data-retention-policies
Command: npx skills add https://github.com/marquesfelip/agents-and-skills --skill data-retention-policies-marquesfelip

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Data stewardship teams often struggle to define and enforce data retention rules that satisfy regulatory requirements and business needs.

Core Features & Use Cases

Policy authoring and regulatory mapping to GDPR, LGPD, PCI, HIPAA, and internal standards.
Lifecycle state definitions (Active, Closed, Archived, Purged) with automated enforcement and evidence generation.
Legal holds, audit trails, and backup-retention considerations to meet compliance demands.

Quick Start

Create a retention policy entry for a new data entity and configure a 30-day purge workflow.

Frequently Asked Questions about data-retention-policies

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I define data retention policies for GDPR and HIPAA compliance?▼

Data retention policies for GDPR and HIPAA compliance are defined by mapping regulatory requirements to data entities and configuring automated lifecycle states like Active, Archived, and Purged. This ensures compliant deletion, archival, and auditing.

What is the best way to automate data lifecycle enforcement and generate audit trails?▼

Automating data lifecycle enforcement involves defining state transitions for user accounts, logs, or backups, which automatically triggers archival or purging. The process generates audit trails and evidence for compliance reviews.

Can I apply legal holds to prevent data purging during an active audit?▼

Legal holds can be applied to data entities to prevent automated purging workflows from executing. This suspends the standard lifecycle state transitions, preserving records indefinitely until the legal hold is released.

Does this approach support configuring retention workflows for transaction logs and backups?▼

Configuring retention workflows for transaction logs and backups is fully supported. You can define specific lifecycle rules and purge timelines for these data-heavy domains to meet internal standards and regulatory demands.

How do I set up a 30-day purge workflow for archived user accounts?▼

To set up a 30-day purge workflow, create a retention policy entry for the user account entity and configure the lifecycle state to transition from Archived to Purged after 30 days. This enforces compliant deletion automatically.

What are the limitations of using manual data purging instead of defined lifecycle states?▼

Manual data purging lacks the automated enforcement, regulatory mapping to standards like PCI or LGPD, and generated audit trails provided by defined lifecycle states. It increases compliance risks during reviews and fails to handle backup-retention considerations.