Skills Compliance
Retention audit for support data
Support generates some of the longest-lived and least-governed personal data a company holds. The policy usually exists. What is actually still in the systems usually differs from it, in both directions — and the two directions are different problems with different owners.
npx rulebase-skills install cx-record-retention-auditWhen to use it
Reach for this when someone says any of these — they are the phrases the skill itself triggers on:
- “are we deleting support data on time”
- “retention audit”
- “how long do we keep transcripts”
- “we still have data from 2018”
How it works
The method, in the order the skill runs it. The full procedure — tables, worked examples and the edge cases — is in the skill itself.
Enumerate everywhere support data lives
The audit is only as good as the inventory, and the inventory is always longer than expected. Beyond the helpdesk: Exports, Third parties, Email, where support conversations arrive and stay, Ticketing attachments, including identity documents customers sent, Logs containing message content or personal data.
Test what is there, not what is configured
Configuration and reality diverge. Query the oldest records in each store.
The conflicts, which are the interesting part
Retention periods are set by different obligations that do not agree, and this is where an audit adds most value: Data protection says keep it no longer than necessary, Limitation periods for legal claims argue for keeping evidence, Tax and accounting rules cover transaction records.
Retention and the erasure right
These interact and are frequently confused: Scheduled retention is proactive and applies to everyone.
Related skills
Free and open source, and vendor-neutral — it reads the conversations from whichever helpdesk you already run. Browse all 149 skills · connect your helpdesk over MCP · source on GitHub
