The general policy and the SMS clause must not contradict each other
The requirementstatement
Where the policy contains both a general sharing disclosure and an SMS-specific non-sharing clause, the two must be reconciled rather than left to contradict.
- 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 (intra-document consistency)
- 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
- Telnyx
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
A document that promises two opposite things has told the reviewer nothing except that nobody read it end to end, and the reviewer resolves it against the brand by taking the permissive clause as controlling. It is the standard outcome of adding a compliance paragraph to an existing policy: the new text is correct, the old text is untouched, and both are live.
How to fix itremediation
Edit the general section so it agrees with the SMS clause — narrow it, or exclude messaging data from it by name — rather than adding a third paragraph explaining the relationship. Done when a reader can find only one answer to "is my number shared?".
A compliant exampleexample
General section: "We share personal information with service providers acting on our behalf, and with no one else. Text messaging opt-in data and consent are excluded from all sharing and disclosure."
Notesnotes
The contradiction itself is the finding, which is why this is separate from POL-062 and POL-064: those fail the permissive clause on its own terms, and this one fails the document for holding both. Where only the permissive clause exists, report it there and pass here.
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-069 is one of 157 policy pages rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.