Message flow must carry the privacy commitment

JSONMarkdown

The requirementstatement

The message-flow / CTA field must state the privacy policy link, or that opt-in data will not be shared.

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
campaign.message_flow
Where it liveslayer
CampaignCAMPAIGN
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 fieldRETRY_FIELD
A better value in the form fixes it. Ekas can rewrite it and re-check.
Who requires itauthorities
BandwidthTelnyx
When it appliesapplicabilityText
Applies to every 10DLC registration.

Why this rule existsrationale

The single commitment carriers care most about is that a mobile number collected for messaging is not passed on, and this is where the consumer is told it. Either form satisfies it — the link or the sentence — which is worth knowing, because a business with no separate privacy page can discharge the requirement with one clause rather than by publishing a document.

How to fix itremediation

Add the privacy policy URL to the disclosure you reproduce in the flow, or state in the flow that mobile opt-in data is never shared with third parties. Done when one of the two appears in the flow text. Put it in campaign.message_flow itself — this field is graded on its own text, not on what a reviewer would find by opening your site.

A compliant exampleexample

The disclosure beside the box reads "We never share your mobile information with third parties" and links https://acmecoffee.com/privacy.

Rules you will hit next

6 other rules read campaign.message_flow. Fixing one field to satisfy a single rule is how a resubmission trades one rejection for another, so read these before you change anything.

CMP-003Message flow must not begin or end with whitespaceBlockingBLOCKINGCMP-059Message flow must describe the mechanism end to endBlockingBLOCKINGCMP-060Every opt-in method in use must be listed in the message flowBlockingBLOCKINGCMP-061Each declared method needs its own complete workflow paragraphBlockingBLOCKINGCMP-072Message flow must state the message typesBlockingBLOCKINGCMP-073Message flow must state message frequencyBlockingBLOCKING

All campaign rules

CMP-078 is one of 94 campaign rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.

Reading the rules is the easy part.

Ekas runs every rule that gates approval, 823 of these 915, against your registration before it reaches the carrier. It reads your site, your policy pages and your opt-in the way a reviewer would, and hands you the fix, not just the verdict.

Talk to UsHow 10DLC works