No other document on the domain may contradict the SMS non-sharing clause
The requirementstatement
The terms of service, the cookie policy and any separate data-sharing page must not contradict the SMS non-sharing clause in the privacy policy.
- 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
- all policy-bearing pages on the brand domain
- 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
- Twilio
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
Reviewers read the whole domain, not the one URL on the form, so a data-sharing page written for advertisers overrides a perfect privacy policy. The other documents are usually owned by other people — marketing writes the cookie notice, legal writes the terms — and nobody is comparing them against a clause added for a messaging registration.
How to fix itremediation
Search every policy-bearing page on the domain for sharing language and bring each into line with the messaging clause. Done when the terms, the cookie notice and any data-sharing page all say the same thing about mobile data.
Common mistakespitfalls
- The cookie policy is the one people forget, because it feels unrelated to SMS — and it is the one most likely to carry a permissive advertising-partner clause.
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 |
Notesnotes
Needs a multi-page crawl. Against a single-page fetch the judge can compare only the documents it holds — the privacy policy and the terms — and must say which pages it could not read rather than clearing the domain.
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-001A privacy policy URL is required on the campaignBlockingBLOCKINGPOL-002A terms and conditions URL is required on the campaignBlockingBLOCKINGPOL-003An uploaded policy document must fit the provider file constraintsBlockingBLOCKINGPOL-005The terms and conditions attestation must be setBlockingBLOCKINGPOL-010Both policy URLs must resolve and return content anonymouslyBlockingBLOCKINGPOL-015The policy host must serve a valid certificate of its ownBlockingBLOCKING
POL-070 is one of 157 policy pages rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.