# POL-234 — An opt-in incentive must be described in both documents

> Where joining the programme earns a discount or reward, both the SMS terms and the privacy policy's financial-incentive notice must describe it.

- **Rule ID:** POL-234
- **Layer:** Policy pages (`POLICY_PAGE`)
- **Checks:** `SMS terms + privacy policy incentive language vs the opt-in offer`
- **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 crawled website or policy page
- **Fix type:** Fix the privacy policy or SMS terms
- **Required by:** CCPA
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/policy-page/pol-234/

## Why this rule exists

The offer is the reason most people join, so it is part of the deal rather than a marketing detail — and California treats it as a financial incentive with its own disclosure. A discount described on the checkout box and nowhere else leaves the subscriber unable to check what they were promised.

## How to fix it

Describe the incentive in the terms — what it is, what it requires, when it expires — and cover it in the policy's financial-incentive notice. Done when the offer on the opt-in is documented in both.

## Example of a compliant value

```text
Join Acme Coffee Rewards by text and get 10% off your next order. The code arrives in your welcome message and is valid for 30 days.
```

## Notes

Conditional on the opt-in offering an incentive, which no applicability dimension expresses; the criteria pass immediately where none is offered. The policy-side twin is POL-111.