> For the complete documentation index, see [llms.txt](https://docs.tryprotege.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tryprotege.com/review/content-scanning/platforms-supported.md).

# Platforms Supported

Below is a list of platforms supported by Protege Review for compliance monitoring and content evaluation. From social media channels to app store listings, our platform helps ensure compliance remediation and analysis across all major digital spaces to keep your brand compliant and secure.

| Platform                  | Status               |
| ------------------------- | -------------------- |
| Apple App Store Listing   | Supported            |
| Discord                   | Available by Request |
| Facebook                  | Supported            |
| Instagram                 | Supported            |
| Google Play Store Listing | Supported            |
| LinkedIn Company Page     | Supported            |
| Reddit                    | Available by Request |
| TikTok                    | Supported            |
| X                         | Supported            |
| YouTube                   | Supported            |
| 小红书 - Little Red Book     | Available by Request |

#### Note:

* If you would like to inquire adding a new platform, please don't hesitate to contact our support team at <support@tryprotege.com>. We're here to assist you throughout the process.


---

# 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.tryprotege.com/review/content-scanning/platforms-supported.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.
