# CON-DISC-BRAND — Consent disclosure must identify the sending brand by name

> The disclosure at the point of consent must name the business that will send the messages.

- **Rule ID:** CON-DISC-BRAND
- **Layer:** Consent flow (`CONSENT_FLOW`)
- **Checks:** `consent disclosure text`
- **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:** AI judgement over the crawled website or policy page; AI vision over a consent artifact (screenshot, scan, MMS media)
- **Fix type:** Fix the website — no form edit clears it
- **Required by:** CTIA, TCR, Twilio, T-Mobile
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/consent-flow/con-disc-brand/

## Why this rule exists

Consent runs to a specific sender, not to messaging in general — that is what makes it non-transferable. A consumer who agreed to hear from "us" on a page they no longer remember cannot meaningfully have consented to the brand that later appears in their inbox, which is precisely the complaint pattern carriers built 10DLC to suppress.

## How to fix it

Put the registered brand name inside the consent sentence itself, not just in the page header or logo. Use the same name you registered — if you registered "Acme Coffee Co, LLC" with DBA "Acme Coffee", either is fine, but a third marketing alias is not.

## Example of a compliant value

```text
By checking this box, you agree to receive recurring automated marketing text messages from Acme Coffee at the number provided. Consent is not a condition of any purchase. Message frequency varies. Message and data rates may apply. Reply STOP to unsubscribe or HELP for help. See our Terms of Service and Privacy Policy.
```