Privacy Policy Missing or Non-compliant

Why This Rejection Happens

The carrier vetting team could not find a compliant Privacy Policy on your website. Either the link is missing, broken (404), or the policy itself is missing the mandatory clause stating that you will not share mobile data with third parties.

• No Privacy Policy link in the website footer.
• Link leads to a "Coming Soon" or "404" page.
• Policy does not explicitly exclude mobile number sharing/selling.
• Policy allows sharing with "affiliates" or "partners" without exception for SMS.

Root Cause Analysis

Primary Triggers

• Data Sharing Loophole: Your policy says "We may share data with marketing partners." This is an instant rejection for 10DLC, as it enables lead generation spam.
• Broken Navigation: The link exists but doesn't work, or the document is a PDF that doesn't load.

Required "No Sharing" Clause

Copy & Paste Compliance Clause

Add this text to the "Information Sharing" or "Third Party Disclosure" section of your Privacy Policy.

Step-by-Step Remediation

Audit Your Policy

Open your website's Privacy Policy. Search for "share", "partner", or "affiliate". If it says you share data for marketing, you must add the exclusion clause.

Make It Visible

Ensure the link is clearly labeled "Privacy Policy" in the footer of your homepage. Do not bury it inside "Terms" or "Legal".

Pre-Resubmission Checklist

• Privacy Policy link is active and not a 404.
• "No sharing for marketing" clause is added.
• Policy is accessible without a login.

Fix It Faster

Generate a compliant privacy policy in minutes.

Need a Compliant Privacy Policy?

Don't risk legal action or rejection. Get a verified policy template today.

What reviewers check for code 805

Code 805 is reported as "Privacy Policy Missing or Non-compliant". 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 805 comes from

Code 805 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 Northline Heating & Air, 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 805 (Privacy Policy Missing or Non-compliant) 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 Northline Heating & Air:

Northline Heating & Air corrected the deficiency reported as code 805 (Privacy Policy Missing or Non-compliant). 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 805 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 851: Privacy Policy Disclosure Missing
• 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 805

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 805?

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

Legal Disclaimer: Privacy policy requirements (Code 805) vary by state. Organizations operating in California, Virginia, Colorado, or other states with comprehensive privacy laws should consult privacy counsel. This tool provides 10DLC compliance support, not legal advice.

© 2025 MyTCRPlus. All rights reserved.