How to fix Twilio error 30908: the privacy policy carriers rejected
By Paul Cranmer, Founder · Last verified November 2026 · Twilio · A2P 10DLC campaign registration
Your A2P 10DLC campaign came back with error 30908. The reviewer opened the privacy policy you registered and did not find what US carriers require for business texting. Usually that is one missing sentence, a policy behind a login, or two policies that say different things. This page lists what the reviewer checks, in the order to fix it, and how to check your links before you resubmit.
Who this is for
- Businesses whose A2P 10DLC campaign was rejected with Twilio error 30908
- Agencies resubmitting campaigns for clients on Twilio or HighLevel
- Lead-generation businesses that share other lead data with partners
Not for
- Toll-free or short code verification (different review)
- Errors about the brand registration itself (EIN, business name)
What the platform requires
- Twilio 30908: the privacy policy must be public (no login), relevant to the brand you registered, and found on the website used in your campaign registration.
- One policy only: two policies that disagree are rejected.
- It must say mobile numbers and messaging consent are never shared. Twilio's passing example: "We do not share, sell, or provide your mobile phone number or messaging consent data to third parties or affiliates for marketing or promotional purposes."
- It should say what you collect for texting and how you use it; for website opt-ins, include message frequency and "Message and data rates may apply."
Get a live URL first
Our SMS consent kit adds that section to a privacy policy hosted with us (or gives you the text to paste into yours), and hosts your SMS terms and a public opt-in page to match.
Get the SMS consent kitStep-by-step: paste your privacy policy URL
- Open the link you registered, logged out. Open the privacy policy URL from your campaign in a private browser window. If it asks for a login, redirects to a home page or shows a PDF download, reviewers see the same: fix the link first.
- Make it one policy. If your website footer links one privacy policy and your campaign registers another, pick one and use it in both places. Two policies that disagree are rejected.
- Add the non-sharing sentence. Add a short text message section that says what you collect for texting (the mobile number and the consent record), what you send, how often, that message and data rates may apply, and STOP and HELP. Include Twilio's sentence that mobile numbers and messaging consent are never shared with third parties or affiliates for marketing.
- Remove wording that contradicts it. Search the whole policy for "may share", "partners", "affiliates" and "lead generators". If any sentence could cover mobile numbers or SMS consent, carve them out explicitly (see error 30932).
- Check the links before you resubmit. Run your privacy policy, SMS terms and opt-in page through the A2P 10DLC checker, fix anything marked Fix, then resubmit the campaign with the same links.
Field labels to look for
- Privacy policy URL (campaign)
- The link reviewers open. Public, https, the brand's own policy.
- Message flow / call to action
- Describe where people opt in and link the privacy policy and terms there too.
Common reasons the form fails
- No sentence saying mobile numbers and SMS consent are not shared
- A policy that lets data go to "partners" or "affiliates" with no SMS carve-out
- A link that needs a login, redirects, or points to a different policy than the website footer
- A template that never names the business registered as the brand
FAQ
Can my privacy policy be hosted on another domain?
No source we found forbids it; 30908 asks that it be relevant to your brand and found on the website in your registration. Link it from your own website's footer and sign-up form so reviewers find it there.
We share leads with partners. Can we still pass?
Yes, if the mobile number and the consent to receive texts are never part of what you share. Say so explicitly; a policy that allows sharing them is rejected.
Does fixing the policy guarantee approval?
No. Reviewers also check the opt-in, the terms and the sample messages. Fix every item the checker marks, then resubmit.