> 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/governmental-and-legal-compliance-policy-for-app-takedown-requests.md).
# Governmental and Legal Compliance Policy for App Takedown Requests
### 1. Handling Governmental and Other App Takedown Requests
Onside maintains structured procedures for handling requests to remove or restrict apps on the Onside Store in the United States, whether based on legal requirements, intellectual property claims, or violations of Onside's own policies. Onside.io Inc. is responsible for reviewing and acting on such requests.
### 2. Takedown Requests Based on Illegality or Legal Requirements
Where a government authority, regulator, law enforcement agency, or court submits a request asserting that an app violates applicable law, Onside will acknowledge the request, take reasonable steps to verify its authenticity, and may temporarily disable access to the app pending review. If the claimed violation is confirmed, Onside will remove the app. Onside cooperates with valid legal process and will notify the affected developer unless prohibited from doing so by law (for example, by a court order or a non-disclosure requirement accompanying legal process).
Onside has zero tolerance for child sexual abuse material and will remove such content immediately upon discovery and report it to the National Center for Missing & Exploited Children (NCMEC) and, where appropriate, law enforcement, consistent with 18 U.S.C. ยง 2258A.
### 3. Takedown Requests Based on Intellectual Property Violations
Requests alleging intellectual property infringement are handled through Onside's Intellectual Property Review Mechanism and Intellectual Property Dispute Resolution Policy for the United States, including the DMCA notice-and-counter-notice process described there. Onside notifies affected developers of such claims and provides an opportunity to respond before taking permanent action.
### 4. Takedown Requests Based on Violation of Marketplace Terms or Policies
Where Onside identifies, or is notified of, a suspected violation of the Onside Store's Terms of Use or Rules and Policies, Onside will assess the app against the applicable policy, notify the developer with an opportunity to respond, and may temporarily suspend the app pending review. If a violation is confirmed, Onside will take appropriate action, up to and including permanent removal, and will notify the relevant parties of the outcome.
### 5. Temporary Measures and Proportionality
Onside calibrates its enforcement actions to the severity of the alleged violation, the urgency of the request, and the potential for harm to users, developers, or rights holders. Temporary suspension may be used as an interim measure while a request or claim is under review.
### 6. Required Information for Takedown Requests
To be processed, a takedown request should identify the specific app at issue, state the legal or policy basis for the request, provide the requester's contact information, and include a good-faith statement affirming the accuracy of the information provided. Onside may decline to act on requests that do not include this information or that Onside cannot verify.
### 7. Contact Information for Takedown Requests
Takedown requests may be submitted to or by mail 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/governmental-and-legal-compliance-policy-for-app-takedown-requests.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.