> For the complete documentation index, see [llms.txt](https://docs.appmysite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmysite.com/frequently-asked-questions/app-features-and-settings/remove-appmysite-branding.md).

# Remove AppMySite branding

### How do I remove AppMySite branding from my app?

Removing AppMySite branding from your app is straightforward and happens automatically when you upgrade to any paid plan. Here’s how it works:

#### **Step 1: Upgrade to a Paid Plan**

* Log in to your AppMySite account.
* Choose any paid plan that suits your needs.
* Complete the payment process to activate your subscription.

{% hint style="success" %}
This feature applies to all paid plans. You don’t need to configure any additional settings to remove the branding.
{% endhint %}

#### **Step 2: Automatic White-Labeling**

* Once your account is upgraded, AppMySite branding is automatically removed from your app.
* Your app becomes white-labelled, meaning there will be no AppMySite branding visible.

#### **Step 3: Publish or Update Your App**

* If your app is already published, update it to reflect the changes.
* For new apps, publish your app to app stores without AppMySite branding.

#### **Step 4: Testing Your App**

* If you are testing your app using the **Preview** feature on the AppMySite dashboard, the launch screen will still show AppMySite branding.
* However, when you test your app using the APK or IPA file or through TestFlight, the AppMySite branding will not appear.
* Publish your app to app stores to deliver a fully white-labeled experience to your app users.

{% hint style="warning" %}
The AppMySite branding appears as “This app was built with AppMySite” in the app header. If you switch back to a free plan, AppMySite branding will be reinstated.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.appmysite.com/frequently-asked-questions/app-features-and-settings/remove-appmysite-branding.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.