The documents must describe the programme as it runs today
The requirementstatement
The terms and the privacy policy must give up-to-date, accurate information about the programme's details and functionality.
- 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 + SMS terms body
- Where it liveslayer
- Policy pagesPOLICY_PAGE
- How Ekas settles itdetectability
- AI · formAI_FORM
- A semantic question about what you wrote: whether a description matches a use case, whether a name looks like a filed entity. Judged by a model against written criteria.
- 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
- CTIAAWS
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
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 itremediation
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.
A compliant exampleexample
Terms updated alongside the campaign: "up to 6 messages per month" replaced by "message frequency varies" when the weekly send was added.
Notesnotes
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.
Rules you will hit next
One other rule reads privacy policy + SMS terms body. Fixing one field to satisfy a single rule is how a resubmission trades one rejection for another, so read these before you change anything.
POL-117No document may designate an exclusive way to revoke consentBlockingBLOCKINGPOL-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 pageHighHIGH
POL-157 is one of 157 policy pages rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.