> For the complete documentation index, see [llms.txt](https://wiki.crosswatch.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.crosswatch.app/related-information/disclaimer.md).

# Disclaimer

Project status, security guidance, legal disclaimer, and support expectations.

### Project status

CrossWatch is in active development. Things can break between releases.

{% hint style="warning" %}
Back up before experiments.
{% endhint %}

### Disclaimer

CrossWatch is an independent community project. It is not affiliated with, endorsed by, or sponsored by Plex, Emby, Jellyfin, Trakt, SIMKL, TMDb, Tautulli, AniList, MDBList, or PublicMetaDB.

CrossWatch uses the AniBridge mappings dataset to translate media identifiers between AniList and providers such as TMDb, TVDB, IMDb, MyAnimeList, and AniDB.

All product names, logos, and brands belong to their respective owners. They are used for identification only.

Third-party APIs have their own rules. Use them without getting yourself banned.

{% hint style="warning" %}
I do my best to keep syncing safe. Syncing can still cause data loss.

Deletes are the riskiest operation. A bad match can remove the wrong item.

Use Dry Run first. Start one-way. Enable delete propagation only after clean runs.
{% endhint %}

This software is provided "as is", without warranties. Backups still beat regret.

### Security

**Do not expose CrossWatch directly to the public internet!**

CrossWatch is intended for LAN/VPN use and may contain security weaknesses.

Putting CrossWatch on the public internet turns it into a target for automated scanners and real attackers. If there are any weaknesses, common ones in self-hosted apps include auth bypasses, weak session handling, missing rate limits, insecure defaults, outdated dependencies, or simple bugs, an attacker can use them to:

* **Get unauthorized access** to the UI and any data it can reach.
* **Steal credentials/tokens** if traffic isn’t properly encrypted end-to-end.
* **Abuse the service** (brute-force logins, spam requests, DoS) if there’s no throttling/WAF.
* **Exploit known CVEs** in the stack (framework/libs) the moment your instance is discoverable.

Therefore:

* Keep CrossWatch **off the public internet** (no direct exposure, no port-forwarding).
* Prefer binding to **localhost / LAN only** and restrict access with your firewall.
* For remote access, use a **VPN** (WireGuard/Tailscale) rather than opening ports.
* Enable [UI authentication](https://wiki.crosswatch.app/crosswatch/settings.md) (Settings - Security).
* Enable [HTTPS/TLS](https://wiki.crosswatch.app/crosswatch/advanced-and-api/https-and-tls.md) (recommended).

### Dependencies

<details>

<summary>Runtime dependencies (for transparency)</summary>

* `fastapi` - API server
* `pydantic` - request/response models
* `uvicorn` - ASGI server
* `requests` - HTTP client
* `plexapi` - Plex API client (third-party)
* `websocket-client` - WebSocket client (events where applicable)
* `websockets` - asyncio WebSocket support
* `python-multipart` - multipart/form-data support
* `packaging` - version parsing and feature gating

</details>

### Support expectations

This is a community project. Support is best-effort.

Be respectful and constructive when you ask for help. If you need guaranteed support, this project is not that.

*


---

# 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://wiki.crosswatch.app/related-information/disclaimer.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.
