Do not silently overwrite a policy the brand already publishes

JSONMarkdown

The requirementstatement

Where the brand already publishes a policy, a generated replacement must be diffed against it and the removed clauses surfaced for review.

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
existing published policy vs the generated draft
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 existing policy usually contains commitments somebody made deliberately — a sector clause, a jurisdiction addendum, a promise made to a customer — and replacing it wholesale deletes them without anyone seeing what went. The business ends up less compliant than before, having run a compliance tool.

How to fix itremediation

Diff the draft against the live page and read the removals before publishing, keeping anything that was there for a reason. Done when every clause the replacement drops has been looked at by a person.

Check this yourselfattestation

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

Have you read what the replacement removes from the policy this brand already publishes?

  1. 1Diff the draft against the live page.
  2. 2Read the removals, looking first for sector language and anything added after a complaint or a legal review.
  3. 3Keep whatever was there for a reason.

What wrong looks like: A wholesale replacement deletes a jurisdiction addendum and a promise made to a customer. The business ends up less compliant than before, having run a compliance tool.

Notesnotes

We can fetch the live policy but we cannot know which of its clauses were deliberate. The user has to compare the two documents themselves and decide what to carry across — sector language and anything added after a complaint or a legal review are the clauses worth looking for first.

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

All policy pages rules

POL-244 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