> For the complete documentation index, see [llms.txt](https://osintverse.gitbook.io/otinstaller/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://osintverse.gitbook.io/otinstaller/faq.md).

# FAQ

**Does it work on Windows or macOS?** On Windows, yes, inside WSL2 with Ubuntu. macOS is not tested yet, and most of the tools are built for Linux first.

**Do I need root?** No. Root is only needed once, for `sudo apt install python3-venv git`. Everything else lives in your home directory under `~/.otinstaller/`.

**Does OTinstaller send my data anywhere?** OTinstaller itself only contacts GitHub and PyPI, to install and update tools. There is no telemetry. The tools you run contact the services they are built to query.

**How do I uninstall it?** `ot remove --all` removes every tool, then `pipx uninstall otinstaller` removes OTinstaller itself. `rm -rf ~/.otinstaller` deletes the config, the API key file and the logs. Results stay wherever you ran your commands.

**Is it legal to use?** The tools are legal to install. Whether a particular use is legal depends on where you are and what you are investigating. Read [Responsible use](/otinstaller/guides/responsible-use.md) before running anything against a real person.

*This page mirrors the* [*OTinstaller README*](https://github.com/OSINTVerseHQ/OTinstaller)*.*


---

# 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://osintverse.gitbook.io/otinstaller/faq.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.