Your privacy policy probably covers a lot of ground. For 10DLC approval, though, reviewers are looking for one specific clause about how you handle mobile data. Think of it as your golden ticket.
The clause you need
Your policy must include this exact wording, or something very close to it:
No mobile information will be shared with third parties or affiliates for marketing or promotional purposes.
If that promise is missing, in other words if your policy does not clearly state that you will not sell or share supporter phone numbers for marketing, your campaign will be rejected.
What this does not mean
This clause does not mean you cannot share data with the partners who help you run your organization. Sharing data with your donor management system or CRM, your customer service platform, or your texting provider, for example, is perfectly fine. Those partners help you operate.
The red flag for carriers is different. It is sharing supporter data for marketing or promotional purposes, such as selling or trading your list. That is the specific thing the clause rules out.
Where the policy has to appear
Your privacy policy must be visible and accessible during the consent phase, no matter which opt-in method you use. That means:
On a donation or signup form, the policy link sits in the footer or next to the opt-in.
In a phone-bank script, you tell the supporter where to find it, or read the key parts aloud.
On a pledge card or paper form, the form links to it.
For a keyword opt-in, the source material points to it.
If a supporter is agreeing to receive texts, they need to be able to reach your privacy policy at that moment.
Ready-made templates
You do not have to write these from scratch. Rally provides customizable templates you can generate and link to: an SMS privacy policy at rallycorp.com/sms-privacy and matching SMS terms of service at rallycorp.com/sms-terms. Both already include the required clause above.
Related articles