# POL-098 — The policy must disclose message frequency

> The privacy policy must disclose how often the programme sends messages.

- **Rule ID:** POL-098
- **Layer:** Policy pages (`POLICY_PAGE`)
- **Checks:** `privacy policy body`
- **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 submitted form
- **Fix type:** Fix the privacy policy or SMS terms
- **Required by:** Twilio
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/policy-page/pol-098/

## Why this rule exists

Twilio asks for the frequency in the privacy policy while CTIA locates it in the terms, so a business that put it in one document and not the other is complying with a real standard and failing a different one. The consumer interest is the same in both places: how often is the thing they just agreed to going to reach them.

## How to fix it

Add the frequency claim to the messaging section of the policy, worded identically to the one in the SMS terms and at the opt-in. Done when all three say the same thing.

## Example of a compliant value

```text
Message frequency varies.
```

## Provider rejection codes

| Provider | Code | Resubmission allowed |
| --- | --- | --- |
| Twilio (gen1) | `30908` | yes |

## Notes

A genuine provider divergence, resolved by requiring it in both documents: Twilio 30908 and 30909 demand it in the privacy policy, CTIA in the terms and conditions. POL-172 is the terms-side rule.