A2P 10DLC Privacy Policy and Terms: What to Include
Updated
Short answer: Your privacy policy must be public and say you will not share mobile numbers or SMS opt-in data with third parties for marketing. Your terms need an SMS section with the program name, a description, rates, frequency, support contact, HELP and STOP, a privacy policy link and a carrier liability line. Both pages must open without a login and be linked right next to your opt-in, and your terms must sit on your business's own domain.
This article covers what carrier reviewers check, not what privacy law requires. It is not legal advice.
The privacy policy
Twilio's registration docs list what The Campaign Registry (TCR) accepts and rejects:
| TCR accepts privacy policies that | TCR rejects privacy policies that |
|---|---|
| Are public, with no login | Require a login |
| State that you will not share users' mobile numbers with third parties | Have no statement about not sharing mobile numbers |
| Disclose message frequency, such as "You may receive up to 4 messages per month." | Are not public at the URL you give |
| Include the statement "Message and data rates may apply." |
Twilio's onboarding guide gives a sentence to include: "We do not sell or share your SMS opt-in data or personal information with third parties for marketing purposes." Its fix for error 30909 adds: "The Privacy Policy must state that mobile numbers aren't shared with third parties and include the messaging disclosures."
Look for clauses that say the opposite. Error 30932 applies "when your privacy policy or opt-in flow shows that mobile opt-in data may be shared with third parties, affiliates, or lead generators". Twilio's article on forbidden message categories goes further: it does not allow any business whose terms or privacy policy "mentions sharing or selling consumer data/opt-in information".
An SMS section you can adapt:
SMS messages. We do not sell or share your SMS opt-in data or personal information with third parties for marketing purposes. We will not share your mobile number with third parties. You may receive up to 4 messages per month. Message and data rates may apply. Reply STOP to unsubscribe or HELP for help.
Check that every sentence is true for your business before you publish it.
The terms and conditions
Twilio's onboarding guide says your terms must include:
- "Program or brand name"
- "Program description"
- "Message and data rates may apply disclosure"
- "Message frequency (or recurring message disclosure)"
- "Customer support contact information"
- "Complete opt-out instructions (HELP and STOP), displayed in bold"
- "Link to the privacy policy"
- A disclosure that states "Carriers are not liable for any delayed or undelivered messages"
Most items have their own rejection code: 30557 (business or program name), 30558 (frequency), 30559 (program description), 30560 (customer support), 30561 (opt-out), 30562 (rates) and 30563 (carrier liability).
An SMS terms section with all eight items, for a made-up gym:
- Acme Fitness Class Reminders. Acme Fitness sends class booking reminders and schedule changes by text message to members who opt in.
- Message frequency varies. Message and data rates may apply.
- For support, email [email protected] or call [your support number].
- Reply STOP to cancel. Reply HELP for help.
- Carriers are not liable for any delayed or undelivered messages.
- Our Privacy Policy is at https://acmefitness.example/privacy.
Where the pages live
- Public, with no login. "Your Privacy Policy link must open a page anyone can view without logging in." The same rule applies to your terms (errors 30973 and 30975).
- The full text, not a stub. "Your Privacy Policy link must open a page that shows the full policy as text." The same rule applies to your terms (errors 30974 and 30976).
- On your own domain. TCR accepts terms pages that "Are hosted on the same domain as the business website (for example, www.example.com/terms)." It rejects terms that redirect to another domain, and PDF files "hosted behind an authentication wall."
- Linked at the opt-in. Error 30564 applies when "Direct text links to your Terms of Service and Privacy Policy are not placed close to the call-to-action opt-in section, or they are hidden inside dropdowns or pop-ups." CTIA says the same of privacy policies: "All applicable privacy policies should be referenced in and accessible from the initial call-to-action."
- The same links everywhere. Twilio: "The privacy policy and terms & conditions links included in these fields should match the links included in your opt-in (web form, text key word campaign, etc.)."
The registration fields
Since June 30, 2026, Twilio's API needs both links to create a campaign. "Starting June 30, 2026, the PrivacyPolicyUrl parameter is required when creating a campaign via the Twilio REST API." The TermsAndConditionsUrl parameter is required from the same date. Leaving them out returns errors 30933 and 30934.
TCR's own user guide marks the terms and privacy policy fields as optional in TCR. It also notes that you still need proper terms and a proper privacy policy.
Checklist
- The privacy policy has the no-sharing statement, the message frequency and "Message and data rates may apply."
- Nothing in either page says you share or sell opt-in data.
- The terms have an SMS section with all eight items, and HELP and STOP are in bold.
- Both pages load for anyone, with no login, and the terms are on your business domain.
- Both are linked as plain text links right next to the opt-in.
- The links in your registration match the links at the opt-in.
Precheckly's Pro plan, at $29 a month, includes 10 A2P registration pre-checks a month. Each one covers your website and privacy policy along with the opt-in flow, campaign description and samples.
For the wording at the opt-in itself, see SMS opt-in language. For other reasons campaigns fail, see why A2P 10DLC campaigns get rejected.
Sources
- A2P 10DLC - Gather the Required Business Information, Twilio
- A2P 10DLC Campaign Onboarding Guide, Twilio
- Forbidden Message Categories in the US and Canada, Twilio
- 30909: Campaign rejected: Message Flow or Call to Action incomplete/unverified, Twilio
- 30932: Campaign rejected: Privacy policy must disclose third-party data sharing, Twilio
- 30933: Campaign registration rejected: Privacy Policy URL is required for A2P 10DLC campaign, Twilio
- 30934: Campaign registration rejected: Terms and Conditions URL is required for A2P 10DLC, Twilio
- 30564: Terms of Service and Privacy Policy links not near opt-in, Twilio
- 30973: Reviewers couldn't open your Privacy Policy page, Twilio
- 30974: Your Privacy Policy page has too little text to review, Twilio
- Error and Warning Dictionary, Twilio
- Messaging Principles and Best Practices, May 2023, CTIA
- CSP User Guide, April 2026, The Campaign Registry
Not legal advice. Carrier rules and provider documentation change, so check the linked sources before you rely on them.