data-retention-policies

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.

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.

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.

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.

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.

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.