Skills Compliance
Building a data-subject erasure plan
Read-only. It produces a plan for review; a platform mutation skill applies it.
npx rulebase-skills install cx-erasure-planWhen to use it
Reach for this when someone says any of these — they are the phrases the skill itself triggers on:
- “delete this customer's data”
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.
The two distinctions that determine everything
Most erasure implementations get one of these wrong, and both failures are serious in opposite directions.
Usage
Input is a canonical export from any platform export skill, so this works identically across every supported helpdesk.
Legal hold overrides erasure
Retention obligations normally take precedence over an erasure request. Supply --legal-hold-file with anything under litigation hold, regulatory retention, or an active dispute. Those entries are marked blocked_legal_hold and are never applied.
What erasure from the helpdesk does not cover
This is the most useful part of the plan, and the part most often missed. Erasing from the helpdesk is not erasing from your business. The plan lists these every run: Attachments and inline images, Voice recordings and transcripts, Canonical exports on disk, including ones produced by this catalog, Backups and snapshots, usually under a separate retention policy, Downstream integrations, The original inbound email in
Reading the plan
Entries are sorted with the ones needing a human decision first, because those are what a reviewer must not skim past.
Troubleshooting
No conversations matched a customer you know exists — check the identifiers against the export's customer_id values. A helpdesk user id is not an email.
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
