Privacy Policy Allows Sharing

Why This Rejection Happens

Carriers have a strict rule: Opt-in data cannot be sold or shared with third parties for marketing purposes. Code 7103 triggers when your privacy policy states that you share, sell, or rent data to "affiliates," "partners," or "third parties" without an explicit exception for mobile messaging data.

Root Cause Analysis

Automated keywords scanners and manual reviewers look for phrases like "marketing partners" or "share with affiliates." Even if you don't actually share phone numbers, if the legal text *allows* it, the campaign will be blocked.

Specific Triggers

• "We share your personal information with third-party partners for their marketing purposes."
• "Data may be sold to affiliates."
• Missing a "No Mobile Information Sharing" clause in the "How We Share Information" section.

How to Fix Your Privacy Policy

1. Locate the "Sharing of Information" Section

   Find where your policy discusses sharing data with third parties, affiliates, or partners.

2. Add the "No Mobile Sharing" Clause

   You must explicitly state that mobile text messaging originator opt-in data and consent will not be shared. Use this exact text:

   No mobile information will be shared with third parties/affiliates for marketing/promotional purposes. All other categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties.

3. Publish and Resubmit

   Update the live webpage. Ensure the URL remains the same. Resubmit your campaign referencing the updated policy.

Need a Policy Template?

Use our generator to create a compliant privacy policy instantly.

Comprehensive TCR rejection remediation powered by MyTCRPlus.com

What reviewers check for code 7103

Code 7103 is reported as "Privacy Policy Allows Sharing". Reviewers read the privacy policy for any language allowing the business to share, sell or rent personal information, including phone numbers, to third parties for their marketing. Carriers prohibit sharing SMS opt-in data, so a general data-sharing clause without an SMS exception causes rejection even if you never actually share numbers.

Where code 7103 comes from

Code 7103 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 has a documented fix that usually needs one targeted correction and a resubmission.

Exclusion clause to add

Rejected:

We may share your information with our partners and affiliates for marketing purposes.

Approved:

We may share information with service providers that help us operate our business. All the above categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties.

Fix and verify before resubmitting

1. Search the policy for "share", "sell", "partners", "affiliates" and "third parties".
2. Add an explicit exclusion stating that mobile numbers and SMS consent are never shared for marketing.
3. Keep sharing with service providers (such as your messaging platform) limited to delivering the service.
4. Place the SMS clause where reviewers will find it, under its own heading.
5. Make sure the SMS terms link to the updated policy.
6. Resubmit with a note that references code 7103 (Privacy Policy Allows Sharing) 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 7103 (Privacy Policy Allows Sharing). Changes made: search the policy for "share", "sell", "partners", "affiliates" and "third parties"; add an explicit exclusion stating that mobile numbers and SMS consent are never shared for marketing; keep sharing with service providers (such as your messaging platform) limited to delivering the service. 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 7103 coming back

• Adding the SMS clause but leaving a contradictory "we may sell your data" sentence elsewhere.
• Using a generic policy generator that includes broad marketing-partner sharing.
• Updating the policy on one page while the campaign links an older copy.

Related rejection codes

• 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
• Code 2124: Verbal Script Missing Frequency Disclosure
• Code 2123: Verbal Script Missing Message Type

Frequently asked questions about code 7103

We never share phone numbers. Why was code 7103 applied?

Reviewers judge the written policy, not your practice. If the policy permits sharing, the campaign fails until the text excludes SMS data.

Is sharing with our SMS platform allowed?

Yes. Sharing with vendors that deliver the service is acceptable; the prohibition covers third parties using the data for their own marketing.