ERROR 7103 & 9108 FIX

Fix RingCentral Rejection: Sharing Clause Missing

Rejected for "Non-Compliant Privacy Policy"? Carriers require specific language about third-party sharing. Copy our approved clause to fix Error 7103 and 9108 instantly.

Copy Required Clause Generate Full Policy
AT&T Compliant RingCentral Verified 5-Min Fix

Understanding Privacy Policy Rejections

RingCentral and TCR scrutinize your privacy policy for one specific vulnerability: the sharing of mobile data. Even if you state "We don't sell data," carriers require explicit language confirming that SMS consent is not shared with affiliates or third parties for their own marketing.

Rejection Reason Privacy Policy Sharing Clause Missing
Error Codes 7103, 9108, 5010
Campaign Impact Blocked / Suspended

Why This Happens

Generic privacy policies generated by tools like Termly or standard legal templates often include broad clauses allowing data sharing with "partners" or "affiliates." Carriers flag this because it could allow a lead generator to sell a consumer's phone number to 50 other companies, violating TCPA consent rules.

How to Fix the Error

Add the following specific clause to your Privacy Policy under the "Information Sharing" or "Third Parties" section. This exact phrasing satisfies AT&T and RingCentral requirements.

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

    Update Your Website

    Edit your live Privacy Policy page. Paste the clause above prominently. Ensure the page is publicly accessible (no password required).

  2. 2

    Update RingCentral Profile

    Go to your 10DLC registration in RingCentral. Verify the URL points directly to your updated Privacy Policy.

  3. 3

    Resubmit Campaign

    Resubmit for verification. The vetting partner will detect the compliant language and approve the policy check.

Technical Requirements

Beyond the specific clause, your privacy policy must meet these technical standards to pass automated and manual review:

Accessibility

  • Direct Link: URL must lead directly to the policy, not a homepage requiring navigation.
  • No PDF: Policy should be HTML text on a webpage, not a downloadable PDF file.

Content

  • Business Name: Policy must clearly state it belongs to the registered brand entity.
  • Contact Info: Must include a way to contact the business (email or phone).

Don't Have a Privacy Policy?

Download our complete, pre-validated Privacy Policy template that includes all required SMS disclosures, data retention policies, and sharing clauses.

Download Full Template

Frequently Asked Questions

Can I just say "We don't sell data"?
No. "Selling" and "Sharing" are distinct. You must explicitly state that mobile information will not be SHARED with third parties/affiliates for marketing purposes.
What if I actually DO share data?
If you share SMS consent data with third parties for their marketing, your campaign will be permanently rejected. 10DLC rules strictly prohibit sharing opt-in consent.
Does this apply to Sole Proprietors?
Yes. All brand types, including Sole Proprietors, must have a compliant privacy policy if they are collecting data for SMS.

Related Resources

Full Privacy Template

Download the complete policy document.

Download

Consent Generator

Create compliant opt-in language instantly.

Use Tool

TCR Rejection Codes

Lookup other potential registration errors.

Browse Database

Legal Disclaimer: This content provides general compliance guidance for RingCentral TCR requirements and does not constitute legal advice. Regulatory requirements vary by jurisdiction. Organizations should consult qualified legal counsel to verify privacy policy compliance with applicable federal and state regulations (TCPA, CTIA, GDPR, CCPA). MyTCRPlus does not provide legal advisory services.