> 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/intellectual-property-review-mechanism-for-app-distribution.md). # Intellectual Property Review Mechanism for App Distribution ### 1. Commitment to Intellectual Property Protection Onside is committed to protecting the intellectual property rights of developers, rights holders, and third parties on the Onside Store in the United States. To that end, Onside operates a manual review process designed to prevent the distribution of apps that infringe copyrights, trademarks, patents, or other proprietary rights. ### 2. Manual Pre-Distribution Intellectual Property Review Process Before an app becomes available on the Onside Store, it passes through the review process described in this Section. ### 3. Submission Requirements Developers must submit a functional description of the app, visual assets (such as screenshots and icons), and a declaration that they own or are authorized to use all content included in the app. Where applicable, developers must provide supporting documentation, such as licenses or permissions, and must agree that their app does not infringe the rights of any third party. ### 4. Initial Intellectual Property Screening Onside conducts an initial manual review to identify obvious intellectual property concerns, including unauthorized use of third-party branding, logos, or other visual elements. Submissions that show clear signs of trademark or copyright infringement, or that impersonate another brand or developer, may be rejected at this stage. ### 5. Detailed Intellectual Property Analysis Apps that pass the initial screening undergo a more detailed review by trained personnel, who compare the app's content and functionality against publicly available trademark and copyright records, assess the developer's originality claims, and review any permissions or licenses submitted. ### 6. Developer Communication and Remediation If a potential issue is identified, Onside notifies the developer with a description of the concern and requests additional documentation or modifications to the app. The app remains unpublished until the issue is resolved to Onside's satisfaction. ### 7. Approval or Rejection Apps that satisfy this review are approved for distribution. Apps that do not are rejected, and Onside provides the developer with the reasons for rejection. ### 8. Ongoing Monitoring and Enforcement After publication, Onside continues to monitor apps for intellectual property compliance through periodic audits and reports from users and rights holders. Suspected infringement is investigated promptly, and Onside may remove or suspend an app if infringement is confirmed. ### 9. Contact Information for Intellectual Property Inquiries Intellectual property inquiries 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/intellectual-property-review-mechanism-for-app-distribution.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.