# POL-251 — Say that carriers, not CTIA, enforce the non-sharing language

> The product should disclose that the SMS non-sharing language is a carrier and TCR requirement rather than a CTIA one.

- **Rule ID:** POL-251
- **Layer:** Policy pages (`POLICY_PAGE`)
- **Checks:** `product export disclosure copy`
- **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:** Human check — only someone holding the document can settle it
- **Fix type:** Supply evidence only you hold
- **Required by:** TCR
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/policy-page/pol-251/

## Why this rule exists

Guidance across the industry attributes the mobile-data non-sharing clause to CTIA, and CTIA has never asked for it — so a business that goes to the source to check finds nothing and concludes the requirement is invented. Being explicit that the registry generates to the stricter carrier standard on purpose is what stops that conversation ending with the clause being removed.

## How to fix it

State the attribution where the clause is generated: carriers and TCR require it, CTIA does not. Done when a user who checks the CTIA handbook and finds nothing still understands why the clause is there.

## Check this yourself

**Does whoever decides whether to publish the non-sharing clause know that carriers and TCR require it, and CTIA does not?**

1. State the attribution where the clause is generated.
2. Done when someone who checks the CTIA handbook, finds nothing, and comes back still understands why the clause is there.

*What wrong looks like:* Industry guidance attributes the clause to CTIA, the business goes to the source to check, finds nothing, concludes the requirement is invented — and deletes the sentence.

## Notes

An honesty requirement about our own output, with no registration surface. POL-050 carries the same correction in its rationale; this rule is the obligation to repeat it to the user at the point they are deciding whether to publish the sentence.