A landing page that collects personal information must publish a privacy policy
The requirementstatement
Any landing site collecting personal information must carry a conspicuously accessible 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
- landing page policy link
- 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
- AT&TBandwidth
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
The page where a consumer types their phone number is the page where they are entitled to know what happens to it, and a policy two clicks away on a different domain does not reach them at the moment it matters. Campaign landing pages are built to convert and routinely ship without the footer the main site has, so this fails on exactly the page the messages point at.
How to fix itremediation
Link the privacy policy from the landing page itself, next to the form rather than only in a footer nobody scrolls to. Done when the policy is reachable in one click from the page that collects the number.
Provider rejection codescodes
The code you get back when this rule is what failed, and whether that provider lets you resubmit.
| Provider | Code | Resubmit |
|---|---|---|
| Twilio | 7100 | Yes |
Notesnotes
WEB-045 asks the same question of the brand home page. Both are kept because a brand routinely satisfies one and not the other: the main site has a footer and the campaign landing page does not.
Rules you will hit next
Other website rules at the same severity. A registration is judged as a whole, not rule by rule.
WEB-001A brand website URL is requiredBlockingBLOCKINGWEB-009The website must resolve and return contentBlockingBLOCKINGWEB-012A parked or for-sale domain is not a websiteBlockingBLOCKINGWEB-013A pre-launch placeholder is not a websiteBlockingBLOCKINGWEB-014Staging, admin and internal hosts must not be the brand websiteBlockingBLOCKINGWEB-016The website must be machine-crawlableBlockingBLOCKING
WEB-116 is one of 93 website rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.