# POL-250 — A generated policy must not describe practices the site does not perform

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

- **Rule ID:** POL-250
- **Layer:** Policy pages (`POLICY_PAGE`)
- **Checks:** `generated policy body vs the site's observed behaviour`
- **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 crawled website or policy page
- **Fix type:** Fix the privacy policy or SMS terms
- **Required by:** CTIA
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/policy-page/pol-250/

## Why this rule exists

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 it

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.

## Notes

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.