# POL-240 — Template policy and website content is a known reject cause

> Policy and terms text recognisable as generator boilerplate must be flagged, because reviewers reject it as evidence the business is not real.

- **Rule ID:** POL-240
- **Layer:** Policy pages (`POLICY_PAGE`)
- **Checks:** `privacy policy + terms body`
- **Severity:** MEDIUM — Usually survives review, but lowers your trust score or invites manual review.
- **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:** Plivo, Telnyx, TCR
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/policy-page/pol-240/

## Why this rule exists

Free generators produce documents that are word-for-word identical across thousands of sites, and reviewers have seen them all — so the document that took five minutes to produce is the one that costs a rejection. It is the most common surprise in this whole layer, because the business believes having a policy was the requirement.

## How to fix it

Replace the generic sections with text about this business — the products it sells, the surfaces it collects numbers on, the vendors it actually uses. Done when nothing in the document would be true of an unrelated company.

## Example of a compliant value

```text
Replace "We may collect information from you when you visit our website" with "We collect your mobile number when you tick the text box at checkout on acmecoffee.com."
```

## Provider rejection codes

| Provider | Code | Resubmission allowed |
| --- | --- | --- |
| Bandwidth | `7103` | yes |

## Notes

The positive form is POL-241, which asks whether brand-specific facts are present. This one detects the generic text; that one detects its absence, and a document can fail both.