A non-marketing programme's policy must not describe promotional texting
The requirementstatement
Where the campaign is not registered for marketing, the policy must not describe promotional or marketing texting.
- Severityseverity
- HighHIGHRejected by at least one carrier or provider, and a common cause of failure at the rest.
- When it bitesphase
- Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
- What is checkedobject
- privacy policy body vs campaign.usecase
- Where it liveslayer
- Policy pagesPOLICY_PAGE
- How Ekas settles itdetectability
- AI · formAI_FORM
- A semantic question about what you wrote: whether a description matches a use case, whether a name looks like a filed entity. Judged by a model against written criteria.
- 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
- AWS
- When it appliesapplicabilityText
- Applies when the use case is NOT MARKETING, MIXED and SWEEPSTAKE.
Why this rule existsrationale
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 itremediation
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.
A compliant exampleexample
Non-marketing policy text: "We text you about your open support ticket. We do not send promotional messages to numbers collected this way."
Notesnotes
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.
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-021Policy URLs must not redirectHighHIGHPOL-023A social profile is not a policy pageHighHIGHPOL-025Exactly one privacy policy must be discoverableHighHIGHPOL-026The policy on the site and the policy attached to the registration must agreeHighHIGHPOL-030Both documents must be linked from the site footer on every pageHighHIGHPOL-053The clause must say NOT SHARED, not merely "not sold"HighHIGH
POL-093 is one of 157 policy pages rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.