If your software platform enables businesses to send text messages via 10DLC (10-Digit Long Code), ensuring your customers have a properly written and accessible Privacy Policy is a critical part of maintaining compliance.

Mobile carriers, The Campaign Registry (TCR), and the CTIA all require Brands — meaning your customers — to disclose how they collect, use, and protect consumer data through a Privacy Policy. Without it, Campaign registration delays, rejections, or even service disruptions are increasingly likely.

In this post, we’ll explain why Privacy Policies matter for 10DLC compliance, what your customers' policies must include, and how you can help them get it right.

Why a Privacy Policy Matters for 10DLC

As the software provider, you play an important role in guiding your customers through compliance — and a Privacy Policy is one of the first checkpoints.

Under CTIA guidelines and mobile carrier standards, all Brands (your customers) must maintain an up-to-date Privacy Policy that outlines their data practices related to messaging.
Without a valid Privacy Policy, a Brand’s Campaign may be delayed, rejected, or flagged for non-compliance — causing potential churn or dissatisfaction with your platform.

A proper Privacy Policy:

• Builds trust between your customers and their end users
• Satisfies TCR and carrier registration requirements
• Helps avoid fines, disruptions, and escalations with mobile carriers

What Your Customers’ Privacy Policies Must Include

Your customers’ Privacy Policies don’t have to be complicated — but they do need to cover specific points to meet 10DLC standards:

• What data they collect (e.g., phone numbers, names, message contents)
• How they use that data (e.g., appointment reminders, shipping notifications, promotions)
• If they share data with third parties, and for what purposes
• Clear opt-out mechanisms for users who no longer wish to receive messages
• Data security practices to protect consumer information
• Contact information for privacy-related inquiries
  
  

Important: The Privacy Policy must specifically mention SMS/text messaging activities — not just web or app data collection.

How to Guide Customers to Link Their Privacy Policy Properly

When registering 10DLC Campaigns, customers must provide a direct link to their Privacy Policy.

You should ensure your customers:

• Display the Privacy Policy link prominently on their website (typically in the footer)
• Provide a live, functional URL (no “coming soon” placeholders)
• Use HTTPS formatting (secure connection)
• Link to it during any user opt-in flows (e.g., signup forms where users agree to receive text messages)

During Campaign vetting, DCAs will manually review the link provided — if it's broken, missing, or inadequate, the Campaign will likely be rejected until fixed.

Common Privacy Policy Mistakes to Watch For

• Missing, broken, or placeholder links
• Terms of Service submitted without a distinct Privacy Policy
• Policies that only address web cookies or browsing data, but omit SMS

How Telgorithm Supports You

At Telgorithm, we specialize in helping software providers deliver fully compliant 10DLC messaging experiences to their customers.

We offer:

• Hands-on Campaign reviews before carrier submission
• Guidance on Privacy Policy expectations during onboarding
• Resources and support to help your team educate your customers
  
  

Helping your customers build compliant messaging programs starts with the basics — and a solid Privacy Policy is one of them. 

Experience our level of compliance guidance firsthand by booking a free 10DLC consultation today — we’ll review 1 of your most challenging Campaigns for free and can help get DCA approval in 48 hours or less.  

‍