{
  "id": "POL-141",
  "slug": "pol-141",
  "title": "The published documents must show when they were last updated",
  "statement": "The privacy policy and the terms must each display the date they were last updated.",
  "rationale": "The date is how a reviewer, and a consumer, tell a maintained document from an abandoned one — CTIA asks for up-to-date, accurate programme information and CCPA requires the date outright. It also settles an argument later: when a programme changes and somebody asks what the terms said at the time, an undated document cannot answer.",
  "layer": "POLICY_PAGE",
  "layerSlug": "policy-page",
  "object": "privacy policy + terms date block",
  "severity": "HIGH",
  "detectability": [
    "DETERMINISTIC"
  ],
  "failureClass": "TERMINAL_POLICY",
  "artifact": "privacy_policy",
  "authorities": [
    "CCPA",
    "CTIA",
    "TCR"
  ],
  "applicabilityText": "Applies to every 10DLC registration.",
  "universal": true,
  "remediation": "Add a \"Last updated\" line carrying a full date at the top or bottom of each document, and change it whenever you change the text. Done when both pages show a date a reader can compare against today.",
  "example": "Last updated: 1 July 2026",
  "pitfalls": [
    "A date generated from the page build changes every deploy and tells a reader nothing about the text. Set it by hand when the wording changes."
  ],
  "notes": "Absorbs POL-142 (a distinct effective date where the two differ), POL-159 (dating the SMS terms) and POL-160 (dating the ToS) — one dating requirement across all three documents. Whether the date is recent enough for the programme it describes is POL-233.",
  "catalogIds": [
    "POL-142",
    "POL-159",
    "POL-160"
  ],
  "phase": "approval",
  "automated": true,
  "url": "https://ekas.io/rules/10dlc/policy-page/pol-141/",
  "markdown": "https://ekas.io/rules/10dlc/policy-page/pol-141.md",
  "registry": "https://ekas.io/rules/10dlc/",
  "updated": "2026-07-25",
  "licence": "CC BY 4.0 — https://creativecommons.org/licenses/by/4.0/"
}
