A2P 10DLC privacy policy rejection — how to fix it
Privacy-policy rejections usually mean the submitted policy is missing, unreachable, generic, or does not say enough about how SMS opt-in data and phone numbers are handled.
Guidance only — A2PCheck is independent and not affiliated with Twilio, The Campaign Registry, or any carrier, and we can't guarantee approval.
What this rejection usually means
The privacy URL does not return a public, relevant policy with SMS-specific language and no-sale/no-sharing disclosures for phone numbers collected for messaging.
Why reviewers care
Users should be able to understand how their mobile number is used before opting into messages. Reviewers also need a public page they can crawl without logging in.
Common rejection wording
- “A2P privacy policy rejected”
- “no sharing phone numbers language”
- “SMS privacy disclosure missing”
- “privacy policy URL 404 10DLC”
Bad vs. better
Weak submission pattern
Our privacy policy says we may share information with partners for marketing and does not mention SMS or mobile phone numbers.
Stronger submission pattern
The public privacy policy explains SMS opt-in data, states that mobile phone numbers collected for SMS are not sold or shared with third parties for their marketing, and links from the same page where consent is captured.
Fix checklist before resubmitting
- Make the privacy policy publicly reachable with a 200 response and no login wall.
- Add SMS-specific language covering how phone numbers and opt-in data are used.
- Include no-sale/no-sharing language for phone numbers collected for SMS marketing.
- Link the policy from the opt-in page and from the business website footer if possible.
- Keep the brand/business name consistent with the campaign and website.
- Do not submit a generic template that contradicts your consent claims.
Related A2PCheck guides
The detailed SMS disclosure checklist.
A policy can be reachable but still inconsistent with the website.
Map the rejection category to the right fix path.
Carriers re-review the whole packet, not just one field.
Dry-run the campaign before your next submission.
Fix the full packet, not just the cited field
A rejection reason is a starting point, not the whole review. Before resubmitting, run the full campaign through the scanner and walk the resubmission checklist. Description, samples, consent, privacy, terms, and URLs should all tell the same story.
Frequently asked questions
What does an A2P 10DLC privacy policy rejection mean?
The privacy URL does not return a public, relevant policy with SMS-specific language and no-sale/no-sharing disclosures for phone numbers collected for messaging.
Can A2PCheck guarantee approval after I fix it?
No. A2PCheck is independent and is not affiliated with Twilio, The Campaign Registry, or any carrier. It catches common readiness issues, but providers and carriers may apply additional review checks.
Should I resubmit after changing only this one field?
Usually no. Carriers re-review the full campaign packet, so fix the cited issue and then re-check the description, samples, opt-in evidence, privacy policy, terms, and website URLs before resubmitting.
Check for privacy policy issues
Paste the campaign packet you plan to submit or resubmit. A2PCheck checks the description, sample messages, opt-in flow, and URLs for common rejection patterns. Free, no signup.