Privacy Policy Disclosure Missing

Why This Rejection Happens

Unlike Code 30908 (Missing Policy), Code 851 usually indicates the policy exists but lacks specific disclosures required for SMS compliance. Carriers require you to explicitly state that you collect "mobile phone numbers" and use them for "SMS/text messaging." Generic terms like "contact information" or "communications" are insufficient.

Compliance Gap Analysis

A standard "GDPR" or "CCPA" privacy policy often groups all contact data together. For 10DLC carriers, this is a red flag. They need to see a distinct acknowledgment that phone numbers are being collected specifically for text messaging purposes.

Missing Elements Checklist

• Failure to list "mobile phone number" as a specific category of collected data
• No explanation of how mobile numbers are used (e.g., "for account alerts" or "for promotional offers")
• Missing contact information for users to exercise privacy rights
• Omission of data retention periods for SMS consent records

How to Fix Code 851

1. Update "Information We Collect" Section

   Edit your privacy policy to explicitly list mobile phone numbers as a collected data point.

   Recommended Language

   "We collect information you provide directly to us, such as your name, email address, and mobile phone number when you sign up for our text messaging program."
2. Update "How We Use Information" Section

   Clearly define the purpose of SMS messaging. Avoid vague terms like "to contact you."

   Recommended Language

   "We use your mobile phone number to send you account notifications, order updates, and promotional offers (if you have opted in). We do not share your mobile phone number with third parties for their marketing purposes."
3. Verify Security & Retention

   Ensure your policy includes a statement about data security and how long you retain consent records (typically 4 years for TCPA compliance).

Carrier Nuances

T-Mobile & AT&T

Strictly enforce the distinction between "contact info" and "mobile numbers." If your policy groups them, it will likely be rejected again.

Verizon

Looks for data sharing disclosures. Even if you fix the "Disclosure Missing" (851), ensure you also include the "No Sharing" clause to avoid triggering code 7103.

Fix It Fast

Generate a complete, compliant privacy policy in minutes.

Comprehensive TCR rejection remediation powered by MyTCRPlus.com

What reviewers check for code 851

Code 851 is reported as "Privacy Policy Disclosure Missing". Reviewers need a publicly accessible privacy policy on the brand's website that explains data collection and contains the SMS non-sharing clause, and the opt-in point must link to it. A missing policy, a policy that does not mention SMS, or an opt-in with no privacy link fails this check.

Where code 851 comes from

Code 851 is a vetting rejection reason applied during brand or campaign review and passed back to you by your CSP. It identifies the specific deficiency the reviewer found, so fixing exactly that item is the fastest route to approval. It is marked High severity: it blocks approval, but it is fully fixable by correcting the submission and resubmitting.

Minimum SMS section for the policy

Compliant version:

SMS messaging. If you opt in to texts from Motion Works PT, we use your number only to send the messages you requested. Message frequency varies. Msg & data rates may apply. Reply STOP to opt out or HELP for help. We do not share or sell mobile numbers or SMS consent to third parties for marketing.

Fix and verify before resubmitting

1. Publish a privacy policy page on the brand domain and link it from the site footer.
2. Include sections on data collected, use, retention, sharing, consumer rights and contact details.
3. Add the SMS clause: no mobile information is shared with third parties or affiliates for marketing.
4. Link the policy directly from the SMS opt-in form, next to the consent text.
5. Enter the policy URL in the campaign and attach a screenshot if the opt-in is not public.
6. Resubmit with a note that references code 851 (Privacy Policy Disclosure Missing) and lists each change made.

Sample resubmission note

Many CSPs let you add a note for the reviewer when you resubmit. A short, specific note shows what changed and speeds up the second review. Example for Motion Works PT:

Motion Works PT corrected the deficiency reported as code 851 (Privacy Policy Disclosure Missing). Changes made: publish a privacy policy page on the brand domain and link it from the site footer; include sections on data collected, use, retention, sharing, consumer rights and contact details; add the SMS clause: no mobile information is shared with third parties or affiliates for marketing. All URLs, keywords and auto-replies were re-tested from an external network before this resubmission, and the campaign text now matches the live opt-in exactly.

Common mistakes that keep code 851 coming back

• Using a template that never mentions text messages.
• Linking the policy in the footer but not at the opt-in point.
• Publishing the policy only inside a logged-in customer portal.

Related rejection codes

• Code 809: Privacy Policy Attachment Missing
• Code 805: Privacy Policy Missing or Non-compliant
• Code 30908: Privacy Policy Missing or Non-compliant
• Code 2131: Verbal Script Missing STOP Instructions
• Code 2128: Opt-in Form Missing HELP Instructions
• Code 2127: Verbal Script Missing STOP Instructions

Frequently asked questions about code 851

Do sole proprietors and small businesses need a full privacy policy?

Yes. Every 10DLC campaign that collects phone numbers must link a policy. It can be short, but it must exist publicly and include the SMS clause.

Does a policy generator satisfy code 851?

It can, if you edit it to include the SMS non-sharing clause and remove any marketing-partner sharing language.