Error 30932: Privacy Policy Rejected
Your privacy policy suggested that mobile data or consent may be shared with third parties. Here is the wording reviewers need to see.
Why Privacy Policies Get Rejected
What does 30932 mean?
The privacy policy or opt in suggests mobile data or consent may be shared with third parties, or it is missing a clear statement that it will not be.
What causes it?
Wording that allows sharing, selling or transferring data, no statement that mobile data is not shared for marketing, or no public privacy policy link in the message flow.
What should the policy say?
That opt in data and consent are not shared with or sold to third parties, affiliates or lead generators for marketing or promotional purposes.
Where should it be linked?
On a public page and linked in your message flow, next to the opt in.
What Does Error 30932 Mean?
Error 30932 means an A2P 10DLC campaign was rejected because your privacy policy or opt-in flow suggests that mobile opt-in data may be shared with third parties, affiliates or lead generators, or because the required non-sharing statement is missing. Carriers need to see, in a public privacy policy, that mobile numbers and SMS consent are not shared for marketing.
Twilio’s error reference lists the causes:
- Policy wording that mobile information or consent may be shared, sold, rented or transferred.
- No clear statement that mobile data will not be shared for marketing or promotional purposes.
- No link to a publicly accessible privacy policy in the message flow.
- Consent treated as transferable between businesses or affiliates.
What Should the SMS Privacy Clause Say?
The SMS privacy clause should say plainly that mobile information and text-messaging opt-in data will not be shared with third parties or affiliates for marketing or promotional purposes, and that this data is excluded from any other sharing the policy describes. It belongs in the public privacy policy that your opt-in flow links to.
Wording commonly used for this clause:
- “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.”
Then check the rest of the policy. A general line elsewhere such as “we may share your information with partners” can still read as covering mobile data, so add the exclusion right next to it.
| 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 transfer. |
| The non-sharing clause above, on a public page linked from the opt-in | Meets the requirement. |
Our SMS privacy policy requirements guide goes section by section, and the free SMS privacy policy generator drafts the clause.
How Do You Fix Error 30932 and Resubmit?
To fix error 30932, add the non-sharing clause to your public privacy policy, remove or qualify any wording that suggests mobile data or consent can be shared or sold, link the policy from every opt-in method, and resubmit the campaign. If several businesses send messages, each one must collect its own consent.
- Edit the live policy page, not just the registration form. Reviewers open it.
- Search the policy for share, sell, rent, transfer, affiliates and partners, and qualify each one for mobile data.
- Link the policy from the opt-in form and the message flow description.
- Collect consent per sender if more than one business will text the same people.
- Resubmit the campaign. See rejected A2P campaigns.
Privacy wording problems often come with website issues; see website rejections. Prefer it handled? We fix the policy and resubmit for $50.
Make Your Policy Carrier Ready
Remove sharing language and add a clear statement.
No Sharing Statement
Mobile data and consent not shared for marketing.
Remove Transfer Wording
No language allowing consent to transfer.
Public Link
Policy linked in the message flow.
Separate Consent
Consent collected for your brand only.
We Fix Your Policy and Resubmit
We correct your privacy wording and resubmit the campaign.
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.
Rejection Fixes Included
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
Does my privacy policy need a separate SMS section?
It needs a clear statement that mobile information and SMS opt-in data are not shared with third parties or affiliates for marketing. Many businesses put it in a short SMS or text messaging section so reviewers find it quickly, and link that policy from the opt-in.
Can I share customer data with my CRM or SMS provider?
Service providers that send your messages are a different case from sharing consent for others’ marketing. The rule targets sharing or selling mobile data and consent to third parties or affiliates for their marketing. Describe processors accurately and keep the non-sharing clause clear.
Does the privacy policy have to be on my own website?
It should be a publicly accessible page that matches your business and is linked from your opt-in flow. Hosting it on your own domain also supports the brand and website checks reviewers run.
Is error 30932 the same as 30908?
They are related. 30908 means a compliant privacy policy is required, and 30932 targets wording that allows mobile data or consent to be shared. Fixing the policy with the non-sharing clause and a public link addresses both.
Rejected for 30932?
Send us your privacy policy and we fix the wording.
