Every 10DLC registration needs to include both a privacy policy and terms of service, and they need to meet specific requirements that protect your business and keep you compliant with industry standards. Both are required for approval.

NOT LEGAL ADVICE

This document serves to provide information related to the United States Application-to-Person 10 Digit Long Code (US A2P 10DLC) registration requirements. See Twilio’s Guidelines for sending SMS messages in the US for more information.

Compliance Requirements
Templates

Compliance Requirements

Privacy Policy

In your privacy policy, our carrier partner checks for language that makes it clear that Messaging Consent data isn't being shared, sold, or bought.

Must be publicly accessible.
Must be linked in your SMS Consent Question.
A compliant Privacy Policy must state that no mobile information will be shared with third parties/affiliates for marketing/promotional purposes. Information sharing to subcontractors in support services, such as customer service is permitted.
If the Privacy Policy does mention that information will be shared with third parties, the following disclaimer must be added under the sharing of information section:

"All the above categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties, excluding aggregators and providers of the Text Message services.

Text messaging originator opt-in data and consent will not be shared with any third parties, excluding aggregators and providers of the Text Message services.”

Terms of Service

Must be publicly accessible.
Must be linked in your SMS Consent Question.
A compliant Terms of Service must include all required messaging program details:
1. Program or brand name
2. Program description
3. “Message and data rates may apply” disclosure
4. Message frequency (or recurring message) disclosure; I.e. “Message frequency may vary”
5. Candidate support contact information
6. Complete opt-out instructions (HELP and STOP), displayed in bold
7. Link to the privacy policy
8. Disclosure that explicitly states "Carriers are not liable for any delayed or undelivered messages"
9. Create a specific section for SMS/messaging if not already present

Note: The Privacy Policy and Terms of Service can be on the same page if there are clear headers showing distinction between each item.

SMS Consent Question (Opt-In / Call-to-Action)

Application Opt-in form, also known as CTA (Call-to-Action), is the place where end-users provide their phone number and consent to receive SMS from a business; I.e. Job Application Form.

Please ensure that the SMS Consent application question contains the following:

Company name	Legal name or DBA of the end-user who will send the messages.
Fee disclosure	“Message and data rates may apply”
Message frequency	“Message frequency varies”. If it is exact, they should say something like “X Msg/Month”
Instructions to opt-out and get help	Reply HELP for help, or STOP to opt-out.
Privacy Policy	Link to Privacy Policy
Terms of Service	Link to Terms of Service
Program description	Types of messages you’ll is going to send (e.g., transactional, conversational, promotional, etc.) - this is also known as the “purpose” of the opt-in flow/CTA.
SMS consent must be optional	Consent for SMS messaging must always be optional and cannot be bundled with consent for any other service or communication method.
No pre-selected SMS consent answers	SMS opt-in questions must never be pre-selected with “Yes”. Pre-determining this field constitutes forced consent and is not compliant with regulations.