A generated policy must not describe practices the site does not perform

The requirementstatement

A generated policy must not describe practices the brand does not actually perform.

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
generated policy body vs the site's observed behaviour
Where it liveslayer
Policy pagesPOLICY_PAGE
How Ekas settles itdetectability
AI · crawlCRAWL
Needs your live site or policy page fetched and read. Ekas crawls it the way a reviewer would.
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
CTIA
When it appliesapplicabilityText
Applies to every 10DLC registration.

Why this rule existsrationale

Generation makes this failure easy in a way that drafting does not: a template section about cookies goes into a document for a site that has none, or a "we do not use tracking" line goes into a document for a site loading three analytics tags. The result is a public statement that is false, which is an FTC deception question rather than a carrier one.

How to fix itremediation

Check every practice claim against the live site before publishing, and delete the sections that describe things the business does not do. Done when each claim in the document can be pointed at on the site.

Notesnotes

The machine-checkable half of POL-108, which asks the same question of a policy the brand already published. This one is the generation-time gate, so it is the one that can stop the false statement being made at all.

Rules you will hit next

Other policy pages rules at the same severity. A registration is judged as a whole, not rule by rule.

All policy pages rules

POL-250 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.