A2P 10DLC SMS Privacy Policy Template (Copy-Paste)

Carriers and The Campaign Registry review the privacy policy you submit with your A2P 10DLC campaign — and reject it when the SMS-specific disclosures are missing. Below is copy-paste language you can adapt, starting with the one clause reviewers look for hardest.

Guidance only — A2PCheck is independent and not affiliated with Twilio, The Campaign Registry, or any carrier, and we can't guarantee approval.

Free — no signup required

Scan your campaign & policy URLs

Paste your campaign details, including your privacy policy URL, and A2PCheck checks whether the policy signals carriers look for are present. Free, no signup.

Independent pre-submission check

No Twilio or TCR submission

Use campaign metadata, not customer PII

Use representative templates and public URLs only. Do not paste real customer phone numbers, customer records, API keys, or internal/signed URLs.

New here? Try a realistic example

Load a complete, carrier-friendly campaign to scan in one click — then tweak it for your own.

Campaign Info

Basic details about your messaging campaign.

Use Case Type *

Business Name

Campaign Description *

0 characters — Too short — describe who opts in, what you send, and how often.

Sample Messages

Provide at least 2 example messages you'll send.

STOP foundHELP foundchecked across your keywords & messages

Opt-In / Message Flow

How users consent to receive your messages.

Message Flow / Opt-In Description *

Consent evidence readiness

Describe where and how subscribers consent — name the opt-in location and the consent language they agree to.

Name the opt-in location (web form, checkout, keyword, QR code, paper form, etc.).
Spell out the consent language — what the subscriber explicitly agrees to.
State the message frequency (e.g. recurring, varies, msgs/month).
Include a "Message and data rates may apply" disclosure.
Link a privacy policy describing how you handle subscriber data.
Clarify that consent isn't a condition of purchase, where that applies.
Capture and retain opt-in evidence (timestamp, source URL, exact consent text/screenshot) for each subscriber.

Guidance only — consent requirements can vary by use case and jurisdiction.

or sign up to run a Full scan

The one clause carriers look for

If your privacy policy says nothing else about SMS, it needs this: an explicit statement that mobile numbers and SMS opt-in consent are not shared with third parties for marketing. Adapt and paste it into your policy.

No mobile information (including phone numbers and SMS opt-in consent) will be sold, rented, or shared with third parties or affiliates for their own marketing or promotional purposes. Text-messaging opt-in data and consent are never shared with any third parties.

Full SMS section template

A complete “SMS / Text Messaging” section you can drop into an existing privacy policy. Replace every [bracketed] placeholder with your real details.

SMS / Text Messaging Program

When you opt in to receive text messages from [Your Business Name], we collect
your mobile phone number and your consent to be contacted by SMS.

How we use it. We use your phone number only to send the messages you opted in
to receive — for example, [appointment reminders / order updates / marketing
offers]. Message frequency varies. Message and data rates may apply.

Sharing. We do not sell, rent, or share your mobile phone number or your SMS
opt-in consent with third parties or affiliates for their own marketing or
promotional purposes. We may share it with service providers that help us send
messages on our behalf (for example, our SMS platform), solely to deliver the
messages you requested.

Your choices. You can opt out at any time by replying STOP to any message. For
help, reply HELP or contact us at [support email / phone]. Opting out of SMS
does not affect your other communications with us.

Contact. Questions about this policy? Contact us at [support email], [address].

What a passing privacy policy includes

An explicit SMS / text-messaging section — not buried inside a generic 'personal information' bucket.
The no-sale / no-sharing-with-third-parties clause for mobile numbers and SMS consent.
How the number is used, message frequency, and that message & data rates may apply.
STOP to opt out and HELP for help, with a real support contact.
Hosted on a public URL on your own domain — reachable without a login.

How to use it

Paste the section into your existing privacy policy, fill in the placeholders, and host it at a public URL you can submit with your campaign. Make sure it matches your opt-in flow and the full privacy policy requirements. If a campaign was already turned down over its policy, see why privacy policies get rejected, then run a free pre-scan before you resubmit.

Frequently asked questions

Does my privacy policy really need to mention SMS specifically?

Yes. Carriers and TCR look for an explicit statement about how you collect and use mobile numbers and SMS consent. A generic 'we value your privacy' policy with no SMS section is one of the most common reasons campaigns are flagged.

Which sentence matters most?

The no-sharing clause: that mobile numbers and SMS opt-in consent are not shared with third parties for their marketing. Reviewers specifically look for this. Missing or weak sharing language is a frequent rejection trigger.

Can I copy this word for word?

Use it as a starting point and adapt it — fill in your business name, contact details, and the message types you actually send. The policy must be true for your business, and carriers cross-check it against your campaign description and opt-in flow.

Where do I host the privacy policy?

On a public URL on your own domain that loads without a login or paywall. A privacy policy that 404s, sits behind a portal, or lives only inside an app is treated as missing during review.

Scan your campaign free Privacy policy requirements