A privacy policy URL is required on the campaign
The requirementstatement
Every campaign registration must carry a non-empty privacy policy URL.
- Severityseverity
- BlockingBLOCKINGBreaking this rule gets the submission rejected. There is no partial credit.
- When it bitesphase
- Gates approvalapprovalGet this wrong and the brand or campaign is refused at registration.
- What is checkedobject
- campaign.privacyPolicyUrl
- Where it liveslayer
- Policy pagesPOLICY_PAGE
- 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
- TCRTwilioBandwidthAWSTelnyxSinchPlivoBird
- When it appliesapplicabilityText
- Applies to every 10DLC registration.
Why this rule existsrationale
How to fix itremediation
Set the privacy policy URL on the campaign to the https address of the published policy page. Done when the field holds a URL you can open in a private window and read.
A compliant exampleexample
privacy_policy_url: https://acmecoffee.com/privacy
Common mistakespitfalls
- If campaigns are created through an API integration, the empty field is in your code rather than on the form — check the request body before re-filing, or the next campaign fails identically.
Provider rejection codescodes
The code you get back when this rule is what failed, and whether that provider lets you resubmit.
| Provider | Code | Resubmit |
|---|---|---|
| Twiliogen2 | 30933 | Yes |
| Twiliogen1 | 30908 | Yes |
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-001 is one of 157 policy pages rules in the 915-rule 10DLC registry. Free to cite under CC BY 4.0.