# POL-201 — The terms must name the contracting entity and its address

> The terms of service must identify the legal entity the consumer is contracting with, and its address.

- **Rule ID:** POL-201
- **Layer:** Policy pages (`POLICY_PAGE`)
- **Checks:** `ToS entity block vs brand.company_name`
- **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:** TCR, Twilio, Telnyx
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/policy-page/pol-201/

## Why this rule exists

The contracting party is who the subscriber has an agreement with, and a reviewer matches that name against the brand record — so terms that say "we" throughout leave the registration with no way to bind the document to the business. Trading names make this fail honestly: the site says Acme Coffee, the registration says Acme Coffee Co, LLC, and the terms say neither.

## How to fix it

Name the registered legal entity and its address in the opening clause of the terms, alongside the trading name if you use one. Done when the entity in the terms is the entity on the brand record.

## Example of a compliant value

```text
These terms are between you and Acme Coffee Co, LLC, 1240 Mission St, Suite 400, San Francisco, CA 94103.
```

## Provider rejection codes

| Provider | Code | Resubmission allowed |
| --- | --- | --- |
| Bandwidth/DCA | `807` | yes |

## Notes

POL-225 makes the stricter comparison — the same entity name across the policy, the terms and the brand record. This rule is the one-document form, so terms that name no entity at all get a specific finding rather than a mismatch.