# POL-101 — The registered brand name must appear in the privacy policy

> The registered brand name or DBA must appear in the privacy policy the campaign links to.

- **Rule ID:** POL-101
- **Layer:** Policy pages (`POLICY_PAGE`)
- **Checks:** `privacy policy body vs brand.displayName / brand.dba`
- **Severity:** BLOCKING — Breaking this rule gets the submission rejected outright.
- **When it bites:** Gates approval — get this wrong and registration is refused
- **How it is detected:** Deterministic (settled in code from the submitted values)
- **Fix type:** Fix the privacy policy or SMS terms
- **Required by:** AWS, Sinch, TCR
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/policy-page/pol-101/

## Why this rule exists

A vetter matches the name on the registration against the name in the policy, and a mismatch is reported as a policy mismatch rather than as a naming question — so a business trading under a shorter name than it registered fails on two documents that are both correct. It is also what tells the consumer whose promise they are reading, which the campaign's samples cannot do for them.

## How to fix it

Put the registered brand name or DBA in the policy text — the identity block is the natural place — and register whichever name the document uses as the brand DBA. Done when the name on the campaign and the name in the policy are the same string.

## Example of a compliant value

```text
The policy names "Acme Coffee", which is the registered DBA of Acme Coffee Co, LLC.
```

## Notes

Absorbs POL-100 (the policy names the company the consumer is consenting to hear from) and BRD-142 (the same entity-naming requirement across the policy and terms). POL-225 makes the stricter comparison across all three documents; this rule is the one-document form, so a brand whose terms page is missing still gets a specific finding here.