# POL-241 — A generated document must carry brand-specific facts

> A generated policy or terms document must contain facts specific to this brand — real product names, the actual opt-in surfaces, the actual vendors.

- **Rule ID:** POL-241
- **Layer:** Policy pages (`POLICY_PAGE`)
- **Checks:** `generated policy and terms body`
- **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 submitted form
- **Fix type:** Fix the privacy policy or SMS terms
- **Required by:** TCR
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/policy-page/pol-241/

## Why this rule exists

A document that could belong to anybody tells a reviewer that nobody described this business to whoever wrote it, and the reviewer's next question is whether the business exists. It is also the difference between a policy that is true and one that is merely plausible: the specifics are what make its promises checkable against the site.

## How to fix it

Name the business, the site, the opt-in surfaces, the message categories and the delivery vendor in the document itself. Done when a reader could identify the business from the policy alone.

## Example of a compliant value

```text
Acme Coffee Rewards collects your number at checkout on acmecoffee.com and sends it to our messaging vendor, who delivers the texts. Nobody else receives it.
```

## Notes

Absorbs OPS-377, which states the same warning from the operational side. POL-240 is the detection of generic text in an existing document; this is the requirement on one we produce.