> 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/publishing-and-distribution/app-store-compliance.md). # App Store compliance ### Are the apps built on AppMySite App Store compliant? Yes, apps built on AppMySite are designed to meet the technical and structural requirements of both the Google Play Store and the Apple App Store. The builds are carefully engineered to align with the latest submission standards set by these platforms, and the system is regularly updated to stay compliant with any changes in guidelines. Our apps are also fully compliant with the latest Google APIs and Apple’s requirements, ensuring that your builds remain up to date with evolving platform standards. While AppMySite ensures your app is technically prepared for submission, approval ultimately depends on meeting each app store’s specific content, design, and policy requirements. This includes adhering to rules related to app functionality, user experience, and data practices, which must be handled during the submission process. {% hint style="warning" %} Apps built with AppMySite meet the technical requirements for Google Play Store and Apple App Store approval. However, compliance with additional guidelines on app content, functionality, and user experience needs to be set up during submission. {% 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/frequently-asked-questions/publishing-and-distribution/app-store-compliance.md?ask=&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.