> For the complete documentation index, see [llms.txt](https://docs.reachplatform.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reachplatform.com/customizations-and-bolt-ons/hosted-checkout-landing-pages/landing-page-approval-guide.md).

# Landing Page Approval Guide

Landing page approval requirements for Reach-powered mobile brands, including Broadband Labels, WCAG accessibility, advertising disclosures, carrier references, data privacy, and licensing.

Build compliant, approval-ready landing pages for your Reach-powered mobile brand. These requirements apply when Reach is the carrier of record.

Reach reviews every landing page before launch. Reach also reviews every later change. These guidelines cover landing pages only.

{% hint style="warning" %}
**Legal review required:** This guide is practical orientation, not legal advice. Confirm your obligations with legal counsel.

Your brand remains responsible for all applicable laws and regulations. This includes CAN-SPAM, TCPA, CPNI, and PII requirements. These laws may govern consent before contact and campaign placement or content.
{% endhint %}

### Approval checklist

Review these items before submitting a page to Reach.

{% columns %}
{% column %}

#### Plan and offer

* Show the Broadband Label with every priced plan.
* Support every marketing claim with evidence.
* Disclose offer conditions beside the claim.
  {% endcolumn %}

{% column %}

#### Brand and privacy

* Identify Reach Mobile as the service provider.
* Do not reference the underlying carrier.
* Collect only necessary personal information.
  {% endcolumn %}
  {% endcolumns %}

### Broadband Label requirements

Reach generates a Broadband Label in the format prescribed for mobile services for each plan, with a unique identifier generated by Reach. This label must be used in connection with each plan.

{% hint style="danger" %}
Do not use an icon, link, expandable element, or popup instead of the label. Display the actual Broadband Label beside the associated plan.
{% endhint %}

* **Show the label at point of sale.** Display it anywhere customers view or compare plan pricing.
* **Keep it close to the plan.** Marketing content and the label must remain in close proximity.
* **Keep claims consistent.** Plan advertisements and customer communications must match the corresponding Broadband Label.

You may use the Reach Mobile Broadband Label UI pattern as a design reference.

### Accessibility requirements

Landing pages must comply with the Web Content Accessibility Guidelines (WCAG) 2.1 Level AA, the internationally recognized accessibility standard published by the World Wide Web Consortium (W3C) to ensure websites and digital content are accessible to people with disabilities.

### Advertising and disclosure requirements

The requirements below are examples, not a complete list:

#### Truthful representations

* Keep all advertisements and representations truthful and non-misleading.
* State essential service details clearly and conspicuously near the offer.
* Do not rely only on a click-through disclosure where this is not permitted.

**Clearly and conspicuously** means readily noticeable, readable, understandable, and audible where relevant. Consider the disclosure's size, color, contrast, location, duration, and audibility.

Do not make unsupported claims about 5G Priority Access, network size, U.S.-based support, month-to-month flexibility, customer ratings, or nationwide coverage.

#### No commitments that change Reach's service terms

Do not make any representation, offer, warranty, or guarantee that changes Reach service terms. Obtain advance written approval through a signed agreement before making one.

This includes commitments that change Reach operations, support, policies, billing practices, or contractual terms.

Do not promise service levels, credits, remedies, free trials, benefits, or cancellation rights beyond applicable terms.

#### "Unlimited" plans

Use **unlimited** only where no billing-cycle data quantity limit applies.

Where speed limits apply, place a clear disclaimer next to the unlimited claim. Do not place it only in a footer.

The disclaimer must explain the trigger for throttling and the throttled speed. Sample disclaimer:

> The rate plan provides unlimited data. The first \_\_\_ gigabytes of data in each month will be provided at \_\_\_ speed, or the maximum speed available from the serving cell site. After that and for the remainder of the month, the plan provides unlimited data at a maximum speed of \_\_\_ Megabits per second.

#### Savings claims

Support every savings claim with a reasonable basis. Comparisons with another carrier must use similar goods or services and explain material differences.

For a price, discount, or saving that requires more than purchase alone, clearly disclose:

* All material requirements and conditions.
* Rebate requirements beside the advertised claim.
* The approximate credit issuance timeline.
* Material differences in a non-equivalent comparison.
* Required actions, such as a trade-in, commitment, or automatic payments.

Do not claim “Save $100+ Per Year” or “Save $50 per month” without substantiated evidence.

#### Free and similar offers

For any **free** offer, clearly disclose every material requirement and condition. If the offer requires a purchase, do not increase that purchase price to recover the free item's cost.

### Reach Mobile identification

Reach Mobile is the carrier and merchant/carrier of record for FCC purposes and all subscribers. Subscribers contract directly with Reach Mobile.

Clearly identify Reach Mobile as the service provider on the landing page and in all marketing and collateral materials.

### Underlying carrier restrictions

MNO Marks include the underlying carrier's name, logo, service marks, trademarks, and affiliates' marks. They are protected brand assets.

{% hint style="danger" %}
Market only under your Reach-approved brand. Do not use the underlying carrier's name, logo, slogans, network claims, branding, or imagery.
{% endhint %}

* Do not identify the MNO as your wireless network provider.
* Do not compare your services with the MNO's network.
* Do not suggest MNO responsibility for service or financial obligations.
* MNO employees cannot authorize use of MNO Marks.

Direct or implied use breaches the relevant MNO agreements. Implied use includes phrases such as “America's Largest 5G Network,” and “America's Best Network”

### Data privacy and CPNI

Collect only personally identifiable information (PII) legitimately necessary to enable mobile services. Use it only for activation and service provision.

Additional PII collection or processing requires:

* Compliance with applicable privacy laws.
* Required consent, notices, and disclosures.
* Reach's prior written approval.

### Third-party licenses

License every font, image, logo, and other material used on your landing page.

### Submit for approval

{% hint style="warning" %}
Reach Mobile must approve every landing page, promotional banner, and marketing campaign before public release. Submit all changes for approval before publication.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.reachplatform.com/customizations-and-bolt-ons/hosted-checkout-landing-pages/landing-page-approval-guide.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
