> ## Documentation Index
> Fetch the complete documentation index at: https://docs.surge.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Required Disclosures and Opt-In Templates

> The three required SMS disclosures, where to place them, and copy-ready opt-in templates for common use cases.

Carriers require specific disclosures at the point of SMS opt-in. This page lists what's required, where to put it, and templates you can adapt for common use cases.

## The three required disclosures

Every SMS opt-in point must display:

1. **Message frequency**: e.g., "Message frequency varies" or "You'll receive up to 4 messages per month"
2. **Cost notice**: exactly "Msg\&data rates may apply" or "Msg\&data rates apply"
3. **Opt-out instructions**: exactly "Reply STOP to opt out" (STOP is the required keyword)
4. **Help instructions**: exactly "Reply HELP for help"

In addition to the above, the following are required as well:

* Identify the business responsible for the messages
* Explain the purpose of the messages (e.g. account notifications, promotional messages, etc.)
* Link to privacy policy
* Link to terms of service

## Where to put disclosures

Disclosures must appear **at the point of opt-in**: next to or immediately below the phone number field and consent checkbox. They should be readable without scrolling. Burying them in a terms of service page or a footer is insufficient.

The font size should be legible (not 8px gray text). Where possible, reviewers visit your actual website, not just screenshots.

## Canonical compliance message

When you send a first message to a new subscriber, include the full opt-in confirmation:

> "You are now opted in to messages from Acme Corp. Frequency varies. Msg\&data rates apply. Reply STOP to opt out."

Replace "Acme Corp" with your actual brand name, not a placeholder.

## Templates by use case

### Marketing

**Opt-in checkbox label:**

> "I agree to receive promotional text messages from Acme Corp"

**Disclosure text beneath the checkbox:**

> "Message frequency varies. Msg\&data rates apply. Reply STOP to opt out. View our [Privacy Policy](https://acme.com/privacy)."

**Confirmation message:**

> "Acme Corp: You're in! Expect exclusive deals and updates. Msg freq varies. Msg\&data rates apply. Reply STOP to opt out."

<Frame style={{ margin: "24px 0" }}>
  <img src="https://mintcdn.com/surge-67d47b03/ZTF1rPDS0FPWBNB_/images/required-disclosures/direct-account-notification-marketing-shared.png?fit=max&auto=format&n=ZTF1rPDS0FPWBNB_&q=85&s=e774c52fe7d5277b75e8d4bbcc5c8627" alt="Example web form with separate unchecked checkboxes for transactional and marketing text messages" width="200" data-path="images/required-disclosures/direct-account-notification-marketing-shared.png" />
</Frame>

***

### Transactional (account notifications, order updates)

**Opt-in checkbox label:**

> "Send me text message updates about my orders and account"

**Disclosure:**

> "You may receive messages about order status, shipping, and account activity. Message frequency varies. Msg\&data rates apply. Reply STOP to opt out."

**Confirmation message:**

> "Acme Corp: You'll now receive order and account updates by text. Reply STOP to opt out. Msg\&data rates apply."

<Frame style={{ margin: "24px 0" }}>
  <img src="https://mintcdn.com/surge-67d47b03/ZTF1rPDS0FPWBNB_/images/required-disclosures/direct-account-notification-dedicated.png?fit=max&auto=format&n=ZTF1rPDS0FPWBNB_&q=85&s=978dd769c987dad683cc0540fb0b155e" alt="Example dedicated web form for SMS account notifications, with consent granted by submitting the form" width="200" data-path="images/required-disclosures/direct-account-notification-dedicated.png" />
</Frame>

<Frame style={{ margin: "24px 0" }}>
  <img src="https://mintcdn.com/surge-67d47b03/ZTF1rPDS0FPWBNB_/images/required-disclosures/direct-account-notification-shared.png?fit=max&auto=format&n=ZTF1rPDS0FPWBNB_&q=85&s=ce260470e3313fc4dc593b5f0834952b" alt="Example web form where SMS signup shares a form with other fields, using an explicit unchecked checkbox" width="200" data-path="images/required-disclosures/direct-account-notification-shared.png" />
</Frame>

***

### Two-factor authentication

**Opt-in checkbox label:**

> "Use my phone number to receive one-time verification codes"

**Disclosure:**

> "We'll send a verification code each time you sign in. Message frequency: one per login. Msg\&data rates apply. Reply STOP to opt out."

<Frame style={{ margin: "24px 0" }}>
  <img src="https://mintcdn.com/surge-67d47b03/ZTF1rPDS0FPWBNB_/images/required-disclosures/direct-2fa-dedicated.png?fit=max&auto=format&n=ZTF1rPDS0FPWBNB_&q=85&s=cbcd62534d817ee12d636e987403fdc6" alt="Example dedicated web form for phone verification codes" width="200" data-path="images/required-disclosures/direct-2fa-dedicated.png" />
</Frame>

Note: For security-only OTP (where the user only receives verification codes, not marketing), some of these disclosures are less critical, but including them is still best practice.

***

### Customer care

**Opt-in at ticket submission:**

> "Text me updates about my support request"

**Disclosure:**

> "You'll receive updates about your support case by text. Frequency depends on case activity. Msg\&data rates apply. Reply STOP to opt out."

***

## Platform vs direct customer templates

If you're a SaaS platform registering on behalf of clients, the brand name in every message should be the **client's brand**, not your platform's brand. The opt-in checkbox label, disclosure text, and confirmation message should all name the client.

> "I agree to receive text messages from Smith Realty"

— not —

> "I agree to receive text messages from YourPlatform on behalf of Smith Realty"

Reviewers flag brand-in-disclosure mismatches. The message recipient should see one consistent brand name throughout: on the website where they opted in, in the SMS messages they receive, and in the registration you submitted.

<Frame style={{ margin: "24px 0" }}>
  <img src="https://mintcdn.com/surge-67d47b03/ZTF1rPDS0FPWBNB_/images/required-disclosures/platform-account-notification.png?fit=max&auto=format&n=ZTF1rPDS0FPWBNB_&q=85&s=e68602e42168a7677e3fad7fa9deb13a" alt="Example platform-branded web form for account notifications, with 'Powered by PLATFORM' attribution" width="200" data-path="images/required-disclosures/platform-account-notification.png" />
</Frame>

<Frame style={{ margin: "24px 0" }}>
  <img src="https://mintcdn.com/surge-67d47b03/ZTF1rPDS0FPWBNB_/images/required-disclosures/platform-account-notification-marketing.png?fit=max&auto=format&n=ZTF1rPDS0FPWBNB_&q=85&s=d34730e4276e9617e5038b5804bd3d95" alt="Example platform-branded web form with separate checkboxes for account notifications and marketing" width="200" data-path="images/required-disclosures/platform-account-notification-marketing.png" />
</Frame>

<Frame style={{ margin: "24px 0" }}>
  <img src="https://mintcdn.com/surge-67d47b03/ZTF1rPDS0FPWBNB_/images/required-disclosures/platform-customer-care.png?fit=max&auto=format&n=ZTF1rPDS0FPWBNB_&q=85&s=8881bd653bc67c56fee4dffc2eda8e15" alt="Example platform-branded web form for customer care text messages" width="200" data-path="images/required-disclosures/platform-customer-care.png" />
</Frame>

<Frame style={{ margin: "24px 0" }}>
  <img src="https://mintcdn.com/surge-67d47b03/ZTF1rPDS0FPWBNB_/images/required-disclosures/platform-customer-care-marketing.png?fit=max&auto=format&n=ZTF1rPDS0FPWBNB_&q=85&s=ac283ca3f425b2061dbeff4a2336b5f7" alt="Example platform-branded web form for customer care with an additional marketing checkbox" width="200" data-path="images/required-disclosures/platform-customer-care-marketing.png" />
</Frame>

## Privacy policy requirements

Your privacy policy should ideally state that you collect phone numbers for SMS communication and describe how you use them. The first section should not imply that agreeing to the policy constitutes SMS consent — that's a common rejection cause.

The main thing the carriers look for in the privacy policy is making sure that SMS consent won't be shared with third parties for things like lead generation and affiliate marketing. Whenever any data will be shared with third parties, we recommend adding the following line to the privacy policy to guarantee this: "All the above categories exclude text messaging originator opt-in data and consent; this information will not be shared with any third parties."

Minimum language to include in your privacy policy:

> "We collect your phone number to send you \[describe use cases]. You may opt out at any time by replying STOP to any text message from us."

### Sample privacy policy template

This is the SMS consent privacy policy template Surge provides to customers as a starting point. Customize it to fit your needs and make sure it accurately reflects your business practices. You can also have it live as a separate "SMS Privacy Policy" that links from your primary policy, so the SMS-specific language is easy for reviewers to find.

```markdown theme={null}
# PRIVACY POLICY

Effective Date: {{effective_date}}

We value your privacy and make every effort to respect your wishes and personal
information. Please read this policy carefully to understand how we collect,
use, and manage your phone numbers.

## COLLECTION OF PHONE NUMBERS

We collect your phone numbers only when you voluntarily provide them to us, for
example, during transactions, inquiries, or when you sign up to receive
notification messages. You can opt in to receive these SMS messages by providing
your phone number.

## USE OF PHONE NUMBERS FOR SMS

SMS messaging charges may be applied by your carrier. We will only share your
phone number with our SMS provider, subject to their privacy policy.

## OPTING OUT OF MESSAGES

If at any time you wish to stop receiving messages from us, you can opt out by
texting STOP.

## PRIVACY OF PHONE NUMBERS

Once you have opted out, we will not send you any more SMS messages, nor will we
sell or transfer your phone number to another party.

## CHANGES TO THIS POLICY

We may periodically update this policy. We will notify you about significant
changes in the way we treat your information by placing a prominent notice on
our site.

We thank you for your understanding and cooperation. If you have any questions
or concerns about this policy, please feel free to contact us via the form on
our site.
```
