Your campaign was likely rejected because the privacy policy is missing, hard to find, or does not say that mobile numbers and SMS opt-in data are never shared or sold for marketing. Publish one clear, public policy with that no-sharing statement, add the URL to your campaign, and edit and resubmit the rejected campaign.
Many privacy policies were written for cookies and email lists, not text messages. 10DLC reviewers look for specific SMS language. If the policy does not promise to keep phone numbers and texting consent private, the campaign can be sent back even when everything else is right.
It means the reviewer read your privacy policy, or tried to, and it did not meet messaging rules. Twilio error 30908 covers a missing policy URL, a policy that will not load, several conflicting policies, or a policy that says mobile information is shared for marketing. CTIA asks senders to display a clear policy that explains how they collect, use, and share consumer information, and to make it reachable from the opt-in call to action.
See the full requirement at privacy policy.
Here is a short sample clause. It is sample language, not legal advice; adapt it to your business.
Text messaging. [Business Name] does not sell, rent, or share mobile phone numbers or text message opt-in data and consent with third parties or affiliates for their marketing or promotional purposes. Any sharing described elsewhere in this policy does not include SMS opt-in data or consent. Message frequency varies. Message and data rates may apply. Reply STOP to opt out or HELP for help.
| What to check | Pass looks like |
|---|---|
| URL | Loads over https with no login |
| Number of policies | Exactly one |
| Brand name | Your business, not a template or reseller |
| SMS clause | No sharing or selling of numbers and consent |
| Links | Footer and opt-in form |
Twilio says to edit the rejected campaign rather than delete it, and that the vetting fee is charged only once per campaign. Vonage lists $15 per vetting event, Telnyx describes $15 per submission or resubmission, and Bandwidth says a $15 fee applies to rejected campaigns that need resubmission. Check your provider's current fees first. Twilio says standard campaigns can take up to several weeks to review.
| Twilio code | What it points to |
|---|---|
| 30908 | Privacy policy missing, unavailable, conflicting, or allows sharing |
| 30932 | Policy allows sharing mobile opt-in data |
| 30933 | PrivacyPolicyUrl field missing |
See the 10DLC website requirements hub for everything else.
Want to know if your current policy has the SMS clause? Scan your site free. Our sites ship with an SMS-ready privacy policy built in; see pricing.
A new .com with hosting, SSL, a privacy policy that covers SMS, SMS terms and a compliant opt-in form, built to the requirements on this page. You submit your own 10DLC registration, and no one can guarantee approval, but a reviewer will have nothing on your site to flag.
One-time price · 14-day money-back guarantee · Daily Compliance Watch
It needs a statement that mobile phone numbers and SMS opt-in data and consent are not shared with or sold to third parties or affiliates for marketing or promotional purposes. Twilio, Telnyx, Bandwidth, Vonage, and Plivo all describe this clause.
Telnyx says the policy must be brand-specific, not a reseller's or a generic template. Plivo also says to avoid boilerplate content. Write a policy that names your business.
It can be if SMS data is included. Twilio error 30932 flags policies that allow sharing mobile opt-in data with third parties, affiliates, or lead generators. Telnyx suggests adding a line that excludes SMS opt-in data and consent from any sharing.
On Twilio, yes for new API campaign submissions after June 30, 2026 (error 30933). TCR lists the field as optional in its own system but says a compliant privacy policy is required.
What your privacy policy must say for A2P 10DLC approval: the no-sharing SMS clause, frequency and rates, one policy only, plus sa...
10DLC campaigns need public SMS terms on your own domain. Learn why missing terms cause rejection, what to include, and a sample t...
If reviewers cannot see how people agree to your texts, your 10DLC campaign gets rejected. Learn what proof they need and how to f...
What SMS terms need for A2P 10DLC: program name, message types, frequency, rates, HELP, STOP, and a public https page. Includes sa...
The 8 website requirements reviewers check for A2P 10DLC: privacy policy, SMS terms, opt-in form, brand match, contact info, HTTPS...