# POL-157 — The documents must describe the programme as it runs today

> The terms and the privacy policy must give up-to-date, accurate information about the programme's details and functionality.

- **Rule ID:** POL-157
- **Layer:** Policy pages (`POLICY_PAGE`)
- **Checks:** `privacy policy + SMS terms body`
- **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:** AI judgement over the submitted form
- **Fix type:** Fix the privacy policy or SMS terms
- **Required by:** CTIA, AWS
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/policy-page/pol-157/

## Why this rule exists

CTIA asks for accuracy rather than mere presence, and a document describing a programme that has since changed is worse than a missing one — a consumer relying on a frequency cap that no longer holds has been misled by a compliance document. Programmes drift constantly: a new message category, a different keyword set, a platform migration, and the terms are rarely part of the change.

## How to fix it

Read both documents against the campaign as registered and correct anything that has moved on — categories, frequency, keywords, contact routes. Done when every factual claim in either document is true of the programme today.

## Example of a compliant value

```text
Terms updated alongside the campaign: "up to 6 messages per month" replaced by "message frequency varies" when the weekly send was added.
```

## Notes

Whether the documents carry a date is POL-141; whether the date is recent enough for the programme is POL-233. This rule is about the substance rather than the dating.