The published documents must show when they were last updated
The requirementstatement
The privacy policy and the terms must each display the date they were last updated.
- 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
- privacy policy + terms date block
- Where it liveslayer
- Policy pagesPOLICY_PAGE
- How Ekas settles itdetectability
- DeterministicDETERMINISTIC
- Settled in code from the values you submitted. No model involved, no judgement call, same answer every time.
- 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
- CCPACTIATCR
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
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 itremediation
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.
A compliant exampleexample
Last updated: 1 July 2026
Common mistakespitfalls
- 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.
Notesnotes
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.
Rules you will hit next
Other policy pages rules at the same severity. A registration is judged as a whole, not rule by rule.
POL-021Policy URLs must not redirectHighHIGHPOL-023A social profile is not a policy pageHighHIGHPOL-025Exactly one privacy policy must be discoverableHighHIGHPOL-026The policy on the site and the policy attached to the registration must agreeHighHIGHPOL-030Both documents must be linked from the site footer on every pageHighHIGHPOL-053The clause must say NOT SHARED, not merely "not sold"HighHIGH
POL-141 is one of 157 policy pages rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.