The policy links must say which document they open
The requirementstatement
The links to the Privacy Policy and the Terms & Conditions must be labelled as those documents, and the pages they open must title themselves the same way.
- Severityseverity
- HighHIGHRejected by at least one carrier or provider, and a common cause of failure at the rest.
- When it bitesphase
- Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
- What is checkedobject
- link text and document titles of the policy links
- Where it liveslayer
- Consent flowCONSENT_FLOW
- How Ekas settles itdetectability
- AI · crawlCRAWLAI · visionVISION
- Needs your live site or policy page fetched and read. Ekas crawls it the way a reviewer would. Needs the pixels: a screenshot of the opt-in surface, a scanned paper form, an MMS attachment.
- 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
- CTIA
- When it appliesapplicabilityText
- Applies when consent was NOT collected by live verbal and IVR.
Why this rule existsrationale
A consumer deciding whether to read the terms needs to know that is what the link is. "Learn more", "details", or a bare "here" tells them nothing, and a reviewer checking whether the required links are present cannot confirm it either. The document side matters for the same reason: a page reachable from a link labelled Privacy Policy that never calls itself one is not obviously the policy at all.
How to fix itremediation
Use the document names as the link text — "Privacy Policy" and "Terms of Service" — and make sure each page carries the matching title as a heading. Done when both the link and the page it opens use the same name.
A compliant exampleexample
By checking this box you agree to Acme Coffee's <a href="/sms-terms">Terms of Service</a> and <a href="/privacy">Privacy Policy</a>.
Common mistakespitfalls
- Bundling both documents behind one link labelled "our policies" fails even when the destination contains both, because the consumer cannot tell what they are agreeing to before they click.
Notesnotes
Excluded from the verbal methods, which have no link text to label — a script names the policy aloud instead, which CON-VERBAL-ELEMENTS already checks as its eighth element.
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-017An offline opt-in still needs a findable business behind itHighHIGHCON-033Opt-in evidence must be the live surface, not a mockup of itHighHIGHCON-038Verbally-collected informational campaigns need the mockup and the messagesHighHIGHCON-042The phone field must be optional on a general-purpose formHighHIGHCON-044A required phone field must carry an SMS disclaimer beside itHighHIGHCON-064A kiosk or terminal must not pre-fill the consumer's numberHighHIGH
CON-093 is one of 101 consent flow rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.