> 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/account/source-code.md).

# Source code

### Will I get the app source code?

If you’re considering using AppMySite to create your mobile app, you might have questions about the source code. Will you have access to it? Will you be able to modify it? In this guide, we’ll address this question and clarify the policy regarding source code ownership with AppMySite. 

#### Would I have access to my app’s source code?

At AppMySite, we prioritize transparency and customer satisfaction.  We want you to be aware that we do not provide access to the source code of the apps created on AppMySite’s platform.

The source code remains the exclusive property of AppMySite and it is not available for purchase or included in any of our plans.

#### AppMySite's commitment to quality 

While you may not have access to the source code, you can rest assured that AppMySite is committed to delivering high quality fully functional mobile apps. Our platform is designed to be user-friendly, allowing you to create, customize, and launch your app with ease.

Our dedicated customer support is always ready to assist you with any questions or issues you may encounter during your app-building journey. We’re here to help you make the most of our platform and create outstanding apps that meet your needs.

{% hint style="danger" %}
The keystore file (also called the APK secret key or app private key) is part of the app’s source code and cannot be shared, as AppMySite is not an open-source platform.
{% 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.appmysite.com/account/source-code.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.