A privacy policy tells people what you do with their information. For texting, reviewers look for a promise that the phone numbers and consent you collect stay with you. CTIA's Messaging Principles ask senders to keep a clear, easy-to-understand privacy policy, show it with clearly labeled links, and make it reachable from the place where people opt in. Providers then add their own specific wording rules.
| Item | Why | Who asks for it |
|---|---|---|
| No sharing or selling of mobile numbers for marketing | Core consent protection | Twilio (30908), Telnyx, Bandwidth, Vonage, Plivo |
| SMS opt-in data and consent excluded from any sharing | Closes the "we share with partners" loophole | Telnyx, Bandwidth, Vonage, Twilio (30932) |
| How you collect, use, and share information | Basic privacy notice | CTIA 5.2.1 |
| Message frequency | Tells people what to expect | Twilio (collect business info, 30896) |
| Rates notice (message and data rates may apply) | Fee disclosure | Twilio (collect business info, 30896) |
| Public, no login needed | Reviewers must be able to open it | Twilio |
| Brand-specific and clearly labeled | Shows it is your policy | Telnyx |
A section that passes review usually covers these points, in plain language:
The carve-out is the part most people miss. A policy can promise no SMS sharing in one paragraph and still fail if another paragraph says you share data with partners.
Included in your Registration Kit: the finished privacy clause written for your business name and your message types, matched to your website, ready to paste. Build my order →
Twilio error 30908 lists "multiple conflicting policies" as a rejection reason. If your site has an old policy in the footer and a new one on another page, a reviewer may find the wrong one. Keep one policy at one URL, link to it everywhere, and paste that same URL into your campaign form.
Put it in three places:
Bandwidth says the link goes in Campaign Details. Twilio added a dedicated Privacy Policy URL field to its Console on February 18, 2026.
| Provider | What they say |
|---|---|
| Twilio | One clear policy stating mobile numbers and messaging consent are not shared with or sold to third parties or affiliates for marketing (30908); no sharing opt-in data with lead generators (30932) |
| Telnyx | Brand-specific, clearly labeled; not sold or shared for promotional or marketing purposes; exclude SMS opt-in data if other data is shared |
| Bandwidth | Mobile info not shared with third parties or affiliates for marketing; opt-in consent data not shared |
| Vonage | No mobile info shared for marketing; originator opt-in data and consent excluded from any sharing |
| Plivo | Includes a no-sharing clause |
Every site we build includes one privacy policy at a single URL, written for your brand name, with an SMS section that covers the no-sharing clause, frequency, rates, STOP, and HELP. It is linked in the footer and next to the opt-in checkbox. Compliance Watch checks daily that the policy page is live and the SMS clause is still there.
Want to know if your current policy has the SMS clause? Compare your site with the checklist, or see pricing for a site with it built in.
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