A resolver that takes the campaign input's URLs when they are https, otherwise falls back to the platform's public legal pages. It forces the www host and refuses to file a development host.
Also called: 30908 · 30882 · privacy policy required · terms and conditions url
- 1The campaign input may carry the builder's own policy and terms URLs.
- 2Non-https or missing values fall back to the platform's public legal pages.
- 3The site origin is normalised to the www host, and any http/local origin is replaced with the canonical production one.
- 4Both URLs are sent on the campaign filing.
Recorded as L2B-3XKDRZ with the carrier codes: the vendor 'made PrivacyPolicyUrl and TermsAndConditionsUrl REQUIRED for new A2P campaign registrations on 2026-06-30. We were sending neither, which is the first cause listed on both rejection codes we hit: 30908 — a compliant privacy policy can not be verified; 30882 — Missing TermsAndConditionsUrl field.' The per-registration design is reasoned: 'a builder registering their OWN brand must point at their OWN policies — ours describe Leads 2 Build, not them, and would fail "relevant to the registered brand".' The www rule is a repeat of an earlier lesson: 'the apex 308-redirects, and an automated vetter that doesn't follow redirects sees a non-200.' The dev-host guard is Keith 08-17: from a local session the environment points at http://localhost and the carrier rejects it.
- Filings omitted two now-mandatory URLs and were rejected.
- Falling back to a redirecting apex or a localhost URL failed automated vetting.
- Using the platform's policies for a builder's own brand failed the relevance check.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →