SMS Privacy Policy Requirements
Carriers reject campaigns when the privacy policy suggests mobile data may be shared. Here is what your policy needs to say.
What Reviewers Look For
Why does my privacy policy matter for A2P?
Reviewers check that your policy does not allow phone numbers or consent to be shared or sold for marketing. A policy that suggests sharing is a known rejection reason.
What statement should I include?
A clear statement that mobile information, opt in data and consent are not shared with or sold to third parties, affiliates or lead generators for marketing or promotional purposes.
What language should I remove?
Any wording that says consent can be transferred, or that phone numbers may be shared with partners for their own marketing.
Where should the policy be linked?
On a public page of your website and linked from your opt in form, so reviewers can find it from your message flow.
What Does an SMS Privacy Policy Need for A2P 10DLC?
For A2P 10DLC, your privacy policy must be public, linked from the opt-in, and state clearly that mobile information and text-messaging opt-in data are not shared or sold to third parties or affiliates for marketing or promotional purposes. Any wording that allows sharing consent or mobile data with partners, affiliates or lead buyers causes a rejection, usually error 30932.
- Public: reachable without a login, on your own domain.
- Linked: from the opt-in form and the campaign’s message flow (code 30550 if missing).
- Non-sharing clause: mobile data and SMS consent excluded from any sharing.
- Consistent: no general “we share with partners” line without the SMS exclusion next to it.
SMS Privacy Policy Clause Example
The clause most businesses use states that no mobile information will be shared with third parties or affiliates for marketing or promotional purposes, and that text-messaging opt-in data and consent are excluded from any other sharing. Put it in a short SMS section of the privacy policy so reviewers find it quickly.
- “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.”
| Policy wording | Effect |
|---|---|
| “We may share personal information with marketing partners.” | Rejection risk unless mobile data is explicitly excluded. |
| “We sell lead data to affiliates.” | Rejected; consent cannot be transferred. |
| The clause above, on a public page linked from the opt-in | Meets the requirement. |
This is commonly used wording, not an official mandated text. The free SMS privacy policy generator drafts it for you.
How Do You Check Your Privacy Policy Before Registering?
Before registering, open the policy in a private browser window, search it for share, sell, rent, transfer, affiliates and partners, add the SMS exclusion wherever those words could cover mobile data, and confirm the link works from your opt-in form. Do the same for your terms, which should describe the SMS program.
- Open the live URL without logging in.
- Search the sharing words and qualify each for mobile data.
- Add the SMS section with the non-sharing clause.
- Link it from the opt-in and the message flow.
- Check the terms mention message frequency, rates, HELP and STOP.
Rejected already? See error 30932 and website rejections.
Privacy Policy Items for SMS
Cover each of these in plain words.
Data Collected
What you collect, including phone numbers.
No Sharing
Mobile data and consent not shared for marketing.
Opt Out
How to stop messages, such as replying STOP.
Public Link
Easy to find and linked from your opt in.
We Check Your Policy and Register You
We review your privacy wording and handle the full registration.
Share Your Details
Send us your business details, website and how you text customers.
We Prepare and Submit
We write your brand and campaign and submit them to The Campaign Registry.
Carrier Review
Carriers review your campaign. Most reviews take a few business days.
Get Approved
Link your numbers and start sending compliant texts.
Policy Checked, One Flat Price
Complete A2P 10DLC verification, done for you. $50 for one business, $399 for ten.
Single Verification
$50
per verification, paid once
For one business that needs carrier approval to text its customers.
- Brand registration with The Campaign Registry
- Campaign registration with use case and sample messages
- Opt in, privacy policy and STOP and HELP review
- Fixes and resubmission until approved
10 Verification Pack
$399
10 verifications, $39.90 each
For agencies and multi location businesses verifying several brands. Just $39.90 per verification.
- Everything in Single Verification
- 10 verifications for your clients or locations
- $39.90 each instead of $50, you save $101
- Fixes and resubmission until each one is approved
Registration and carrier fees are charged separately by your SMS provider.
Frequently Asked Questions
Do I need a separate SMS privacy policy?
No. You need a clear SMS section or clause inside your public privacy policy that says mobile information and SMS consent are not shared for marketing, and a link to that policy from your opt-in.
Can I share data with my SMS provider or CRM?
Service providers that process and send your messages are different from sharing data for other companies’ marketing. The requirement targets sharing or selling mobile data and consent to third parties or affiliates for their marketing.
Where should the privacy policy link go?
In the opt-in form next to the consent checkbox or keyword instructions, in the campaign’s message flow description, and in your site footer. A missing policy link in the opt-in flow is rejected with code 30550.
Does my terms of service page matter too?
Yes. Reviewers also check for a Terms of Service link in the opt-in flow, code 30549 if it is missing. The terms should describe the SMS program, message frequency, rates and how to get help or opt out.
Is Your Privacy Policy Ready?
Send us your website and we review the SMS wording for you.
