# POL-023 — A social profile is not a policy page

> A social-media profile or post must not be submitted as the privacy policy or terms URL where the brand has a website.

- **Rule ID:** POL-023
- **Layer:** Policy pages (`POLICY_PAGE`)
- **Checks:** `privacy policy URL + terms URL host`
- **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:** Deterministic (settled in code from the submitted values)
- **Fix type:** Fix the field — a better value in the form clears it
- **Required by:** TCR
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/policy-page/pol-023/

## Why this rule exists

A profile page is not a document: it has no stable URL for a specific text, no version, and no guarantee the platform will show the same thing to a logged-out reviewer. Businesses do it because they published their terms as a pinned post and that is the only link they have, which is exactly the situation the fix addresses.

## How to fix it

Publish the policy as a page on the brand website and submit that URL. Done when the policy URL opens a document on your own domain rather than a profile on somebody else's.

## Example of a compliant value

```text
privacy_policy_url: https://acmecoffee.com/privacy, not https://facebook.com/acmecoffee/about
```

## Provider rejection codes

| Provider | Code | Resubmission allowed |
| --- | --- | --- |
| Bandwidth | `1100` | yes |

## Notes

Single secondary source in the catalog with no carrier code behind it, so HIGH rather than BLOCKING. Fires only where a website exists — a brand with no site at all should upload the document instead, which is POL-003.