# POL-093 — A non-marketing programme's policy must not describe promotional texting

> Where the campaign is not registered for marketing, the policy must not describe promotional or marketing texting.

- **Rule ID:** POL-093
- **Layer:** Policy pages (`POLICY_PAGE`)
- **Checks:** `privacy policy body vs campaign.usecase`
- **Severity:** HIGH — Rejected by at least one carrier or provider, and a common cause of failure at the rest.
- **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 privacy policy or SMS terms
- **Required by:** AWS
- **Applies:** Applies when the use case is NOT MARKETING, MIXED and SWEEPSTAKE.
- **Canonical URL:** https://ekas.io/rules/10dlc/policy-page/pol-093/

## Why this rule exists

The inverse of the use-case match, and the one with the different fix: here the policy is broader than the registration, so a reviewer reads it as a marketing programme registered as transactional to get an easier consent standard. It usually arrives through a policy written for the whole business being pointed at a single transactional campaign.

## How to fix it

Either narrow the policy so its messaging section describes only the transactional programme, or register the marketing use case and collect promotional-grade consent. Done when the policy claims no more than the registration does.

## Example of a compliant value

```text
Non-marketing policy text: "We text you about your open support ticket. We do not send promotional messages to numbers collected this way."
```

## Notes

The converse of POL-077, which forces the marketing use case when the policy mentions promotions. Same pair of documents, opposite direction, different fix — narrow the policy rather than widen the registration.