> For the complete documentation index, see [llms.txt](https://docs.onside.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onside.io/store/onside-rules-and-policies-united-states/app-marketplace-guidelines.md). # App Marketplace Guidelines ### 1. Compliance With Laws and Regulations All apps distributed through the Onside Store in the United States must comply with applicable U.S. federal and state laws, as well as the laws of any other jurisdiction in which the app is made available, including laws governing data protection, consumer protection, intellectual property, and content standards. Apps may not facilitate illegal activity, including the sale of illegal substances, fraud, harassment, human trafficking, or copyright infringement. ### 2. Intellectual Property Protection Developers must respect the intellectual property rights of others and must not use third-party trademarks, copyrighted material, or patented technology without authorization. Developers must respond promptly to intellectual property claims raised through Onside's Intellectual Property Review Mechanism or Intellectual Property Dispute Resolution Policy. Failure to comply may result in suspension or removal of the app from the Onside Store. ### 3. Fraudulent and Malicious Behavior Apps may not engage in deceptive practices, including false or misleading descriptions, manipulated ratings or reviews, or impersonation of other apps, brands, or individuals. Apps must be free of malware, spyware, or other code designed to damage, disrupt, or gain unauthorized access to a user's device or data. Apps must handle user data transparently and obtain appropriate consent before collecting or sharing it. ### 4. Monitoring and Enforcement Onside uses a combination of automated tools and manual review to monitor compliance with these Guidelines, and investigates apps flagged through user reports. Developers remain responsible for their app's compliance throughout its lifecycle on the Onside Store, and violations may result in suspension, removal, or termination of the developer's account. ### 5. Quality and Accuracy Standards Apps must function reliably as described and must not be intentionally incomplete, unstable, or misleading about their functionality. App descriptions, screenshots, pricing, and other metadata must be accurate and not deceptive. User interfaces should be appropriate for the app's stated audience. ### 6. Review and Appeals Process Apps submitted to the Onside Store undergo a compliance review before and after publication. A developer who disagrees with a rejection, suspension, or removal decision may appeal by contacting Onside through the designated support channel and providing additional information for reconsideration. ### 7. Contact Information Questions about these Guidelines may be directed to or to Onside.io Inc., 1712 Pioneer Ave Ste 500, Cheyenne, Wyoming, US 82001-4406.
--- # 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.onside.io/store/onside-rules-and-policies-united-states/app-marketplace-guidelines.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.