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

> ## Agent Instructions
> Use Stable documentation by default. Honor an explicit Beta request or a URL under /docs/beta/. If the requested version conflicts with the installed CLI package or API origin, clarify the target before writing integration code.
> Pages under /docs/beta/ document Beta; other product pages document Stable. Keep the CLI package, commands, API origin, and credentials within the selected version. State the documentation version in your answer.
> For MCP search, always pass version: Stable or version: Beta. Unfiltered search mixes both versions. For filesystem reads, keep Beta queries under /beta/ and exclude /beta/ from Stable queries; discover paths before reading them.
> The public docs base is https://photon.codes/docs. Convert MCP page paths to public URLs under that base, preserving /beta/ when present. Read https://photon.codes/docs/skill.md for version selection and https://photon.codes/docs/llms.txt for the version indexes.

# Privacy policy and terms for 10DLC

> Add the SMS privacy statement that 10DLC reviewers require, and keep your terms consistent with how people opt in and out.

Reviewers open the privacy policy and the terms that you enter under
**Policies** on the campaign. They check that both pages protect the phone
numbers and the consent that you collect.

## Privacy policy requirements

* **The brand's own policy:** the privacy policy must belong to the registered
  brand. Reviewers don't accept the policy of a platform or reseller, or a
  generic policy such as Google's, in place of the brand's policy.
* **No selling or sharing:** the policy must say that mobile information and
  SMS consent are not sold or shared with third parties for marketing or
  promotional purposes. "We don't sell your data" is not enough, because
  sharing without a sale, for example with affiliates, is also prohibited.
* **No exceptions elsewhere:** no other section can allow personal information,
  including phone numbers, to be shared with third parties or affiliates for
  marketing, lead generation, or third-party analytics. If a section allows
  this kind of sharing, state that SMS data is excluded from it.
* **Easy to find:** link to the policy from the opt-in form, or show the
  statement on the form itself.

### Statement to add

At minimum, add this sentence to the privacy policy:

```text wrap theme={null}
Mobile information will not be sold or shared with third parties for promotional or marketing purposes.
```

Reviewers prefer a fuller statement, especially if your policy has a section on
sharing personal information:

```text wrap theme={null}
SMS opt-in data and consent are excluded from all of the sharing described above. We will not share this information with any third parties. We will not share your opt-in to an SMS campaign with any third party for purposes unrelated to providing you with the services of that campaign. We may share your personal data, including your SMS opt-in or consent status, with third parties that help us provide our messaging services, including platform providers, phone carriers, and other vendors that help deliver text messages.
```

## Terms requirements

* **Consistent with the privacy policy:** the terms can't say that end-user
  information will be shared.
* **Describe the SMS program:** say what messages people will receive, how often,
  that message and data rates may apply, and how to get help.
* **Opt out by reply:** say that people opt out by replying STOP to the number
  that texts them. An opt-out through another number, such as a short code, is
  not accepted.
* **Consistent with the opt-in:** the terms must match the consent text on the
  opt-in form and the description in **How people opt in and out**.

### Example SMS terms

```text wrap theme={null}
SMS terms. When you opt in, Example Co sends you order updates and delivery alerts by text. Message frequency may vary. Message and data rates may apply. To stop receiving texts, reply STOP to any message from us. For help, reply HELP or email support@example.com. Carriers are not liable for delayed or undelivered messages. We do not sell or share your mobile information with third parties for promotional or marketing purposes. See our Privacy Policy at https://example.com/privacy.
```

## Where to enter the pages

Enter the URLs of your **Privacy policy** and **Terms & conditions** under
**Policies** when you register the campaign. To change them after a
rejection, select **Edit the campaign** on the campaign page. Link to the same
pages from your opt-in form.

Both pages must be public, must open without a sign-in, and must be the live
version that contains the statements above.

## Common mistakes

| Mistake | How to fix it |
| - | - |
| The policy belongs to your platform, not to the brand | Publish a privacy policy on the brand's own website. |
| The policy only says that data is not sold | Add that mobile information is also not shared for marketing. |
| A sharing section includes phone numbers and lists advertising or marketing partners | State that SMS data and consent are excluded from that sharing. |
| The terms describe opting out through another number | Say that people reply STOP to the number that texts them. |
| A link is broken or needs a sign-in | Use a public URL, and test it in a private browser window. |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.