An opt-in incentive must be described in both documents
The requirementstatement
Where joining the programme earns a discount or reward, both the SMS terms and the privacy policy's financial-incentive notice must describe it.
- Severityseverity
- MediumMEDIUMUsually survives review, but lowers your trust score or invites a manual look you would rather avoid.
- When it bitesphase
- Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
- What is checkedobject
- SMS terms + privacy policy incentive language vs the opt-in offer
- Where it liveslayer
- Policy pagesPOLICY_PAGE
- How Ekas settles itdetectability
- AI · crawlCRAWL
- Needs your live site or policy page fetched and read. Ekas crawls it the way a reviewer would.
- What the fix involvesfailureClass
- Fix the policyTERMINAL_POLICY
- The fix lives in your privacy policy or SMS terms. Ekas can generate the missing clauses.
- Who requires itauthorities
- CCPA
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
How to fix itremediation
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.
A compliant exampleexample
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.
Notesnotes
Rules you will hit next
Other policy pages rules at the same severity. A registration is judged as a whole, not rule by rule.
POL-234 is one of 157 policy pages rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.