Skills Compliance
Data minimisation in support
Support forms and ticket schemas grow. Every incident adds a field, every integration adds a property, every team adds a custom attribute — and nothing is ever removed, because removing a field feels riskier than keeping it.
npx rulebase-skills install cx-data-minimisation-reviewWhen to use it
Reach for this when someone says any of these — they are the phrases the skill itself triggers on:
- “do we collect too much data”
- “which fields do we actually use”
- “why do we ask customers for this”
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.
Inventory, then test for use
List every field where personal data can land: Ticket and conversation fields, standard and custom, Contact and customer record fields, Intake and contact-form fields, per form and per channel, Fields populated by integrations, Fields populated by automation, Free-text fields, which can contain anything.
Collection, not just retention
Retention review asks how long you keep it. Minimisation asks whether to collect it at all, and that is the more effective intervention because it removes the data from every downstream system at once.
Free text is the hard part
You cannot minimise what customers volunteer, and support conversations are free text by nature. What you can do.
Removing a field safely
The reason nothing gets removed is that removal feels risky. Make it a bounded change: Confirm nothing reads it.
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
