# CMP-050 — The description must not contain personal data

> The campaign description must not contain individual names, account numbers or other personal data.

- **Rule ID:** CMP-050
- **Layer:** Campaign (`CAMPAIGN`)
- **Checks:** `campaign.description`
- **Severity:** MEDIUM — Usually survives review, but lowers your trust score or invites manual review.
- **When it bites:** Gates approval — get this wrong and registration is refused
- **How it is detected:** AI judgement over the submitted form
- **Fix type:** Fix the field — a better value in the form clears it
- **Required by:** Twilio
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/campaign/cmp-050/

## Why this rule exists

The description is stored and read across several organisations — the CSP, the registry, the carriers — and none of them is the right custodian for a customer's name or account number. It gets there through a well-meant example: someone illustrates the programme with a real message they sent, and the illustration carries a real person in it.

## How to fix it

Replace any real person, account number or order reference with a category or a bracketed placeholder. Done when nothing in the field identifies an individual.

## Example of a compliant value

```text
Acme Coffee texts customers their order status — not "we text customers like Maria Alvarez about order 4471 on card ending 8891".
```

## Provider rejection codes

| Provider | Code | Resubmission allowed |
| --- | --- | --- |
| Twilio | `30886` | yes |