Keep a dated copy of both documents as submitted

JSONMarkdown

The requirementstatement

Both policy pages should be captured at submission so the exact version that was reviewed can be produced later.

Severityseverity
MediumMEDIUMUsually survives review, but lowers your trust score or invites a manual look you would rather avoid.
When it bitesphase
Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
What is checkedobject
privacy policy + terms as submitted
Where it liveslayer
Policy pagesPOLICY_PAGE
How Ekas settles itdetectability
Human checkHUMAN
Only someone holding the document or making the call can settle it. Ekas tells you exactly what to look at.
What the fix involvesfailureClass
Supply evidenceTERMINAL_EVIDENCE
Needs proof only you hold: a screenshot, a recording, a scan of the form people signed.
Who requires itauthorities
TCR
When it appliesapplicabilityText
Applies to every 10DLC registration.

Why this rule existsrationale

An appeal turns on what the reviewer actually saw, and by the time one is filed the pages have usually been edited — often in response to the rejection itself. Without a capture there is no way to show that the document met the requirement on the day, so a winnable appeal becomes an argument nobody can settle.

How to fix itremediation

Save a dated PDF or archive capture of both pages at the moment you submit, and keep it with the registration record. Done when you can produce the exact text that was live on the submission date.

Check this yourselfattestation

No tool can settle this one for you. Here is the check, and what wrong looks like.

Do you hold a dated capture of both policy pages exactly as they were on the day you submitted?

  1. 1Print both pages to PDF, or take an archive capture, before pressing submit.
  2. 2Store it with the registration record.
  3. 3Done when you can produce the exact text that was live on the submission date.

What wrong looks like: The appeal turns on what the reviewer saw, and by then the pages have been edited — often in response to the rejection itself. A winnable appeal becomes an argument nobody can settle.

Notesnotes

Product hygiene rather than a published carrier rule — the catalog records it as a recommendation. Nothing we hold proves a capture was taken, so this is on the user: print both pages to PDF, or archive them, before pressing submit.

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-020A non-English site needs an English policyMediumMEDIUMPOL-027The policy URLs must stay live after approvalMediumMEDIUMPOL-058A service-provider carve-back is required, not prohibitedMediumMEDIUMPOL-076The privacy policy must describe data handling, not sell the programmeMediumMEDIUMPOL-104The policy must say how message content is handledMediumMEDIUMPOL-105The policy must describe its security safeguards at a high levelMediumMEDIUM

All policy pages rules

POL-028 is one of 157 policy pages rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.

Reading the rules is the easy part.

Ekas runs every rule that gates approval, 823 of these 915, against your registration before it reaches the carrier. It reads your site, your policy pages and your opt-in the way a reviewer would, and hands you the fix, not just the verdict.

Talk to UsHow 10DLC works