# POL-212 — Email and other-channel marketing terms must be kept separate from SMS consent

> Marketing terms for email and other channels must be kept separate from the SMS consent terms.

- **Rule ID:** POL-212
- **Layer:** Policy pages (`POLICY_PAGE`)
- **Checks:** `ToS marketing-communications section`
- **Severity:** LOW — Best practice. Worth fixing, rarely fatal on its own.
- **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:** Twilio
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/policy-page/pol-212/

## Why this rule exists

One control covering several channels is the bundled-consent defect Twilio codes at 30913, and the document is where the bundling is usually written down first — "by subscribing you agree to receive email and text messages" makes it official. Separating them in the terms is what lets a subscriber take one and not the other, which is the whole point.

## How to fix it

Give the SMS programme its own section, with its own consent statement, rather than describing it inside a general marketing-communications clause. Done when a reader can see that agreeing to one channel does not sign them up for the other.

## Example of a compliant value

```text
Email newsletter and text messaging are separate programmes with separate sign-ups. Joining one does not join you to the other.
```

## Provider rejection codes

| Provider | Code | Resubmission allowed |
| --- | --- | --- |
| Twilio (gen1) | `30913` | yes |

## Notes

Graded LOW because the document form of the defect is a drafting question; the BLOCKING form — a single control collecting consent for both — lives in the consent-surface layer, where the harm actually happens.