A privacy policy must be reachable from the website
The requirementstatement
The brand website must link to a reachable 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
- brand website
- Where it liveslayer
- WebsiteWEBSITE
- 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 websiteTERMINAL_WEBSITE
- The fix lives on your site. No amount of rewording the form clears it.
- Who requires itauthorities
- CTIATCRTwilioBandwidth
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
Reviewers navigate from the site to the policy rather than trusting the URL field alone, and a policy that exists but is unlinked reads as one created solely for the registration. CTIA also requires it to be reachable from the call to action.
How to fix itremediation
Link the privacy policy from the site footer and from the opt-in surface.
Rules you will hit next
6 other rules read brand website. Fixing one field to satisfy a single rule is how a resubmission trades one rejection for another, so read these before you change anything.
WEB-012A parked or for-sale domain is not a websiteBlockingBLOCKINGWEB-013A pre-launch placeholder is not a websiteBlockingBLOCKINGWEB-016The website must be machine-crawlableBlockingBLOCKINGWEB-017The site must not be gated by geo, bot challenge or app wallBlockingBLOCKINGWEB-021The site must not be behind a login or access wallBlockingBLOCKINGWEB-022A login-gated product needs a public description pageBlockingBLOCKING
WEB-045 is one of 93 website rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.