30908: Campaign vetting rejection - Compliant Privacy Policy Required

Your A2P 10DLC campaign submission was rejected during vetting because the privacy policy in your registration could not be verified as compliant. This usually means the privacy policy was missing from the website or message_flow, contained conflicting information, or did not include the required statement that mobile information and messaging consent are not shared with third parties or affiliates for marketing or promotional purposes.

• Your campaign registration request does not include a PrivacyPolicyUrl. This field is required for all new A2P 10DLC campaign submissions.
• A compliant privacy policy was not found on the website you submitted or in the message_flow details.
• Your registration points to multiple privacy policies or inconsistent policy content, which prevents review from confirming which policy applies.
• Your privacy policy says mobile information, opt-in data, or consent data is shared, sold, or otherwise provided to third parties or affiliates for marketing or promotional purposes.
• Your privacy policy does not clearly explain what data you collect and how you use it for messaging.
• Your website-based opt-in flow is missing required messaging disclosures in the privacy policy, such as message frequency or the "message and data rates may apply" disclosure.

• Add a PrivacyPolicyUrl to your campaign registration request. The URL must be publicly accessible, not behind a login, and point to a privacy policy relevant to your registered brand.
• Add a publicly accessible privacy policy to the website used in your campaign registration and include the direct policy link in your message_flow. If you register through the API, provide the same public URL in PrivacyPolicyUrl.
• Update the privacy policy so it clearly states that mobile information and messaging consent are not shared with third parties or affiliates for marketing or promotional purposes.
• Make sure the privacy policy explains what customer data you collect and how that data is used in your messaging program.
• If your opt-in flow happens on a website, include the required messaging disclosures in the privacy policy, including message frequency and "message and data rates may apply."
• Remove duplicate or conflicting privacy policies so reviewers can verify one clear policy for the registered brand and campaign.
• After you update the privacy policy and registration details, resubmit the campaign for review in Console or retry the campaign submission through the API.

• A2P 10DLC - Gather the Required Business Information
• Troubleshooting and rectifying A2P Campaigns
• A2P 10DLC Campaign Approval Best Practices