Privacy policy and terms URLs must be different pages

The requirementstatement

The privacy policy URL and the terms of service URL must not be the same page.

Severityseverity
HighHIGHRejected by at least one carrier or provider, and a common cause of failure at the rest.
When it bitesphase
Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
What is checkedobject
campaign.privacy_url + campaign.terms_url
Where it liveslayer
CampaignCAMPAIGN
How Ekas settles itdetectability
DeterministicDETERMINISTIC
Settled in code from the values you submitted. No model involved, no judgement call, same answer every time.
What the fix involvesfailureClass
Fix the fieldRETRY_FIELD
A better value in the form fixes it. Ekas can rewrite it and re-check.
Who requires itauthorities
TCRTwilio
When it appliesapplicabilityText
Applies to every 10DLC registration.

Why this rule existsrationale

The privacy policy and the terms answer different questions — how data is handled versus what the program is — and reviewers check them separately. Brands routinely paste the same combined-legal-page URL into both fields, and a presence-only check passes it while a reviewer opening both links does not.

How to fix itremediation

Link the privacy policy and the terms of service separately. If you only have one combined page, publish a distinct SMS terms page.

A compliant exampleexample

Privacy: https://acmecoffee.com/privacy · Terms: https://acmecoffee.com/terms

Notesnotes

Catalog POL-017. Brands paste the same URL twice constantly and "both fields present" passes today.

Rules you will hit next

One other rule reads campaign.privacy_url + campaign.terms_url. Fixing one field to satisfy a single rule is how a resubmission trades one rejection for another, so read these before you change anything.

All campaign rules

CMP-URL-DISTINCT is one of 94 campaign 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.