{
  "id": "POL-150",
  "slug": "pol-150",
  "title": "The SMS terms must exist as a document of their own",
  "statement": "The SMS terms must be published as a distinct, directly accessible document rather than only as a clause inside the general website terms.",
  "rationale": "A consumer who wants to know what they signed up for should not have to read a commercial terms-of-sale document to find it, and a reviewer given a general ToS has to hunt for the messaging clauses and decide whether what they found is the programme. Both problems disappear with a page whose whole subject is the text programme, which is why most providers ask for one.",
  "layer": "POLICY_PAGE",
  "layerSlug": "policy-page",
  "object": "SMS terms document",
  "severity": "BLOCKING",
  "detectability": [
    "CRAWL"
  ],
  "failureClass": "TERMINAL_POLICY",
  "artifact": "sms_terms",
  "authorities": [
    "Bandwidth",
    "TCR",
    "Sinch",
    "Plivo",
    "Twilio",
    "Klaviyo",
    "Infobip"
  ],
  "codes": [
    {
      "provider": "Bandwidth",
      "code": "TFV 1504",
      "remediable": true
    },
    {
      "provider": "Twilio",
      "code": "30882",
      "remediable": true,
      "generation": "gen1"
    }
  ],
  "applicabilityText": "Applies to every 10DLC registration.",
  "universal": true,
  "remediation": "Publish a dedicated SMS terms page — /sms-terms is the conventional path — and register that URL on the campaign, keeping a cross-referencing section in the general ToS. Done when the terms URL opens a page whose subject is the messaging programme.",
  "pitfalls": [
    "Registering the general ToS URL and relying on a reader scrolling to the SMS section satisfies POL-211 and fails this rule. The two are kept separate because providers genuinely differ, so the safe build is a dedicated page plus an anchored section."
  ],
  "notes": "Contested in the catalog: no primary source mandates a dedicated page over an anchored ToS section, and the canonical position taken here is to generate both. POL-211 is the relaxed form — an anchored section satisfies that and fails this.",
  "phase": "approval",
  "automated": true,
  "url": "https://ekas.io/rules/10dlc/policy-page/pol-150/",
  "markdown": "https://ekas.io/rules/10dlc/policy-page/pol-150.md",
  "registry": "https://ekas.io/rules/10dlc/",
  "updated": "2026-07-25",
  "licence": "CC BY 4.0 — https://creativecommons.org/licenses/by/4.0/"
}