The policy links at the opt-in must open real policy pages
The requirementstatement
The Terms and Privacy Policy links beside the consent control must resolve to live pages carrying those documents — not 404s, placeholders, or unfinished templates.
- 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 links on the opt-in surface
- 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
- CTIATCRTwilioBandwidth
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
A dead policy link is worse than a missing one: the consent block claims the documents exist and the reviewer proves they do not, which puts the whole submission's accuracy in question rather than just the link. It happens most on sites where the policies were generated during a rebuild and the routes changed afterwards.
How to fix itremediation
Open both links from a private browsing window and confirm each returns a real, finished document. Fix the routes rather than the link text, and check for template markers — a generated policy that still says {{COMPANY_NAME}} resolves fine and fails just as hard. Done when both links return a page that names your business.
Common mistakespitfalls
- A link that redirects to the homepage rather than 404ing looks healthy to a link checker and is treated as a missing policy by a reviewer.
Notesnotes
Partially settleable today: where the policy text has been fetched, this can be judged from the content. Where the fetch failed, the registry carries no HTTP status, so the rule returns UNCLEAR rather than assuming a 404 — the same crawler gap CON-024 records.
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-008The live CTA and the declared message flow must say the same thingBlockingBLOCKINGCON-010The three subscriber-management attributes must be declared trueBlockingBLOCKINGCON-013Subscriber attributes must agree with the message bodies suppliedBlockingBLOCKINGCON-023Evidence URLs must resolve without a loginBlockingBLOCKINGCON-024The opt-in URL must serve a certificate that verifiesBlockingBLOCKINGCON-027The opt-in URL must land on a page that carries the opt-inBlockingBLOCKING
CON-094 is one of 101 consent flow rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.