# POL-195 — No affiliate-marketing or lead-generation language in the terms

> The SMS terms must contain no affiliate-marketing or lead-generation language anywhere.

- **Rule ID:** POL-195
- **Layer:** Policy pages (`POLICY_PAGE`)
- **Checks:** `SMS terms and ToS body`
- **Severity:** BLOCKING — Breaking this rule gets the submission rejected outright.
- **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, Twilio, TCR, Bird
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/policy-page/pol-195/

## Why this rule exists

AWS and Twilio both mark this non-remediable: a rejection under it ends the campaign rather than starting a fix, because the language is read as a description of the business model rather than as a clause. Terms copied from a template that came from an affiliate network carry it without anyone reading it, which is a very expensive way to inherit somebody else's wording.

## How to fix it

Delete every reference to affiliates, partners, referral commissions and lead sharing from the terms before submitting, and check the source of any template you used. Done when nothing in the document suggests the subscriber's details reach another business.

## Example of a compliant value

```text
Replace "our partners may contact you with related offers" with "only Acme Coffee will text you, and only about the Acme Coffee programme you joined."
```

## Common mistakes

- The codes are non-remediable, so this must be fixed before submission rather than after a rejection. A campaign rejected under 30951 cannot be edited back into life.

## Provider rejection codes

| Provider | Code | Resubmission allowed |
| --- | --- | --- |
| Twilio (gen2) | `30951` | no |
| Bandwidth/DCA | `708` | no |