The site hosting the policy must itself be live and real
The requirementstatement
Where consent is collected offline, the site hosting the policy pages must still be a live, authentic site rather than a shell built to hold them.
- 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
- policy host site
- Where it liveslayer
- Policy pagesPOLICY_PAGE
- 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
- AerialinkAWS
- When it appliesapplicabilityText
- Applies when consent was collected by paper form, QR code, point of sale, live verbal and IVR.
Why this rule existsrationale
An offline programme can be flawless on paper and still sink on the site nobody thought was being assessed, because the policy has to live somewhere and that somewhere gets crawled like any other brand site. A single-page host stood up to carry two documents looks exactly like the shell sites the authenticity screen exists to catch.
How to fix itremediation
Host the policy pages on the business's real website. Where there is none, publish a small but genuine site describing the business alongside the documents, rather than a bare page carrying only the policy text.
Provider rejection codescodes
The code you get back when this rule is what failed, and whether that provider lets you resubmit.
| Provider | Code | Resubmit |
|---|---|---|
| Bandwidth/DCA | 807 | Yes |
Notesnotes
Tagged to the offline consent methods, which is where the catalog states it and where it bites: a web opt-in already puts the site itself under WEB-024, so this rule adds nothing there.
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-001A privacy policy URL is required on the campaignBlockingBLOCKINGPOL-002A terms and conditions URL is required on the campaignBlockingBLOCKINGPOL-003An uploaded policy document must fit the provider file constraintsBlockingBLOCKINGPOL-005The terms and conditions attestation must be setBlockingBLOCKINGPOL-010Both policy URLs must resolve and return content anonymouslyBlockingBLOCKINGPOL-015The policy host must serve a valid certificate of its ownBlockingBLOCKING
POL-024 is one of 157 policy pages rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.