# POL-141 — The published documents must show when they were last updated

> The privacy policy and the terms must each display the date they were last updated.

- **Rule ID:** POL-141
- **Layer:** Policy pages (`POLICY_PAGE`)
- **Checks:** `privacy policy + terms date block`
- **Severity:** HIGH — Rejected by at least one carrier or provider, and a common cause of failure at the rest.
- **When it bites:** Gates approval — get this wrong and registration is refused
- **How it is detected:** Deterministic (settled in code from the submitted values)
- **Fix type:** Fix the privacy policy or SMS terms
- **Required by:** CCPA, CTIA, TCR
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/policy-page/pol-141/

## Why this rule exists

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.

## How to fix it

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 of a compliant value

```text
Last updated: 1 July 2026
```

## Common mistakes

- 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.