# POL-071 — No document may reserve the right to sell or share consent itself

> Neither the privacy policy nor the terms may reserve a right to sell, rent or share the consumer's consent.

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

## Why this rule exists

Consent names a sender; it is not an asset that can change hands, and a document claiming otherwise describes the business model the whole framework exists to stop. Twilio treats this as making the business noncompliant rather than the document, so it is a much worse finding than an over-broad data-sharing clause — and it usually arrives through a template borrowed from an affiliate network.

## How to fix it

Delete any clause reserving rights over the consent itself — to sell it, rent it, share it, or pass it to partners — from both documents. Done when the only thing either document says about consent is how to give it and how to withdraw it.

## Example of a compliant value

```text
Your consent to receive text messages from Acme Coffee applies only to Acme Coffee. We do not sell, rent, share or transfer it to anyone.
```

## Provider rejection codes

| Provider | Code | Resubmission allowed |
| --- | --- | --- |
| Twilio (gen2) | `30932` | yes |

## Notes

Distinct from the data-sharing rules: those are about the number and what is known about the person, this one about the permission. A policy can be impeccable about data and still claim a right over the consent.