Why This Rejection Happens
The URL is reachable (returns a 200 OK), but the content on the page is NOT a Privacy Policy. It might be your homepage, a "Contact Us" page, or a Terms of Service page without privacy clauses.
Root Cause Analysis
The Fix
Ensure the URL links directly to a dedicated Privacy Policy document.
✓ Correct Content
A page titled "Privacy Policy" that explicitly mentions how you handle phone numbers and opt-in data.
✗ Incorrect Content
Linking to your homepage (www.brand.com) and hoping they find the policy in the footer.
Generate Compliant Policy
Get a text-perfect privacy policy hosted instantly.
Comprehensive TCR rejection remediation powered by MyTCRPlus.com
What reviewers check for code 7102
Code 7102 is reported as "Privacy Policy Link Invalid". Reviewers click the privacy policy link from your campaign and from the opt-in page. The link has to resolve to a live page on the brand's own domain, over HTTPS, without redirects to the homepage, login walls or PDF downloads that fail on mobile. The page must actually be a privacy policy, and for 10DLC it must contain an SMS clause stating that mobile information is not shared with third parties for marketing.
Where code 7102 comes from
Code 7102 is a campaign review reason code used to report a specific deficiency found during manual campaign vetting. CSPs surface it in the rejection notice alongside any other codes found in the same review, so check for companion codes before resubmitting. It is marked High severity: it blocks approval, but it is fully fixable by correcting the submission and resubmitting.
Required SMS clause for the privacy policy
Compliant version:
Text messaging: Lakeview Residential collects your mobile number only to send the messages you request. 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.
Fix and verify before resubmitting
- Open the privacy URL on a phone in a private window and confirm it returns the policy itself (HTTP 200), not a redirect.
- Use a stable path such as /privacy-policy/ and link the same URL from the opt-in form, SMS terms and footer.
- Add the SMS non-sharing clause near the top of the policy, under a heading such as "Text Messaging".
- Update the campaign's privacy policy field with the exact final URL, including https://.
- Resubmit only after confirming the link works from outside your network (vetting runs from US cloud IPs).
- Resubmit with a note that references code 7102 (Privacy Policy Link Invalid) 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 Lakeview Residential:
Lakeview Residential corrected the deficiency reported as code 7102 (Privacy Policy Link Invalid). Changes made: open the privacy URL on a phone in a private window and confirm it returns the policy itself (HTTP 200), not a redirect; use a stable path such as /privacy-policy/ and link the same URL from the opt-in form, SMS terms and footer; add the SMS non-sharing clause near the top of the policy, under a heading such as "Text Messaging". 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 7102 coming back
- Linking a privacy page hosted on a website builder subdomain instead of the brand domain.
- Leaving the policy as a Google Doc or PDF that some reviewers cannot open.
- Changing the URL after submission without updating the campaign.
Related rejection codes
- Code 7101: Privacy Policy URL Broken
- Code 7100: Privacy Policy URL Missing
- Code 2131: Verbal Script Missing STOP Instructions
- Code 2128: Opt-in Form Missing HELP Instructions
- Code 2127: Verbal Script Missing STOP Instructions
- Code 2126: Opt-in Form Missing STOP Instructions
Frequently asked questions about code 7102
Does code 7102 mean my policy wording is wrong?
Not necessarily. Code 7102 is triggered when the reviewer cannot reach or verify the privacy policy at the URL supplied. Fix the link first, then confirm the policy includes the SMS non-sharing clause so you do not trigger a content-based privacy code on resubmission.
Can I host the privacy policy on my CSP's or a third party's site?
Reviewers expect the policy on the brand's own domain so they can tie it to the registered business. A third-party host is a frequent reason for repeat rejections.