The policy URLs must stay live after approval

JSONMarkdown

The requirementstatement

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

Severityseverity
MediumMEDIUMUsually survives review, but lowers your trust score or invites a manual look you would rather avoid.
When it bitesphase
After you are livepostFalls due once you are sending: STOP handling, quiet hours, suppression, record retention.
What is checkedobject
registered policy URLs after approval
Where it liveslayer
Policy pagesPOLICY_PAGE
How Ekas settles itdetectability
Post-submissionUNDETECTABLE_PRE_SUBMISSION
The subject does not exist yet at submission time: a reply window, an expiring PIN, a queue position. Reported with its deadline.
What the fix involvesfailureClass
Wait on someone elseTERMINAL_EXTERNAL
Needs an external system or a waiting period, such as IRS propagation, a vetting result, or a carrier queue.
Who requires itauthorities
TwilioTCR
When it appliesapplicabilityText
Applies to every 10DLC registration.

Why this rule existsrationale

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 itremediation

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 codescodes

The code you get back when this rule is what failed, and whether that provider lets you resubmit.

ProviderCodeResubmit
Twiliogen130908Yes

Check this yourselfattestation

No tool can settle this one for you. Here is the check, and what wrong looks like.

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. 1Add both URLs to your uptime or link monitoring.
  2. 2Redirect rather than delete if a path has to change.
  3. 3Tell 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.

Notesnotes

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.

Rules you will hit next

Other policy pages rules at the same severity. A registration is judged as a whole, not rule by rule.

POL-020A non-English site needs an English policyMediumMEDIUMPOL-028Keep a dated copy of both documents as submittedMediumMEDIUMPOL-058A service-provider carve-back is required, not prohibitedMediumMEDIUMPOL-076The privacy policy must describe data handling, not sell the programmeMediumMEDIUMPOL-104The policy must say how message content is handledMediumMEDIUMPOL-105The policy must describe its security safeguards at a high levelMediumMEDIUM

All policy pages rules

POL-027 is one of 157 policy pages rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.

Reading the rules is the easy part.

Ekas runs every rule that gates approval, 823 of these 915, against your registration before it reaches the carrier. It reads your site, your policy pages and your opt-in the way a reviewer would, and hands you the fix, not just the verdict.

Talk to UsHow 10DLC works