The no-sharing statement must be reachable from the consent point

The requirementstatement

The disclosure, or the privacy policy it links to, must state that mobile information is not shared with third parties for marketing purposes.

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: consent disclosure text; privacy policy body
Where it liveslayer: Consent flowCONSENT_FLOW
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: TelnyxBandwidthTwilioAWSSinchInfobipBird
When it appliesapplicabilityText: Applies to every 10DLC registration.

Why this rule existsrationale

This is the single clause carriers care most about, because number-sharing is the mechanism behind most of the traffic 10DLC exists to suppress. It has to be findable from the opt-in rather than buried, since it is the promise the consumer is relying on when they hand over the number — and it is the clause free policy generators are least likely to include.

How to fix itremediation

Add the sentence "Mobile information will not be sold or shared with third parties for promotional or marketing purposes." to the privacy policy, and make sure the opt-in links to that policy. "Sold" alone is not enough — Telnyx requires both words, because sharing without payment is the case that actually happens.

A compliant exampleexample

We will not sell or share your mobile information with third parties for promotional or marketing purposes. Text messaging originator opt-in data is not shared with any third parties.

Common mistakespitfalls

A general "we do not sell your personal data" clause does not satisfy this — the clause must name mobile information or phone numbers specifically.

Provider rejection codescodes

The code you get back when this rule is what failed, and whether that provider lets you resubmit.

Provider	Code	Resubmit
Telnyx	805	Yes
Twiliogen2	30908	Yes

Rules you will hit next

Other consent flow rules at the same severity. A registration is judged as a whole, not rule by rule.

CON-096Nothing in the flow may contradict the no-sharing promiseBlockingBLOCKING CON-008The live CTA and the declared message flow must say the same thingBlockingBLOCKING CON-010The three subscriber-management attributes must be declared trueBlockingBLOCKING CON-013Subscriber attributes must agree with the message bodies suppliedBlockingBLOCKING CON-023Evidence URLs must resolve without a loginBlockingBLOCKING CON-024The opt-in URL must serve a certificate that verifiesBlockingBLOCKING

All consent flow rules

CON-095 is one of 101 consent flow rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.