# POL-027 — The policy URLs must stay live after approval

> The registered privacy policy and terms URLs must remain reachable after the campaign is approved.

- **Rule ID:** POL-027
- **Layer:** Policy pages (`POLICY_PAGE`)
- **Checks:** `registered policy URLs after approval`
- **Severity:** MEDIUM — Usually survives review, but lowers your trust score or invites manual review.
- **When it bites:** Falls due after approval, once you are live and sending
- **How it is detected:** Not knowable before submission — reported with its deadline
- **Fix type:** Wait on an external system or a required interval
- **Required by:** Twilio, TCR
- **Applies:** Applies to every 10DLC registration.
- **Canonical URL:** https://ekas.io/rules/10dlc/policy-page/pol-027/

## Why this rule exists

Approval is not the end of the checking: the URLs are re-crawled afterwards, and a page that disappears triggers re-vetting rather than a request to restore it. Sites get redesigned and paths get renamed months later by people who have never heard of the registration, so the failure arrives long after anyone connects it to a cause.

## How to fix it

Keep both URLs live for the life of the campaign, and redirect rather than delete if a path has to change. Done when the registered links still open the documents months after approval.

## Provider rejection codes

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

## Check this yourself

**Are the two registered policy URLs on whatever you use to monitor your own site, and does a redesign count as a registration event?**

1. Add both URLs to your uptime or link monitoring.
2. Redirect rather than delete if a path has to change.
3. Tell whoever owns the site that these two paths are registered, because they will be renamed by someone who has never heard of the registration.

*What wrong looks like:* A redesign renames a path months after approval. The re-crawl finds nothing, triggers re-vetting rather than a request to restore it, and nobody connects the two events.

## Notes

Absorbs OPS-269, which states the same monitoring duty with its re-vetting consequence. Nothing at submission time can settle it. The user has to add the two registered URLs to whatever they use to watch their own site, and to treat a redesign as a registration event.