10DLC privacy policy example
You don't need a new privacy policy – you need an SMS section inside the one you have. Below is a complete example for a demo business; the paid pack fills it in with your details and provider.
Example SMS section
## Text messaging (SMS)
Bright Smile Dental PLLC ("Bright Smile Dental") sends text messages to people who have opted in, for the following purposes: appointment reminders and promotional offers.
**Information we collect.** When you opt in we collect your mobile phone number, the date and time of your consent, how you consented (for example the web form, keyword or paper form) and the wording you agreed to. We use this information only to send the messages you requested and to keep a record of your consent and any opt-out.
**No sharing of mobile information.** No mobile information will be shared with third parties or affiliates for marketing or promotional purposes. Text messaging originator opt-in data and consent will not be shared with any third parties, except service providers (such as our messaging platform, Twilio) that process it only to deliver our messages. All other categories of sharing described in this policy exclude text messaging originator opt-in data and consent.
**Frequency and cost.** Up to 4 msgs/month. Message and data rates may apply.
**Opting out and help.** Reply STOP to any message to unsubscribe; you will receive one confirmation and no further messages. Reply HELP for help, or contact us at [email protected] or (512) 555-0100.
**Retention.** We keep consent and opt-out records for as long as you are subscribed and for a reasonable period afterwards to show compliance.
_Last updated: 2026-11-20_
The sentence that matters most
"No mobile information will be shared with third parties or affiliates for marketing or promotional purposes" – plus the clarification that SMS opt-in data and consent are excluded from all other sharing. Without it, reviewers return 30908. If your general policy says you may share data with partners and has no SMS exception, you get 30932.
What TCR accepts and rejects
| Accepted | Rejected |
|---|---|
| Public page, no login | Login-gated policy |
| States mobile numbers are not shared | No non-sharing statement |
| Discloses message frequency | Policy on a PDF or behind a click (30973, 30974) |
| Includes "Message and data rates may apply" | Policy names only your software provider (30981) |
FAQ
Can I use my booking software's privacy policy?
No. From 9 December 2026 Twilio returns 30981 when the policy names only another business. Publish your own policy that names your business.
Does it have to be a separate page?
No – an SMS section inside your existing privacy policy is fine, as long as the URL you submit opens it directly.
Official sources
- Twilio: A2P 10DLC – Gather the Required Business Information – checked Nov 20, 2026
- Twilio error 30908 – checked Nov 20, 2026
- Twilio error 30932 – checked Nov 20, 2026
- Twilio Changelog (13 Nov 2026): New error codes for A2P 10DLC campaign rejections – checked Nov 20, 2026
- CTIA Messaging Principles and Best Practices (May 2023) – checked Nov 20, 2026
Independent service. Not affiliated with Twilio, The Campaign Registry or any carrier. Templates, not legal advice; we do not guarantee carrier approval.