No clause anywhere in the policy may permit sharing data for third-party marketing
The requirementstatement
The whole policy — not just the SMS section — must contain no clause permitting sale, rental, or sharing of personal data for third-party marketing.
- Severityseverity
- BlockingBLOCKINGBreaking this rule gets the submission rejected. There is no partial credit.
- When it bitesphase
- Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
- What is checkedobject
- privacy policy body (whole document)
- 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
- TCRTwilioT-MobileAWS
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
How to fix itremediation
Find and remove or narrow every clause permitting data sharing for marketing. Where you must keep a sharing clause for other purposes, carve messaging data out of it explicitly with "excluding text messaging originator opt-in data and consent".
Provider rejection codescodes
The code you get back when this rule is what failed, and whether that provider lets you resubmit.
| Provider | Code | Resubmit |
|---|---|---|
| Twiliogen2 | 30932 | Yes |
Rules you will hit next
2 other rules read privacy policy body (whole document). Fixing one field to satisfy a single rule is how a resubmission trades one rejection for another, so read these before you change anything.
POL-064 is one of 157 policy pages rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.